MESSAGE TO MEMBERS OF PUBLIC WHO HAVE SUBMITTED PULL REQUESTS PREVIOUSLY
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 386
- Forks
- 94
- PR merge metrics
- No merged PRs in 30d
Description
First off. Thanks for all the small pull requests to make the site better!
The instructions for github.com/nasa started off as a simple markdown file. Someone suggested making it into a webpage and contributed the first big upgrade. Many small and medium pull requests followed making it a little better each time. Hopefully it was also good practice for some of you.
There was some concern about it being a website with NASA information without a nasa.gov ending to the URL. Other similar things are explicitly docs for approved open-source code projects. This was documentation for the org account, so somewhat of a gray area. Hence, the instructions for use of github.com/nasa on was shifted to a markdown file that is not a website but rather a file. Apologies to those who submitted pull requests to improve the previous site.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read docs/INSTRUCTIONS.md to see the current instructions file and compare it with the former website context described here. The issue is an announcement and apology rather than a request for a specific change, so no completion condition is defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html, markdown
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100