Initiatives are proposals to improve SourceCred in some way. Initiatives will be a focal point for minting new cred and flowing it to contributors.
Here’s the template for an initiative:
## Description: [//]: # (Describe your initiative here. What's the context for why it matters? What general features will it have?) ## Benefits: [//]: # (Why will the project benefit if we prioritize this initiative?) ## Implementation plan: [//]: # (Describe the steps that need to go into this initiative.) ## Deliverables: [//]: # (What _concretely_ should we expect to see from this initiative? How will we know to what degree this initiative's goals have been achieved?) ## Dependencies: [//]: # (A list of links to other initiatives. This section is used to track what other work this initiative depends on. When describing a complex initiative, it's normal to split it up into many smaller dependencies, and then have the final goal depend on those smaller steps.) ## References [//]: # (Here you can add any references that influenced the initiative, or would give the reader helpful context if they want to learn more. This section is important for flowing cred to the references; think of it a bit as like the "citations" section in a research paper.) [//]: # (The references should consist of a list of hyperlinks. If content has already been linked in elsewhere, there's no need to link to it again.) ## Contributions: [//]: # (A list of links to contributions that worked on this initiative. For example, if you've sent in a pull request that makes progress on this initiative, link to it here.)
Every initiative should be made into a wiki post (after writing one, you can click the gear icon at the bottom of the post, and then click convert to wiki). This way everyone can add more references, dependencies, and contributions to the initiative. (Use that privilege responsibly ).