Re: Proposal: Pipeline Authoring SIG

2018-11-09 Thread Oleg Nenashev
GSoC is about coding, so it should be specific kind of documentarion. W.r.t. pure docs, we will have better news soon. Stay tuned for announcements :) Regarding GSoC, we are looking for proposals and mentors for the next year. Any idea will be appreciated. For example, I will submit 2 proposals

Re: Proposal: Pipeline Authoring SIG

2018-11-09 Thread Kristin Whetstone
For at least improving the documentation, we're looking at turning some of that into a GSoC project . That could definitely be expanded to cover more areas here too. Comments and mentors appreciated! On

Re: Proposal: Pipeline Authoring SIG

2018-11-03 Thread 夏润泽
I'm interested  在 2018年10月15日星期一 UTC+8下午5:12:13,Andrew Bayer写道: > > I’d like to propose the creation of a “Pipeline Authoring” SIG, with > myself as the lead. The focus of this SIG would be on improving all aspects > of the user experience around authoring Jenkins Pipeline. This includes: > *

Re: Proposal: Pipeline Authoring SIG

2018-11-01 Thread steventerrana
Hey Andrew, Excited to see this being kicked off. Let me know how I can help! On Monday, October 15, 2018 at 5:12:13 AM UTC-4, Andrew Bayer wrote: > > I’d like to propose the creation of a “Pipeline Authoring” SIG, with > myself as the lead. The focus of this SIG would be on improving all

Re: Proposal: Pipeline Authoring SIG

2018-10-19 Thread Oleg Nenashev
I'm in On Friday, October 19, 2018 at 9:10:50 AM UTC+2, Jon Brohauge wrote: > > I'll be there at the Contributor Summit. -- 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,

Re: Proposal: Pipeline Authoring SIG

2018-10-19 Thread Jon Brohauge
I'll be there at the Contributor Summit. -- 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

Re: Proposal: Pipeline Authoring SIG

2018-10-17 Thread me
I'm interested in following this group as well. On Monday, October 15, 2018 at 2:12:13 AM UTC-7, Andrew Bayer wrote: > > I’d like to propose the creation of a “Pipeline Authoring” SIG, with > myself as the lead. The focus of this SIG would be on improving all aspects > of the user experience

Re: Proposal: Pipeline Authoring SIG

2018-10-16 Thread Andrew Bayer
Oh, and here's the registration link for the Contributor Summit - https://www.eventbrite.com/e/jenkins-contributor-summit-nice-tickets-48353733318 A. On Tue, Oct 16, 2018 at 5:00 PM Christian C. wrote: > I'm interested =) > > On Tuesday, October 16, 2018 at 4:20:21 PM UTC+2, Andrew Bayer

Re: Proposal: Pipeline Authoring SIG

2018-10-16 Thread Christian C.
I'm interested =) On Tuesday, October 16, 2018 at 4:20:21 PM UTC+2, Andrew Bayer wrote: > > Hey, interested people who'll be in Nice next week - will you be attending > the Contributor Summit on Tuesday? I'm thinking of trying to schedule a > breakout for Pipeline Authoring SIG in the afternoon

Re: Proposal: Pipeline Authoring SIG

2018-10-16 Thread Andrew Bayer
Hey, interested people who'll be in Nice next week - will you be attending the Contributor Summit on Tuesday? I'm thinking of trying to schedule a breakout for Pipeline Authoring SIG in the afternoon on Tuesday if there's sufficient interest. A. On Tue, Oct 16, 2018 at 11:53 AM Christian C.

Re: Proposal: Pipeline Authoring SIG

2018-10-16 Thread Christian C.
Hi all! On Monday, October 15, 2018 at 11:12:13 AM UTC+2, Andrew Bayer wrote: > > If you’d like to be part of the initial group of participants, please > respond on this thread. > I'd be happy to join up in Nice next week @ Jenkins World! =) We use a competely dockerized config-as-code (jcasc)

Re: Proposal: Pipeline Authoring SIG

2018-10-16 Thread Baptiste Mathus
+1. Pipeline is now a critical component and a Jenkins sub-ecosystem on its own so it makes sense to have something dedicated to handle it and its future. I guess you should include https://github.com/jenkinsci/JenkinsPipelineUnit ? Le mar. 16 oct. 2018 à 09:58, Andrew Bayer a écrit : > That

Re: Proposal: Pipeline Authoring SIG

2018-10-16 Thread arch
I could provide Chinese Pipeline documents or translation. On Tue, Oct 16, 2018 at 3:39 PM Andrew Bayer wrote: > Definitely! Both Liam and myself will be at Nice. > > A. > > On Mon, Oct 15, 2018 at 9:03 PM Jon Brohauge > wrote: > >> Andrew, >> >> Very interesting idea. Been desperately trying

Re: Proposal: Pipeline Authoring SIG

2018-10-16 Thread Andrew Bayer
Definitely! Both Liam and myself will be at Nice. A. On Mon, Oct 15, 2018 at 9:03 PM Jon Brohauge wrote: > Andrew, > > Very interesting idea. Been desperately trying to test my vars/ groovy > scripts with varying degrees of success. I'd love to contribute where I > can. Maybe we can meet up at

Re: Proposal: Pipeline Authoring SIG

2018-10-15 Thread arch
Great idea. On Tue, Oct 16, 2018 at 4:32 AM wrote: > I'm definitely interested in being part of this as well. > > > On Monday, October 15, 2018 at 2:12:13 AM UTC-7, Andrew Bayer wrote: >> >> I’d like to propose the creation of a “Pipeline Authoring” SIG, with >> myself as the lead. The focus of

Re: Proposal: Pipeline Authoring SIG

2018-10-15 Thread ben
I'm definitely interested in being part of this as well. On Monday, October 15, 2018 at 2:12:13 AM UTC-7, Andrew Bayer wrote: > > I’d like to propose the creation of a “Pipeline Authoring” SIG, with > myself as the lead. The focus of this SIG would be on improving all aspects > of the user

Re: Proposal: Pipeline Authoring SIG

2018-10-15 Thread Jon Brohauge
Andrew, Very interesting idea. Been desperately trying to test my vars/ groovy scripts with varying degrees of success. I'd love to contribute where I can. Maybe we can meet up at Jenkins World in Nice? Regards Jon Brohauge -- You received this message because you are subscribed to the

Re: Proposal: Pipeline Authoring SIG

2018-10-15 Thread Liam Newman
Andrew, Thanks for taking the lead on this. As noted, I'm eager to talk about documenting pipeline, but talking more about best practices and public examples. One example would be, github.com/mozilla/fxapom (and the related shared library). I'll loop the maintainers of that into this