From: | David Graham - SPI Secretary <cdlu(at)spi-inc(dot)org> |
---|---|
To: | spi-general(at)lists(dot)spi-inc(dot)org, board(at)spi-inc(dot)org |
Subject: | Call for discussion: adding member projects? |
Date: | 2004-10-29 15:18:11 |
Message-ID: | Pine.LNX.4.55.0410291116250.7321@baffin |
Views: | Raw Message | Whole Thread | Download mbox |
Thread: | |
Lists: | spi-general |
Lately we've had two requests from projects - OpenC++ and the GNUStep
project - who are interested in joining SPI as member projects.
Traditionally, the board has alone approved or disapproved projects,
though in 1999 a committee was formed to handle member projects:
http://www.spi-inc.org/corporate/resolutions/resolution-1999-09-21.iwj
The now apparently defunct (did it ever actually exist?) Project Committee
did not handle researching or approving member projects, but I'd like to
propose that we recreate a Project Committee whose job it is to handle
applications for member projects as well as day-to-day affairs for these
projects, if applicable.
That said, a more important problem is setting out guidelines for what
projects are and are not eligible to become member projects on SPI.
As I see it, any free software or open source project that needs some form
of capabilities not available to non-incorporated projects is eligible to
join, but accepting every project out there would make us quite large,
quite fast.
What guidelines or even strict rules should we use in the acceptance or
rejection of member project requests?
---
David Graham, SPI Secretary
cdlu(at)spi-inc(dot)org D5F45889
From | Date | Subject | |
---|---|---|---|
Next Message | David Graham - SPI Secretary | 2004-10-29 15:42:17 | Re: Resolution 2004-10-28.dbg.1: Treasurer's Budget |
Previous Message | Martin Schulze | 2004-10-29 13:16:02 | Re: Resolution 2004-10-28.dbg.1: Treasurer's Budget |