-
Notifications
You must be signed in to change notification settings - Fork 1
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
Code of Conduct - need to add #43
Comments
So BOSC has a CoC, usually from ISMB or this year GCC, but the OBF itself doesn't have a CoC. That said, if the OBF adopts a CoC I think it would be easiest to simply use theirs. @ljgarcia @DennisSchwartz - does this sound ok and reasonable to you? I think @rowlandm and I like this plan. |
I like this plan of using the one from OBF.
…On 5/31/18, Yo Yehudi ***@***.***> wrote:
So BOSC has a CoC, usually from ISMB or this year GCC, but the OBF itself
doesn't have a CoC. That said, if the OBF adopts a CoC I think it would be
easiest to simply use theirs.
@ljgarcia @DennisSchwartz - does this sound ok and reasonable to you? I
think @rowlandm and I like this plan.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#43 (comment)
|
It does make sense, yes.
…On 31/05/2018 20:22, rowlandm wrote:
I like this plan of using the one from OBF.
On 5/31/18, Yo Yehudi ***@***.***> wrote:
> So BOSC has a CoC, usually from ISMB or this year GCC, but the OBF
itself
> doesn't have a CoC. That said, if the OBF adopts a CoC I think it
would be
> easiest to simply use theirs.
>
> @ljgarcia @DennisSchwartz - does this sound ok and reasonable to you? I
> think @rowlandm and I like this plan.
>
> --
> You are receiving this because you were mentioned.
> Reply to this email directly or view it on GitHub:
> #43 (comment)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#43 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFLQNBq7wFsJNoWpwFBt3iubM-KmflVLks5t4EMAgaJpZM4UU39I>.
|
I think it's a great idea to re-use a CoC that others (who maybe have more resources) have spend time on working out. Do we know if the OBF is planning to adopt a Code of Conduct soon? Otherwise we could spend some time looking at the CoCs of other OSS projects and maybe copy theirs :P |
Stemformatics code of conduct: Copied mostly from Galaxy code of counduct: |
I would be very happy to copy from that wholesale if everyone else is?
…On Sun, 10 Jun 2018 at 02:44, rowlandm ***@***.***> wrote:
Stemformatics code of conduct:
https://docs.google.com/document/d/1YPyFOtzDc3P_bno-9MHTnwdOOPOo7MpFpiBqqBxTksc/edit
Copied mostly from Galaxy code of counduct:
https://github.com/galaxyproject/galaxy/blob/master/CODE_OF_CONDUCT.md
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#43 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AI14jjy8eJV7Wlsfd6_4J2cKT3i2fbf2ks5t7HnygaJpZM4UU39I>
.
|
Fine by me!
…On Mon, Jun 11, 2018 at 6:54 PM Yo Yehudi ***@***.***> wrote:
I would be very happy to copy from that wholesale if everyone else is?
On Sun, 10 Jun 2018 at 02:44, rowlandm ***@***.***> wrote:
> Stemformatics code of conduct:
>
>
https://docs.google.com/document/d/1YPyFOtzDc3P_bno-9MHTnwdOOPOo7MpFpiBqqBxTksc/edit
>
> Copied mostly from Galaxy code of counduct:
> https://github.com/galaxyproject/galaxy/blob/master/CODE_OF_CONDUCT.md
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#43 (comment)
>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/AI14jjy8eJV7Wlsfd6_4J2cKT3i2fbf2ks5t7HnygaJpZM4UU39I
>
> .
>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#43 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAZo0haN40AW1Jx8djxnzH8MHIlkuyyjks5t7jBXgaJpZM4UU39I>
.
|
Ideally be inspired by OBF CoC.
The text was updated successfully, but these errors were encountered: