docs: add readme with links to community docs #4#6
Conversation
|
Looks good. Thanks for getting this going. |
|
@GBKS whats the procedure to get this merged? lol |
GBKS
left a comment
GBKS
left a comment
There was a problem hiding this comment.
Not so sure about the "Getting started" section yet. Getting started could also be about joining the community by registering on Slack, reading up on things and participating in a few conversations. Maybe that could be split into "How to get involved in the community" and "How to get involved in projects", or something like that. For project lists, we also have the Github project boards.
| Anything related to group consensus and coordination of the Bitcoin Design Community. | ||
|
|
||
| ### Getting Started | ||
| 1. Pick existing [project](https://docs.google.com/document/d/1P20rPq6V6w78dXpBqLiiiB-kSypZOzXaG9ZUErYIq28/edit) in the space and do something small |
There was a problem hiding this comment.
My understanding of our process is that we'll use GitHub Projects, so the link should point to the list of active projects on GitHub not a Google doc
There was a problem hiding this comment.
From the google doc
A more mature idea can be posted as an issue on GitHub (in the most appropriate repository and project board) after some discussion
- It seems you can't create GitHub projects unless you are a maintainer of the repo.
- I'm not sure how the project setup would work for the external projects like BTC pay.
- Would it be best suited to be added to a markdown file until we get the website online with a projects page? WIP; https://github.com/BitcoinDesign/Meta/blob/a14632fe76f00de0c0f25f9f9acd2f67dfc164f8/Projects.md
| 1. Pick existing [project](https://docs.google.com/document/d/1P20rPq6V6w78dXpBqLiiiB-kSypZOzXaG9ZUErYIq28/edit) in the space and do something small | ||
| 2. If you are passionate. Just do it. Worst case you publish it on your own | ||
| 3. Contribute to parts of the design guide and website even if it is a slower process to get things approved | ||
|
|
There was a problem hiding this comment.
IMO we should remove negative language like "even if it is a slower process" ... let's be optimistic when introducing new people to the project :)
| ### Projects | ||
|
|
||
| - Project list — [Doc](https://docs.google.com/document/d/1P20rPq6V6w78dXpBqLiiiB-kSypZOzXaG9ZUErYIq28/edit) | ||
|
|
There was a problem hiding this comment.
same comment as above - need to point to github not google docs
|
|
||
| - Slack Channel — [#open-design](https://bitcoindesign.slack.com/archives/C015GFYSJNA) | ||
| - Discussions -- [Issues](https://github.com/BitcoinDesign/Meta/issues) | ||
|
|
There was a problem hiding this comment.
seems like the project lifecycle in the google doc should be placed in markdown on github and then pointed to as part of "governance" (or, process)
| - Project list — [Doc](https://docs.google.com/document/d/1P20rPq6V6w78dXpBqLiiiB-kSypZOzXaG9ZUErYIq28/edit) | ||
|
|
||
| ### Governance / Opensource Design | ||
|
|
There was a problem hiding this comment.
maybe use softer language "process" vs. "governance"?
|
@johnsBeharry as this is a PR you created, could you please review the outstanding changes @moneyball suggested? |
3 participants
Problem
Solution
Create a README.md
Result
Created a README.md with links to process documents and channels of the bitcoin design slack.