Heads-up: Jenkins 2.221 weekly release delay

[Oleg Nenashev]

Hi all,

Just a quick update w.r.t. the weekly release status. The automatic release
on the weekend did not go through on KK's release environment. Kohsuke
suspects a power outage, and it is hard to fix it remotely. ETA for the fix
- late Wed or Thursday in the US timezone.

We can use the delay as an opportunity to merge a few extra pull requests.
Keep in mind that the LTS baseline selection is coming soon (Feb 26), and
we are interested to have a stable weekly release by then.

Best regards,
Oleg

-- 
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/CAPfivLCJ7%2BmxA%3DqFCJzv%2B4BBwsVDhevaHhpHK%3Da%3DzKOfKMcGgQ%40mail.gmail.com.

Re: About - Simple Pull Request Plugin

[Aytunc Beken]

Hi Oleg, 

Nice to meet you Vu Tuan. 

I have some doubts, may be you can help me understand things.

- Why the name of the plugin is different ? Also It says it is about pull 
requests from various version controls. If this plugin will continue 
focusing on both, It will be good to separate them.
- I was planing to use ModelASTPipelineDef 
(org.jenkinsci.plugins.pipeline.modeldefinition.ast) for converting Yaml to 
Jenkins and vice versa. As this is internal model of Declarative pipeline, 
It will be easy to maintain.

I will be glad if I can get your ideas/comment about these.

Thanks. Regards

-- 
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/0bbcc3ac-9f88-45be-afb1-21c82f52b38c%40googlegroups.com.

Re: Core Infrastructure Initiative (CII) compliance for the Jenkins core - status thread

[Tracy Miranda]

Hi Oleg,

Thanks for putting this together and establishing that baseline score!

IMHO it is a great exercise to run through as proven by the issues you
raised in the email. (Also nice to see the badge linked when I click on
Jenkins on the CDF  and CNCF
landscapes).
I look forward to the follow on threads, plus also plan to take a more
detailed look at the report.

Thanks,
Tracy

On Tue, Feb 18, 2020 at 6:50 AM Oleg Nenashev 
wrote:

> Hi all,
>
> This is a follow-up to the Community Bridge funding thread
>  and
> to contributor summit discussions about CII. As discussed there, Linux
> Foundation expects all projects on Community Bridge to be also a part of
> the Core Infrastructure Initiative  which
> is their program for strengthening security in open-source projects. In
> particular, there is a badge program here
> . All Community Bridge
> projects are expected to eventually pass certification there.
>
> I believe that being compliant with CII is a net positive thing for us,
> because it can help to promote the project and to address some
> quality-related and certification queries from current and potential
> Jenkins users (e.g. see this recent thread
> ). It
> also unlocks access to  targeted security project funding / engineering
> time donations by CII corporate members (Assistance program
> ) and to
> tooling like Snyk.
>
> I started working on a CII checklist for the Jenkins core, plugins are out
> of the scope for me at the moment. You can find the current status on this
> page . We
> are currently at the *80%* completion state, and there are some open
> topics which need to be clarified. I have summarized the topics below after
> the email, and I will start follow-up threads for them so that they can be
> discussed separately.
>
> CII is definitely a case when the remaining 20% for the work require 80%
> of effort, but I hope to gradually get to the full certification checklist
> for the Jenkins core. Even if we do not pass the certification criteria
> there, it is nice to have a documented status for quality/security
> expectations. I will appreciate any feedback about the CII compliance in
> general and about the self-certification page
> .
> Unfortunately documentation-as-code is not supported there, but I am happy
> to incorporate any suggested changes.
>
> Best regards,
> Oleg
>
>  Open topics:
>
> *Problem 1. Incoming issues triage *(section status
> ).
> We do not longer have an active triage team which would be regularly
> reviewing incoming issues in Jira. Alex Earl made a proposal to have an
> official triage team in 2017 (dev list thread
> ),
> but it was not implemented at the moment. I was doing regular issue triage
> until Dec 2018 before I stepped down (see the same thread). Right now we
> regularly look at the Jenkins release community ratings and reported
> regressions, but I would not say we have a real triage process, especially
> for RFEs and bugs reported to non-core components
>
>- CII Criteria:
>- " The project MUST acknowledge a majority of bug reports submitted
>   in the last 2-12 months (inclusive); the response need not include a 
> fix."
>   - " The project SHOULD respond to a majority (>50%) of enhancement
>   requests in the last 2-12 months (inclusive).  "
>   - My assumption is that we are below these criteria
>- *Potential solution*: Maybe we should revise this topic. Since we
>have more active core maintainers now, maybe we could have a rotation for
>the incoming issues in Jenkins Jira. To be discussed in a separate thread
>
> *Problem 2. Quality and Code analysis warnings* (section status
> ).
> The project MUST enable one or more compiler warning flags, a "safe"
> language mode, or use a separate "linter" tool to look for code quality
> errors or common simple mistakes, if there is at least one FLOSS tool that
> can implement this criterion in the selected language. Jenkins core
> addresses it, because we have a bunch of tools enabled like Spotbugs,
> Animal Sniffer or Maven Enforcer. But there are some downstream criteria
>
>- Problematic CII criteria:
>- The project should fix warnings or mark them in the source code as
>   false positives. Ideally there would be no warnings, but a 

