- Name of project or network and describe organizational makeup
- List member projects of applicant networks
- List team members of applicant projects and their roles
- Designate of the Representative(s)
- A short written section describing the project or network
- Include the type of project or network (i.e. software,
educational resource, publisher, art project)
- Also include any programming languages, writing styles,
target platforms or technical information regarding the creation
of content
- Link technical resources which contextualize the project's
creation
- Describe the userbase and contributors attempting to be
appealed to
- Describe long-term goals for the endeavor:
- What will it look like in a year?
- What does it gain from joining the Network?
- What does it bring to the table for other Network members?
- Prompt questions to answer here could include the following
(optional):
- How does this endeavor contribute to the ecosystem it
integrates?
- What specific problems is this new endeavor solving?
- Do any existing projects solve these problems already? If so, how is
this endeavor different?
- Is this a highly experimental endeavor that innovates its field, a
refined reimplementation of a tried-and-true solution, or something in
between?
- Feel free to include any extra information deemed important to specify;
the application cannot account for everything
- (If not already existing) a clear description of the vision of the project
or network's minimum viable product
- Remember to Release Early, Release Often
- Minimum viable products are not complete or fully functional; they must
simply demonstrate promising work
- Estimated timespans for the project or network (i.e. one month, a few
months, a year, continuous) and a roadmap for the completed project
- Project licensing details