Kake L Pugh wrote:
Hello. As people may have noticed, I've been doing some OpenGuides hacking recently.
Yay hay! Excellent! Kake++
I've got a few ideas for more things I might like to do, but I've been holding off slightly since (a) I don't understand how commit access etc works these days, and (b) I have this sort of vision in my head of loads of you all beavering away on stuff, and I didn't want to step on toes or clash with someone else's work.
The theory is that we coordinate this through the dev wiki, with people's home pages carrying their personal todo lists. Granted I haven't updated mine for a long while, but I'm going through lots of personal stuff at the moment.
Do you have acces to trac? If not, prod Dom with an htpasswd.
However, I'm not sure how true (b) is, so I was wondering, if people have a moment, could they write a quick update for the mailing list on what (if anything) they're working on at the moment? I'm sure this would be of interest to people other than me, as well.
Ideally we _should_ all be sharing our code changes with the rest of the OpenGuides community. Unfortunately, there are some extremely forked code bases out in the big wide world, which is making upgrades difficult for some.
I'm a firm believer in a single code base and repository. I'm also a firm believer that the dev wiki is the place to put informtion about what we are working on. I will update my personal todo list before the end of the weekend. I encourage others on list who have accounts on trac to do likewise.
(And if _nobody_ is currently working on anything, this may well prove an incentive for me to get my finger out!)
Probably not the case, but I'll certainly be (re)moving items of mine which say they are in progress, which aren't. Anyway, I don't think there's a hive of activity on OG and Wiki::Toolkit right now, so as far as I'm concerned, go for it.
We had a flurry of activity in December, with the Oxford hackfest and immediatey afterwards.
It may be worth touching base with Dom about any major changes or releases in the pipeline.
Welcome back, we missed you.
Ivor,