This is an appeal from a fellow user, not the core team.
Do
you want to help? I know I do, probably other people do as well. We've made use of TWiki in our homes and businesses, and we
owe it to
each other to give something back.
I don't mean new functionality, as welcome as it usually is. I mean a bit of housekeeping.
From
BugReport it looks as though there are 114 bug reports that nobody has even looked at yet, or at least not decided what to do with them yet. AFAICT only core team members ever look into these problems. The load must be painful! Imagine how that number could come down if a lot more people each had a look into those bugs, and if necessary, generated a patch to fix them? The core team will still own the decision making process on the final outcome of the patch, but most of the time all they should have to deal with is sitting in judgement on, and then applying, ready-made patches. I suspect progress would be a lot faster. Everyone likes to see bugs getting solved!
So, if you have managed to write even a few lines of perl, and have made use of TWiki in the past to further your own ends, then help
pay something back to the community by looking into these bugs. Even non-coders can help by verifying whether bugs still exist in recent releases or not, and assisting in documentation fixes and reviews. Submitters, especially, should make a point of going back and checking on the status of their bugs.
Remember, many eyes make light work! Let's help the
CoreTeam get Cairo out the door!
So what are you going to do?
-- Thanks Crawford for the appeal. Indeed that would help tremendously, to the benefit of the
CodevCommunity 
--
PeterThoeny - 12 Apr 2004
- I'm going to verify that a couple of bugs are still there, and if I can fix them. --
CrawfordCurrie - 12 Apr 2004 - 02:35
- i'll provide a patch for
save content without edit --
WillNorris - 12 Apr 2004 - 22:42
rdf and touchgraph discussion moved to TouchGraph.-- MattWilkie - 26 Apr 2004
- Bounce --
CrawfordCurrie - 28 Apr 2004 - 06:23