Nightlife/Projects/Policy

Fedora Nightlife Policy for Projects (DRAFT)

Nightlife will need a set of policies and procedures for how projects can join. Here is a list of possible requirements for a project to join Nightlife, to be discussed, refined and approved in the Fedora community:

• Open Source: The source code for all executables must be available available under an OSI-approved open source license
• Maintained/Packaged: The project must have binaries packaged and actively maintained at Fedora
• Open Data: Any results computed by Nightlife for a project must have an acceptable (to-be-defined) open policy around them
• Safe: Projects must not do any harm to the environments of Nightlife users or be harmful in nature
• Secure: Projects must package their binaries according to some set of security practices (e.g. use SELinux, virtualization, etc)
• Beneficial: Projects must provide some kind of good benefit
• Legal: Projects must not do anything illegal, according to US Law (e.g. no massive encoding of pirated media)
• Active: Projects must be active to remain in Nightlife
• Acknowledgment: Projects that leverage Nightlife will have to acknowledge Nightlife in some way (e.g. link to Web site)

Policy/Procedure Questions

• What is the process for a project to request and be approved for Nightlife?
• What is the process for reviewing projects to determine that they are maintaining eligibility for Nightlife?
• How will we determine how to allocate Nightlife resources amongst projects? Will some projects receive higher priorities than others (either by user preference or Fedora Nightlife policy)?
• Are there any types of projects which we will categorically not accept?