Contributing and conduct

[betatim]

Some fairly standard information on conduct and how to contribute.

Straight forward:

• every collaborator can merge PRs
• all changes are proposed by forking the repository and then making a PR
• no one can merge their own work
• use common sense, and
• be nice to everyone

We should get along swimmingly!

[khinsen]

Does it make sense to add this now? The proposal is submitted, so this repository should not evolve much from now on. We should start another one for the real work.

[cranmer]

Hi,

We could make a release, perhaps push to zenodo the version that was submitted, and still use this repository for further discussions.

Kyle

On Mar 1, 2016, at 7:14 AM, Konrad Hinsen [email protected] wrote:

Does it make sense to add this now? The proposal is submitted, so this repository should not evolve much from now on. We should start another one for the real work.

—
Reply to this email directly or view it on GitHub #110 (comment).

[ctb]

RIO has offered to publish open science prize proposals -- https://twitter.com/RIOJournal/status/703141211612155904 How about doing that?

[cranmer]

Fine with me. A release seems to make sense independently
On Tue, Mar 1, 2016 at 9:36 AM C. Titus Brown [email protected]
wrote:

RIO has offered to publish open science prize proposals --

https://twitter.com/RIOJournal/status/703141211612155904

How about doing that?

—
Reply to this email directly or view it on GitHub
#110 (comment)
.

[khinsen]

@ctb +1

@cranmer +1 as well, though it will take me some time to get used to the term "release" for a piece of prose that moreover is not supposed to evolve. I'd call it an archival copy, but the result is the same.

But the real question concerning this PR is if we continue to use it as a place for discussion.

[lukasheinrich]

👍 for both release w/ zenodo and publishing in RIO (if it's not too involved)

[betatim]

I wanted to add it mainly for people who come here for the discussions in the issues. I think it makes sense to have those in this repo for a while longer.

I think we should use #15 to come up with a few next steps. One of them should be creating everpub/specs or everpub/mocks (or similar) where we post mockups or specs for how things might work together.

[khinsen]

👍