Okay, I'll set it up for the 17th. On Wednesday, May 2, 2018 at 12:40:32 AM UTC-7, James Rawlings wrote: > > > On 2 May 2018, at 05:21, Michael Neale <[email protected] <javascript:>> > wrote: > > Lets see what James says about May 8th (should be ok). > > Yeah can we go for every other Thursday starting the 17th May? There’s > conferences and meetings on next week so starting the following would be > best. > > > On those other topics - yes bigger discussion. jenkins-x/jx issues are > currently used as github issues are "dogfooded" - but I believe there is > JIRA support so I think in time they can move to jira under a jenkins-x > component. > > As for repos: there are currently 36 (and growing) in the org - so would > need to namespace them to move them into main org. A lot of them are > infra/biuld pack type things. There is also jenkins-infra which has 64, > which is separate (but I guess it is managed out of band). If it is a > matter of managing access to repos etc - could be solved I am sure. > > On Wednesday, May 2, 2018 at 1:26:58 PM UTC+10, Liam Newman wrote: >> >> Oleg: By "listing Jenkins X under sub-projects" do you also mean moving >> the repositories under jenkinsci org on github and using the Jenkins JIRA? >> I support that, but it something that should probably go on a separate >> thread. >> >> James, Michael, >> Obviously I dropped the ball on April 26th. Shall I schedule the next >> meeting on the May 8th? >> >> On Thursday, April 19, 2018 at 3:30:12 AM UTC-7, Oleg Nenashev wrote: >>> >>> No, it can happen at any moment IMHO. I do not see JEP-400 to be a >>> blocker for referencing this project from jenkins.io. OTOH I am not >>> sure it is within Jenkins organization governance now. E.g. using external >>> org blocks Jenkins GitHub admins from managing permission requests, etc. >>> Are there plans to migrate by the way? JEP-400 does not cover these >>> governance things. >>> >>> BR, Oleg >>> >>> On Thu, Apr 19, 2018 at 12:17 PM, Michael Neale <[email protected]> >>> wrote: >>> >>>> Does that have to happen after the JEP is accepted? >>>> >>>> -- >>>> 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/j_pqY84Pjag/unsubscribe >>>> . >>>> To unsubscribe from this group and all its topics, send an email to >>>> [email protected]. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/jenkinsci-dev/ed611774-7746-48d6-bfa9-1b1ac3592b00%40googlegroups.com >>>> . >>>> 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] <javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/747821e2-6de5-4b9a-bc5f-c08632ae54a6%40googlegroups.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/747821e2-6de5-4b9a-bc5f-c08632ae54a6%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/8b763cd3-112a-4ec7-8e6c-cc580200175d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
