[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse.org-architecture-council] PMC Approval Lag?

OK with discussing all this.

I remember an epic chat over the phone when we tried to convince the BPEL editor project that they would be better off being hosted at the STP project. I'd be happy to discuss how it went - I think Oisin remembers it as well.

I think we should help the Technology project by doing a bit of marketing for other TLPs. I also note that not all incubating projects go to the Technology TLP (which is why I am confused about its role). 

I'll try to break that down and add those topics to the next call if that's ok ?

On Thu, Apr 1, 2010 at 11:15, Oisin Hurley <oisin.hurley@xxxxxxxxx> wrote:
> The Tools versus Technology split still makes sense IMHO. Technology fills
> the need to have a default place to hold incubators while they mature.

This is our 'Eclipse Incubator' :)

> a)      The PMC does need to be more active and responsive. It should also
> likely be fully representative of the projects it includes.

+1

> b)      There are a number of projects which appear to be staying in
> Technology longer than they should. Once a project is mature, it should
> typically be looking for a new home. (Yes, there are always exceptions, but
> that should be the general rule.) So I think the Technology PMC should be
> encouraging mature projects to evaluate whether they should move.

+1

> No, I don’t think that the AC have the authority to refactor the projects.
> That requires the PMCs.

As the AC, we can merely suggest... :)

So - two items for the next AC meeting, perhaps:
 1)  That the Tools PMC look to expansion and staffing from more of its
      contained projects;
 2)  That the Technology PMC take steps to help mature Technology
      contained projects to move out from under the Technology umbrella.

 cheers
 --oh

 --oh
_______________________________________________
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.