Proposal: Open Governance - Tracking key action items/requests in GitHub Issues

[Oleg Nenashev]

Hi all,

I would like to follow-up on a Jenkins governance help offer from Rick in this thread.

Currently we do the most of the planning and discussions via mailing lists and governance meetings. For common community members, it might be difficult to see what are the initiatives/projects being handled by the board at the moment. It is also hard for potential contributors to see the governance backlog and to contribute to the open items in our TODO list.

What if we create a new public github repo like jenkinsci/governance and put key issues/projects there, e.g. (Adoption of EasyCLA, CDF Project representatives Elections, Contributor summit, etc.). It should not be a replacement for the mailing lists OR a micromanagement tool, but we can use it to provide a way to highlight key problems we are about working on. The new repo can be also used as a public RFE tracker and maybe even a Q&A forum for the governance matters though, again, it should not replace the mailing discussions.

Such approach would partially overlap with the Jenkins public roadmap, but only for big initiatives which need to be represented there.

What do you think?

Best regards,

Oleg Nenashev

[Matt Sicker]

I think it's a good idea. I'm a huge fan of asynchronous
communications like that which make it easier for part time
contributors to keep up to date. (Of course, I'm biased since that's
what we do at Apache)

> --
> 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/92e0af37-e7eb-49c8-8c10-599daf071928n%40googlegroups.com.

[Mark Waite]

I like the idea.  +1 from me 

[Oleg Nenashev]

I have got +1s from Ulli and Ewelina in the original discussion in the board mailing list. Thanks to everyone for feedback!

I will go ahead and setup the repository.

Later we could also try out using it for governance meeting notes with HackMD

BR, Oleg

[Baptiste Mathus]

I think that's a great idea. +1

Typically I suppose we'll create an issue for the LTS baseline selection, etc. We'll also then get for free linking between PRs and issues (like the release lead checklist, the backporting PR etc.)

I'm slightly concerned it may reduce our discussions here but there's no silver bullet. 

-- Baptiste

[Oleg Nenashev]

I will leave the decision w.r.t LTS processes to Tim Jacomb and the Jenkins release team. IMHO this is the matter of the Jenkins core maintenance, not of the community governance.

If we want to move discussions to GitHub (not sure about that), we could enable GitHub discussions or even GitHub issues/projects in the Jenkins core repo. No need to keep it in a separate repository.

BR, Oleg

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/j6Tjb8wiLKE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS684sxzEPanEcE%2Bb_W84L3wzNZQAgbzu6fuCaKcPdWBBw%40mail.gmail.com.

[Sudarshan Thanekar]

Hi All,

I am new on Jenkins, I have below issue with Jenkins pipeline. 

I have committed code in development branch still master branch Jenkins pipeline is triggered.

I have set -   branch-specifier  -  origin/master

Regards,

Sudarshan Thanekar

 

[Daniel Beck]

On Mon, May 17, 2021 at 11:59 PM Oleg Nenashev <o.v.ne...@gmail.com> wrote:

What if we create a new public github repo like jenkinsci/governance and put key issues/projects there, e.g. (Adoption of EasyCLA, CDF Project representatives Elections, Contributor summit, etc.). It should not be a replacement for the mailing lists OR a micromanagement tool, but we can use it to provide a way to highlight key problems we are about working on. The new repo can be also used as a public RFE tracker and maybe even a Q&A forum for the governance matters though, again, it should not replace the mailing discussions.

This nicely illustrates that GitHub's repo-based model can weird, as these aren't repo-related issues; there may not even be a repo (beyond a README). Would be better off as a new project in Jira.

[Tim Jacomb]

Creating a Jira project is a much higher barrier to entry, subscribing to project / issues is not something someone that is a little interested is going to do.

In GitHub it’s 2 clicks

+1 for the governance repo at least as a trial

--
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/CAMo7PtJPdGuiqS_X6u4s_Y4JU-umDU51XoXEKMi3%3DT-ZPAjNyw%40mail.gmail.com.

[Oleg Nenashev]

Thanks to everyone for the feedback! I added the topic to the today's Jenkins Governance Meeting update so that we could formally agree whether we start a trial.

FTR https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#heading=h.1gtco63t6ztr 

@Sudarshan Please use https://gitter.im/jenkinsci/newcomer-contributors or start a new thread for your question.

[Daniel Beck]

On Tue, May 18, 2021 at 2:08 PM Tim Jacomb <timja...@gmail.com> wrote:

Creating a Jira project is a much higher barrier to entry,

Projects are created by admins, once.

 

subscribing to project / issues is not something someone that is a little interested is going to do.

In GitHub it’s 2 clicks

One click per issue ("Watch"). Granted, watching everything is more work, but someone who is a little interested is probably not going for dozens of issues with notifications all the time.

OTOH the tools to keep track of issues are a lot better, we can have custom fields and dashboards, etc.