I'll keep GSOC in mind. We should also start labeling issues with 2.0. Tyler On Mar 1, 2015 11:39 PM, "Mattmann, Chris A (3980)" < [email protected]> wrote:
> Good idea, Nick. The vision parser I threw up I labeled with > gsoc2015 - if there are any takers, please send them my way! > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Chris Mattmann, Ph.D. > Chief Architect > Instrument Software and Science Data Systems Section (398) > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA > Office: 168-519, Mailstop: 168-527 > Email: [email protected] > WWW: http://sunset.usc.edu/~mattmann/ > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Adjunct Associate Professor, Computer Science Department > University of Southern California, Los Angeles, CA 90089 USA > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > > > > > > -----Original Message----- > From: Nick Burch <[email protected]> > Reply-To: "[email protected]" <[email protected]> > Date: Sunday, March 1, 2015 at 8:14 PM > To: "[email protected]" <[email protected]> > Subject: Re: Curating Issues > > >On Sun, 1 Mar 2015, Tyler Palsulich wrote: > >> I've started labeling some issues as "new-parser" and "newbie." I think > >> these should be helpful for organization. Please let me know if there > >>is > >> another label we've already been using for those. I put "new-parser" on > >> any requests to support a new filetype, even if it doesn't require a > >> full on Parser (e.g. just magic). > > > >I don't know if anyone has the time to mentor, but there's just about > >still time to get something into GSoC for 2015. If we do have someone who > >could mentor a student in the summer, then it could be worth tagging any > >"summer sized" issues with gsoc2015. > >http://community.apache.org/gsoc.html > >has some more info for anyone new to gsoc > > > >Nick > >
