Re: [eclipse.org-eclipsecon-program-committee] BOFs

[Kevin McGuire <Kevin_McGuire@xxxxxxxxxx>]

> this makes
it harder for a project team to hold a BOF because they can't announce
it advance

I agree that it's important they be
used for the intended purpose.  However, it seems counter productive
to do anything which reduces the value of BOFs to those who "legitimately"
need them.  Can the program committee not accept/deny them as they
would any other kind of submission and thus weed ou the problem ones? 

> so we will
probably open up advance BOF scheduling to project teams but not to the
general public.

Can you elaborate on how that would
work on a practical level?  How do you know who is who?  E.g.
do you require someone to be a committer or PMC member?  If yes then
what about new projects which aren't passed the proposal stage yes?

Regards,
Kevin

Bjorn Freeman-Benson <bjorn.freeman-benson@xxxxxxxxxxx>
Sent by: eclipse.org-eclipsecon-program-committee-bounces@xxxxxxxxxxx

11/27/2008 12:32 AM

Please respond to
Eclipsecon Program Committee list        <eclipse.org-eclipsecon-program-committee@xxxxxxxxxxx>

To	Eclipsecon Program Committee list <eclipse.org-eclipsecon-program-committee@xxxxxxxxxxx>
cc
Subject	Re: [eclipse.org-eclipsecon-program-committee] BOFs

Scott, everyone,
Yes, BOFs are a problem every year: the problem is that companies try to
use them to get around the program committee and around sponsoring. Thus
we (Donald and Mike and Wayne and I) have decided to make them even more
last minute than before and probably not even scheduled through the submission
system. This decision is not all positive: this makes it harder for a project
team to hold a BOF because they can't announce it advance so we will probably
open up advance BOF scheduling to project teams but not to the general
public.

That's the current thinking...
- Bjorn
3) In an early con call there was interest
in making BOFs more informal (adHoc) 

My opinion is that we can open up BOFs in late January/February.  Does
that sound reasonable?
-- 
[end of message]_______________________________________________
eclipse.org-eclipsecon-program-committee mailing list
eclipse.org-eclipsecon-program-committee@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-eclipsecon-program-committee