Public SourceMage Discussion List

[Mark Bainter <mbainter-smgl AT trampledstones.com>]

Arjan Bouter [abouter AT sourcemage.org] wrote:
> On Wed, 25 May 2011 14:00:14 -0500
> David Kowis <dkowis AT shlrm.org> wrote:
> 
> > It's been mentioned to me that we should have one for quill and some of
> > the other projects there, perhaps castfs.
> 
> On the other hand we have other projects like Quill, Enthrall and Castfs.
> While these projects are useful, they can be dispelled or switched off.
> 
> I think that's probably the best way to divide projects: can they be 
> disabled
> without affecting usability.

That's probably a decent approach to that.  We may also need to consider
some secondary factors like complexity and/or codebase size.  I think in the 
end 
it's something of a grey area, but this is a good basic measurement to go by.

> I suggest we group these other projects together without making them 
> components.

I don't know that I would group them together, as that generally means
one person will be administering all of those projects.  I do like the
idea of putting some new sort of "PM" over those projects that's less
official than the rest.  

Maybe what we need is to make a primary project for those, and then make
subprojects over them.  Have a component lead over small projects, and
then simple project leaders over each of the subprojects.  

Not only does that make it easier to manage those subjprojects and keep
them moving forward, but it gives people a chance to get their feet wet
as a lead, and might be a good way to find new candidates for future
component lead elections.


--