Hi, I definitely support any code of conduct. It would be better than nothing.
>From the content perspective I'm mostly concerned about the confidentiality of the process. According to the current process Jenkins board is *the only one *entity, which performs analysis, makes decisions and takes actions. It means that this process is not transparent from the community perspective. IMHO there should be additional decision makers outside the Board (e.g. Community Team <https://wiki.jenkins-ci.org/display/JENKINS/Proposal+-+Project+sub-teams> ?). In any case, this Code of Conduct cannot be applied before the re-election of Jenkins Board. All its members work for a single company and have a potential conflict of interest. For example, there may be a conflict between this company employee and external contributor causing bidirectional personal attacks. It happened several months ago, for example. The board must have more legitimacy before applying such process. Best regards, Oleg понедельник, 7 декабря 2015 г., 18:10:54 UTC+3 пользователь Baptiste Mathus написал: > > +1 globally, > > and +1 too with Christopher about the need for clarification of who is > deemed "Project maintainers", and expected to take actions (maybe it's only > to be rephrased as "the board", after having been reported or something). > > Also, not sure it's important, but there's also the #jenkins-commit > channel (which isn't RO, maybe we want to change that btw, like for > #jenkins-meeting outside the meeting hours). > > Cheers > > 2015-12-05 16:54 GMT+01:00 Christopher Orr <ch...@orr.me.uk <javascript:>> > : > >> On 05/12/15 16:22, Christopher Orr wrote: >> > Similarly, "project spaces" is not further expanded upon — all jenkinsci >> > repos? jenkins-infra? plugin repos/wikis/websites? >> >> My previous email was a bit long, so I wanted to try and list the spaces >> that I could think of, where it seems that adherence to a Code of >> Conduct should probably be encouraged for participants: >> >> Source control >> - GitHub commits, PRs, issues, wikis >> - jenkinsci >> - i.e. core, misc repos, plus all hosted plugins >> - jenkins-infra >> - jenkinsci-cert >> - SVN commits [assuming SVN isn't read-only] >> - svn.jenkins-ci.org >> >> Websites >> - Everything hosted on jenkins-ci.org and its subdomains, including: >> - Issue tracker >> - Wiki page content >> - Wiki comments (we could simplify by finally disabling this ;) >> - Blog post comments >> >> Mailing lists >> - https://jenkins-ci.org/content/mailing-lists >> - http://lists.jenkins-ci.org/mailman/listinfo >> >> IRC channels >> - #jenkins >> - #jenkins-meeting >> - #jenkins-infra >> - #jenkins-community >> >> Online events, e.g. Hangouts >> - Office Hours >> >> >> The Jenkins project is pretty big! :) >> >> Regards, >> Chris >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to jenkinsci-de...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/566308BC.3050400%40orr.me.uk >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Baptiste <Batmat> MATHUS - http://batmat.net > Sauvez un arbre, > Mangez un castor ! > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/b65441aa-fa73-46c9-afb4-fc4bc1202679%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
