Skip to content
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

Closed
cognitom opened this issue Aug 26, 2015 · 9 comments
Closed

INFORMATION FOR CONTRIBUTORS #1167

cognitom opened this issue Aug 26, 2015 · 9 comments

Comments

@cognitom
Copy link
Member

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:

  • gh-pages branch on riot/riot
  • demo dir on riot/riot
  • doc dir on riot/riot

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.

@nippur72
Copy link
Contributor

Should we continue to file issues on the main riot repo, or in each separate repos?

@cognitom
Copy link
Member Author

@nippur72 if the file related to the separated repo, pls make a new issue or PR there.
In other cases, for example, core Riot files, general proposals or discussions, it would be nice in this riot/riot repo, I think :-)

@nippur72
Copy link
Contributor

@cognitom ok, also new issue labels (riot-compiler, riot-observable, ...) might be useful in organizing issues.

@cognitom
Copy link
Member Author

@nippur72 how about just submodule ? We have already 11 labels 😲

@tipiirai
Copy link
Contributor

Agreed. Less is more :)

On a single repository I usually go with just one label: critical and that has worked well.

@GianlucaGuarini
Copy link
Member

@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 critical label but it wouldn't mean that much to me without bug, question, feature request... :)
@cognitom I think we could avoid to introduce new labels, anytime there will be a bug/feature request related to one of our submodules we could move it easily to the right repo see here 4 ex

@cognitom
Copy link
Member Author

Yep! Less is more 👍
How about document bugs? Move them to riot/riot.github.io?

@tipiirai
Copy link
Contributor

I'll obviously let you guys use as many labels as necessary. The need for more tags raises when the amount of requests grows.

@GianlucaGuarini
Copy link
Member

closing this issue ✌️

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

No branches or pull requests

4 participants