docs(contribute): extend contribution guidelines
Hello!
My name is Alba, and I'm working at The Neighbourhoodie, the implementation partner of the STF. This MR addresses the work agreed on the /contribute page.
I have a set of questions that would help me improve this MR:
- The
Contribute to testing
section is quite sparse. Is there any way I could link directly to the tests being written? Is this something you'd be interested in? - I've highlighted 3 projects in the
Contribute to tools
section. I think listing a few of them is beneficial. Are the ones I selected the ones you wish to have highlighted? I can switch to your preferences; let me know if that's the case. - What parts of your current workflow have I not described?
- In what other ways can people contribute that I have not described yet?
- What are the current overarching goals and challenges of this project, and how can people contribute to them that I have not reflected yet?
Feel free to let me know if there are any other adjustments you'd like! Thank you
Merge request reports
Activity
added 31 commits
-
086c6cee...b5a1de50 - 30 commits from branch
reproducible-builds:master
- 8bd7f29b - docs(contribute): extend contribution guidelines
-
086c6cee...b5a1de50 - 30 commits from branch
added 7 commits
-
8bd7f29b...12222b23 - 6 commits from branch
reproducible-builds:master
- 8ed11ff7 - docs(contribute): extend contribution guidelines
-
8bd7f29b...12222b23 - 6 commits from branch
- Resolved by Chris Lamb
First up, just to say I think this is a really great start and that I'm sorry it's been waiting here without response for a 3 weeks. Let me tackle your questions in turn:
- The
Contribute to testing
section is quite sparse. Is there any way I could link directly to the tests being written? Is this something you'd be interested in?
Yes, I think that would be good. The source for the tests is primarily in this Git repo. Alas there is a broken link to an "about" page on the test output pages, but I think a link to the
README
page of the wiki would be a good start.- I've highlighted 3 projects in the
Contribute to tools
section. I think listing a few of them is beneficial. Are the ones I selected the ones you wish to have highlighted? I can switch to your preferences; let me know if that's the case.
Those 3 tools are ideal IMHO.
- What parts of your current workflow have I not described?
To clarify, do you perhaps mean in terms of a workflow for a new (who will need do some specific, project-specific things), or a generalised workflow for "regular" developers?
- In what other ways can people contribute that I have not described yet?
Good question. Folks can:
- Make their own software reproducible
- Use our tools (eg. diffoscope) in other contexts and therefore increase their userbase?
- What are the current overarching goals and challenges of this project, and how can people contribute to them that I have not reflected yet?
Hmm, big existential question. I think a bullet point about "complete, end-to-end integration into existing operating systems" and "tools to expose reproducibility / trust status to everyday users" would fit under this (at least to start).
Again, thanks — I personally think this could be merged now, but feel free to make more changes and ping me here.
- The
added 4 commits
-
8ed11ff7...c852eafe - 3 commits from branch
reproducible-builds:master
- 89bc5724 - docs(contribute): extend contribution guidelines
-
8ed11ff7...c852eafe - 3 commits from branch
mentioned in issue #9 (closed)