Personal tools
You are here: Home Joining SPI (projects)
Document Actions

Joining SPI (projects)

Here's a quick summary on how to join SPI as a member project. It's not complete, but shoudl serve as a general guide on the process.

  1. Have a close read of 2004-08-10.iwj.1

    This describes associated project status, what we can do for your project, and what we expect from our member projects
    As a summary, we provide two main services to our projects:
    • Property
      This includes Money (donations and holding), Intellectual Property (copyrights) and Other (for example, hardware)
    • Legal advice and Representation
  2. Informal Discussion

    If you're interested, please contact a board member for any further information you need, and to explain a little bit about what your project and organisation is. They should be able to give you an idea on if your projetc is suitable for joining SPI. You may also need to survey your project members for agreement on joining SPI
  3. Resolution

    If satisfied with the discussion, a board member will submit a resolution inviting the project to join SPI.
    This resolution will state the SPI Board's current understanding of who is authorised to act for the project; it will invite the project to join with SPI according to this Framework; and it will state a date at which the invitation will lapse if not accepted.

    We will need to know who is authorized to act for your project  (most commonly to approve disbursements but not restricted to this purpose).
    You may also have the option to appoint an advisor to the SPI board, who will be on our Board mailing list (but will not vote as a director would). This position is generally not filled by projects, and the board will advise if they wish to offer an advisor postion.
    It would be best if the names of the people filling both of those roles can be emailed to the board signed with a reasonably well-known OpenPGP key.

    A sample is below:
    WHEREAS

    1. [PROJECTNAME] is a significant Free Software project.

    2. The [PROJECTNAME] developers would like SPI's support and assistance,
    including [Insert services needed here] and possibly other services
    including [Insert what you may want later here], to be decided later by
    [PROJECTNAME];

    THE SPI BOARD RESOLVES THAT

    3. [PROJECTNAME] is formally invited to become an SPI Associated Project,
    according to the SPI Framework for Associated Projects, SPI
    Resolution 1998-11-16.iwj.1-amended-2004-08-10.iwj.1, a copy of
    which can be found at
    http://lists.spi-inc.org/pipermail/spi-announce/2004/000092.html

    4. Currently, [NAMES] are recognised by SPI as the authorititive
    decisionmakers for [PROJECTNAME];
    [Describe the decision making process here, eg:
    any two out of the three must agree any any particular decision
    (including any decision to delegate).
    [NAMES] have undertaken to base their decisons on consensus
    following consultation on relevant [PROJECTNAME] mailing list(s).
    ]

    5. This invitation will lapse, if not accepted, 60 days after it is
    approved by the SPI Board.
  4. Acceptance

    Those named in Section 4 of the resolution need to formally accept the invitation within the timeframe
Powered by Plone™. Visual theme by AdaptiveWave.