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

11–20 of 35 posts

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

#11

Post by wmf »

viraptor wrote: post #5

Not sure I understand the issue here. JIRA doesn't force you to do anything with the source. "a monolithic subversion database" depends only on the project, not on the bugtracker. Set up a custom field where you put a url and/or git hash... and problem solved. Probably not as nice as Github which integrates both, but on the other hand Github's issue tracking capabilities are far behind JIRA's (no proper workflow, no…

It reads like he's going out of his way to not mention Apache or Hadoop, but then at the end he says it's Apache. So maybe it could have been expressed better.

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

#12

Post by viraptor »

shareme wrote: post #6
Lazare wrote: post #2

I would complain that JIRA itself is closed-source...but the author is recomending Github as an alternative, which is also closed-source. Ah well. :)

nope github has been opensource for awhile dude

Could you post a link to the source in that case?

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

#13

Post by rsutphin »

xbryanx wrote: post #3

Maybe I'm not familiar with the background, but I'm not sure why JIRA specifically is getting singled out here, instead of just saying "bugtracker." Please help me understand further.

I think the OP is referring to the Apache Foundation's process for accepting patches from non-committers. All Apache projects require a copyright grant. The only way (AFAIK) that they allow you to express that you grant the copyright for your changes to the foundation is by checking a box when you upload the patch to their issue tracking system, which happens to be JIRA.

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

#14

Post by rjurney »

wmf wrote: post #11
viraptor wrote: post #5

Not sure I understand the issue here. JIRA doesn't force you to do anything with the source. "a monolithic subversion database" depends only on the project, not on the bugtracker. Set up a custom field where you put a url and/or git hash... and problem solved. Probably not as nice as Github which integrates both, but on the other hand Github's issue tracking capabilities are far behind JIRA's (no proper workflow, no…

It reads like he's going out of his way to not mention Apache or Hadoop, but then at the end he says it's Apache. So maybe it could have been expressed better.

Thanks, updated it to say Apache in the first sentence.

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

#15

Post by user2634 »

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 and weird, like Macintosh.

It's much easier to pass around git .patch files. Anyone can post anonymously (no email or account required) a .patch file on project's phpBB forum. Because it's usual phpBB, anyone can review anonymously and it's possible to post screenshots. It takes just 1-2 minutes to post a patch. Just select your commits in TortoiseGit and click "Create Patch Serial". There are graphical instructions for TortoiseGit in sticky thread on patches forum.

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

#17

Post by tikhonj »

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.)

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

#18

Post by jacknagel »

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.

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

#20

Post by aaronblohowiak »

FfejL wrote: post #8
Lazare wrote: post #2

I would complain that JIRA itself is closed-source...but the author is recomending Github as an alternative, which is also closed-source. Ah well. :)

Certainly true that JIRA is neither Gratis nor Libre, nor does Atlassian accepted patches from the public. But it's Open Source in the sense that every license holder can download and build it: http://confluence.atlassian.com/display/JIRA/Building+JIRA+f... (disclosure: I am a former Atlassian employee)

it doesn't fit the OSI definition, but it is what microsoft calls "shared source".
Post reply on HN