-
-
Notifications
You must be signed in to change notification settings - Fork 104
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
Comments
The question:
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? |
I guess not, just wondering if we should get a sense for who's involved, not really needed
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 |
Should we create a |
yeah, link to raw is probably best |
Just realized we could skip the |
sure, that works |
We should add a link to the page to edit to update |
@richfitz to which page? |
@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). |
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. |
Ah, sorry. I'll add a wiki entry for the post acceptance checklist. |
Do we really need a will contribute part at this stage? Why does this matter now?
Can we list concrete things to check off here?
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?
The text was updated successfully, but these errors were encountered: