Skip to content

update readme #2127

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

Merged
merged 5 commits into from
Mar 14, 2023
Merged

update readme #2127

merged 5 commits into from
Mar 14, 2023

Conversation

parteekcoder
Copy link
Contributor

issue #2126

Updated README.md to help contributors

@welcome
Copy link

welcome bot commented Feb 23, 2023

🎉 Thanks for opening this pull request! Please check out our contributing guidelines if you haven't already.

@raclim
Copy link
Collaborator

raclim commented Feb 23, 2023

Hi @parteekcoder, thanks for working on this. We currently do have documentation for setting up your development environment within our contributor docs that includes these instructions.

I do think these docs could be harder to find, and having it noted somewhere in the README will make it more accessible. Maybe instead of the installation instructions, you can add a link to the contributor docs and some contextual information about them. Let me know what you think!

@parteekcoder
Copy link
Contributor Author

Hi @parteekcoder, thanks for working on this. We currently do have documentation for setting up your development environment within our contributor docs that includes these instructions.

I do think these docs could be harder to find, and having it noted somewhere in the README will make it more accessible. Maybe instead of the installation instructions, you can add a link to the contributor docs and some contextual information about them. Let me know what you think!

@raclim so shall I remove these installation steps and just mention the documenation link in the README.md?

@parteekcoder
Copy link
Contributor Author

hey @raclim now you can check and please tell if you like to mention anything else also

And please @raclim can you please guide how can I contribute to p5.js-web-editor project in GSOC this year

Copy link
Collaborator

@raclim raclim left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just updated with some comments! Once these are done, I think it'll be ready to go!

@parteekcoder
Copy link
Contributor Author

parteekcoder commented Mar 7, 2023

now @raclim @catarak @davepagurek you can review I updated this PR as you told

@parteekcoder parteekcoder requested a review from raclim March 12, 2023 18:49
@raclim raclim merged commit 458a2a3 into processing:develop Mar 14, 2023
@parteekcoder
Copy link
Contributor Author

hey @raclim thanks for merging,
I want to ask that I want to contribute in p5web-editor in the project "Adding Test Coverage", but as I see the project list on there only the p5 projects at high priority
can you please guide me with this

@raclim
Copy link
Collaborator

raclim commented Mar 14, 2023

Hi @parteekcoder!

The projects labelled as "High Priority" only apply to the ones in the p5.js Github repository. The projects listed for the p5.js Web Editor do not have any designated priority, so please feel free to select any that speak to you the most. For this year's Google Summer of Code, we advise potential contributors to have a drafted proposal to receive the best feedback. I'll try to have an updated post for this outlining these steps later today!

@parteekcoder
Copy link
Contributor Author

yeah but first all the high priority projects are assigned by GSoC admin then only the low ones , processing organization have many projects for each repository that's i just want to ask that is this project "Adding Test Coverage" or any other project in p5web-editor has the priority

@raclim
Copy link
Collaborator

raclim commented Mar 14, 2023

All of the projects listed for the p5.js Web Editor are ones that we would consider highly needed or "high priority", which is why there are no designated labels for them. Adding increased test coverage is a project we'd love further development on, but it does not hold a higher or lower priority compared to the other web editor projects.

Thus, please feel free to follow through with drafting a proposal around it if it's something you're interested in!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants