Hi,
Please let's make sure that this issue is bumped up all the time.
I am trying to think of a suitable plan of attack on Drigg.
Drigg is actually three modules:
* Drigg
* EVF
* User Karma
My plan at the moment is to have ZERO issues open for User Karma and EVF as soon as physically possible -- possibly this week. The only features left should be some clear and implementable feature requests (the ones I am able to do) and some postponed ones (the ones I am NOT able to do without help).
Drigg is a different story. There are 106 issues open. Some of them are bugs. Some of them are simple support requests that really could be closed. Some of them are feature requests. The plan is to close EVERY bug as soon as possible, apply the existing patches, and do the same in terms of feature requests: have some open there (the ones I can do) and some postponed (the ones I need help with, especially the ones where Javascript is involved).
Friendlist, the other module that I passed on, has also been left undeveloped for 3+ months by the developer, but luckily he told me that he's about to work on it again. So that's one less thing to worry about.
I need hep for all this.
The first thing I need, is a list of link to all of the patches that are actually ready to be rolled. I won't be able to test them very carefully -- please help me with that. I will apply pretty much all of the patches.
After that, we need to triage the existing bugs. So, mark the most important ones as "critical", then the normal ones as "normal" and the others as "minor". Please start doing so now if you like. I will work through them ASAP.
I will be travelling in 1 week. I plan on getting done as much as possible before now and then, so that we can all see where we are heading.
After that, we will need to think of some kind of revenue model for Drigg. People with established Drigg sites might just chip in $150/month for example -- even 10 sites like that will justify me working on Drigg full time for one week each month, which would be great. (But I would do more than that, obviously, time permitting).
Let's get this mess sorted out.
Merc.
Comments
Comment #1
mercmobily commentedBump
Comment #2
philbar commentedPatches Ready To Go!
2 have been tested by the community. The other 3 still need to be tested.
Comment #3
mercmobily commentedHi,
Well, it looks like it's the two of us, philbar.
I think Drigg is a great module and it's totally worthwhile getting it to a point where there are no outstanding stupid bugs. However, I have to be honest, I am not sure it's a module that a lot of people would use. People have moved on from digg-like sites (maybe they discovered that there can only be one digg?).
Once we manage to do all this, I think we should move on and create a "drigg distribution" that has all sors of fancy things in it (friends, photos upload, the lot) to see if we can market this as something for social networking...
Merc.
Comment #4
mercmobily commented