Risk-First is turning out to be a big undertaking, and any help would be gratefully appreciated.
The basic route to feedback is simply to Open An Issue and explain what needs to be done. We'd be very grateful to hear your ideas.
At the top of each page, there's an image in to show what kind state the page is in.
Means this is probably a placeholder page, and needs fleshing out. If you have ideas, please submit them in an issue|
Most of the text is correct, but there are likely to be place-holders. Open issues if there are glaring omissions/inaccuracies.
In this state if:
- It's written
- It's proofed on the wiki
- It's proofed in the PDF
- All images are present
Get involved! Please help by reviewing the page and letting us know what you think!
If there is no status banner, the page is published:
- Has been reviewed by 3rd party for grammatical or spelling errors
- Has been up for public readership for some time
i.e. Ready for consumption, enjoy!
- If you "Star" the project in GitHub you will receive an invite to Join the Risk-First Organisation.
- Alternatively, fork the repo and issue a pull request in the usual way.
- Feel free to raise issues on the project to ask for corrections / improvements.
Both this main repo (risk-first/website) and it's wiki (risk-first/website.wiki) are identical. The reason for this is to allow the main GitHub workflow to operate (forking / pull requests).
In order to merge pull requests:
- Perform the pull request through the normal GitHub UI.
- Pull the changes to the local repo
- Ensure that the origin for the wiki is added to the local repo:
git remote set-url --add --push origin [email protected]:risk-first/website.wiki.git
git pushto push to both therisk-first/websiteandrisk-first/website.wikirepos.
If you submit an issue, an edit, an article, whatever, you will be credited by name in the publications derived from this project.