[Campus-princeton-staff] IMPORTANT: Mentoring information

Fri Nov 21 23:54:15 UTC 2014

Possibly, I'll take a look at what sort of "GoodFirstBugs" there are. Maybe
some of the cleanup tasks can be done without compiling locally.

Justin Lin

On Fri, Nov 21, 2014 at 12:21 PM, Lisha Ruan <lruan at princeton.edu> wrote:

> Hi Justin,
>
> Actually, do you think buildbots would be sufficient for the workshop? I
> think that students will be making small changes, since they only have a
> few hours to get started on the project. If they can avoid a long build
> process, that'd be preferable.
>
> Best,
> Lisha
>
> On Fri, Nov 21, 2014 at 11:45 AM, Lisha Ruan <lruan at princeton.edu> wrote:
>
>> Hi Justin,
>>
>> All right, thanks! I'll add your instructions for Chromium to the
>> projects page.
>>
>> Best,
>> Lisha
>>
>> On Fri, Nov 21, 2014 at 11:41 AM, Justin Lin <jlin at justinlin.net> wrote:
>>
>>> I sent the wrong link.. I meant this:
>>> http://www.chromium.org/developers
>>>
>>> Justin Lin
>>>
>>> On Fri, Nov 21, 2014 at 11:38 AM, Justin Lin <jlin at justinlin.net> wrote:
>>>
>>>> I think it takes maybe 30 minutes to check things out, then a lifetime
>>>> for it to do the first build. Incremental builds are fast however (couple
>>>> seconds to a couple minutes depending on how your environment is setup).
>>>> However, there are ways to just just write code and have Google's server
>>>> farm build and test it (i.e. buildbots
>>>> <http://www.chromium.org/developers/testing/try-server-usage>). So,
>>>> for small changes we can do that instead.
>>>>
>>>> Here are better instructions. There's links to the builds for all
>>>> platforms.
>>>> http://dev.chromium.org/developers/contributing-code
>>>>
>>>>
>>>> Actually minor note: I probably wouldn't add Beaker to the projects
>>>> page simply because we would not be able to support it very well, but we
>>>> can mention it to students who might have not picked a project yet.
>>>>
>>>> Thanks!
>>>>
>>>> Justin Lin
>>>>
>>>> On Fri, Nov 21, 2014 at 11:22 AM, Lisha Ruan <lruan at princeton.edu>
>>>> wrote:
>>>>
>>>>> Hi Justin,
>>>>>
>>>>> For Chromium, will the 10 hours just be waiting for the checkout and
>>>>> build to finish? How long will someone have to spend actively working on
>>>>> the build? Also, are there build instructions for Mac and Windows?
>>>>>
>>>>> I'll add Beaker to the projects page, too.
>>>>>
>>>>> Best,
>>>>> Lisha
>>>>>
>>>>> On Fri, Nov 21, 2014 at 7:49 AM, Justin Lin <jlin at justinlin.net>
>>>>> wrote:
>>>>>
>>>>>> A bit late, but I can help with contributing to the Chromium (aka
>>>>>> Chrome) project.
>>>>>>
>>>>>> Language: C++
>>>>>> Mentors: #chromium on freenode, the chromium-dev
>>>>>> <https://groups.google.com/a/chromium.org/forum/#!forum/chromium-dev>
>>>>>> mailing list, and me :). Bug tracking is at http://crbug.com, and
>>>>>> WebKit issues are at https://bugs.webkit.org/.
>>>>>>
>>>>>> Like Firefox, there's a good number of prerequisites to do that can
>>>>>> be found here
>>>>>> <https://code.google.com/p/chromium/wiki/LinuxBuildInstructions>. It
>>>>>> probably takes something like 10 hours to checkout and build on a laptop
>>>>>> the first time though.
>>>>>>
>>>>>>
>>>>>> It also might be worth mentioning that Two Sigma has an open source
>>>>>> project called beaker: http://beakernotebook.com/. It's a pretty
>>>>>> cool polyglot scientist's notebook. Source code and issue tracking:
>>>>>> https://github.com/twosigma/beaker-notebook. Although I think those
>>>>>> of us coming have limited direct experience with contributing to beaker, we
>>>>>> can certainly help with setting up and basic issues. However, we can put
>>>>>> students in touch with the right people if anybody ends up interested in
>>>>>> seriously contributing to the project after the event.
>>>>>>
>>>>>> Thanks,
>>>>>> Justin
>>>>>>
>>>>>> Justin Lin
>>>>>>
>>>>>> On Fri, Nov 21, 2014 at 2:04 AM, Lisha Ruan <lruan at princeton.edu>
>>>>>> wrote:
>>>>>>
>>>>>>> Great, thanks Valerie!
>>>>>>>
>>>>>>> *To the mentors:* I'm about to send to the students a list of
>>>>>>> projects that they can contribute to during the workshop:
>>>>>>> https://openhatch.org/wiki/Princeton_Workshop_Projects
>>>>>>>
>>>>>>> If you want me to add a project to that page, let me know.
>>>>>>>
>>>>>>> On Thu, Nov 20, 2014 at 8:14 PM, Valerie Morin <vmorin at princeton.edu
>>>>>>> > wrote:
>>>>>>>
>>>>>>>> Yep, til 6
>>>>>>>>
>>>>>>>>
>>>>>>>> On Nov 20, 2014, at 7:49 PM, Lisha Ruan <lruan at princeton.edu>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>> I believe we have the room until 6. Valerie, can you confirm that?
>>>>>>>>
>>>>>>>> That's a good point, but I also think often students don't last
>>>>>>>> through the whole contributions workshop if they get stuck and feel they're
>>>>>>>> not making progress. If we can avoid that, they may want to keep working.
>>>>>>>>
>>>>>>>> It looks like about 1/2 of students are familiar with git/Github,
>>>>>>>> but not many with IRC. I was thinking the students familiar with git/Github
>>>>>>>> can start choosing, setting up, and maybe working on a project during the
>>>>>>>> git mini projects portion. Not sure if there's any way to get around
>>>>>>>> listening to the presentation for those who know the material already.
>>>>>>>>
>>>>>>>> Also, I don't think we should extend the workshop past 5 pm (not
>>>>>>>> officially, though students can stay later). If we make the contributions
>>>>>>>> portion longer, we should shorten something else.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, Nov 20, 2014 at 7:42 PM, Shauna Gordon-McKeon <
>>>>>>>> shaunagm at gmail.com> wrote:
>>>>>>>>
>>>>>>>>> We find that students don't last more than 2.5 hours - they've
>>>>>>>>> already spent several hours learning new materials, and they need to take a
>>>>>>>>> break by the end of the workshop.  There are often a few students who are
>>>>>>>>> so into things that they'll keep going for hours, so when possible we do
>>>>>>>>> like to keep the room book for after the event.  Lisha, Katherine, do you
>>>>>>>>> know if we've got the room past 4?
>>>>>>>>>
>>>>>>>>> It looks like there are about 12 sign-ups (so about 6-8 attendees)
>>>>>>>>> who already have experience with the things we'll be teaching in the
>>>>>>>>> morning tutorials.  If you'd like to do the workshop for longer, we can see
>>>>>>>>> if they'd be interested in starting early with your project.  (We've done
>>>>>>>>> this a couple times and it generally works pretty well.)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Thu, Nov 20, 2014 at 7:38 PM, Peter Wolanin <pwolanin at gmail.com
>>>>>>>>> > wrote:
>>>>>>>>>
>>>>>>>>>> I had said I'd be willing to present a section on what is open
>>>>>>>>>> source
>>>>>>>>>> - from the schedule it looks like that's missing and you'll only
>>>>>>>>>> have
>>>>>>>>>> "Open Source Communication Tools"?
>>>>>>>>>>
>>>>>>>>>> Also - only 2.5 hours for the workshop?
>>>>>>>>>>
>>>>>>>>>> -Peter
>>>>>>>>>>
>>>>>>>>>> On Wed, Nov 19, 2014 at 11:12 PM, Lisha Ruan <lruan at princeton.edu>
>>>>>>>>>> wrote:
>>>>>>>>>> > Hi mentors,
>>>>>>>>>> >
>>>>>>>>>> > Again, thank you all so much for volunteering to mentor at the
>>>>>>>>>> Princeton
>>>>>>>>>> > open source workshop on Saturday! :)
>>>>>>>>>> >
>>>>>>>>>> > This email has all the information about what you'll be
>>>>>>>>>> expected to do as a
>>>>>>>>>> > mentor.
>>>>>>>>>> >
>>>>>>>>>> > Here's the schedule for the workshop. Students will arrive at
>>>>>>>>>> 10 am; we're
>>>>>>>>>> > expecting about 30 students. The room will be set up in round
>>>>>>>>>> tables, and
>>>>>>>>>> > students will sit around the tables with at least one mentor at
>>>>>>>>>> each table.
>>>>>>>>>> > From 10 - 11 am, there will be breakfast and laptop setup.
>>>>>>>>>> Here's what the
>>>>>>>>>> > students will be doing for laptop setup; if they have problems,
>>>>>>>>>> they'll ask
>>>>>>>>>> > you guys for help. From 11 - 12 pm, we'll have the
>>>>>>>>>> communications tools
>>>>>>>>>> > presentation, which I just sent an email about.
>>>>>>>>>> >
>>>>>>>>>> > From 12 - 1 pm, the students will be doing git mini projects.
>>>>>>>>>> Here are the
>>>>>>>>>> > exercises they'll be doing. Since you all said that you're
>>>>>>>>>> comfortable with
>>>>>>>>>> > git, I'm assuming that you can each lead a group of students
>>>>>>>>>> during git mini
>>>>>>>>>> > projects. Your role would be to answer any questions and
>>>>>>>>>> troubleshoot
>>>>>>>>>> > problems. If you don't want to lead a group, please let me know.
>>>>>>>>>> >
>>>>>>>>>> > From 1 - 1:45 pm, we'll have lunch. From 1:45 - 2:15 pm, we'll
>>>>>>>>>> have a
>>>>>>>>>> > "musical chairs" Q&A panel: students will split into small
>>>>>>>>>> groups and
>>>>>>>>>> > panelists will rotate among them, answering questions and
>>>>>>>>>> having a
>>>>>>>>>> > conversation. From 2:15 - 4:45 pm, we'll have the contributions
>>>>>>>>>> workshop,
>>>>>>>>>> > when students will choose an open source project to contribute
>>>>>>>>>> to, work on
>>>>>>>>>> > an introductory ticket, and hopefully submit a pull request.
>>>>>>>>>> >
>>>>>>>>>> > Please reply with your responses to these questions:
>>>>>>>>>> >
>>>>>>>>>> > 1) Are you willing to be on the Q&A panel? (In-person mentors
>>>>>>>>>> only) Anyone
>>>>>>>>>> > who actively contributes to an open source project (or has done
>>>>>>>>>> so in the
>>>>>>>>>> > past) can be on the panel. Again, you'll be rotating around
>>>>>>>>>> small groups of
>>>>>>>>>> > students, answering questions and having a conversation.
>>>>>>>>>> >
>>>>>>>>>> > 2) Is there a project that you're familiar with, that you can
>>>>>>>>>> lead students
>>>>>>>>>> > in contributing to during the contributions workshop? Last
>>>>>>>>>> year, we had many
>>>>>>>>>> > students get stuck on the tickets they were working on and not
>>>>>>>>>> end up
>>>>>>>>>> > submitting a pull request. I think the contributions workshop
>>>>>>>>>> will be much
>>>>>>>>>> > more successful if the projects are ones that the mentors are
>>>>>>>>>> familiar with
>>>>>>>>>> > and can help students with. If you'll be leading students on a
>>>>>>>>>> project, it'd
>>>>>>>>>> > be great if you could find some introductory tickets for
>>>>>>>>>> students to work
>>>>>>>>>> > on.
>>>>>>>>>> >
>>>>>>>>>> > If yes to question 2) Is there anything students should set up
>>>>>>>>>> before the
>>>>>>>>>> > workshop to prepare for working on your project? (e.g.
>>>>>>>>>> installing anything)
>>>>>>>>>> > We'll send out an email asking students to do this setup, but
>>>>>>>>>> prepare for
>>>>>>>>>> > some to not have it done.
>>>>>>>>>> >
>>>>>>>>>> > Lastly -- again, it's really important that we have someone
>>>>>>>>>> give the
>>>>>>>>>> > communication tools presentation! Let me know if you can give
>>>>>>>>>> it, it would
>>>>>>>>>> > be super appreciated!! :)
>>>>>>>>>> >
>>>>>>>>>> > If you have any questions that I haven't answered, please ask!
>>>>>>>>>> Also, if you
>>>>>>>>>> > have any ideas for the workshop, please tell me.
>>>>>>>>>> >
>>>>>>>>>> > Best,
>>>>>>>>>> > Lisha
>>>>>>>>>> _______________________________________________
>>>>>>>>>> Campus-princeton-staff mailing list
>>>>>>>>>> Campus-princeton-staff at lists.openhatch.org
>>>>>>>>>> http://lists.openhatch.org/mailman/listinfo/campus-princeton-staff
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openhatch.org/pipermail/campus-princeton-staff/attachments/20141121/64227deb/attachment-0001.html>