I thought that #2 was just saying that new bugs should be
automatically reported to the dev list so to facilitate easy
discussion.


On Thu, 13 Jan 2005 11:29:58 -0800 (PST), Martin Cooper
<[EMAIL PROTECTED]> wrote:
> 
> 
> On Thu, 13 Jan 2005, Manfred Geiler wrote:
> 
> > Sean Schofield schrieb:
> >> 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)
> 
> I would recommend against #2. You almost always care about who is
> submitting issues, and comments and attachments to them, and those people
> need to be logged in for you to be able to know that.
> 
> --
> Martin Cooper
> 
> > Thoughts?
> >
> > Manfred
> >
> 


-- 
-Heath Borders-Wing
[EMAIL PROTECTED]

Reply via email to