[eclipse.org-architecture-council] [Bug 250823] New: Request a TAG for i

[bugzilla-daemon@xxxxxxxxxxx]

https://bugs.eclipse.org/bugs/show_bug.cgi?id=250823  
Product/Component: Community / Architecture Council
           Summary: Request a TAG for important E-Mail to the AC
           Product: Community
           Version: unspecified
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Architecture Council
        AssignedTo: eclipse.org-architecture-council@xxxxxxxxxxx
        ReportedBy: oec@xxxxxxxxxxxxx


Martin Oberhuber is trying to get a handle on the AC and to focus it on it's
mission.  This requires participation of the AC in his initiatives.  He has
been trying things like emails, role calling, google calendar to try and track
peoples attendance.  It is a thankless job (and thank you for doing it MO :).

  I would like to describe what works for us at OCS.  The convention here is
that important email has the keyword URGENT in the subject line.  OCS'ers are
required to respond to URGENT emails at the top of their priority list.  In
this way, even though a mailing list may have 99% noise, one always knows what
is URGENT.

  If the AC adopted this, then MO could spend less of his time tracking
participation, as everyone would be required to respond to URGENT emails.  If
an AC member does not respond to URGENTs, then kick him/her/it off the AC.

  In this manner, MO could stop having to manually track (and define)
participation and, by requiring prompt input from all the navel gazers, he can
execute the mission of the AC quickly and efficiently.

   Actually, it would be best if all eclipse mailing lists adopted this, since
they all tend to go through periods of much spam, with the occasional jewel.


-- 
Configure bugmail: https://bugs.eclipse.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.