Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [eclipse.org-architecture-council] Inactive EAC Members Process

Martin,

 

My apologies. I worded my email poorly.

 

As you guessed, my comments were only directed at #3, where the AC removes dormant members. You definitely do not need permission to create a “dormant” status tag.

 

Mike Milinkovich

Office: +1.613.224.9461 x228

Mobile: +1.613.220.3223

mike.milinkovich@xxxxxxxxxxx

 

From: Oberhuber, Martin [mailto:Martin.Oberhuber@xxxxxxxxxxxxx]
Sent: Monday, August 25, 2008 2:15 PM
To: mike.milinkovich@xxxxxxxxxxx; eclipse.org-architecture-council
Subject: RE: [eclipse.org-architecture-council] Inactive EAC Members Process

 

Hi Mike,

 

I'm not sure if I can follow you.

 

The idea of a "dormant" status was in order to get an accurate list of active members,

even though some members can not be removed. So, we are not talking about changes

of membership here, but just about a "status tag" helping our internal operation, to see

what members are actually active.

 

I thought that the step which allows removing dormant appointed members after 1 year

of inactivity were consistent with the  EAC charter [1], which used to talk about the

AC being able to remove members disruptive to its business, but that page seems to

have gone magically since I last checked it 3 weeks ago. Also, the development process [2]

now suddenly talks about 2-year renewable membership rather than 3 years.

 

I'm a bit confused by the recent change that I see in those documents, is there a

way I can get notified about such changes?

 

Anyways, if your comment is just about the AC not being able to remove members

itself, but having to recommend members-to-remove to the EMO(ED), I'm totally

fine with it.

 

 

Thanks,

--

Martin Oberhuber, Senior Member of Technical Staff, Wind River

Target Management Project Lead, DSDP PMC Member

http://www.eclipse.org/dsdp/tm

 

 

 


From: eclipse.org-architecture-council-bounces@xxxxxxxxxxx [mailto:eclipse.org-architecture-council-bounces@xxxxxxxxxxx] On Behalf Of Mike Milinkovich
Sent: Monday, August 25, 2008 7:54 PM
To: 'eclipse.org-architecture-council'
Subject: RE: [eclipse.org-architecture-council] Inactive EAC Members Process

To be consistent with the Bylaws, this (excellent) proposal needs to reflect that the membership in the EAC is by virtue of representing a PMC, a strategic developer member or appointed by the Executive Director. (Please see Section 7.2 of the Bylaws.)

 

I think that this can easily be done by simply adding a step where changes to the EAC membership list are approved by the Executive Director.

 

Mike Milinkovich

Office: +1.613.224.9461 x228

Mobile: +1.613.220.3223

mike.milinkovich@xxxxxxxxxxx

 

From: eclipse.org-architecture-council-bounces@xxxxxxxxxxx [mailto:eclipse.org-architecture-council-bounces@xxxxxxxxxxx] On Behalf Of Oberhuber, Martin
Sent: Monday, August 18, 2008 8:52 AM
To: eclipse.org-architecture-council
Subject: [eclipse.org-architecture-council] Inactive EAC Members Process

 

Hi all,

 

In order to get a better handle on what members of the EAC are

actually active, I'd like to propose the following:

  1. We add an "EAC Member (dormant)" status similar to the Committer Emeritus status. Dormant members do not take part in active discussions, but retain their right to take part (because they represent a Strategic Member Company or a PMC, or have been appointed but don't currently have time). Dormant members get separately listed on the councils page.
  2. Members enter the dormant status after 3 months of inactivity (counting mailing list submissions, and meeting attendance), or at their personal request (such as a person taking a sabbatical, for instance). We might want to discuss whether dormant members can actually still mentor any project or not.
  3. Appointed members get removed after 1 year in the dormant status (members representing a strategic member, or PMC can not be removed).

In order to track meeting attendance, I have edited the Aug 14 meeting notes, adding a "No Answer" section which lists those people who have not yet said whether they were at the meeting or not. Attendee and non-attendee lists are now sorted alphabetically for easier maintenance. Note that for future meetings, just clicking the "Yes" or "No" link of the Google Calendar Invitation will be sufficient to express attendance or non-attendance.

 

For this time, I'd like to ask those on the following list, who are still interested in the Council, to edit the Wiki page, or let me know by private mail whether they were actually at the meeting or not: Chris Aniszczyk, Wayne Beaton, Adrian Colyer, Naci Dai, Timothy Deboer, John Duimovich, John Graham, Kevin Haaland, Thomas Hallgren, Jochen Krause, Wenfeng Li, Mike Milinkovich, Philippe Mulet, Georg Schmidt, Mark Vandenbrink, David Williams, Andrew Young.

 

In order to make the proposed process (at least a little bit) automated, I'm wondering whether Bjorn's Project Dash / Committer Activity Meter could be beefed up to count EAC Mailing List submissions, and get the meeting attendance list fed in manually somehow?

 

In general, when a person is about to become dormant, I guess I'd prefer trying to see whether it's possible to motivate the person to become active again. On the other hand, we have a lot of excellent, bright people on the projects who could be freshly nominated into the EAC. As mentioned during the meeting, nominations can be made by a simple E-Mail to the mailing list.

 

Thoughts or ideas?

 

Thanks,

--

Martin Oberhuber, Senior Member of Technical Staff, Wind River

Target Management Project Lead, DSDP PMC Member

http://www.eclipse.org/dsdp/tm

 


Back to the top