You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@mahout.apache.org by Timothy Mann <ma...@gmail.com> on 2012/10/21 01:46:16 UTC

Code Cleanup and Documentation

Hi,

I'm interested in cleaning up code and adding documentation related to the
classifier packages. What is the best way to provide patches, since these
aren't exactly bugs? Should I just create JIRA "improvement" entries
describing the cleanup and add patches? Thanks for your help.

-Timothy A. Mann

Re: Code Cleanup and Documentation

Posted by Jake Mannix <ja...@gmail.com>.

+1 to this, your help is much appreciated, we love JIRA tickets with
patches attached. :)

On Sat, Oct 20, 2012 at 10:24 PM, Ted Dunning <te...@gmail.com> wrote:

> Yes.  Just create JIRA's and have at it.  All help is welcome for cleanups.
>
> On Sat, Oct 20, 2012 at 4:46 PM, Timothy Mann <mann.timothy@gmail.com
> >wrote:
>
> > Hi,
> >
> > I'm interested in cleaning up code and adding documentation related to
> the
> > classifier packages. What is the best way to provide patches, since these
> > aren't exactly bugs? Should I just create JIRA "improvement" entries
> > describing the cleanup and add patches? Thanks for your help.
> >
> > -Timothy A. Mann
> >
>



-- 

  -jake

Re: Code Cleanup and Documentation

Posted by Ted Dunning <te...@gmail.com>.

Yes.  Just create JIRA's and have at it.  All help is welcome for cleanups.

On Sat, Oct 20, 2012 at 4:46 PM, Timothy Mann <ma...@gmail.com>wrote:

> Hi,
>
> I'm interested in cleaning up code and adding documentation related to the
> classifier packages. What is the best way to provide patches, since these
> aren't exactly bugs? Should I just create JIRA "improvement" entries
> describing the cleanup and add patches? Thanks for your help.
>
> -Timothy A. Mann
>