[Jenkins-events] [vJAM] - Next meetup - Jenkins contribution 101?

Mon May 23 23:40:55 UTC 2016

does it make sense to break this up into multiple vJAM sessions? 1 to 2
sessions per month

On Mon, May 23, 2016 at 4:27 PM, R. Tyler Croy <tyler at monkeypox.org> wrote:

>
> Top-posting because I'm just the worst.
>
>
> I do not think it is prudent to schedule anything until we have some
> speakers
> lined up. And as Alyssa mentioned that no less than two weeks notice is
> preferrable. I believe anything over two talks is going to be too much for
> one
> event, since this is "online" there's not break times between like you
> might
> have at a normal meetup. IMHO 2x45 minute talks would be the most ideal
> format.
>
> If we can lock in a couple speakers before the end of the week, one talking
> 'standard' plugin dev, and one talking pipeline plugin dev (e.g. adding
> fancy
> new steps), then I think we can sanely schedule something for June 14-16.
>
>
>
> I understand the GSoC angle here, but these sessions will be recorded for
> posterity and while we might miss some interactivity from students, it's
> not as
> if the content will be lost and gone forever :)
>
>
>
> On Fri, 20 May 2016, Alyssa Tong wrote:
>
> > Hi Oleg,
> >
> > pls see my response embedded inline..
> >
> > On Thu, May 19, 2016 at 10:52 PM, Oleg Nenashev <o.v.nenashev at gmail.com>
> > wrote:
> >
> > > Hi,
> > >
> > > Can we do this the second wk of June? This will give us about 2wks get
> > >> people to RSVP. So that means I will need content to post on
> meetup.com
> > >> as soon as possible, by tomorrow if possible.
> > >>
> > >
> > > Second week is less preferable from GSoC PoV, but I think mentors will
> be
> > > able to provide enough information. Jun 8 is a governance meeting. So
> maybe
> > > Jun 7 (common meeting time)? Would it be fine if we publish it without
> a
> > > final list of talks/speakers? Maybe we could allocate the slot and
> provide
> > > a preliminary list of talks.
> > >
> > > AT: June 7 sounds good - in general anything between Tues & Thurs works
> > best.. We can definitely post a "Tentative" agenda and clearly state
> agenda
> > items might change. And then it's usually best to get the word out there
> > about the event as soon as possible, at minimum 2 wks out so more eyes
> can
> > get on it.
> >
> > Regarding the duration, I think we should not go beyond 3 hours. So it
> > > means about 3 talks (2 short + 1 long) + Q&A. So maybe we could even
> > > allocate 2 meetup slots.
> > >
> > > AT: +1. I liked how we did it last time where each speaker had 30 mins
> > for their session. So 30-45min sessions works best.
> >
> > As for Q&A - I would suggest having others online to help answer
> questions
> > in real time (via text). Any questions not covered via text it can be
> asked
> > on the call or followup via blog. I really like this approach because it
> > encourages an active interaction thru out the sessions.
> >
> > If you could focus on Pipeline DSL plugin development rather than on
> > >> traditional plugin development (the extensions are not from the same
> > >> classes, etc.) it would be beneficial to Alex's project, the External
> > >> Workspace Manager Plugin.
> > >
> > >
> > > I think classic plugin development is still important (plugin
> structure,
> > > extension points, how to build/debug, simple UI). But I agree that
> Pipeline
> > > plugin development training would be useful as well.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > 2016-05-20 1:59 GMT+03:00 Martin d'Anjou <martin.danjou14 at gmail.com>:
> > >
> > >> Steven,
> > >>
> > >> If you could focus on Pipeline DSL plugin development rather than on
> > >> traditional plugin development (the extensions are not from the same
> > >> classes, etc.) it would be beneficial to Alex's project, the External
> > >> Workspace Manager Plugin.
> > >>
> > >> Thanks in advance,
> > >> Martin
> > >>
> > >>
> > >> On 16-05-19 03:51 PM, Oleg Nenashev wrote:
> > >>
> > >> Hello,
> > >>
> > >> I wanted to follow-up on the second online meetup. Since we have
> > >> newcomers in the project (GSoC students, new plugin devs), it may be
> useful
> > >> to conduct a Jenkins Development 101 meetup.
> > >>
> > >> I would propose to conduct a meetup and repeat presentations from
> > >> Hacksgiving and other intro presentations in order to minimize
> preparation
> > >> efforts.
> > >>
> > >> Possible talks:
> > >>
> > >>    - (?) - Top-level community overview
> > >>       - I have some slides for it, but may be a subject for a Jenkins
> > >>       board representative
> > >>       - Steven - Plugin development
> > >>    - Tyler - jenkins.io - Writing blogposts and documentation
> > >>    - Daniel - Stapler
> > >>    - Tom(?) - new JavaScript-based UI development flow
> > >>    - Oleg(?) - Test Automation in Jenkins Project
> > >>    - All - Q&A Session
> > >>
> > >> What do you think? Maybe we could conduct such event on the
> first/second
> > >> week of June.
> > >>
> > >> Thanks in advance,
> > >> Oleg
> > >> --
> > >> You received this message because you are subscribed to the Google
> Groups
> > >> "jenkinsci-gsoc-all-public" group.
> > >> To unsubscribe from this group and stop receiving emails from it,
> send an
> > >> email to jenkinsci-gsoc-all-public+unsubscribe at googlegroups.com.
> > >> To post to this group, send email to
> > >> jenkinsci-gsoc-all-public at googlegroups.com.
> > >> To view this discussion on the web visit
> > >> <
> 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
> >
> > >>
> https://groups.google.com/d/msgid/jenkinsci-gsoc-all-public/CAPfivLBEAAMRnd42cFN-x_%3D3__32N2%3DaH%2BcKHUyw%2B5QnCikLVA%40mail.gmail.com
> > >> .
> > >> For more options, visit https://groups.google.com/d/optout.
> > >>
> > >>
> > >>
> > >
>
> - R. Tyler Croy
>
> ------------------------------------------------------
>      Code: <https://github.com/rtyler>
>   Chatter: <https://twitter.com/agentdero>
>
>   % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
> ------------------------------------------------------
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-events/attachments/20160523/9710c337/attachment-0001.html>