-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: create a docs folder #303
Labels
Comments
can i be assigned this issue? |
Hi @ithiel883! Thank you for volunteering! I believe #309 will fix this, so I'm actually going to assign it to myself. If you're interested in other good getting-started issues, here are a few. If you're interested, comment there. And if you run into any trouble, comment and we'll try to give some guidance 😄 |
asraa
added a commit
that referenced
this issue
Jun 9, 2022
* add contrbuting guidelines Signed-off-by: Asra Ali <[email protected]> * Update CONTRIBUTING.md, add MAINTAINERS.md Follow-up from #190 (thanks @asraa!). I did not add a DCO requirement at this point, as that was controversial in #190. I filed #308 to track that. I tried to address all *other* feedback in #190. Fixes #212. Fixes #306. * Move docs into a "docs" folder. Fixes #303. * Whitespace fixes * Address PR comments - TODO for testing instructions - Remove obsolete TODO * Full URL in testing * Fix @joshuagl suggestions Co-authored-by: Asra Ali <[email protected]>
Repository owner
moved this from 🆕 New
to 🏗 In progress
in [go-tuf] Project planning - v0.6.0 (Target: 2022-11-30)
Jun 9, 2022
rdimitrov
moved this from 🏗 In progress
to ✅ Done
in [go-tuf] Project planning - v0.6.0 (Target: 2022-11-30)
Jun 9, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, there's no
docs
folder for the project and it make sense to have one given there are already a few issues related to adding specific guidelines and documentations.The text was updated successfully, but these errors were encountered: