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

meta questions #2

Closed
karthik opened this issue Mar 11, 2015 · 11 comments
Closed

meta questions #2

karthik opened this issue Mar 11, 2015 · 11 comments
Labels

Comments

@karthik
Copy link
Member

karthik commented Mar 11, 2015

Who has/will contribute to this package?

Do we really need a will contribute part at this stage? Why does this matter now?

Are you willing to follow the rOpenSci policies (link), including transferring your repo to the rOpenSci GitHub organization account?

Can we list concrete things to check off here?

Are you willing to follow the [rOpenSci packaging guidelines](https://github.com/ropensci/packaging_guide? If you have disagreements with them, explain.

This seems like a rather big question for a binary answer. I'm not even sure most current rOpenSci packages can safely answer yes to those. Should we break those down here?

@richfitz richfitz added the meta label Mar 11, 2015
@richfitz
Copy link
Member

The question:

Are you willing to follow the rOpenSci policies (link), including transferring your repo to the rOpenSci GitHub organization account?

Seems like we might want to flag these things will come in the README (or in a longer "process" document that includes things like setting up the slack links) and then once we have provisional acceptance, tag the issue to indicate that and paste in a set of check boxes for this sort of stuff?

@sckott
Copy link
Contributor

sckott commented Mar 11, 2015

@karthik

Do we really need a will contribute part at this stage? Why does this matter now?

I guess not, just wondering if we should get a sense for who's involved, not really needed

Can we list concrete things to check off here? (wrt policies)

yes, once we agree on the policies, let's just make a bulleted list with checkboxes, or one checkbox to agree to all

On packaging guidelines -we could just say Are there any you disagree with? If so, explain - and if we agree to let that thing slide, cool cool

@karthik
Copy link
Member Author

karthik commented Mar 11, 2015

Should we create a template.md and put things there for people to copy and paste into an issue? We can link to the raw version of that file (so boxes and such won't get rendered) making it a bit easier.

@sckott
Copy link
Contributor

sckott commented Mar 11, 2015

yeah, link to raw is probably best

@karthik
Copy link
Member Author

karthik commented Mar 11, 2015

Just realized we could skip the template.md and stick everything in contributing.md instead.

@sckott
Copy link
Contributor

sckott commented Mar 11, 2015

sure, that works

@richfitz
Copy link
Member

We should add a link to the page to edit to update ropensci.org/packages/index.html in the instructions

@sckott
Copy link
Contributor

sckott commented Apr 13, 2015

@richfitz to which page?

@karthik
Copy link
Member Author

karthik commented Apr 13, 2015

@richfitz Good idea, but I'm ambivalent on adding this to contributing.md. We generally don't want to add post acceptance instructions here (same reason a journal doesn't send you printer instructions with submitting guidelines).
Also worried that even though the html is trivial, it's not exactly obvious what one needs to do to edit and what the tags mean etc.

@richfitz
Copy link
Member

OK, cool. You added it as a thing to do on #6 but I don't know where to edit and thought it was a general thing that the contributor would add.

@karthik
Copy link
Member Author

karthik commented Apr 14, 2015

Ah, sorry. I'll add a wiki entry for the post acceptance checklist.

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

No branches or pull requests

3 participants