JIRA and text patches are anti-open-source
datasyndrome.com
JIRA and text patches are anti-open-source
1–10 of 35 posts
Re: JIRA and text patches are anti-open-source
#2I would complain that JIRA itself is closed-source...but the author is recomending Github as an alternative, which is also closed-source. Ah well. :)
Re: JIRA and text patches are anti-open-source
#3Maybe 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.
Re: JIRA and text patches are anti-open-source
#4I would complain that JIRA itself is closed-source...but the author is recomending Github as an alternative, which is also closed-source. Ah well. :)
git would be enough. Committers could use whatever they want to merge. Most people would choose github. But git is GPL, not Apache. Thus the problem...
Re: JIRA and text patches are anti-open-source
#5Not 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 structure for custom information, etc.) You'll have to figure out what's more important to you.
Re: JIRA and text patches are anti-open-source
#6I 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
Re: JIRA and text patches are anti-open-source
#7Maybe 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.
Specifically the problem is uploading text patches to JIRA, as compared to doing pull requests on github.
Re: JIRA and text patches are anti-open-source
#8I 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)
Re: JIRA and text patches are anti-open-source
#9Maybe 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.
Yeah, all his arguments are true for most bugtrackers.
By Jira he seems to really mean 'Jira at Apache' - which is their bugtracker for most projects.
Re: JIRA and text patches are anti-open-source
#10The 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 feature, (open source, with whitelisted contributors) and then the need for the JIRA mess all goes away.