BitcoinDesign
Create a collaboration issue template
Similar to how we have a community call template for issues it would be handy to have a design collaboration template. Christoph has already laid out one that I think works pretty well below. This way project owners can come to us and make these issues instead of us make it for them.
[insert incredibly well-designed cover image, see other collaboration issues for inspiration but feel free to put your own touch on it. Landscape formats work best.]
Collaboration type: Pick from this list
[The Bitcoin Design community has laid out several collaboration types in the above linked playbook, please choose and link to the one that fits your project needs.]
Goal
[What is the goal of this collaboration?]
Project context
[Give some context to the project. Why was it started? What is its purpose? Is it FOSS, OSS or closed source?]
Team
[Who is currently working on the project and what are their roles? What roles are you looking to fill, if any?]
Timeline
[What steps, if any, do you have outlined to take to achieve your design goal?]
Notes
[Add any extra notes that may be relevant to this collaboration.]
Links
[Include any relevant links, such as links to your projects GitHub repo, website, app etc.]
Something relevant to add here is that if projects come to us they might not know what kind of collaboration type they require. For these types of projects it might be useful to list some steps to take and we can help them decide what their needs are. I would propose the three steps outlined in collaboration type #1 below as steps to take BEFORE deciding on a collaboration type:
- Review the guide to find a direction or solution
- Engage in Slack conversations to share ideas and get feedback
- Participate in a design review session
- Decide what type of design collaboration is suited for your project.
This would only be targeted towards projects that have no design focus whatsoever which is relatively common in open source projects.
@Bosch-0 TBH, my assumption is that projects won't just show up and create issues, but some of us regular contributors will create them after talking to the team and figuring out what the right plan of action is. They can, of course, but some conversation beforehand would be healthy to clarify what's needed and get support in the community.
Yeah you're assumption is most likely correct, this concept is still quite new so I guess we can see how things proceed and adjust accordingly.
Going to close this issue, as it's been 2+ years without activity. Collaborations seem to be going fine without a template. We can re-open if someone feels strongly about it.