Thank you!
On Friday, June 19, 2020 at 11:09:28 AM UTC-7, slide wrote:
>
> You should be good to go on permissions to the repo and with release
> permissions. Welcome aboard!
>
> On Fri, Jun 19, 2020 at 11:06 AM Slide >
> wrote:
>
>> +1 from me as the most recent maintainer. One thing to note i
You should be good to go on permissions to the repo and with release
permissions. Welcome aboard!
On Fri, Jun 19, 2020 at 11:06 AM Slide wrote:
> +1 from me as the most recent maintainer. One thing to note is that
> po-cifs relies heavily on the po plugin (it's the basis for multiple po
> plugin
+1 from me as the most recent maintainer. One thing to note is that po-cifs
relies heavily on the po plugin (it's the basis for multiple po plugins),
so you may need to maintain that one as well.
On Fri, Jun 19, 2020 at 11:04 AM Patrick Wilkerson
wrote:
> Hello,
>
> I would like to adopt publish
Hello,
I would like to adopt publish-over-cifs plugin.
I am wanting to submit a fix for JENKINS-18242. I have submitted a pull request
14 days ago and have had no response (also plugin is marked for adoption).
* Link to a plugin you want to adopt:
https://github.com/jenkinsci/publish-over-ci
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
Hi all,
Materials from the meeting:
- Recording: https://youtu.be/3g0GKvVHfgI
- Meeting notes:
https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#heading=h.cgd8zbewht8o
- Summary: At this meeting we discussed the terminology updates and
agreed o
On Fri, Jun 19, 2020 at 12:30 PM Tim Jacomb wrote:
> On Fri, 19 Jun 2020 at 10:36, Daniel Beck wrote:
>
>> Having a screen like
>> https://github.com/jenkinsci/configuration-as-code-plugin/issues/new/choose
>> could help here, but that's far from universal right now. Is this something
>> that co
On Fri, 19 Jun 2020 at 10:36, Daniel Beck wrote:
> Having a screen like
> https://github.com/jenkinsci/configuration-as-code-plugin/issues/new/choose
> could help here, but that's far from universal right now. Is this something
> that could be defined via .github? Having a screen similar to this
> On 18. Jun 2020, at 21:51, Fábio Silva wrote:
>
> Since one of the pull requests has already been accepted, what should I do to
> make it merged? Do I need more privileges?
>
Wait a while first. These PRs are all only a few days old, maintainers
typically review things during their spare
> On 19. Jun 2020, at 11:47, Radosław Antoniuk wrote:
>
>> I would be surprised if we wouldn't regularly get 0-days because people with
>> just a GH account don't bother to do it properly, and just report issues on
>> GH. If that is enabled in repos without someone regularly reviewing incomi
>
> I would be surprised if we wouldn't regularly get 0-days because people
> with just a GH account don't bother to do it properly, and just report
> issues on GH. If that is enabled in repos without someone regularly
> reviewing incoming issues, or by a maintainer who's unaware of how we
> handle
> On 18. Jun 2020, at 22:50, Tim Jacomb wrote:
>
> The security team already uses a different project in Jira to everyone else,
> I don't think we need to change that currently, maintainers will just use
> whatever the security team decides I would think?
>
> Mentioned this earlier:
> > One
To add to Jesse's numbers here's a summary for the JenkinsCI organisation:
Org report: jenkinsci
Total repositories: 2290
Number with GitHub issues enabled: 355 (15%)
Total issues open: 3338
Total issues closed: 17941
Total issues: 21279
https://gist.github.com/timja/a939f198752b218c3270ac043eb08
13 matches
Mail list logo
