The code of conduct was approved at the Jenkins Governance Meeting on Jul
01:
https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#heading=h.6rx5y09hwmti.
https://github.com/jenkins-infra/jenkins.io/pull/3477 is accepted, with 7
approvals and no negative votes i
Thanks to everyone who reviewed it! Just a reminder, today we will be
voting for approving the pull request as a new Code of Conduct version
On Wed, Jun 24, 2020, 12:27 Oleg Nenashev wrote:
> Hi all,
>
> Pull request with Code of conduct is ready for update:
> https://github.com/jenkins-infra/je
Hi all,
Pull request with Code of conduct is ready for update:
https://github.com/jenkins-infra/jenkins.io/pull/3477
Best regards,
Oleg
On Friday, June 19, 2020 at 2:12:07 PM UTC+2, Oleg Nenashev wrote:
>
> UPD: At the Jun 17 Governance meeting we discussed the Code of Conduct
> update and agr
UPD: At the Jun 17 Governance meeting we discussed the Code of Conduct
update and agreed to go forward with updating to Contributor Covenant 2.0
(6 votes in favor, no against/abstains). We have NOT approved the new code
of Conduct yet.
Next steps:
- Oleg - to propose a pull request to jenki
Update w.r.t the code of conduct update options:
- We got a response from Dan Lorenc (CDF TOC chair) about going with 2.0:*
"I think from the TOC perspective, we're fine with anything above
Contributor Covenant 1.3. We'd prefer projects upgrade over time, but don't
want to be prescr
HiJeff,
I agree that Contributor Covenant 2.0 is generally better, especially for a
large community like Jenkins. This version basically includes statements of the
Community Covenant which covers wider areas. I am fine with exploring this
option more.
I have contacted the Contributor Covenant
3:31 PM, Tracy Miranda wrote:
+1 for proposal (1.4 version)
Tracy
On Fri, Jun 12, 2020 at 5:06 PM Oleg Nenashev <mailto:o.v.nenas...@gmail.com>> wrote:
Dear all,
As a follow-up to the previous Governance meeting, I would like to
propose updating the Jenkins Code of Cond
+1 for proposal (1.4 version)
Tracy
On Fri, Jun 12, 2020 at 5:06 PM Oleg Nenashev
wrote:
> Dear all,
>
> As a follow-up to the previous Governance meeting, I would like to propose
> updating the Jenkins Code of Conduct
> <https://www.jenkins.io/project/conduct> (CoC). Cur
I am a +1 to the proposal and feel this will benefit the community greatly.
> On Jun 12, 2020, at 2:05 PM, Oleg Nenashev wrote:
>
> Dear all,
>
> As a follow-up to the previous Governance meeting, I would like to propose
> updating the Jenkins Code of Conduct <https://w
Dear all,
As a follow-up to the previous Governance meeting, I would like to propose
updating the Jenkins Code of Conduct
<https://www.jenkins.io/project/conduct> (CoC). Currently it is based
on Contributor
Covenant 1.3
<https://www.contributor-covenant.org/version/1/3/0/code-of-conduc
> Looks like we have a volunteer, Oleg! :)
Uhm, not a big deal. I can do it.
среда, 13 января 2016 г., 0:55:24 UTC+3 пользователь Christopher написал:
>
> Yeah, I'm on a couple of other lists where the meeting links get posted
> to the list at the end.
>
> Looks like we have a volunteer, Oleg!
Yeah, I'm on a couple of other lists where the meeting links get posted
to the list at the end.
Looks like we have a volunteer, Oleg! :)
On 12/01/16 14:39, Oleg Nenashev wrote:
> Maybe makes sense to just Governance meeting summaries to the mailing list.
> I mean the automatically generated log
Maybe makes sense to just Governance meeting summaries to the mailing list.
I mean the automatically generated log with decisions and TODOs
пятница, 8 января 2016 г., 20:18:43 UTC+3 пользователь R Tyler Croy написал:
>
>
> In case you don't regularly follow the Jenkins blog or twitter, we now
> h
In case you don't regularly follow the Jenkins blog or twitter, we now have a
code of conduct: https://jenkins-ci.org/conduct
Some more information about it is in the blog post about it:
https://jenkins-ci.org/blog/2016/01/07/official-code-of-conduct/
Cheers
- R. Tyler Croy
-
ack, 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.
> >
t 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>
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
+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-co
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
ike 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 s
ll 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 impo
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
22 matches
Mail list logo
