Tags:
create new tag
, view all tags

Preface

Just to qualify all this beforehand, I am going through the steps indicated in ReadmeFirst but in the short term, all I'm really looking for is a forum to post code patch suggestions. I was mucking w/ a custom skin and came across the %REVISIONS% variable that I noted I could not format. On investigation, I found the source in TWiki::UI::View.pm labeled w/ SMELL and TODO. So I scrubbed the SMELL and did the TODO while providing the format functionality I was looking for in the first place. I just wanted to share my work, not necessarily become an active contributor, though that may very well happen in the not-so-distant future.

Right, off we go...

About Lucas Smith

Well, given that the Background section should tell you about me, I'll just digress here for a minute or two. I work for Knowledge Learning Corporation (formerly Kindercare Learning Centers Inc before we were acquired). We're currently "trying out" Twiki, but that really means that we're going to be using Twiki until something else falls out of the sky or is mandated from up the ranks. All good by me, as I'm the primary (read: sole) perl hacker here, and I'm perfectly comfortable working in the Twiki framework, and think it has a great future. So far, it's proven to meet our needs quite well. Mind you, we were limping along quite badly in the Collaboration arena until just recently (Forum? What's that?). Right, on with the good stuff...

Background

I've been developing in (mod_)?perl, php, html, css, javascript, etc for going on five years now. I'd say I'm quite good with perl and javascript and likely much better than average with css. </toot>

What I can contribute

I have a penchant for code refinement. If something doesn't work for me, I make it work, and usually clean up a few things along the way. I also enjoy the design portion. It took me 2 days in twiki before I started customizing my own skin.

Concerns ALERT!

As I stated, I work at KLC/Kindercare. I registered an account on twiki.org and now everybody here that visits a page on the twiki site gets the left nav header "Welcome Lucas Smith...". Am I correct in identifying this as IP based identification? Having used IP based ids previously (for a quick hack), I know that it has some pretty critical inadequacies. Especially when DEVELOP access is concerned. I'm requesting ci access for me, not for everybody at KLC smile

-- LucasSmith - 23 Feb 2005

Hey Lucas, why not try posting some patches for a while, just to raise your profile and see how you get on and if the volume gets too high we'll have to force you to check in! hehe!

I'll certainly support you in getting rid of SMELLs in DevelopBranch. I'd love some help in refactoring and cleanups - I sometimes feel like I'm a lonely voice in the wilderness.

Yes, it's IP based ids. There are other solutions, such as SessionPlugin, but on the priniciple that IP ids is the simplest thing that can work, that's the default session memory.

-- CrawfordCurrie - 24 Feb 2005

Sounds good. The big question is: How do I post patches?

Ironically enough, I thought of a better solution than my original fix. Funny how that happens.

I think this could be a perfect solution, given that I don't want my good name marred by my wonderful coworkers (as permitted by the IP ids) smile

-- LucasSmith - 24 Feb 2005

The best way to submit a patch is as a .diff file attached to a ChangeProposal, making sure it's clear what SVN version the patch is against.

Usually creating a checkout area, making your changes, and then doing an svn diff will be sufficient.

-- CrawfordCurrie - 25 Feb 2005

Edit | Attach | Watch | Print version | History: r5 < r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r5 - 2005-02-25 - CrawfordCurrie
 
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by Perl Hosted by OICcam.com Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.