<div dir="ltr"><div><div>Hi,<br><br></div>The event has been announced: <a href="http://www.meetup.com/Jenkins-online-meetup/events/231401509/">http://www.meetup.com/Jenkins-online-meetup/events/231401509/</a><br></div><div>Thanks Alyssa!<br><br></div><div>@Jesse<br></div><div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">BTW what date range is being discussed? I am moving in early June so I<br>
may or may not be able to do it.</blockquote><div><br></div><div>The target date for the meetup is June 14th. Does it work for you? <br></div></div><div><br></div>BR, Oleg<br></div><div class="gmail_extra"><br><div class="gmail_quote">2016-05-25 15:10 GMT+03:00 Minudika Malshan <span dir="ltr"><<a href="mailto:minudika001@gmail.com" target="_blank">minudika001@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>+1 <br></div>Looking forward to learn more about on Plugin development and UI<br></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Wed, May 25, 2016 at 2:58 AM, Oleg Nenashev <span dir="ltr"><<a href="mailto:o.v.nenashev@gmail.com" target="_blank">o.v.nenashev@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr"><div><div><div><div>I agree with Tyler that 2 longer talks are preferable. I would also add a short talk to the end (e.g. testing).<br><br></div>Then I would vote for something like that:<br><br></div>Meetup #1. Plugin Development. Basics<br></div>* Steven - Plugin Development. Classic talk (40 min)<br></div>* Jesse (?) - Plugin Development. Pipeline (40 min)<br><div>* TBD: Oleg - Jenkins Test Harness [and Pipeline extensions?] (20 min)<br></div><div><div><div><div><br></div><div>Meetup #2. Plugin Development. UI<br></div><div>* Daniel - Stapler [and Jelly/Groovy] (40 min)<br></div><div>* Tom - New JavaScript-based UI development flow (40 min)<br></div><div>* (? Andrew/Oliver/Bobby) - Acceptance Test Harness (20 min)<br></div><div><br></div><div>Meetup #3. Jenkins contribution 101 - Unconfirmed<br>* (?) - Top-level community overview<br></div><div>* (?) - Common project infrastructure: GitHub, Pull-requests, Jenkins-on-Jenkins, etc. <br></div><div>* Tyler(?) - <a href="http://jenkins.io" rel="noreferrer" target="_blank">jenkins.io</a> - Writing blogposts and documentation</div><div><div><div><br></div><div>Best regards,<br></div><div>Oleg<br></div></div></div></div></div></div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">2016-05-24 9:11 GMT+03:00 Oleg Nenashev <span dir="ltr"><<a href="mailto:o.v.nenashev@gmail.com" target="_blank">o.v.nenashev@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>We've got preliminary confirmation from Daniel, Steven, Tom and me. So we have enough speakers to schedule the first presentation independently from the format we select.<br><br></div>I have not scheduled anything on the weekend (motivation loss), but we can go forward now.<br><div><div><br></div>BR, Oleg<br></div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">2016-05-24 2:40 GMT+03:00 Alyssa Tong <span dir="ltr"><<a href="mailto:alytong13@gmail.com" target="_blank">alytong13@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">does it make sense to break this up into multiple vJAM sessions? 1 to 2 sessions per month</div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, May 23, 2016 at 4:27 PM, R. Tyler Croy <span dir="ltr"><<a href="mailto:tyler@monkeypox.org" target="_blank">tyler@monkeypox.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Top-posting because I'm just the worst.<br>
<br>
<br>
I do not think it is prudent to schedule anything until we have some speakers<br>
lined up. And as Alyssa mentioned that no less than two weeks notice is<br>
preferrable. I believe anything over two talks is going to be too much for one<br>
event, since this is "online" there's not break times between like you might<br>
have at a normal meetup. IMHO 2x45 minute talks would be the most ideal format.<br>
<br>
If we can lock in a couple speakers before the end of the week, one talking<br>
'standard' plugin dev, and one talking pipeline plugin dev (e.g. adding fancy<br>
new steps), then I think we can sanely schedule something for June 14-16.<br>
<br>
<br>
<br>
I understand the GSoC angle here, but these sessions will be recorded for<br>
posterity and while we might miss some interactivity from students, it's not as<br>
if the content will be lost and gone forever :)<br>
<div><div><br>
<br>
<br>
On Fri, 20 May 2016, Alyssa Tong wrote:<br>
<br>
> Hi Oleg,<br>
><br>
> pls see my response embedded inline..<br>
><br>
> On Thu, May 19, 2016 at 10:52 PM, Oleg Nenashev <<a href="mailto:o.v.nenashev@gmail.com" target="_blank">o.v.nenashev@gmail.com</a>><br>
> wrote:<br>
><br>
> > Hi,<br>
> ><br>
> > Can we do this the second wk of June? This will give us about 2wks get<br>
> >> people to RSVP. So that means I will need content to post on <a href="http://meetup.com" rel="noreferrer" target="_blank">meetup.com</a><br>
> >> as soon as possible, by tomorrow if possible.<br>
> >><br>
> ><br>
> > Second week is less preferable from GSoC PoV, but I think mentors will be<br>
> > able to provide enough information. Jun 8 is a governance meeting. So maybe<br>
> > Jun 7 (common meeting time)? Would it be fine if we publish it without a<br>
> > final list of talks/speakers? Maybe we could allocate the slot and provide<br>
> > a preliminary list of talks.<br>
> ><br>
> > AT: June 7 sounds good - in general anything between Tues & Thurs works<br>
> best.. We can definitely post a "Tentative" agenda and clearly state agenda<br>
> items might change. And then it's usually best to get the word out there<br>
> about the event as soon as possible, at minimum 2 wks out so more eyes can<br>
> get on it.<br>
><br>
> Regarding the duration, I think we should not go beyond 3 hours. So it<br>
> > means about 3 talks (2 short + 1 long) + Q&A. So maybe we could even<br>
> > allocate 2 meetup slots.<br>
> ><br>
> > AT: +1. I liked how we did it last time where each speaker had 30 mins<br>
> for their session. So 30-45min sessions works best.<br>
><br>
> As for Q&A - I would suggest having others online to help answer questions<br>
> in real time (via text). Any questions not covered via text it can be asked<br>
> on the call or followup via blog. I really like this approach because it<br>
> encourages an active interaction thru out the sessions.<br>
><br>
> If you could focus on Pipeline DSL plugin development rather than on<br>
> >> traditional plugin development (the extensions are not from the same<br>
> >> classes, etc.) it would be beneficial to Alex's project, the External<br>
> >> Workspace Manager Plugin.<br>
> ><br>
> ><br>
> > I think classic plugin development is still important (plugin structure,<br>
> > extension points, how to build/debug, simple UI). But I agree that Pipeline<br>
> > plugin development training would be useful as well.<br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > 2016-05-20 1:59 GMT+03:00 Martin d'Anjou <<a href="mailto:martin.danjou14@gmail.com" target="_blank">martin.danjou14@gmail.com</a>>:<br>
> ><br>
> >> Steven,<br>
> >><br>
> >> If you could focus on Pipeline DSL plugin development rather than on<br>
> >> traditional plugin development (the extensions are not from the same<br>
> >> classes, etc.) it would be beneficial to Alex's project, the External<br>
> >> Workspace Manager Plugin.<br>
> >><br>
> >> Thanks in advance,<br>
> >> Martin<br>
> >><br>
> >><br>
> >> On 16-05-19 03:51 PM, Oleg Nenashev wrote:<br>
> >><br>
> >> Hello,<br>
> >><br>
> >> I wanted to follow-up on the second online meetup. Since we have<br>
> >> newcomers in the project (GSoC students, new plugin devs), it may be useful<br>
> >> to conduct a Jenkins Development 101 meetup.<br>
> >><br>
> >> I would propose to conduct a meetup and repeat presentations from<br>
> >> Hacksgiving and other intro presentations in order to minimize preparation<br>
> >> efforts.<br>
> >><br>
> >> Possible talks:<br>
> >><br>
</div></div>> >> - (?) - Top-level community overview<br>
> >> - I have some slides for it, but may be a subject for a Jenkins<br>
> >> board representative<br>
<span>> >> - Steven - Plugin development<br>
> >> - Tyler - <a href="http://jenkins.io" rel="noreferrer" target="_blank">jenkins.io</a> - Writing blogposts and documentation<br>
> >> - Daniel - Stapler<br>
</span>> >> - Tom(?) - new JavaScript-based UI development flow<br>
> >> - Oleg(?) - Test Automation in Jenkins Project<br>
> >> - All - Q&A Session<br>
<span>> >><br>
> >> What do you think? Maybe we could conduct such event on the first/second<br>
> >> week of June.<br>
> >><br>
> >> Thanks in advance,<br>
> >> Oleg<br>
> >> --<br>
> >> You received this message because you are subscribed to the Google Groups<br>
> >> "jenkinsci-gsoc-all-public" group.<br>
> >> To unsubscribe from this group and stop receiving emails from it, send an<br>
> >> email to <a href="mailto:jenkinsci-gsoc-all-public%2Bunsubscribe@googlegroups.com" target="_blank">jenkinsci-gsoc-all-public+unsubscribe@googlegroups.com</a>.<br>
> >> To post to this group, send email to<br>
> >> <a href="mailto:jenkinsci-gsoc-all-public@googlegroups.com" target="_blank">jenkinsci-gsoc-all-public@googlegroups.com</a>.<br>
> >> To view this discussion on the web visit<br>
</span>> >> <<a href="https://groups.google.com/d/msgid/jenkinsci-gsoc-all-public/CAPfivLBEAAMRnd42cFN-x_%3D3__32N2%3DaH%2BcKHUyw%2B5QnCikLVA%40mail.gmail.com?utm_medium=email&utm_source=footer" rel="noreferrer" target="_blank">https://groups.google.com/d/msgid/jenkinsci-gsoc-all-public/CAPfivLBEAAMRnd42cFN-x_%3D3__32N2%3DaH%2BcKHUyw%2B5QnCikLVA%40mail.gmail.com?utm_medium=email&utm_source=footer</a>><br>
> >> <a href="https://groups.google.com/d/msgid/jenkinsci-gsoc-all-public/CAPfivLBEAAMRnd42cFN-x_%3D3__32N2%3DaH%2BcKHUyw%2B5QnCikLVA%40mail.gmail.com" rel="noreferrer" target="_blank">https://groups.google.com/d/msgid/jenkinsci-gsoc-all-public/CAPfivLBEAAMRnd42cFN-x_%3D3__32N2%3DaH%2BcKHUyw%2B5QnCikLVA%40mail.gmail.com</a><br>
<span>> >> .<br>
> >> For more options, visit <a href="https://groups.google.com/d/optout" rel="noreferrer" target="_blank">https://groups.google.com/d/optout</a>.<br>
> >><br>
> >><br>
> >><br>
> ><br>
<br>
</span>- R. Tyler Croy<br>
<br>
------------------------------------------------------<br>
Code: <<a href="https://github.com/rtyler" rel="noreferrer" target="_blank">https://github.com/rtyler</a>><br>
Chatter: <<a href="https://twitter.com/agentdero" rel="noreferrer" target="_blank">https://twitter.com/agentdero</a>><br>
<br>
% gpg --keyserver <a href="http://keys.gnupg.net" rel="noreferrer" target="_blank">keys.gnupg.net</a> --recv-key 3F51E16F<br>
------------------------------------------------------<br>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
<p></p>
-- <br>
You received this message because you are subscribed to the Google Groups "jenkinsci-gsoc-all-public" group.<br>
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="mailto:jenkinsci-gsoc-all-public+unsubscribe@googlegroups.com" target="_blank">jenkinsci-gsoc-all-public+unsubscribe@googlegroups.com</a>.<br>
To post to this group, send email to <a href="mailto:jenkinsci-gsoc-all-public@googlegroups.com" target="_blank">jenkinsci-gsoc-all-public@googlegroups.com</a>.<br></div></div></div></div>
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-gsoc-all-public/CAPfivLCGgwJEfr1nFNpVTfk3fMuZ80Fnx9xYWo3SYgn2GnrDgg%40mail.gmail.com?utm_medium=email&utm_source=footer" target="_blank">https://groups.google.com/d/msgid/jenkinsci-gsoc-all-public/CAPfivLCGgwJEfr1nFNpVTfk3fMuZ80Fnx9xYWo3SYgn2GnrDgg%40mail.gmail.com</a>.<span class=""><div><div><br>
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank">https://groups.google.com/d/optout</a>.<br>
</div></div></span></blockquote></div><br></div>
</blockquote></div><br></div>