We dont have a published 'code of conduct' document

[psh]

I took a look at our Github “Community Profile” (https://github.com/commons-app/apps-android-commons/community) which highlights that our project doesn’t have a published code of conduct. Digging a little deeper there’s a suggestion that the “Contributor Covenant” (see: https://www.contributor-covenant.org/) might be a good starting point.

I read through it and it seems to have been adopted by a large number of solid open-source projects and I don’t see anything I’d object to. How does everyone feel about adopting it for our project?

[misaochan]

Good point @psh ! The "Contributor Covenant" looks good to me. I did wonder if we would be expected to use the Wikimedia code of conduct instead, but that would be much less specific and at any rate it isn't an explicit requirement for us. So I think we can go ahead with your suggestion for now unless WMF requests otherwise.

[psh]

Can someone with contacts at WMF reach out to them to see if the "Contributor Covenant" is compatible with the WMF guidelines before we jump in?

[misaochan]

I could send an email to Legal after further discussion, if anyone wants to chime in. :)

I would also like to request one edit, if we use that code of conduct. As the project maintainer, I do try to keep on top of all the conversation that goes on here, but I cannot guarantee that I will always be able to keep track of everything. Sometimes I might be on leave, or sometimes there is just too much going on at the moment and I might miss something.

So I would propose that the right and responsibility to enforce the code should be shared between all collaborators, if you guys are willing to do so. Collaborators are able to edit, remove etc posts as well. There are a few things that only Owners can do, but those are much less likely to be needed and more likely to be long term measures - ie not something that needs to be done immediately like removing a blatantly offensive post.

[chrisdebian]

@psh Hi, Paul. Just trying to help prioritize what development work gets done next. Would you be able to have a look at this #6034 and potentially add your thoughts/ priorities to the spreadsheet?

Thanks,

Chris.