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

Create resources based on open source survery #427

Closed
1 task
garethahealy opened this issue Jun 4, 2017 · 5 comments
Closed
1 task

Create resources based on open source survery #427

garethahealy opened this issue Jun 4, 2017 · 5 comments

Comments

@garethahealy
Copy link
Collaborator

garethahealy commented Jun 4, 2017

The following survey suggests we should add a few "admin" style info:

1/2 are just docs, 3 can be done via a github bot.

@garethahealy
Copy link
Collaborator Author

@orange-buffalo ; views?

@garethahealy
Copy link
Collaborator Author

garethahealy commented Jun 4, 2017

CLABot

or

cla-assistant

@buzdin
Copy link
Member

buzdin commented Jun 4, 2017

My view is to keep it simple. Dozer is not under Apache or other legal entity, so generally speaking no one cares about license agreements. It will just increase the barrier to entry for those willing to contribute.
Code of conduct idea for an open source project seems like a really strange idea to me. I know that there is a trend somewhere out there, but would not go and just copy paste some text to the website.

Contributing guide is a must. I made a placeholder some time ago https://github.com/DozerMapper/dozer/wiki/Contributing-to-Dozer
:)

@orange-buffalo
Copy link
Contributor

I agree with @buzdin that having CLA would complicate contribution process, especially for new members. I believe that it would be enough to have a short statement in contribution guide in this regard, something like "By contributing to Dozer project you agree that you contribution is managed and distributed in compliance with Dozer license" (or any fancier expression if you familiar with more formal legal statements :) ).

As for code of conduct, I don't mind having it in the project. But to me this is something more typical for big companies / huge projects with lots of contributors. Again, having a statement in contribution guide like "Please respect others and be polite" would be quite sufficient.

I suggest to move the contribution guide from wiki to the CONTRIBUTING.md file in the root of the project. Then GitHub will provide link to this document every time new issue/PR is created (https://github.com/blog/1184-contributing-guidelines).

@garethahealy
Copy link
Collaborator Author

Am happy with what you've both said. Am just throwing ideas out there :)

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

No branches or pull requests

3 participants