This repository has been archived by the owner on Mar 9, 2024. It is now read-only.
Clarify that the projects should be developed on the Ecosystem and not on personal accounts #49
Conversation
This file contains 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
…t on personal accounts
|
Would be nice to have this (and all PR in this repo) reviewed by at least one other @monero-ecosystem/maintainers before merging. Please leave a review. |
|
Oh yeah that's me - I kept intending to make an actual larger change before merging but never got around to it. I'll pr it now. |
dginovker
approved these changes
Aug 14, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I noticed some maintainers have personal clones of their project in their personal account (see comment in #45). This is not optimal if the repository was active for long time before moving it to the Ecosystem because all links, which are automatically redirected to the new repo, will be broken. Not a big deal anyway, and it's understandable that the maintainers wish to have a clone in their personal account. Still not optimal though, since create confusion.
What would be problematic is the situation where the maintainer push commits to the personal repo and maybe sync this one with the official repo in the Ecosystem. This could create many problems and would confuse users/contributors, who would have not clear where the project is developed and could create a lot of confusion. Just imagine a user opening an issue on the repo on the Ecosystem referring to a commit in the personal account of the maintainer. Would be a mess.
The point of the Ecosystem is to develop the projects on the Ecosystem itself, creating a community of developers and users. Committing on a personal clone and using the repo in the Ecosystem as a mirror is incompatible with the goals of the Ecosystem. This PR edits the readme to make this point clearer.