Re: Proposal: Moving the plugin adoption labels from Wiki to GitHub topics

[Oleg Nenashev]

https://github.com/jenkins-infra/plugin-site/pull/130 for the plugin site 
update

On Tuesday, February 18, 2020 at 10:05:40 AM UTC+1, Oleg Nenashev wrote:
>
> Yes, plugin site is something I will be doing (see the comments above).
> The problem is rather with GitHub repositories and direct access to them. 
> In this case a badge could improve visibility of the adoption status.
> We could serve a badge from the plugin site for that, but IMHO it is a 
> separate topic.
>
> BR, Oleg
>
>
> On Tue, Feb 18, 2020 at 10:02 AM Tim Jacomb  wrote:
>
>> The badge could be automatically added on the plugin site if one of the 
>> adopt topics is added to the GitHub repo?
>>
>> On Tue, 18 Feb 2020 at 08:01, Ivan Fernandez Calvo <
>> kuisathave...@gmail.com> wrote:
>>
>>> Sure, the badge is something additional,
>>>  something that users can see when they go to the documentation, then 
>>> they can decide 
>>> if they want to use a plugin in adoption.
>>>
>>> -- 
>>> 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/7e802140-b00c-4ccc-adcf-c84be95ab610%40googlegroups.com
>>> .
>>>
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "Jenkins Developers" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/jenkinsci-dev/UoEqG5AaWJU/unsubscribe.
>> To unsubscribe from this group and all its topics, 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/CAH-3BicYmYzqjqo7TbOogb5LhuNBNtgmWcgd2Ld8C65aJduzbQ%40mail.gmail.com
>>  
>> 
>> .
>>
>

-- 
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/4b79681a-3dc1-4af5-a4f3-d816e5b07ba3%40googlegroups.com.

Core Infrastructure Initiative (CII) compliance for the Jenkins core - status thread

[Oleg Nenashev]

Hi all,

This is a follow-up to the Community Bridge funding thread
 and
to contributor summit discussions about CII. As discussed there, Linux
Foundation expects all projects on Community Bridge to be also a part of
the Core Infrastructure Initiative  which
is their program for strengthening security in open-source projects. In
particular, there is a badge program here
. All Community Bridge
projects are expected to eventually pass certification there.

I believe that being compliant with CII is a net positive thing for us,
because it can help to promote the project and to address some
quality-related and certification queries from current and potential
Jenkins users (e.g. see this recent thread
). It
also unlocks access to  targeted security project funding / engineering
time donations by CII corporate members (Assistance program
) and to
tooling like Snyk.

I started working on a CII checklist for the Jenkins core, plugins are out
of the scope for me at the moment. You can find the current status on this
page . We
are currently at the *80%* completion state, and there are some open topics
which need to be clarified. I have summarized the topics below after the
email, and I will start follow-up threads for them so that they can be
discussed separately.

