I have two suggestions.
1.) We should start using the javadoc comments for all new classes, methods, etc. Users will want to see a nice javadoc when they evaluate whether to use my faces. The other Apache projects have this, we should too. We should at least do this going forward and eventually we should go back and document the legacy stuff.
+1 for all stuff (new and "legacy")
This is what Ted meant with "a bit vote-happy", isn't it. Do we really vote one writing javadoc here?! ;-)
2.) It would be *real* nice to have the CVS commits and the JIRA bug reports emailed to the dev list. Its hard to carry on two separate discussions about a bug (one on JIRA plus one on the dev list). Also, unless you are actively checking JIRA you don't know when a new bug has been posted.
I orginally configured the MyFaces Notification Scheme at Jira to send all new issues to the dev list. This notification together with some permissions I added/modified are no longer there. Perhaps they got lost on moving JIRA data to the new server and version?
Well, there is still a notification on new issues for Group myfaces-developers. So every committer should get emails now (I do).
Well, I did not find a way to define a default issue owner in JIRA. Anyway, JIRA allows some fine-grained settings. These pages should be accessible to all myfaces committers (please tell me if not):
http://issues.apache.org/jira/secure/admin/EditNotifications!default.jspa?schemeId=10330
http://issues.apache.org/jira/secure/admin/EditPermissions!default.jspa?schemeId=10280
I propose the following changes:
1. Add the [email protected] list to these notifications: "Issue Created", "Issue Updated", "Issue Resolved" and "Issue Commented"
2. Give permission "Create Issues", "Add Comments" and "Create Attachments" to Group "Anyone" (Currently only logged in users are able to submit issues as far as I understand it)
Thoughts?
Manfred
