[oi-dev] OpenIndiana Code of Conduct

[Adam Števko]

Hi Peter,

> On Jul 22, 2016, at 2:00 PM, Peter Tribble <peter.tribble at gmail.com> wrote:
> 
> Adam,
> 
> Thanks for doing this. In my view, it's long overdue.

Thanks for you support. It might be long overdue, but rather late than never.  I hope this step will make former developers come back.


> Comments below.
> 
> As part of a larger effort at providing a more formal governance structure for the OpenIndiana project,
> 
> So, there is a wider context to this. Which is a good thing, but it would be good to have
> that fleshed out. Not necessarily conclusions, but it would be good for the community at
> large to understand what's missing and what's being done about it.

Yes, the wider context exists. The idea is to make every possible step to move project out of decline. There are few more things current developer have in the pipeline:
  - CoC (debated now),
  - governing board elections,
  - mission statement update,

  - new end-user documentation (based on Michael’s work),
  - oi-userland changes and further simplifications to lower barrier for contributing. There will be a call for new package contributions,
  - new ways to try out and develop OI (vagrant boxes, qcow2 images and netboot.xyz integration),
  - some infrastructure work (wiki update, long needed cleanup and reorganization, infra reinstall and better coverage via more mirrors),
  - forum, so people can communicate and help each other (it seems that mailing lists and IRC channels are not sufficient),

  - stable version based on hipster (/dev -> /stable will be a seamless transition. So far, plain upgrade works, but zones complicate it a little bit and that has to be sorted out).

There is a lot of work to be done, but unless we can get more developers on board, not everything can be accomplished in reasonable time. With stable release, we might need a few more devs, who could fill the ranks and help with maintenance. So I hope that the order of steps is logical and reasonable to everybody. To be clear, some things are already happening (mostly technical related). Political ones are a matter of discussion of course and shall be discussed and further agreed. The idea is to come up with some proposal, which could be discussed.

This list is very brief and I could write a blog post detailing every point if interested. However, it will take me a few days. Just let me know if you want to have it in more details or enough information was provided.

> 
> I’d like to announce on the behalf of OI developers the adoption of an OpenIndiana Code of Conduct. The draft text for this new document can be found at http://www.openindiana.org/community/code-of-conduct/ <http://www.openindiana.org/community/code-of-conduct/>.
> 
> We would also like to point out this draft document is open to discussion and acceptance by the community.
> Our desire is for the discussion to be civil and for it to center around the verbiage of the Code of Conduct.
> We do not wish for the discussion to go off topic, or question the need for such a document.
> 
> Please compose your thoughts and comment with as few replies as necessary so the community may solidify the final text of this document.
> 
> Overall, I'm happy with most of this. It's about the right length, as well.
> 
> I think you need an explicit reporting mechanism. Something like "email abuse at openindiana.org <mailto:abuse at openindiana.org>"
> or the like. (Of course, you need that to be routed somewhere.) And the first statement about
> confidentiality means that the 2nd part about not being made public is redundant. There's also
> no mention of consequences.

Michael and I slightly modified our initial proposal to include your points:
Violations of the CoC should be reported to the distribution maintainers via abuse at openindiana.org <mailto:abuse at openindiana.org>.
Neither reporters nor reported persons will, or should be, made public.
Upon receipt of a problem report, the distribution maintainers will investigate the issue and determine whether it warrants further action. Any further action will be proportional to the severity of the problem.
I also discussed your points with Alexander in Saint Petersburg and we came to the conclusions that mentioning every possible way to handle punishment would be a much longer list. So, we thought that putting it this way is better.
I hope that you are OK with it. If you have any further comments, please let us know.

Cheers,
Adam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20160724/261f2067/attachment-0005.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20160724/261f2067/attachment-0005.bin>