CII is definitely a case when the remaining 20% for the work require 80% of
effort, but I hope to gradually get to the full certification checklist for
the Jenkins core. Even if we do not pass the certification criteria there,
it is nice to have a documented status for quality/security expectations. I
will appreciate any feedback about the CII compliance in general and about
the self-certification page
.
Unfortunately documentation-as-code is not supported there, but I am happy
to incorporate any suggested changes.

Best regards,
Oleg

 Open topics:

*Problem 1. Incoming issues triage *(section status
).
We do not longer have an active triage team which would be regularly
reviewing incoming issues in Jira. Alex Earl made a proposal to have an
official triage team in 2017 (dev list thread
),
but it was not implemented at the moment. I was doing regular issue triage
until Dec 2018 before I stepped down (see the same thread). Right now we
regularly look at the Jenkins release community ratings and reported
regressions, but I would not say we have a real triage process, especially
for RFEs and bugs reported to non-core components

   - CII Criteria:
   - " The project MUST acknowledge a majority of bug reports submitted in
  the last 2-12 months (inclusive); the response need not include a fix."
  - " The project SHOULD respond to a majority (>50%) of enhancement
  requests in the last 2-12 months (inclusive).  "
  - My assumption is that we are below these criteria
   - *Potential solution*: Maybe we should revise this topic. Since we have
   more active core maintainers now, maybe we could have a rotation for the
   incoming issues in Jenkins Jira. To be discussed in a separate thread

*Problem 2. Quality and Code analysis warnings* (section status
).
The project MUST enable one or more compiler warning flags, a "safe"
language mode, or use a separate "linter" tool to look for code quality
errors or common simple mistakes, if there is at least one FLOSS tool that
can implement this criterion in the selected language. Jenkins core
addresses it, because we have a bunch of tools enabled like Spotbugs,
Animal Sniffer or Maven Enforcer. But there are some downstream criteria

   - Problematic CII criteria:
   - The project should fix warnings or mark them in the source code as
  false positives. Ideally there would be no warnings, but a project MAY
  accept some warnings (typically less than 1 warning per 100 lines or less
  than 10 warnings).
  - It is SUGGESTED that projects be maximally strict with warnings in
  the software produced by the project, where practical.
   - *Problem*: We ignore some warnings without explicitly supressing them
   (Javadoc and other minor things). And we definitely do not set maximally
   strict requirements, our SpotBugs runs on the High threshold by default.
   Stefan Spieker is doing a great job with the issues cleanup, for "Medium",
   but there are still a lot of issues left
   - *Potential solution:* Fail the Suggested 

Re: About - Simple Pull Request Plugin

[Oleg Nenashev]

Since you follow the existing plugin design, IMHO it would be better to
just keep extending it. It is in alpha now, so there is no compatibility
requirements.

CC Vu Tuan who is the current maintainer

BR, Oleg

On Mon, Feb 17, 2020, 20:04 Aytunc Beken  wrote:

