-
-
Notifications
You must be signed in to change notification settings - Fork 122
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
Author vs Contributor #38
Comments
I do not think there is a formal definition anywhere and I think your approach makes sense. |
When implementing the "idea" requires a total rebuilding of the module in a new version while migrating it, the developer deserves the authorship in my opinion, so I agree on all the points brought by @Tardo. |
Agree: this is all very subjective on the level of work/originality of the contributor. Question is today there is no formal definition of the concept (AFAIK). Is it necessary or letting the users decide case by case (my preferred way) is good enough? Do we have often discussions on the topic? |
Hello, This is perfect, but like say @elicoidal, I don't see nothing formal. This is a great solution against people that they put as author for simple changes. Greetings |
Hi, another day... another question xD
When you are an author and when you are an contributor?
-> Add new feature = Author
-> Migrate a module = Contributor
---> Migrate a module (rewriting: JS massive changes or something like that) = Author
-> Fix issues = Contributor
-> Add new module = Author
I'm in the correct way?
The text was updated successfully, but these errors were encountered: