Merc,
Would it be possible for me to maintain the default drigg theme in a theme project?
I know in the past you have made it clear that maintaining the default theme is low priority for you. I don't know if you still hold that view. If so, I think I can handle maintaining it. I know HTML and CSS far more than I know PHP.
For the most part, development has stopped on the theme (apart from adding div classes and sub-categories). I've contributed to most recent issues associated with it.
The theme has been a clear point of confusion for support request and bug reports. I think giving it a separate theme project will clear up some of the confusion and will take much of the workload away from you in the Drigg issue queue.
On the project page, I will clearly note that the theme was not created by myself, but that I'm simply managing it. You can also have co-maintainer status since you will likely make changes when new drigg functionality calls for it.
I was going request for CVS access and just create the project on my own because I know you are busy, but I want to get you approval first.
I got the idea from trying to fix #340967: Remove Dependency on Extra Voting Forms (Test Alternative Voting Modules) by adding the dependencies[] to the info file of the theme, but unfortunately it won't work: #474684: Allow themes to declare dependencies on modules.
Comments
Comment #1
mercmobily commentedHi,
Having the theme as an external resource is a bit of a pain, mainly because the default theme and Drigg are so tightly connected.
The theme basically only makes sense if used with Drigg. It also means less admin work for me, and the knowledge that the theme is always there. It also makes the creation of drigg_distr.tgz (which I have to rewrite) much harder if the theme is in a different spot. And it makes instalation dependent on two different parts. Hummm...
What if I give you CVS access to Drigg, and you can change the theme from there?
I would be _totally_ happy for you to be recognised as the maintainer/author of the theme. Basically I hacked the theme together paying a professional web developer, so the last thing I want to do is claim any merit for it :D
Please let me know,
Merc.
Comment #2
philbar commentedI had a feeling you might say that.
Co-maintainer will work too. I filled out a CVS access request.
It is my pleasure to take some of the workload off of you. We should have a stable 6.x build in no time.
Comment #3
mercmobily commentedHi,
I can't find your request.
You need to file a request to the Drigg project. Then I have to approve it. And then you should be able to make changes!
I really want a stable D6 version of Drigg ASAP. Otherwise, by the time we finish Digg-like sites will be totally out of fashion.
In fact, they already are. The next step is to make a nice super-distribution with lots of good modules (friendlist, etc.) to create community-style sites...
Merc.
Comment #4
AjK commentedCVS account approved and added to the project.
Comment #5
mercmobily commentedHi,
...? Normally you would have to add a request to me, to get access to Drigg, and then I say yes, and then the infrastructure guys grant it...
Ah, I guess they used this issue as evidence!
Merc.
Comment #6
mercmobily commented