-
-
Notifications
You must be signed in to change notification settings - Fork 967
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
INFORMATION FOR CONTRIBUTORS #1167
Comments
Should we continue to file issues on the main |
@nippur72 if the file related to the separated repo, pls make a new issue or PR there. |
@cognitom ok, also new issue labels ( |
@nippur72 how about just |
Agreed. Less is more :) On a single repository I usually go with just one label: |
@tipiirai even if riotjs has a pretty simple api the issues we must solve are really different so I like to organize them with several labels hoping this could help also the other contributors. It would be nice to have just the |
Yep! Less is more 👍 |
I'll obviously let you guys use as many labels as necessary. The need for more tags raises when the amount of requests grows. |
closing this issue ✌️ |
Hello all, we've been changing the structure this few weeks. Here's some links at this point. Check these before your contribution, thanks!
Now, we have several repos:
Additionally preparing a new example site and repo:
Removing:
Note: The structure above could be changed before v2.3, pls check the latest information.
TODO: include this information to CONTRIBUTING.md by the release of v2.3
cc: @tipiirai @GianlucaGuarini @aMarCruz @rsbondi feel free to update this issue.
The text was updated successfully, but these errors were encountered: