-Re: Issues piling up
Sebastian Schelter 2011-08-17, 10:13
I ran through the issues and compiled a list of tasks I'll care about,
please keep them open.
MAHOUT-710 Implementing K-Trusses
I'll pick up work on that in a few weeks.
MAHOUT-777 Improve TransposeJob to use a Combiner
Patch needs review from Jake (or anyone else willing to do that)
MAHOUT-767 Improve RowSimilarityJob performance for count-based distance
Currently working on that.
MAHOUT-773 Implement Random Walk with Restarts
I have a working patch, but Ted suggested the use of random projections,
I'll have a look into that if I get hold of a linear algebra guru :)
MAHOUT-737 Implicit Alternating Least Squares SVD
This one needs input from Tamas Jambor, the code looked good, yet he has
to rework it to avoid a matrix inversion.
MAHOUT-609 Add an option to make RecommenderJob write out it's computed
This should be a small change that I'll add in some spare time or before
the next release.
On 17.08.2011 11:48, Sean Owen wrote:
> Hi all, I'm again seeing the issue count tend to pile up. I try to run
> through regularly to resolve anything addressed to me, and even things that
> aren't but that I am confident enough to fix. It would be great if everyone
> could do the same in a spare 1-2 hours this week, if only to say "yes, go
> ahead on that patch" or "no I don't think this is a good idea". Especially
> the committers who have not been active in a while.
> To me, this is the most essential work we can do, because without responses
> from those with power to commit, new community members get the message that
> their contributions are ignored, or that nobody's home. That's no good.
> Understanding that individuals may not have time to actively write their own
> new changes and improvements, it seems that the least we can all do is
> involve and respond to external input, to bring in those who want to make
> I'd also like to sweep through the issues that have not been touched in 6+
> months and close some that just do not seem to be getting any traction or
> attention. The theory is that closing stuff that by all accounts won't get
> looked at better communicates what's coming in the project, and focuses
> attention on issues that might get looked at.
> Before I start that though, would welcome anyone to peek at everything
> that's open and assign, comment, ping, etc. anything that needs to be kept