tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tyler Palsulich <tpalsul...@gmail.com>
Subject Re: Curating Issues
Date Sun, 01 Mar 2015 22:34:43 GMT
Alright. I'm up to TIKA-694 and still goin'. :)

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).

"newbie" should be used for new contributors.

I'll take no offense if someone reopens/closes anything after I've touched
it.

Tyler

On Sat, Feb 28, 2015 at 11:59 PM, Mattmann, Chris A (3980) <
chris.a.mattmann@jpl.nasa.gov> wrote:

> Hey Tyler if you want to take a whack, here are some criteria
> I tend to use:
>
> 1. Bug report from 1+ years old.
>   - Close it - either not reproducible, fixed in a later version
> and not come back to, or not as bad of a bug anymore since it’s
> not a blocker.
>
> 2. Feature request from 1+ years old that no one has acted upon.
>  - Good candidate for closing - if it was important someone would
> have acted up on it.
>
> 3. Issue from 1+ years old with lots of discussion on it
>   - Poke the issue - see if a consensus can be reached, if not
> move forward and close.
>
> 4. Issue that is your own that you aren’t interested in anymore
> that is 1+ years old
>   - Close it you didn’t work on it then, may not get back to it
> and no one else has
>
> 5. Issue that is 2+ years old
>   - Close, regardless, unless it has patch
>
> 6. Issue that is 1+ years old, with patch, uncommitted
>   - Try to apply patch or minimal effort to bring current with
> trunk and apply
>   - if too much work ask for help
>   - if 1+ weeks and no one replies, close it and move forward
>
> There are more but that’s a start. I’ll check out this article
> thanks for sending it.
>
> Cheers,
> Chris
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 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: chris.a.mattmann@nasa.gov
> WWW:  http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Associate Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
>
>
>
>
> -----Original Message-----
> From: Tyler Palsulich <tpalsulich@gmail.com>
> Reply-To: "dev@tika.apache.org" <dev@tika.apache.org>
> Date: Saturday, February 28, 2015 at 8:53 PM
> To: "dev@tika.apache.org" <dev@tika.apache.org>
> Subject: Curating Issues
>
> >Hi Folks,
> >
> >I just read an article [0] about managing a large project's issues list.
> >Tika currently has 331 open issues. Do we know if all of these have been
> >"triaged"? At what point do we want to label an issue as stale and close
> >it
> >off? What is our preferred split between when to make an issue and when to
> >send a message to the mailing list?
> >
> >Have a good weekend,
> >Tyler
> >
> >[0] http://words.steveklabnik.com/how-to-be-an-open-source-gardener?r=1
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message