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

User contribution guide #11

Open
seabbs opened this issue Nov 6, 2019 · 4 comments
Open

User contribution guide #11

seabbs opened this issue Nov 6, 2019 · 4 comments

Comments

@seabbs
Copy link

seabbs commented Nov 6, 2019

Depending on your thinking regarding user contributions it would be really great to have some sort of guidance for how you would like features to be suggested.

I have implemented this as a folder previously (and in the README but other solutions could be equally as good.

Linked to #6

@giabaio
Copy link
Owner

giabaio commented Nov 7, 2019

So far, most of the contributions have either come from my wider "team" (=people and students with whom I work), so it's all been relatively informal. I'm happy to think of a more formal way, if needs be --- or you can simply push requests, especially if we're starting with relatively smaller and less fundamental changes/additions... Of course, happy to go more specific if we're doing something more series - eg by creating projects and assigning tasks etc...

I'm closing this now, but again, discussion can continue.

@giabaio giabaio closed this as completed Nov 7, 2019
@seabbs
Copy link
Author

seabbs commented Nov 12, 2019

My thoughts on this are that one of the great strengths of R is that it is open source and can capture community best practices in an organic way. Lowering the barriers to entry for this - by providing guidelines etc. can make this much easier. It is also community recognized best practice so it may make users trust the package more. The tidyverse are great example of packages that make this easy (https://github.com/tidyverse/dplyr/tree/master/.github).

For example, I imagine that you receive a lot of personal communication about the package but it would be really great to move this into the open (by encouraging the use of GitHub etc.). Having said that I do see some of this in the issues here so that is good. In a similar vein having the future work centralized somewhere (i.e GitHub issues) with clear guidelines for how to contribute would make it much easier to know how to give back.

I typically list all future work on GitHub for packages and have had users do the work before I could get to it (which for dull things like docs is very nice!). So there is also a time-saving element :).

Would you be happy for a pull request based on the example I linked above?

@giabaio
Copy link
Owner

giabaio commented Nov 23, 2019

Yes.

@giabaio giabaio reopened this Nov 23, 2019
giabaio pushed a commit that referenced this issue Jul 21, 2020
@n8thangreen
Copy link
Contributor

closed

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

3 participants