On 12/13/11 5:57 PM, Christian Schwarz wrote:
+1 for all points..
...and some comments and additions:
Javadoc and Unit tests :
Same here : lots to do, but definitively mandatory. The Javadoc in MINA 3
is not bad, but need some cleanup. Unit tests, that's clearly an area we
should spend some time.
Talking about test what about codecoverage ? If u use eclipse as IDE
http://www.eclemma.org/ can assist here!
Gonna have a look at it.
Community support:
Actually we have the mailing lists and jira to communicate in all
directions. It both works well, but i think the user communication can be
improved. The mailing list doesn't provider any styling of the text, so
codesnippets are hard to read. Stackoverflow can help here, there is
actually a tag for MINA with some questions->
http://stackoverflow.com/search?q=apache-mina . The MINA development team
could register a RSS-Feed for this tag to provide support. There is a huge
acceptance in the community for stackoverflow !
The thing is that at Apache, if it's not on the mailing list, it does
not exist... So, definitively, we have to use either JIRA or the mailing
list.
Some projects are currently being testing GiT at the ASF, and hopefully,
we would be able to use that in 2012, making it easy to share code
snippet (even if it's unlikely that github could be used).
ATM, for code snippet, the best would be to use a link to an external
web site, like pastbin.com
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