> Hi Oleg,
>
> Sorry for my late response. I think the requirements you defined will make
> plugin more usable. So I will try to also implement those requirements.
> So I am planing to start working on this plugin. How should I proceed ?
>
> Thanks.
>
> On Thursday, February 13, 2020 at 8:35:51 PM UTC+1, Oleg Nenashev wrote:
>>
>> Hi Aytunc,
>>
>> Your approach is quite similar to what is documented in my project idea.
>> I went a bit beyond w.r.t implementation options, but the approach you
>> suggest is one of the most straightforward ways to implement Pipeline as
>> YAML.
>>
>>  - Develop a Converter which will convert yml files to legacy declarative
>>> or scripted pipelines .
>>>
>> There is no legacy declarative or scripted pipelines :) . They keep
>> evolving, and I do not think that YAML support is going to replace them
>> anytime soon.
>> https://github.com/jenkinsci/simple-pull-request-job-plugin is an
>> example of such converter.
>> The converter approach makes total sense as a standalone solution,
>>
>> Develop a converter screen where uses can convert their declarative
>>> pipelines to yaml or vice versa.
>>>
>> Would be great
>>
>>
>>
>> On Wednesday, February 12, 2020 at 1:50:25 PM UTC+1, Aytunc Beken wrote:
>>>
>>> Hi Oleg,
>>>
>>> Thanks for the details. The projects which are proposed/developed are
>>> similar what I want to achieve. However, approach may differ.
>>>
>>> What I planned was this:
>>>  - Develop a Converter which will convert yml files to legacy
>>> declarative or scripted pipelines .
>>>Reason: Just wanted not to interfere with the core pipeline
>>> mechanism. A smart, well developed converter will be enough to make it work.
>>>  - Develop a converter screen where uses can convert their declarative
>>> pipelines to yaml or vice versa.
>>>Reason: Users should not spend time to convert their legacy
>>> pipelines. UI converter will same lots of time.
>>>
>>> How these sounds for you ? Not sure how much it is parallel within your
>>> mind.
>>>
>>> Thanks.
>>>
>>>
>>> On Wednesday, February 12, 2020 at 1:26:47 PM UTC+1, Oleg Nenashev wrote:

 UPD. I have officially submitted this project idea:
 https://groups.google.com/forum/#!topic/jenkins-pipeline-authoring-sig/Ko8KTEcK_vY
 and jenkins-infra/jenkins.io#2849
 

 Hi Aytunc, what would be your plan there? the GSoC project idea does
 not block anyone from working on this area, but it might make sense to
 sync-up with other interested contributors.

 Best regards,
 Oleg

 On Monday, February 10, 2020 at 5:14:51 PM UTC+1, Oleg Nenashev wrote:
>
> Hi,
>
> No ongoing work right now, but indeed there is a lot of interest in
> the community.
> If you are interested to work on it, this is great!
>
> Actually I am planning to submit a follow-up project idea for Google
> Summer of Code 2020. I have already referenced it in
> https://gitter.im/jenkinsci/pipeline-authoring-sig , but I have not
> announced it yet through official channels.
> The draft idea is here:
> https://github.com/jenkins-infra/jenkins.io/blob/ff5527bb98f1b28159f88894c9abbe346eeaf3d2/content/projects/gsoc/2020/project-ideas/pipeline-as-yaml-experiment.adoc
> If you plan to work on this area in short-term, I will adjust my
> project idea accordingly.
>
> Best regards,
> Oleg
>
>
> On Monday, February 10, 2020 at 11:05:01 AM UTC+1, Aytunc Beken wrote:
>>
>> Hi,
>>
>> I was planning to work on a new plugin for enabling Yaml files for
>> Pipelines. However I found this plugin and it looks similar.
>>
>> https://jenkins.io/blog/2018/07/17/simple-pull-request-plugin/
>>
>> Does any one knows about it? Does is still continues ?
>>
>> Thanks. Regards
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/6ieyOlLQX0I/unsubscribe.
> To unsubscribe from this group and all its topics, 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/93176789-754f-4526-8226-b0e3c081bf12%40googlegroups.com
> 
> .
>

-- 
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 

Re: Proposal: Jenkins Core PR reviewers team

[Baptiste Mathus]

+1 to add Marky too.

On Tue, Feb 18, 2020 at 9:59 AM Tim Jacomb  wrote:

> +1 from my side
>
> On Tue, 18 Feb 2020 at 08:10, Francisco Javier Fernandez <
> fjfernan...@cloudbees.com> wrote:
>
>> Oleg, Marky, +1 from my side. Any help is always more than welcome!
>>
>> El domingo, 16 de febrero de 2020, 19:59:06 (UTC+1), Marky Jackson
>> escribió:
>>>
>>> Thank you kindly Oleg, please do get well. Sending healing thoughts.
>>>
>>> On Feb 16, 2020, at 10:30 AM, Oleg Nenashev  wrote:
>>>
>>> Hi Marky. As we discussed in PM, I have an action item to follow-up on
>>> that. Sorry that I cannot provide the response time you expect, but I was
>>> mostly off over past days (sick leave). I will do my best to propose formal
>>> criteria for newcomer core PR reviewers next week. The informal criteria
>>> before was several months of activities in the core and a number of
>>> substantial contributions.
>>>
>>> If others vote in favor of adding Marky to the Core PR Reviewers, I am
>>> +1 w.r.t that.
>>>
>>> BR, Oleg
>>>
>>>
>>>
>>> On Sun, Feb 16, 2020, 19:10 Marky Jackson  wrote:
>>>
 I wanted to circle back around on this

 On Thursday, February 13, 2020 at 4:48:44 PM UTC-8, Marky Jackson wrote:
