how best to manage open source project in RTC?
I have a piece of Java software which I'm thinking of releasing as open
source. Being a big fan of RTC, I'd like to manage the project with it
but I'm wondering how that would scale to a putative open-source community.
I guess that as long as I have no more than 2 other "committers" I could
get by with Express-C. IIRC that would allow unlimited other people to
report work items, track status, and so on? Anyone else wanting to
contribute a fix or feature could just get source from the tarball and
send in a patch.
Most likely this would be fine, but are there otherr options? It doesn't
look like there's a real bridge to Subversion, but if there was that
might be an possibility. Is there by any chance a more open license for
open-source use? And is there any problem using Express-C in the way
described?
Thanks,
MK
source. Being a big fan of RTC, I'd like to manage the project with it
but I'm wondering how that would scale to a putative open-source community.
I guess that as long as I have no more than 2 other "committers" I could
get by with Express-C. IIRC that would allow unlimited other people to
report work items, track status, and so on? Anyone else wanting to
contribute a fix or feature could just get source from the tarball and
send in a patch.
Most likely this would be fine, but are there otherr options? It doesn't
look like there's a real bridge to Subversion, but if there was that
might be an possibility. Is there by any chance a more open license for
open-source use? And is there any problem using Express-C in the way
described?
Thanks,
MK
2 answers
Hi,
I think you have several options.
Information about usage of RTC in opensource and academic environments are published here: http://jazz.net/community/academic/
I haven't really looked ito it though.
There also is a bridge to SVN that can tie change sets to work items. The only disadvantage is the work item number needs to be typed in manually each time you deliver.
The setup description is somewhere in the RTC help.
Ralph
I think you have several options.
Information about usage of RTC in opensource and academic environments are published here: http://jazz.net/community/academic/
I haven't really looked ito it though.
There also is a bridge to SVN that can tie change sets to work items. The only disadvantage is the work item number needs to be typed in manually each time you deliver.
The setup description is somewhere in the RTC help.
Ralph
We provide free licenses for open source projects. See the following
page for more details and how to request your free licenses.
http://jazz.net/community/academic/?p=openSourceUse
Cheers,
Jean-Michel
On 8/19/2009 9:06 AM, Mervyn Keene wrote:
page for more details and how to request your free licenses.
http://jazz.net/community/academic/?p=openSourceUse
Cheers,
Jean-Michel
On 8/19/2009 9:06 AM, Mervyn Keene wrote:
I have a piece of Java software which I'm thinking of releasing as open
source. Being a big fan of RTC, I'd like to manage the project with it
but I'm wondering how that would scale to a putative open-source community.
I guess that as long as I have no more than 2 other "committers" I could
get by with Express-C. IIRC that would allow unlimited other people to
report work items, track status, and so on? Anyone else wanting to
contribute a fix or feature could just get source from the tarball and
send in a patch.
Most likely this would be fine, but are there otherr options? It doesn't
look like there's a real bridge to Subversion, but if there was that
might be an possibility. Is there by any chance a more open license for
open-source use? And is there any problem using Express-C in the way
described?
Thanks,
MK
Comments
Jean-Michel Lemieux wrote:
We provide free licenses for open source projects. See the following
page for more details and how to request your free licenses.
http://jazz.net/community/academic/?p=openSourceUse
Thanks to both. Clearly this is what I should look into. There does seem
to be a catch-22 FWIW; one of the requirements is that:
"The project is visibly active with builds posted regularly on the
project's website and frequent contributions to the project's work
items, mailing lists and/or newgroups."
For a brand-new project, I don't see how to demonstrate that at first
release. I can only hope the people running this program are reasonable.
MK
Yes, very reasonable. As long as your OS code is distributed with a
recongnized OS license and have a website describing the project, you
are fine.
Cheers,
Jean-Michel
On 8/23/2009 1:14 PM, Mervyn Keene wrote:
Jean-Michel Lemieux wrote:
We provide free licenses for open source projects. See the following
page for more details and how to request your free licenses.
http://jazz.net/community/academic/?p=openSourceUse
Thanks to both. Clearly this is what I should look into. There does seem
to be a catch-22 FWIW; one of the requirements is that:
"The project is visibly active with builds posted regularly on the
project's website and frequent contributions to the project's work
items, mailing lists and/or newgroups."
For a brand-new project, I don't see how to demonstrate that at first
release. I can only hope the people running this program are reasonable.
MK