On Oct 18, 2010, at 16:22, Dertinger, Matthew wrote:

> Hi Maurizio,
> 
> Yes, what you are talking about is the intent of the Twigs project.  There's 
> a mindmap started if you'd like to take a look 
> <http://mind42.com/pub/mindmap?mid=9aca75ce-f8c6-4e58-bef3-c9a44a2306bc>.  
> Also, feel free to edit or post comments to the Wiki page 
> <http://wiki.magnolia-cms.com/display/WIKI/Magnolia+Twigs+Module>.  If you'd 
> like to contribute to the project I'd love to have you're help. If you're not 
> yet set up as a Magnolia Contributor 
> <http://documentation.magnolia-cms.com/contribute.html#WriteCode>, you may 
> need to do that, but I'm not sure whether it applies to Forge projects.  
> Greg, could you provide feedback about this?

The CLA is not needed for forge projects, Magnolia Intl. does not own CI over 
them.

Maurizio will need to be registered as a developer for the project to be able 
to commit etc though; let me know.

> As for the name choice, I was originally going to call it STKX, as a sort of 
> homage to the band, Styx <http://en.wikipedia.org/wiki/Styx_%28band%29>, but 
> alas, Greg thought it might be too confusing to have an STK, ETK, and a STKX. 
>  So stepping down from STKX to Twigs seemed an appropriate solution.  
> Besides, part of the intent of the project is to be an incubator for features 
> that could eventually find there way into the STK.  So a twig grows into a 
> stick.

:)

> 
> Thanks,
> Matt
> 
> > From: Grégory Joseph <[email protected]>
> > Reply-To: Magnolia User-List <[email protected]>
> > Date: Mon, 18 Oct 2010 14:52:01 +0200
> > To: Magnolia User-List <[email protected]>
> > Subject: Re: [magnolia-user]  new module
> > 
> > 
> > Hi Maurizio,
> > 
> > Sounds like its quite close to Matt initiated with the "Twigs" project ? 
> > (I'll 
> > let him expand on the name choice, although I *think* i have an idea;))
> > 
> > http://wiki.magnolia-cms.com/display/WIKI/Magnolia+Twigs+Module
> > 
> > On Oct 18, 2010, at 11:42, Maurizio wrote:
> > 
> >> 
> >> Hi all,
> >> I would like to know who will be interested in creating a new Magnolia 
> >> module 
> >> in order to extend / increase STK and Magnolia basic paragraphs / controls.
> >> The following can be a basic list of features I’m interested in:
> >> - Social paragraphs (Twitter, Flickr, Facebook, Youtube...)
> >> - Google Maps controls (single marker, multiple marker with clustering, …)
> >> - Meteo / Weather paragraphs, in order to show weather forecasts – 
> >> situation
> >> - …
> >> - … (what do you expect here? Let’s discuss!)
> >> 
> >> For the first points I have the possibility to port what I’ve done in a 
> >> real 
> >> projects into a generic and reusable way, but I would first know:
> >> 1) If there is someone interested in..
> >> 2) If other people have done something like this (I hope yes..) in real 
> >> projects and want to share their work/ideas
> >> 3) If Magnolia itself, in Basel, is going to increase STK library in this 
> >> (or 
> >> similar) way.
> >> 
> >> What do you think?
> >> Maurizio
> >> 
> >> 
> >> 
> >> ----------------------------------------------------------------
> >> For list details see
> >> http://www.magnolia-cms.com/home/community/mailing-lists.html
> >> To unsubscribe, E-mail to: <[email protected]>
> >> ----------------------------------------------------------------
> > 
> > 
> > 
> > ----------------------------------------------------------------
> > For list details see
> > http://www.magnolia-cms.com/home/community/mailing-lists.html
> > To unsubscribe, E-mail to: <[email protected]>
> > ----------------------------------------------------------------
> > 
> 
> 
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------



----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to