>
> I am happy to be included and thank you Gavin
>
> On Feb 13, 2020, at 4:46 PM, 'Gavin Mogan' via Jenkins Developers <
> jenkin...@googlegroups.com> wrote:
>
> Sorry ya'll, with the new approved core developers, I'm going to step
> down as a core-pr-reviewer. Its a little overwhelming to me, and I'm not
> comfortable with core/java, but i'm still up for helping out randomly 
> where
> i can, especially for plugins, and web/javascript stuff. I'll lurk 
> randomly
> elsewhere.
>
> (this leaves room for Marky though)
>
> On Sun, Feb 2, 2020 at 1:04 AM Marky Jackson 
> wrote:
>
>> I love a good challenge.
>> Let’s hold off on this request and I will get some general reviews
>> under my belt for some time and reapply at a later date.
>> Thanks kindly for the consideration.
>>
>> On Feb 1, 2020, at 11:53 PM, Daniel Beck  wrote:
>>
>>
>> Extrapolating from the introduction of this team would mean people
>> should first be regular core PR reviewers. There's no process barrier to
>> just start doing that.
>>
>> Right now,
>> https://github.com/jenkinsci/jenkins/pulls?utf8=%E2%9C%93=is%3Apr+involves%3Amarkyjackson-taulia
>> looks a little empty.
>>
>> --
>> 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 jenkin...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtLNMKCiby_hamQ%2BpUBZyVZBzyTphw8LiTE1Y1xsbz9EOw%40mail.gmail.com
>> 
>> .
>>
>>
>> --
>> 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 jenkin...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/6001CF17-C6EB-4F86-ABF0-3754580C0BE3%40gmail.com
>> 
>> .
>>
>
> --
> 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 jenkin...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DusuUMUQuMqXYwbQ6vf%2BqaXgNzT9cg_5M9QYJzh7c%3DVbWg%40mail.gmail.com
> 
> .
>
>
> --
 You received this message because you are subscribed to a topic in the
 Google Groups "Jenkins Developers" group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/jenkinsci-dev/0sdrcSOQW64/unsubscribe
 .
 To unsubscribe from this group and all its topics, send an email to
 jenkin...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-dev/46d147a4-3f81-4eea-93ad-3a355329eb28%40googlegroups.com
 
 .

>>> --
>>> You received this 

Re: Proposal: Moving the plugin adoption labels from Wiki to GitHub topics

[Oleg Nenashev]

Yes, plugin site is something I will be doing (see the comments above).
The problem is rather with GitHub repositories and direct access to them.
In this case a badge could improve visibility of the adoption status.
We could serve a badge from the plugin site for that, but IMHO it is a
separate topic.

BR, Oleg


On Tue, Feb 18, 2020 at 10:02 AM Tim Jacomb  wrote:

> The badge could be automatically added on the plugin site if one of the
> adopt topics is added to the GitHub repo?
>
> On Tue, 18 Feb 2020 at 08:01, Ivan Fernandez Calvo <
> kuisathave...@gmail.com> wrote:
>
>> Sure, the badge is something additional,
>>  something that users can see when they go to the documentation, then
>> they can decide
>> if they want to use a plugin in adoption.
>>
>> --
>> 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/7e802140-b00c-4ccc-adcf-c84be95ab610%40googlegroups.com
>> .
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/UoEqG5AaWJU/unsubscribe.
> To unsubscribe from this group and all its topics, 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/CAH-3BicYmYzqjqo7TbOogb5LhuNBNtgmWcgd2Ld8C65aJduzbQ%40mail.gmail.com
> 
> .
>

-- 
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/CAPfivLB9CQ0A707E-jiJV5_jtC5L6pbG9MMYTp%2BDYoqCkuu0sA%40mail.gmail.com.

