RasmusPraestholm Would Like to Check-in
Who am I?
I'm a professional IT monkey currently employed for 5+ years in the IT department of an insurance company with a wide range of IT interests. I enjoy automating the heck out of things, finding creative ways to use tools in ways never envisioned, and adopting new tech despite institutional challenges. My main language focus is Java, but I'm flexible and learn fast. I'm happy when organizing things and find no issue too small to do right.
What do I want?
write access to
SVN for the following branches:
Core
wikiplugins
What can I do?
I've been tinkering with Foswiki since before the fork and have made the occasional small contribution like a (very newbie'ish) Kubuntu guide way back, helping organize the fork naming discussion, fixing typos here and there, and dreaming about doing more. I have been maintaining a wiki at my office for about 4 years and am constantly trying to get it more widely used and make it more useful (company is fairly slow at adopting new stuff)
Eventually I'd like to make my hobby startup official and get into wiki and automation frameworks / consulting.
Why do I want to do it?
Over time I have spotted many little doc issues that by my nature cause occasional twitching from the desire to fix. Lots of those are simple typos but also expand into enhancing documentation in general for both core docs. My understanding is that fixing doc for System and various Extension topics is best done in
SVN, thus with access I have one less excuse for not doing it!
Down the road I'd like to get more into Extensions. Currently I'm tweaking an install of
NatSkin and
BugsContrib and I wouldn't mind contributing back doc and sample pages (like a nice tasks section in the left bar for Nat)
I originally signed up for the wiki gnome team, but lost track of where it was going. I guess I still have the urge to gnome around some
I see the two tasks for general doc for 1.1.3 and 2.0, and my one question (general concept) is whether small things like typos should be checked in for 1.1.3 or if it is fully frozen even for doc typos - will a check-in for 2.0 make it to the next patch/minor release? Assuming 2.0 isn't the next released after 1.1.3
Other Notes
Topics I have contributed to
goodness me, yes please - and welcome to the foswiki developers
I've added your 'commit bit'
--
SvenDowideit - 08 Apr 2011