I'm not saying that k5 becoming political is bad, but what you are seeing is a side effect of the migration.

If there's a little bit of change rattling around in the bottom of the jar these days, then why not throw a coin or two out to the programmers who have made substantial contributions to scoop?

Or if you've got specific features you want added, then why not offer rewards for them? I'm not suggesting you pay full contract rates, but wouldn't $50 or $100 here and there send a signal that when you work on Scoop, you're not just whitewashing Rusty Sawyer's picket fence?

I'm not a developer, by any means, but I do know a bit about community websites, and I think this Scoop thing is one of the coolest applications I've seen in a long time. I think time will tell that the people who have created this (all of you who have pitched in), have created something quite special, and revolutionary.

So Rusty makes a few bucks, all of you that pitched in along the way can say you were part of the revolution. That'll be much more valuable to your self-worth when you're 90 and reflecting on what you've added to the world in your life. More valuable than a few bucks here and there. Not that a few bucks here and there wouldn't help things along.

If and when I get my Scoop site up and running (a child of WiseNomad.com), I'll know more of what I'd like to see developed and kick in some coin, at least what I can.

At some point, I'll get around to reading Scoop, at which point I'd definitely be interested in contributing.  

I wonder how many other people WOULD contribute, but don't.  

>  Who are you?
My name is Marco :)

> Are you working on Scoop right now? If so,
> what are you doing?

I'm trying to add multi language support.
(Italian, at the moment)

> Have you done some work recently but had to set
> it aside for some reason? If so, would you be
> willing to turn over whatveer you've got to
> someone else, if someone wants to complete it?

I never worked for scoop.

> Are you minimally proficient in perl and have
> some free time? Would you be willing to take
> over someone's unfinished project?

I would like continue to work on the scoop localization.    

I try to describe my solution:    

I have added 3 new VARS:  
 default_lang = default language of the website.    
 enabled_lang = list of languages enabled from the admin.  
 language_list = list of the languages supported by scoop.    

I added a box (language_box) to each template that show the list of the enabled languages (enabled_lang).

When you click on the language (italian, for example) you call a function box that reload the blocks's table for the chosen language and save the selected language in the session data (the names of the blocks tables is: blocks_it, blocks_en etc..).    

Now I'm trying to export all the "language" dependent values from the code to the blocks tables.  

In some cases it's possible to export whole chunk of html from the code to a blocks record, in some cases it's more simple to export only a word/words or a sentence.    

For this reason i've created two new category blocks: words and sentences.    

For the translation of the days of the week and Months I'm thinking that the best solution could be to translate this information with regex expression. Another solution could be to use perl library (like datetime).    

I would like to know what do you think about this.    

P.S.  Sorry for my bad bad bad english