-
-
Notifications
You must be signed in to change notification settings - Fork 4
Home
PLAS: Pittsburgh LAN Administration System
We're currently using the Wiki primarily to assist contributors with setup issues and project management workflow.
We're using GitHub's Issues system for now. It's not as robust as we'd like to to be (lacks blocks, assigning, resolution status, prioritization, etc.), so we might end up moving it to Launchpad or setting up our own Trac or Bugzilla instance.
We're making up for the lack of status/resolution using the labels. Each issue should have at least two labels. One describes the nature (Defect, Enhancement, Testing) the other describes the priority (Critical, High, Medium, Low). Other labels will be created as necessary, probably describing the subsystem to which the issue applies.
In order to contribute, submit a patch to colindean or submit a pull request to the maintainer of the subsystem affected. As of 2010-10-24, colindean is the maintainer of everything except the testing harness (that's billturner).
Code contributed must be licensed as AGPL. Contributors retain copyright for now, but we will likely follow Diaspora's lead in asking contributors to sign a dual assignment agreement in the event that the contributor is unreachable should the license for PLAS ever need to be changed or if ownership of the project changes.