RE: [eclipse.org-architecture-council] EAC Reminders

[Eugene Chan <ewchan@xxxxxxxxxx>]

+1 for Thursdays also.

Thanks.
____________________________________________

Eugene Chan
email: ewchan@xxxxxxxxxx

John Graham <jgraham@xxxxxxxxxx>
Sent by: eclipse.org-architecture-council-bounces@xxxxxxxxxxx

08/26/2008 02:03 PM

Please respond to
"eclipse.org-architecture-council"        <eclipse.org-architecture-council@xxxxxxxxxxx>

To	"eclipse.org-architecture-council" <eclipse.org-architecture-council@xxxxxxxxxxx>
cc
Subject	RE: [eclipse.org-architecture-council] EAC Reminders

+1 for Thursdays.

On Tue, 2008-08-26 at 13:58 -0400, Tim deBoer wrote:
> 
> +1 for Thursdays. I also have a standing meeting on Tuesdays, so
> alternating is ok too. 
> 
> Tim deBoer
> deboer@xxxxxxxxxx 
> 
> 
> From: 
> Darin Wright/Ottawa/IBM@IBMCA 
> To: 
> "eclipse.org-architecture-council"
> <eclipse.org-architecture-council@xxxxxxxxxxx> 
> Date: 
> 08/26/2008 10:05 AM 
> Subject: 
> RE:
> [eclipse.org-architecture-council]
> EAC Reminders
> 
> 
> ______________________________________________________________________
> 
> 
> 
> +1 for Thursdays. I have a standing meeting on the Tuesday timeslot
- 
> alternating is also OK.
> 
> Darin Wright
> 
> 
> 
> 
> "Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>
> Sent by: eclipse.org-architecture-council-bounces@xxxxxxxxxxx
> 08/25/2008 11:07 AM
> Please respond to
> "eclipse.org-architecture-council" 
> <eclipse.org-architecture-council@xxxxxxxxxxx>
> 
> 
> To
> "eclipse.org-architecture-council" 
> <eclipse.org-architecture-council@xxxxxxxxxxx>
> cc
> 
> Subject
> RE: [eclipse.org-architecture-council] EAC Reminders
> 
> 
> 
> 
> 
> 
> Good to have some discussion!
> 
> One point about alternating is that it's not only about remembering
> when
> the next call is. It's also about scheduling other calls, and seems
> to 
> create some ripple effect:
> 
> If it's important for me to regularly join alternating AC meetings,
> then I 
> 
> cannot organize standing meetings on either Tuesday or Thursday. 
> Unless I'm OK with not joining a standing meeting every 2 months.
> 
> But we have the voting system for finding the best possible
> compromise. If you can't ever attend a meeting on Tuesday,
> you can vote it -1. That is, you have a +1/-1 vote for each of
> the alternatives, giving 3 votes in total which you can exercise 
> or not.
> 
> Assuming Neil's -1 for Tuesday and Oliver's -1 for Thursday
> (who said they definitely can't join these days), we currently get:
> 
> +2 Thursday (Andrew, Jeff, Martin - Oliver)
> +3 Alternating (Jeff, Neil, Boris)
> +3 Tuesday (Jeff, Oliver, Chris, Martin - Neil)
> 
> I'm not in favor of re-voting (in the interest of getting a decision
> soon), but feel free to change a vote or add one which you 
> have not exercised yet.
> 
> Cheers,
> --
> 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 
> Boris Bokowski
> Sent: Monday, August 25, 2008 5:32 PM
> To: eclipse.org-architecture-council
> Subject: Re: [eclipse.org-architecture-council] EAC Reminders
> 
> +1 for alternating. With all the Google calendars we have in place
now
> for 
> Eclipse related events, it should be possible to use a more
> complicated 
> call schedule.
> 
> Boris
> 
> Neil Hauge wrote:
> > +1 for Alternating.
> > 
> > If we don't alternate, then some will be forever unable to attend
on
> a 
> > set day.  I would not be able to attend Tuesday at 11am
due to a 
> > standing PMC meeting.  Alternating seems to be the most
inclusive 
> option.
> > 
> > I think if alternating is not the winner, we should have a re-vote
> for 
> > Tuesday or Thursday to get a clear count. : )  In any case,
my
> secondary 
> 
> > vote would be +1 for Keep Thursday.
> _______________________________________________
> eclipse.org-architecture-council mailing list
> eclipse.org-architecture-council@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council
> 
> IMPORTANT: Membership in this list is generated by processes internal
> to 
> the Eclipse Foundation.  To be permanently removed from this
list,
> you 
> must contact emo@xxxxxxxxxxx to request removal.
> 
> _______________________________________________
> eclipse.org-architecture-council mailing list
> eclipse.org-architecture-council@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council
> 
> IMPORTANT: Membership in this list is generated by processes internal
> to the Eclipse Foundation.  To be permanently removed from this
list,
> you must contact emo@xxxxxxxxxxx to request removal.
> 
> 
> _______________________________________________
> eclipse.org-architecture-council mailing list
> eclipse.org-architecture-council@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council
> 
> IMPORTANT: Membership in this list is generated by processes internal
to the Eclipse Foundation.  To be permanently removed from this list,
you must contact emo@xxxxxxxxxxx to request removal.

_______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council

IMPORTANT: Membership in this list is generated by processes internal to
the Eclipse Foundation.  To be permanently removed from this list,
you must contact emo@xxxxxxxxxxx to request removal.