Re: Proposal: Moving the plugin adoption labels from Wiki to GitHub topics

[Tim Jacomb]

The badge could be automatically added on the plugin site if one of the
adopt topics is added to the GitHub repo?

On Tue, 18 Feb 2020 at 08:01, Ivan Fernandez Calvo 
wrote:

> Sure, the badge is something additional,
>  something that users can see when they go to the documentation, then they
> can decide
> if they want to use a plugin in adoption.
>
> --
> 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/7e802140-b00c-4ccc-adcf-c84be95ab610%40googlegroups.com
> .
>

-- 
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/CAH-3BicYmYzqjqo7TbOogb5LhuNBNtgmWcgd2Ld8C65aJduzbQ%40mail.gmail.com.

Re: Proposal: Jenkins Core PR reviewers team

[Tim Jacomb]

+1 from my side

On Tue, 18 Feb 2020 at 08:10, Francisco Javier Fernandez <
fjfernan...@cloudbees.com> wrote:

> Oleg, Marky, +1 from my side. Any help is always more than welcome!
>
> El domingo, 16 de febrero de 2020, 19:59:06 (UTC+1), Marky Jackson
> escribió:
>>
>> Thank you kindly Oleg, please do get well. Sending healing thoughts.
>>
>> On Feb 16, 2020, at 10:30 AM, Oleg Nenashev  wrote:
>>
>> Hi Marky. As we discussed in PM, I have an action item to follow-up on
>> that. Sorry that I cannot provide the response time you expect, but I was
>> mostly off over past days (sick leave). I will do my best to propose formal
>> criteria for newcomer core PR reviewers next week. The informal criteria
>> before was several months of activities in the core and a number of
>> substantial contributions.
>>
>> If others vote in favor of adding Marky to the Core PR Reviewers, I am +1
>> w.r.t that.
>>
>> BR, Oleg
>>
>>
>>
>> On Sun, Feb 16, 2020, 19:10 Marky Jackson  wrote:
>>
>>> I wanted to circle back around on this
>>>
>>> On Thursday, February 13, 2020 at 4:48:44 PM UTC-8, Marky Jackson wrote:

 I am happy to be included and thank you Gavin

 On Feb 13, 2020, at 4:46 PM, 'Gavin Mogan' via Jenkins Developers <
 jenkin...@googlegroups.com> wrote:

 Sorry ya'll, with the new approved core developers, I'm going to step
 down as a core-pr-reviewer. Its a little overwhelming to me, and I'm not
 comfortable with core/java, but i'm still up for helping out randomly where
 i can, especially for plugins, and web/javascript stuff. I'll lurk randomly
 elsewhere.

 (this leaves room for Marky though)

 On Sun, Feb 2, 2020 at 1:04 AM Marky Jackson 
 wrote:

> I love a good challenge.
> Let’s hold off on this request and I will get some general reviews
> under my belt for some time and reapply at a later date.
> Thanks kindly for the consideration.
>
> On Feb 1, 2020, at 11:53 PM, Daniel Beck  wrote:
>
>
> Extrapolating from the introduction of this team would mean people
> should first be regular core PR reviewers. There's no process barrier to
> just start doing that.
>
> Right now,
> https://github.com/jenkinsci/jenkins/pulls?utf8=%E2%9C%93=is%3Apr+involves%3Amarkyjackson-taulia
> looks a little empty.
>
> --
> 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 jenkin...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtLNMKCiby_hamQ%2BpUBZyVZBzyTphw8LiTE1Y1xsbz9EOw%40mail.gmail.com
> 
> .
>
>
> --
> 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 jenkin...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/6001CF17-C6EB-4F86-ABF0-3754580C0BE3%40gmail.com
> 
> .
>

 --
 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 jenkin...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DusuUMUQuMqXYwbQ6vf%2BqaXgNzT9cg_5M9QYJzh7c%3DVbWg%40mail.gmail.com
 
 .


 --
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "Jenkins Developers" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/jenkinsci-dev/0sdrcSOQW64/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> jenkin...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/46d147a4-3f81-4eea-93ad-3a355329eb28%40googlegroups.com
>>> 
>>> .
>>>
>> --
>> 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 jenkin...@googlegroups.com.
>> To view 

