[Imc-alternatives] okay, what do we have to do to get this to happen?

[Jay]

Strypey,

I absoultely volunteer to be part of the solutionwire clerk team, 
especially having been eager for the solutionswire to exist for so 
many years. :)  I'm running ragged now and can't put quality time 
toward the economic alternatives feature you're suggesting, but it 
sounds like an absoultely essential one to have front and center at 
both our beta site and www.indymedia.org.  If it's still in the works 
in a week or two I should be able to join in that fun.

I like the idea of an online working bee.  You and Dave are in the 
same part of the world so maybe you should set the time to make sure 
it's good for you.  Robbt, whereabouts are you...?
Jay

At 10/11/2008, you wrote:
>Kia ora koutou
>
>Absolutely agree that Alt-IMC is an idea whose time has come.
>
>Jay wrote:
>
> > Dave, when you said you could get something basic up in a day, was
> > that just irrational exuberance (hee hee!) or do you think you may be
> > able to throw something together?  (I know you work more in Plone but
> > my personal sense is that Drupal has less of a learning curve and
> > would be better for our currnet purposes.)
>
>Potential volunteer pool is an important consideration for a 1.0 site
>that is fully harmonized with the new architecture. For a short-term
>beta site, the priority is maturity of codebase. Rob, is a Drupal 6.0
>site, with no modules, going to need some much hacking to support indy
>basics: open-publishing, anonymity, no logs etc? Is a Plone site, Dave?
>If we are going to choose one or the other, which has the greatest
>number of the features we want, working, right now?
>
>However, if our eventual goal is to be part of the distributed
>architecture, it makes sense to me to build even the beta site in a way
>that totally separates database from front-end. So, could we have both a
>Drupal front-end and a Plone front-end with some kind of cms-agnostic
>database that's shared (or two of them that mirror each others entries)?
>
>Each feature we want could be incorporated from whichever codebase
>currently implements it best. Because we're are using the same taxonomy
>(which could also be part of a mirrored database), and if we use open
>standards or defining microformats (or whatever) for information
>sharing, it shouldn't be hard to cross-data over between the two
>front-end engines if we need to, right? Give them the same style sheet
>(with appropriate tweaking) and it'll all seem like one site, right Nick?
>
>I suggest we have an online working bee, set a date and time at least
>4-5 of us can make it for a few hours, connect on irc, exchange pgp
>public keys, divvy up tasks, exchange any passwords we need to do our
>chosen tasks, and make it happen! I'm busy the next two days but any
>time after that I could put in some hours.
>
>Also, can we have some volunteers to be solutionswire clerks, and
>feature editors, for the beta site? I'll put my hand up for features and
>some clerking. I agree that the existing alternatives features forms the
>basis of the introductory feature, and provides a beta taxonomy. Perhaps
>content-orientated volunteers (if the droning tech talk hasn't put you
>to sleep ;) could collaboratively confirm the taxonomy, subedit the
>text, and check the links ready to go up as the first content of the
>beta when the techs get it live?
>
>Onwards and upwards!
>Strypey
>
>--
>BTW Fight the 'Anti-Counterfeiting Trade Agreement'!
>http://indymedia.org.nz/newswire/display/76066/index.php
>
>"Whether gods exist or not, there is no way to get absolute certainty
>about ethics. Without absolute certainty, what do we do? We do the
>best we can."
>- Richard Stallman
>http://www.gnu.org/philosophy
>
>http://www.creativecommons.org.nz
>http://www.indymedia.org.nz
>_______________________________________________
>Imc-alternatives mailing list
>Imc-alternatives at lists.indymedia.org
>http://lists.indymedia.org/mailman/listinfo/imc-alternatives