Update readme and create more flushed out contributing documentation #11131
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
corwintines
requested review from
samajammin,
wackerow,
pettinarip,
minimalsm,
jmcook1186 and
nhsz
as code owners
✅ ethereum-org-website-dev deploy preview ready
|
github-actions
bot
added
content 🖋️
corwintines
changed the title
|
Hey @corwintines ! Just noticed some extra spacing on this url --> https://ethereumorgwebsitedev01-readmeupdate.gatsbyjs.io/en/contributing/testing/#user-experience
For reference, In the above video, I'm trying to click the links which should navigate me to that part.
For reference: https://appwrite.io/community
We can add require guidance which can be helpful for developers who require assistance. Assistance can be related to setting up the project , problems related to codebase, structure, etc. Lastly, I would love to work on these issues. Feel free to assign me. |
|
|
|
@corwintines this should have been simple bullet points, not a lengthy paragraph :P |
|
this should be under the headline, not at the end |
konopkja
reviewed
Sep 25, 2023
|
|
||
| --- | ||
|
|
||
| If you would like to get involved in testing release candidates, please say hi in the `👾 ｜ website-code` channel of the Discord. We also host bi-weekly community testing events held in Discord and [gather.town](https://www.gather.town/) where we all hop on together to test the release candidate. Come join and say hi! |
There was a problem hiding this comment.
Suggested change
| If you would like to get involved in testing release candidates, please say hi in the `👾 ｜ website-code` channel of the Discord. We also host bi-weekly community testing events held in Discord and [gather.town](https://www.gather.town/) where we all hop on together to test the release candidate. Come join and say hi! |
Comment on lines
13
to
15
| ## How to get involved | ||
|
|
||
| There are a number of ways to get involved with testing. We are looking for any content, design, or user experience bugs or regressions that may have been introduced in the release candidate. |
There was a problem hiding this comment.
Suggested change
| ## How to get involved | |
| There are a number of ways to get involved with testing. We are looking for any content, design, or user experience bugs or regressions that may have been introduced in the release candidate. | |
| ## How to get involved | |
| We are looking for any content, design, or user experience bugs or regressions that may have been introduced in the release candidate. | |
| If you would like to get involved, please say hi in the `👾 ｜ website-code` channel of the Discord. | |
| We also host bi-weekly community testing events held in Discord and [gather.town](https://www.gather.town/) where we all hop on together to test the release candidate. Come join and say hi! | |
There was a problem hiding this comment.
@corwintines have you thought about poap rewards for QA testing?
There was a problem hiding this comment.
A bit. We currently don't offer anything, but I would like to see this as something we do for 2024.
|
|
||
| The QA testing contributions is an initiative to test release candidates for ethereum.org before they are deployed into production. Testing is a vital part in a products release cycle to catch bugs and regressions that may have been introduced before a release. | ||
|
|
||
| On Tuesdays we create a release candidate that goes into the staging branch. Information about the release candidate will be posted in the `👾 ｜ website-code` channel in our [Discord](https://discord.gg/ethereum-org). You can also find the release notes for the release candidate on the [releases page](https://github.com/ethereum/ethereum-org-website/releases) in the GitHub repository. The release candidate will be tagged as a `pre-release` until it has been merged into master. After QA testing, we deploy the release candidate into production if there are no release blocking bugs found on Thursday. More info on the deploy process for ethereum.org can be found [here](https://github.com/ethereum/ethereum-org-website/blob/dev/docs/deploy-process.md). |
There was a problem hiding this comment.
Suggested change
| On Tuesdays we create a release candidate that goes into the staging branch. Information about the release candidate will be posted in the `👾 ｜ website-code` channel in our [Discord](https://discord.gg/ethereum-org). You can also find the release notes for the release candidate on the [releases page](https://github.com/ethereum/ethereum-org-website/releases) in the GitHub repository. The release candidate will be tagged as a `pre-release` until it has been merged into master. After QA testing, we deploy the release candidate into production if there are no release blocking bugs found on Thursday. More info on the deploy process for ethereum.org can be found [here](https://github.com/ethereum/ethereum-org-website/blob/dev/docs/deploy-process.md). | |
| in the GitHub repository. The release candidate will be tagged as a `pre-release` until it has been merged into master. After QA testing, we deploy the release candidate into production if there are no release blocking bugs found on Thursday. More info on the deploy process for ethereum.org can be found [here](https://github.com/ethereum/ethereum-org-website/blob/dev/docs/deploy-process.md). | |
| - **Every Tuesday** we create a release candidate that goes into the staging branch. | |
| - Info about the release candidate is posted in the `👾 ｜ website-code` channel in our [Discord](https://discord.gg/ethereum-org). | |
| - Find the release notes for the release candidate on the [releases page](https://github.com/ethereum/ethereum-org-website/releases) | |
| - The release candidate will be tagged as a `pre-release` | |
| - **On Thursday** the release candidate is published on production. | |
| - More info on the deploy process for ethereum.org can be found [here](https://github.com/ethereum/ethereum-org-website/blob/dev/docs/deploy-process.md). | |
✅ Deploy Preview for ethereumorg ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
Just updated with latest from |
wackerow
requested changes
Feb 13, 2024
wackerow
added
documentation 📖
|
This issue is stale because it has been open 30 days with no activity. |
github-actions
bot
added
the
Status: Stale
wackerow
removed
needs review 👀
Status: Stale
|
This issue is stale because it has been open 30 days with no activity. |
github-actions
bot
added
the
Status: Stale
github-actions
bot
added
the
abandoned
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixes: #8524