[OSCTC-planning] Moving forward on specific projects to have bugs lined up for Princeton project time

[Asheesh Laroia]

FWIW, https://groups.google.com/forum/#!topic/svg-edit/7VuiEXTZbKM is
a sample email indicating what we need more concretely.

On Tue, Nov 19, 2013 at 9:56 PM, Asheesh Laroia <lists at asheesh.org> wrote:
> OMG HELLO JOSH THE AMAZING
>
> I'm torn, as I love Firefox, but I have seen build times be a problem
> at these events. We could clearly indicate that it only applies for
> people meeting has high system requirements -- 4GB or more RAM, 10GB
> of disk space, what else would you suggest? What installed pre-reqs
> (XCode? anything else for a Mac?) would be needed?
>
> Also, we could remark that it's going to take 45 min to build, so tell
> them to get started on that with a mentor during lunch.
>
> I would love to give it a shot if we're willing to indicate to
> attendees they're guinea pigs for a version 2 that would work even
> better. I think listing pre-requisites and getting a head-start on the
> build during lunch would fix the most important issues.
>
> On Tue, Nov 19, 2013 at 9:48 PM, Josh Matthews <josh at joshmatthews.net> wrote:
>> This is something Mozilla could probably do with some Firefox bugs, but I
>> fear that the initial 45-90 minutes build required would not fit well within
>> the event constraints. Am I correct?
>>
>> Cheers,
>> Josh
>>
>>
>> On 20 November 2013 13:43, Asheesh Laroia <lists at asheesh.org> wrote:
>>>
>>> Hi all, and Shauna,
>>>
>>> I wanted to report on my progress getting specific projects to offer
>>> 2-5 good bitesize bugs each lined up for the Princeton event. (This is
>>> also known as "OpenHatch-affiliated projects". It's more than just
>>> having bugs lined up; it's having the bugs be truly good for
>>> newcomers, and having people from the projects be around during the
>>> event, and having enough supporting documentation so that the bugs can
>>> plausibly be solved.)
>>>
>>> I have a "basically definitely yes" from MissKat on #dreamwidth-dev
>>> for that project. (Also this is a person whom I had the pleasure of
>>> meeting at conferences.)
>>>
>>> I asked the SymPy folks on IRC.
>>>
>>> I pinged the d3 maintainer by private email.
>>>
>>> I asked the svg-edit people on their public mailing list.
>>>
>>> I documented this on the spreadsheet here:
>>>
>>> https://docs.google.com/spreadsheet/ccc?key=0AoHP1ey91UqPdGVDbmI4cnFOTmFEcUcwN3RiOTZMcUE#gid=0
>>>
>>> Question for you Shauna:
>>>
>>> I see "Thoughtworks" in the list. I am not sure what that refers to,
>>> so I thought I'd ping to indicate that confusion.
>>>
>>> Overall, thanks for making that spreadsheet. I will keep it updated as
>>> things progress with these projects.
>>>
>>> -- Asheesh.
>>> _______________________________________________
>>> OSCTC-planning mailing list
>>> OSCTC-planning at lists.openhatch.org
>>> http://lists.openhatch.org/mailman/listinfo/osctc-planning
>>
>>
>>
>> _______________________________________________
>> OSCTC-planning mailing list
>> OSCTC-planning at lists.openhatch.org
>> http://lists.openhatch.org/mailman/listinfo/osctc-planning
>>