It just imho. I see better activity for user related issues from plugin maintainers that are not in CB yet. From CB i see only commit fixes without jenkins issue ids that mostly look like issues come from CB customers. Of course CB developers will have priority on their internal issues.
For infra DanielBeck has no power and knowledge yet or why current work stoppage was not fixed? Last months Oleg, Daniel and me spent trying to get any info about infra, accesses. Hopefully they got access and now instead of helping them you propose a Lead that never worked with this infra before. What is the difference then? INFRA must be fixed and update without any leads, just fix and resolve issues! Board people are board people :) The best community person is Jessy, he answers on all questions. On Monday, February 16, 2015 at 6:55:00 PM UTC+3, Stephen Connolly wrote: > > On 16 February 2015 at 15:43, Kanstantsin Shautsou <[email protected] > <javascript:>> wrote: > >> imho Assuming that now only CloudBees persons has power under jenkins, >> it's main development and everything is locked on CB people, then we have >> no way. >> > > Oh my oh my, I am disappointed that you feel that way. > > On the infra side KK has DB and ON neither of whom currently work for > CloudBees. > > On the board side, only KK works for CloudBees. > > We try to ensure that we are just one voice in the community and it would > sadden us greatly if the community felt that we were in charge. > > I would love to hear what has you forming that view point? > > - FYI some of the work I do for the community is outside of > M-F/9:00am-5:30pm which means that it is my own personal contributions and > not related to CloudBees, Inc. > > >> For lead i know 0 contributions from Adam in jenkins development or >> infra. As first step i will be glad to see him as just man who will resolve >> real issues with rtyler/kohsuke approval and decide to be a lead later. >> >> >> On Monday, February 16, 2015 at 5:56:34 PM UTC+3, Kohsuke Kawaguchi wrote: >>> >>> My apologies for a delay in handling INFRA-240 >>> <https://issues.jenkins-ci.org/browse/INFRA-240>. As the ticket >>> indicates now, I've resolved the problem. The issue was that ldap >>> daemon wasn't restarted when I installed a new certificate last week. So it >>> continued running with the old certificate, and when it expired, >>> Artifactory started refusing to talk to it. >>> >>> Local apps on cucumber weren't affected because it was using unsecured >>> communication. I need to figure out why JIRA and Confluence were unaffected >>> by this. Perhaps they have the password locally cached, perhaps they have >>> LDAP connections pooled and long-running, or perhaps they don't properly >>> check the certificate. >>> >>> >>> The next thing I want to talk about is that I think this is a symptom of >>> a deeper issue, which is that the infra ops coverage has fallen way behind. >>> Tyler isn't spending time on this project as he used to be, and the time I >>> spend on Jenkins infra is not as much as it needs to be, too. >>> >>> In the last 6 months or so, we've handed out infra acecss right to a few >>> more people (Daniel Beck and Oleg Nanoshev, IIRC), and that was good for >>> better time zone coverage and what not. But the problem still remains that >>> there is a leadership vacuum, that no one sufficiently "owns" the infra, >>> and that's difficult to solve by adding more hands alone. >>> >>> So here's what I'd like to propose: >>> >>> - Formalize our ops team more by designating the lead that reports >>> to the board. The lead shall be chosen in the discussion during the >>> project >>> meeting. >>> - Under the new lead, accept another round of ops team members to >>> help spread the workload. I know for example Kostasya is interested in >>> helping. >>> - Kohsuke (and Tyler if he can join) and the ops team will schedule >>> a series of "transfer of information" sessions to bring the new ops lead >>> and the team up to speed about how things are put together today. >>> - Identify and remove single-point-of-failure in our infra. Off the >>> top of my head: >>> - I think I'm currently the only one who has the private key to >>> sign update center root CA. >>> - jenkins-ci.org domain name still appears to be registered under >>> Tyler's personal account. >>> >>> >>> As the ops lead, I'd like the project to consider Adam Papai >>> <https://github.com/woohgit>. He's been a long time user of Jenkins and >>> he is a member of the CloudBees ops team. I'm sensitive to the fact that he >>> works for CloudBees and how that can come across, but OTOH this will be a >>> part of his day job, and I think that ensures that he can allocate >>> necessary time to the effort. >>> >>> What do people think? >>> >> -- >> 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 [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/f8b3b3ff-1d0e-48db-b214-acee31e3bf41%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-dev/f8b3b3ff-1d0e-48db-b214-acee31e3bf41%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/a5c6de55-645a-4829-9c06-ea3244948db2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
