Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

JIRA and text patches are anti-open-source

datasyndrome.com

Post reply on HN
Print view View original

21–30 of 35 posts

Re: JIRA and text patches are anti-open-source

#21

Post by user2634 »

jacknagel wrote: post #18
user2634 wrote: post #15

Github is complicated. I tried to make account one time. I registered and an email address was required which they promised not to share with anyone. But then I found that that email address is shared to the whole world in git commit summary! Later I had bigger problem, with setting up public key in TortoiseGit. Instructions at http://help.github.com/win-set-up-git/ didn't work for me. Github website also feels alien…

>But then I found that that email address is shared to the whole world in git commit summary! If you're talking about the email address in the commit itself, that's part of the commit object and not anything GitHub does behind your back. If you publish the commit anywhere, not just GitHub, the email address has become public knowledge.

"Set up git" instructions tell this:

  git config --global user.name "Your Name"

  git config --global user.email user4325434@mailinator.com
You have to use same email as in registration or else it won't push.

Re: JIRA and text patches are anti-open-source

#22

Post by losethos »

5 When they went across the lake, the disciples forgot to take bread. 6 “Be careful,” Jesus said to them. “Be on your guard against the yeast of the Pharisees and Sadducees.” 7 They discussed this among themselves and said, “It is because we didn’t bring any bread.”

8 Aware of their discussion, Jesus asked, “You of little faith, why are you talking among yourselves about having no bread? 9 Do you still not understand? Don’t you remember the five loaves for the five thousand, and how many basketfuls you gathered? 10 Or the seven loaves for the four thousand, and how many basketfuls you gathered? 11 How is it you don’t understand that I was not talking to you about bread? But be on your guard against the yeast of the Pharisees and Sadducees.” 12 Then they understood that he was not telling them to guard against the yeast used in bread, but against the teaching of the Pharisees and Sadducees.

----

Jesus sounded high on drugs! Of course the disciples were confused.

"Good loved Jacob and hated Esau." Kevin? No. It's fruitful to meditate on Jacob. He wrestled an angel or God. He was a trickster in ways I think are outrageous -- was hardly a goody-goody waiting for God to serve justice. very Jewish. I don't really like him.

Born American is a birthright. Born an intellectual.

Don't feel guilty if God has given you something. Say "thank-you" and enjoy.

God says... C:\LoseThos\www.losethos.com\text\WALDEN.TXT

nt as it is early! If the snow lies deep, they strap on his snowshoes, and, with the giant plow, plow a furrow from the mountains to the seaboard, in which the cars, like a following drill-barrow, sprinkle all the restless men and floating merchandise in the country for seed. All day the fire-steed flies over the country, stopping only that his master may rest, and I am awakened by his tramp and defiant snort at midnight, when in some remote glen in the woods he fronts the elements incased in ice

Re: JIRA and text patches are anti-open-source

#23

Post by dhconnelly »

arohner wrote: post #10

The standard argument here is that the project requires all contributors to sign some form of document granting rights to the project. The project uses JIRA's permissions to whitelist people who have signed the doc. i.e. in Clojure's case, the Contributor Agreement grants copyright to the submitter AND Rich Hickey, so he can change the project's license in the future, if need be. It seems like Github should add this…

Why couldn't pull requests just be kept on hold until the contributor signs the agreement?

Re: JIRA and text patches are anti-open-source

#24

Post by getsat »

tikhonj wrote: post #17
user2634 wrote: post #15

Github is complicated. I tried to make account one time. I registered and an email address was required which they promised not to share with anyone. But then I found that that email address is shared to the whole world in git commit summary! Later I had bigger problem, with setting up public key in TortoiseGit. Instructions at http://help.github.com/win-set-up-git/ didn't work for me. Github website also feels alien…

Maybe I'm missing something, but I think GitHub gets the email address it displays in the commit messages from Git rather than your account. (That is, it gets it from whatever you set with git-config.)

This is correct. You can use whatever email you want in your commits. Your Github email is not shared by Github to any other party.

Re: JIRA and text patches are anti-open-source

#25

Post by getsat »

user2634 wrote: post #21
jacknagel wrote: post #18

Earlier quoted context omitted.

>But then I found that that email address is shared to the whole world in git commit summary! If you're talking about the email address in the commit itself, that's part of the commit object and not anything GitHub does behind your back. If you publish the commit anywhere, not just GitHub, the email address has become public knowledge.

"Set up git" instructions tell this: git config --global user.name "Your Name" git config --global user.email user4325434@mailinator.com You have to use same email as in registration or else it won't push.

Nope. Authentication is done using your ssh key pair.

All my commits are done by noreply@example.com, but that is obviously not my Github email on either my personal or work accounts.

Re: JIRA and text patches are anti-open-source

#26

Post by [deleted] »

user2634 wrote: post #21
jacknagel wrote: post #18

Earlier quoted context omitted.

>But then I found that that email address is shared to the whole world in git commit summary! If you're talking about the email address in the commit itself, that's part of the commit object and not anything GitHub does behind your back. If you publish the commit anywhere, not just GitHub, the email address has become public knowledge.

"Set up git" instructions tell this: git config --global user.name "Your Name" git config --global user.email user4325434@mailinator.com You have to use same email as in registration or else it won't push.

[deleted]

Re: JIRA and text patches are anti-open-source

#27

Post by TeHCrAzY »

dhconnelly wrote: post #23
arohner wrote: post #10

The standard argument here is that the project requires all contributors to sign some form of document granting rights to the project. The project uses JIRA's permissions to whitelist people who have signed the doc. i.e. in Clojure's case, the Contributor Agreement grants copyright to the submitter AND Rich Hickey, so he can change the project's license in the future, if need be. It seems like Github should add this…

Why couldn't pull requests just be kept on hold until the contributor signs the agreement?

My guess would be the sheer volume of commits would be unmanageable unless the process was somehow automated

Re: JIRA and text patches are anti-open-source

#28

Post by arohner »

dhconnelly wrote: post #23
arohner wrote: post #10

The standard argument here is that the project requires all contributors to sign some form of document granting rights to the project. The project uses JIRA's permissions to whitelist people who have signed the doc. i.e. in Clojure's case, the Contributor Agreement grants copyright to the submitter AND Rich Hickey, so he can change the project's license in the future, if need be. It seems like Github should add this…

Why couldn't pull requests just be kept on hold until the contributor signs the agreement?

The real issue is verifying that the person has a CA at all. You don't want to scan a list for a person's name on every merge.

In JIRA, it's easier for the committer, because only contributors have the correct permissions to submit a patch at all. GitHub currently has no analogue.

Re: JIRA and text patches are anti-open-source

#29

Post by rjurney »

arohner wrote: post #10

The standard argument here is that the project requires all contributors to sign some form of document granting rights to the project. The project uses JIRA's permissions to whitelist people who have signed the doc. i.e. in Clojure's case, the Contributor Agreement grants copyright to the submitter AND Rich Hickey, so he can change the project's license in the future, if need be. It seems like Github should add this…

This sounds like a workable solution. Github adds a feature, apache opens to github. Compromise?

Re: JIRA and text patches are anti-open-source

#30

Post by rjurney »

arohner wrote: post #10

The standard argument here is that the project requires all contributors to sign some form of document granting rights to the project. The project uses JIRA's permissions to whitelist people who have signed the doc. i.e. in Clojure's case, the Contributor Agreement grants copyright to the submitter AND Rich Hickey, so he can change the project's license in the future, if need be. It seems like Github should add this…

Wait, this is a checkbox on jira, is it not?
Post reply on HN