Re: Proposal: Jenkins Core PR reviewers team

[Francisco Javier Fernandez]

Oleg, Marky, +1 from my side. Any help is always more than welcome!

El domingo, 16 de febrero de 2020, 19:59:06 (UTC+1), Marky Jackson escribió:
>
> Thank you kindly Oleg, please do get well. Sending healing thoughts.
>
> On Feb 16, 2020, at 10:30 AM, Oleg Nenashev  > wrote:
>
> 
> Hi Marky. As we discussed in PM, I have an action item to follow-up on 
> that. Sorry that I cannot provide the response time you expect, but I was 
> mostly off over past days (sick leave). I will do my best to propose formal 
> criteria for newcomer core PR reviewers next week. The informal criteria 
> before was several months of activities in the core and a number of 
> substantial contributions.
>
> If others vote in favor of adding Marky to the Core PR Reviewers, I am +1 
> w.r.t that.
>
> BR, Oleg
>
>
>
> On Sun, Feb 16, 2020, 19:10 Marky Jackson  > wrote:
>
>> I wanted to circle back around on this
>>
>> On Thursday, February 13, 2020 at 4:48:44 PM UTC-8, Marky Jackson wrote:
>>>
>>> I am happy to be included and thank you Gavin
>>>
>>> On Feb 13, 2020, at 4:46 PM, 'Gavin Mogan' via Jenkins Developers <
>>> jenkin...@googlegroups.com > wrote:
>>>
>>> Sorry ya'll, with the new approved core developers, I'm going to step 
>>> down as a core-pr-reviewer. Its a little overwhelming to me, and I'm not 
>>> comfortable with core/java, but i'm still up for helping out randomly where 
>>> i can, especially for plugins, and web/javascript stuff. I'll lurk randomly 
>>> elsewhere.
>>>
>>> (this leaves room for Marky though)
>>>
>>> On Sun, Feb 2, 2020 at 1:04 AM Marky Jackson >> > wrote:
>>>
 I love a good challenge.
 Let’s hold off on this request and I will get some general reviews 
 under my belt for some time and reapply at a later date.
 Thanks kindly for the consideration.

 On Feb 1, 2020, at 11:53 PM, Daniel Beck >>> > wrote:


 
 Extrapolating from the introduction of this team would mean people 
 should first be regular core PR reviewers. There's no process barrier to 
 just start doing that.

 Right now, 
 https://github.com/jenkinsci/jenkins/pulls?utf8=%E2%9C%93=is%3Apr+involves%3Amarkyjackson-taulia
  
 looks a little empty.

 -- 
 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 jenkin...@googlegroups.com .
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtLNMKCiby_hamQ%2BpUBZyVZBzyTphw8LiTE1Y1xsbz9EOw%40mail.gmail.com
  
 
 .


 -- 
 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 jenkin...@googlegroups.com .
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-dev/6001CF17-C6EB-4F86-ABF0-3754580C0BE3%40gmail.com
  
 
 .

>>>
>>> -- 
>>> 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 jenkin...@googlegroups.com .
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DusuUMUQuMqXYwbQ6vf%2BqaXgNzT9cg_5M9QYJzh7c%3DVbWg%40mail.gmail.com
>>>  
>>> 
>>> .
>>>
>>>
>>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "Jenkins Developers" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/jenkinsci-dev/0sdrcSOQW64/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> jenkin...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/46d147a4-3f81-4eea-93ad-3a355329eb28%40googlegroups.com
>>  
>> 
>> .
>>
> -- 
> 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 jenkin...@googlegroups.com .
> To view this discussion on the web visit 
> 

Re: Proposal: Moving the plugin adoption labels from Wiki to GitHub topics

[Ivan Fernandez Calvo]

Sure, the badge is something additional,
 something that users can see when they go to the documentation, then they can 
decide 
if they want to use a plugin in adoption.

-- 
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/7e802140-b00c-4ccc-adcf-c84be95ab610%40googlegroups.com.