Request for Comment: Jenkins Code of Conduct
76 views
Skip to first unread message
R. Tyler Croy
Dec 4, 2015, 8:09:57 PM12/4/15
to jenkin...@googlegroups.com, jenkins...@googlegroups.com
As the Jenkins community has grown, it has become clear that we need to write
down what behaviors we welcome in our community, but more importantly, what is
not welcome.
I would like to invite you all to review and provide feedback on the following
wiki page: <https://wiki.jenkins-ci.org/display/JENKINS/Code+of+Conduct>
I take responsibility for the board dragging their feet on this topic and wish
to remedy that as soon as possible. I cannot stress the importance of this
topic enough and while I hope that we do not find ourselves in a position which
needs addressing, I believe it is critical to the long-term health of the
Jenkins community that this be defined.
If you have questions or concerns that you do not wish to advertise publicly,
please email me off-list.
Cheers
- R. Tyler Croy
------------------------------------------------------
Code: <https://github.com/rtyler>
Chatter: <https://twitter.com/agentdero>
% gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
------------------------------------------------------
Slide
Dec 5, 2015, 8:53:39 AM12/5/15
to jenkin...@googlegroups.com, jenkins...@googlegroups.com
+1
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/20151205010827.GH23766%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.
Christopher Orr
Dec 5, 2015, 10:22:45 AM12/5/15
to jenkin...@googlegroups.com
Hi there,
Thanks for the update!
While the Contributor Covenant seems reasonable, it also appears to be a
pretty generic template, and I find it leaves a lot of ambiguity that
could be expanded upon.
From the first sentence, the Code of Conduct applies to "this project" —
which I would assume means Jenkins core, and I guess also its
infrastructure. But that's not clear to me and, given that a large part
of Jenkins is its plugin ecosystem, I don't know where plugins, their
maintainers, and contributors fit into this.
"Project maintainers have the right and responsibility to ... ban
temporarily or permanently any contributor for other behaviors that they
deem inappropriate" — this reads as if any Jenkins core developer can
unilaterally ban somebody at any point based on their subjective opinion?
This seems out of place — I would expect only the board to have this
power, having followed the "Reporting" and "Handling of violations"
procedures mentioned later.
Similarly, "project spaces" is not further expanded upon — all jenkinsci
repos? jenkins-infra? plugin repos/wikis/websites?
I find the recently published Go Code of Conduct @
https://golang.org/conduct to be very clear about these points, as well
as approaching the entire topic from a more positive standpoint —
focussing more on the motivations, and the project's desired goals,
rather than sounding almost entirely negative.
In particular, I find the "Gopher values" are very well put, and cover
many of the topics that have come up on the Jenkins developers' mailing
list this year regarding being patient, thoughtful, and staying
constructive with criticism.
There is also a clear definition of what "project spaces" are, including
GitHub organisations, code review tools, a list of mailing lists and IRC
channels. The statement about external groups and conferences is also
helpful, and would be useful for Jenkins given the growth of Jenkins
Area Meetups.
Reporting is covered slightly more in more depth, or at least the
timeline is a bit clearer than what we have at the moment, though the
Jenkins version does a good job about being clear on the possible
outcomes. The change proposal process and summary at the end are also nice.
Anyway, for the Jenkins project, progress is certainly being made, and
thanks to Tyler for doing this! :)
Regards,
Chris
Thanks for the update!
While the Contributor Covenant seems reasonable, it also appears to be a
pretty generic template, and I find it leaves a lot of ambiguity that
could be expanded upon.
From the first sentence, the Code of Conduct applies to "this project" —
which I would assume means Jenkins core, and I guess also its
infrastructure. But that's not clear to me and, given that a large part
of Jenkins is its plugin ecosystem, I don't know where plugins, their
maintainers, and contributors fit into this.
"Project maintainers have the right and responsibility to ... ban
temporarily or permanently any contributor for other behaviors that they
deem inappropriate" — this reads as if any Jenkins core developer can
unilaterally ban somebody at any point based on their subjective opinion?
This seems out of place — I would expect only the board to have this
power, having followed the "Reporting" and "Handling of violations"
procedures mentioned later.
Similarly, "project spaces" is not further expanded upon — all jenkinsci
repos? jenkins-infra? plugin repos/wikis/websites?
I find the recently published Go Code of Conduct @
https://golang.org/conduct to be very clear about these points, as well
as approaching the entire topic from a more positive standpoint —
focussing more on the motivations, and the project's desired goals,
rather than sounding almost entirely negative.
In particular, I find the "Gopher values" are very well put, and cover
many of the topics that have come up on the Jenkins developers' mailing
list this year regarding being patient, thoughtful, and staying
constructive with criticism.
There is also a clear definition of what "project spaces" are, including
GitHub organisations, code review tools, a list of mailing lists and IRC
channels. The statement about external groups and conferences is also
helpful, and would be useful for Jenkins given the growth of Jenkins
Area Meetups.
Reporting is covered slightly more in more depth, or at least the
timeline is a bit clearer than what we have at the moment, though the
Jenkins version does a good job about being clear on the possible
outcomes. The change proposal process and summary at the end are also nice.
Anyway, for the Jenkins project, progress is certainly being made, and
thanks to Tyler for doing this! :)
Regards,
Chris
Christopher Orr
Dec 5, 2015, 10:54:44 AM12/5/15
to jenkin...@googlegroups.com
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
> Similarly, "project spaces" is not further expanded upon — all jenkinsci
> repos? jenkins-infra? plugin repos/wikis/websites?
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
Baptiste Mathus
Dec 7, 2015, 10:10:54 AM12/7/15
to jenkin...@googlegroups.com
+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
--
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.
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.
Oleg Nenashev
Dec 14, 2015, 3:21:56 AM12/14/15
to Jenkins Developers, m...@batmat.net
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?).
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 написал:
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?).
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 написал:
Christopher Orr
Jan 5, 2016, 7:05:26 PM1/5/16
to jenkin...@googlegroups.com
Ahead of tomorrow's meeting, and as the wiki page is locked for editing,
I just wanted to mention a couple of quick (minor) things:
1. About emailing individual board members, it says "their emails should
be visible from their Confluence profile page" — the correct email
address seems to only be available for two of three members.
Maybe the addresses should be directly on the board page, or the code of
conduct page, to make things a little easier? Or Dean can fix his
profile.. :)
2. I still find it weird that events not controlled by the Jenkins
project are listed as "spaces" where the code of conduct applies;
specifically "FOSDEM" and "Jenkins Area Meetups".
Both are independent events, and I think that "Other community hosted by
the Jenkins community whether online or offline" already covers things
like the Jenkins project being at FOSDEM/SCALE/etc.
(Should the first "community" in that sentence be "events"?)
What could be added instead is (again stolen from Go): "Other Jenkins
groups (such as conferences, meetups, and other unofficial forums) are
encouraged to adopt this Code of Conduct. Those groups must provide
their own moderators and/or reporting system."
i.e. we encourage independent JAMs and conferences (Jenkins World?) to
follow the same code.
Regards,
Chris
On 05/12/15 02:08, R. Tyler Croy wrote:
>
I just wanted to mention a couple of quick (minor) things:
1. About emailing individual board members, it says "their emails should
be visible from their Confluence profile page" — the correct email
address seems to only be available for two of three members.
Maybe the addresses should be directly on the board page, or the code of
conduct page, to make things a little easier? Or Dean can fix his
profile.. :)
2. I still find it weird that events not controlled by the Jenkins
project are listed as "spaces" where the code of conduct applies;
specifically "FOSDEM" and "Jenkins Area Meetups".
Both are independent events, and I think that "Other community hosted by
the Jenkins community whether online or offline" already covers things
like the Jenkins project being at FOSDEM/SCALE/etc.
(Should the first "community" in that sentence be "events"?)
What could be added instead is (again stolen from Go): "Other Jenkins
groups (such as conferences, meetups, and other unofficial forums) are
encouraged to adopt this Code of Conduct. Those groups must provide
their own moderators and/or reporting system."
i.e. we encourage independent JAMs and conferences (Jenkins World?) to
follow the same code.
Regards,
Chris
On 05/12/15 02:08, R. Tyler Croy wrote:
>
R. Tyler Croy
Jan 6, 2016, 12:27:22 PM1/6/16
to jenkin...@googlegroups.com
(replies inline)
On Wed, 06 Jan 2016, Christopher Orr wrote:
> Ahead of tomorrow's meeting, and as the wiki page is locked for editing,
> I just wanted to mention a couple of quick (minor) things:
>
> 1. About emailing individual board members, it says "their emails should
> be visible from their Confluence profile page" ??? the correct email
an easily findable place is a reasonable requirement for the board :)
> 2. I still find it weird that events not controlled by the Jenkins
> project are listed as "spaces" where the code of conduct applies;
> specifically "FOSDEM" and "Jenkins Area Meetups".
>
> Both are independent events, and I think that "Other community hosted by
> the Jenkins community whether online or offline" already covers things
> like the Jenkins project being at FOSDEM/SCALE/etc.
> (Should the first "community" in that sentence be "events"?)
>
> What could be added instead is (again stolen from Go): "Other Jenkins
> groups (such as conferences, meetups, and other unofficial forums) are
> encouraged to adopt this Code of Conduct. Those groups must provide
> their own moderators and/or reporting system."
I've incorporated some of this feedback, but I think it is important to
recognize the difference between an event like FOSDEm which has a board code of
conduct that applies to the whole event, a more specific one (ours) which would
ostensibly apply to individuals representing Jenkins in an official capacity
(e.g. manning the stand).
> i.e. we encourage independent JAMs and conferences (Jenkins World?) to
> follow the same code.
Agreed!
I've incorporated this feedback, thanks
> On 05/12/15 02:08, R. Tyler Croy wrote:
> >
> > As the Jenkins community has grown, it has become clear that we need to write
> > down what behaviors we welcome in our community, but more importantly, what is
> > not welcome.
> >
> > I would like to invite you all to review and provide feedback on the following
> > wiki page: <https://wiki.jenkins-ci.org/display/JENKINS/Code+of+Conduct>
> >
> >
> > I take responsibility for the board dragging their feet on this topic and wish
> > to remedy that as soon as possible. I cannot stress the importance of this
> > topic enough and while I hope that we do not find ourselves in a position which
> > needs addressing, I believe it is critical to the long-term health of the
> > Jenkins community that this be defined.
> >
> >
> > If you have questions or concerns that you do not wish to advertise publicly,
> > please email me off-list.
> >
> >
> >
> > Cheers
> > - R. Tyler Croy
> >
> > ------------------------------------------------------
> > Code: <https://github.com/rtyler>
> > Chatter: <https://twitter.com/agentdero>
> >
> > % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
> > ------------------------------------------------------
> >
>
On Wed, 06 Jan 2016, Christopher Orr wrote:
> Ahead of tomorrow's meeting, and as the wiki page is locked for editing,
> I just wanted to mention a couple of quick (minor) things:
>
> 1. About emailing individual board members, it says "their emails should
> address seems to only be available for two of three members.
>
> Maybe the addresses should be directly on the board page, or the code of
> conduct page, to make things a little easier? Or Dean can fix his
> profile.. :)
I put this on the Governance Board page, I think listing contact addresses in
>
> Maybe the addresses should be directly on the board page, or the code of
> conduct page, to make things a little easier? Or Dean can fix his
> profile.. :)
an easily findable place is a reasonable requirement for the board :)
> 2. I still find it weird that events not controlled by the Jenkins
> project are listed as "spaces" where the code of conduct applies;
> specifically "FOSDEM" and "Jenkins Area Meetups".
>
> Both are independent events, and I think that "Other community hosted by
> the Jenkins community whether online or offline" already covers things
> like the Jenkins project being at FOSDEM/SCALE/etc.
> (Should the first "community" in that sentence be "events"?)
>
> What could be added instead is (again stolen from Go): "Other Jenkins
> groups (such as conferences, meetups, and other unofficial forums) are
> encouraged to adopt this Code of Conduct. Those groups must provide
> their own moderators and/or reporting system."
recognize the difference between an event like FOSDEm which has a board code of
conduct that applies to the whole event, a more specific one (ours) which would
ostensibly apply to individuals representing Jenkins in an official capacity
(e.g. manning the stand).
> i.e. we encourage independent JAMs and conferences (Jenkins World?) to
> follow the same code.
I've incorporated this feedback, thanks
> On 05/12/15 02:08, R. Tyler Croy wrote:
> >
> > As the Jenkins community has grown, it has become clear that we need to write
> > down what behaviors we welcome in our community, but more importantly, what is
> > not welcome.
> >
> > I would like to invite you all to review and provide feedback on the following
> > wiki page: <https://wiki.jenkins-ci.org/display/JENKINS/Code+of+Conduct>
> >
> >
> > I take responsibility for the board dragging their feet on this topic and wish
> > to remedy that as soon as possible. I cannot stress the importance of this
> > topic enough and while I hope that we do not find ourselves in a position which
> > needs addressing, I believe it is critical to the long-term health of the
> > Jenkins community that this be defined.
> >
> >
> > If you have questions or concerns that you do not wish to advertise publicly,
> > please email me off-list.
> >
> >
> >
> > Cheers
> > - R. Tyler Croy
> >
> > ------------------------------------------------------
> > Code: <https://github.com/rtyler>
> > Chatter: <https://twitter.com/agentdero>
> >
> > % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
> > ------------------------------------------------------
> >
>
> --
> 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.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/568C5A3D.9070400%40orr.me.uk.
> 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.
Reply all
Reply to author
Forward
0 new messages