On Wed, Jun 30, 2010 at 11:22 AM, Fabrizio Morbini <fmorb...@gmail.com> wrote: > One route we took in the past to release open source projects was to > post them on sourceforge. > The major advantage i see is that we would have direct access to the > svn repository. > <snip/>
Correct, then you won't have to wait for karma. Here is (roughly) the logical progression as it works at the ASF: http://apache.org/foundation/how-it-works.html#roles The time it takes to get from a contributor/developer to committer depends on things like the number, size and quality of contributions, community interaction etc. > do you see any problem taking this road and just linking the future > sourceforge project in the Apache commons scxml website to let anybody > interested in scxml know of this resource? > <snap/> Its your choice (obvious, but anyway). It may have a slightly higher likelihood of being maintained here since we already have an SCXML community, but its hard to speculate how much community support it will receive. And ofcourse, we are happy to link to any SCXML tooling projects. Thats no problem and easy to do :-) -Rahul > thanks > > On Tue, Jun 29, 2010 at 21:06, Rahul Akolkar <rahul.akol...@gmail.com> wrote: >> On Tue, Jun 29, 2010 at 6:53 PM, Fabrizio Morbini <fmorb...@gmail.com> wrote: >>> Hi, i saw some messages regarding a project developing a visual editor >>> for scxml as an Eclipse plugin. >>> >>> We have written a simple editor for scxml too. it's rough but usable. >>> It uses the jgraphx library to do the layout of nodes and there are >>> many points that could be improved. >>> >>> Are people interested in using it? (or even collaborating to the project) >>> >> <snip/> >> >> IMO, it'd be useful for the community to have such a light(er)-weight >> editor become available. >> >> In terms of collaboration: >> >> * If you are interested in donating the starter code for the editor >> (rough edges et al perfectly fine), we can probably create a sandbox >> space for it >> * In such cases we are looking for not just code but contributors who >> are willing to maintain and update the code that they contribute, >> write documentation for it etc. >> * If you are not an Apache committer, you will have to submit the >> code and subsequent updates as patches via the project JIRA (as you >> won't have write access to SVN) >> * Before any contributions are accepted, we will need (minimally) an >> Individual Contributor License Agreement (ICLA) [1] to be filed with >> the ASF by you (assuming you own said code and are willing to donate >> it) >> >> Let us know if you have any questions about the items above or how to >> proceed should you decide on contributing. >> >> -Rahul >> >> [1] http://www.apache.org/licenses/icla.txt >> >> >>> thanks, >>> fabrizio. >>> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
