ajwang / groovypptest

Automatically exported from code.google.com/p/groovypptest
0 stars 0 forks source link

Wishlist: Adopt an open source development methodology #280

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
(Disclaimer: This is a request rather than a complaint/criticism. I enjoy using 
Groovy++ and appreciate all the work you've put into it.)

At the moment, Groovy++ is developed with a cathedral mentality:

http://catb.org/esr/writings/homesteading/cathedral-bazaar/

Despite being open source, it's still being developed as though it's an 
in-house project.

New releases appear without changelogs. (What changed? What was fixed? What's 
new?)

The source code repo is empty apart from a few examples:

https://code.google.com/p/groovypptest/source/browse/

Checking out the "source" results in 40,000 (!) WordCount data files being 
downloaded, rather than the Groovy++ source code. Yes, it's available in a zip 
file, but that almost actively discourages hacking, learning, exploring, 
experimenting &c.

The best way to get other people contributing (assuming that's what you want) 
is to allow them to clearly see how you go about fixing bugs and adding 
features. I've encountered a few type-inference bugs like this one:

http://code.google.com/p/groovypptest/issues/detail?id=246

- which I presume might be fixable by someone outside of the core team if 
would-be patchers could see at a glance what previous fixes entailed without 
manually diffing source tarballs (i.e. implementing a SCM by hand).

Basic "how to contribute to this project" info is missing:

http://contributing.appspot.com/

If you're committed to "hosting" the project here (rather than, say, on GitHub, 
which actively encourages "social coding"), please consider, at the very least, 
committing (or syncing) the core Groovy++ source code to a public repository, 
and releasing changelogs. In fact, if you do the former, you could get the 
latter for free:

http://dustin.github.com/java-memcached-client/changelog.html

Original issue reported on code.google.com by chocol...@cpan.org on 29 Jul 2010 at 3:25

GoogleCodeExporter commented 8 years ago
http://dustin.github.com/2009/01/17/changelog.html

Original comment by chocol...@cpan.org on 29 Jul 2010 at 3:43

GoogleCodeExporter commented 8 years ago

Original comment by alex.tka...@gmail.com on 31 Aug 2010 at 5:58

GoogleCodeExporter commented 8 years ago

Original comment by alex.tka...@gmail.com on 4 Sep 2010 at 3:14