Let me just clarify something about notifications. The notification scheme is automatic - all notifications regarding additions and changes to JIRA tickets will go to the respective mailing lists - the SC or as I noted above the TC for SitRep. That is to ensure that JIRA is part of our public record. Plus anyone who wants to go to JIRA and review the list of issues can do so anytime. From a read-only perspective it is a totally open, public record. Membership in the JIRA project means that members can add new issues and comments and edit their comments. The chair and editors can further update tickets, change their status, etc. So notifications will happen - no one has to forward or take any other action. Project membership is just needed so the people can add issues and comment on them. Let me know if you have any questions. /chet On Thu, Jan 12, 2012 at 10:39 AM, Rex Brooks <
rexb@starbourne.com> wrote: > Hi Elysa, > > After conversing with Chet, I decided to just send the issues manually to > the active individuals on the roster. It turns out to be more work for Chet > than a few keystrokes, and, if I remember correctly, not possible to do "en > masse" so that is what I am doing. I plan to do this over the weekend or > Monday, before next week's SC meeting for SitRep. Tim wasn't on the call > Tuesday, so we didn't take any major decisions on this. That's still going > to be a bit of work for me. > > Cheers, > Rex > > > On 1/12/12 5:17 AM, Elysa Jones wrote: >> >> Rex and Chet, >> >> I am just now about to embark on entering comments into the CAP-AU Profile >> Project and I'm sure I'll need some help. We decided in a meeting >> yesterday >> to use JIRA and that we wanted all SC members noticed on JIRA activity. >> We >> have the same issue that we want other TC members to be able to optionally >> be included in any notifications. I agree with Rex below. So, which way >> will we go? I want to be able to announce and give a little direction to >> the TC members on our call Tues >> >> Thanks, >> Elysa >> >>