On Oct 20, 2010, at 15:33, Dertinger, Matthew wrote:

> 
> Hi Philipp,
> 
>> We are currently co-ordinating the work for STK 1.4 and we will bundle this
>> release with Magnolia 4.4. As the timeframe is very short, this will be a
>> maintenance release and mainly bring updates for the javascript libraries 
>> like
>> jquery, ...
> 
> That's great news about JQuery updates.  :)
> 
>> We could also bundle various sub modules (twitter, youtube, ...) under the
>> main project - twigs in that case.
> 
> I was thinking about this too, I don't want to get too fine grained with sub
> modules, though.  I was thinking of maybe grouping by type - for instance a
> 'social' sub module that would cover features related to twitter, youtube,
> facebook, linkedin, flickr, etc.  I'm very interested to hear ideas about
> how to best structure these sub modules.

I think the right approach is to simply start with one module, split it when it 
becomes "necessary". If I look at the mindmap, "social", "microformats" sound 
like definite "split" candidates, but you might also want to split "API"-stuff 
out at some point.. with refactoring tools and version handlers, it shouldn't 
be too much of an issue ;)


>> Lets co-ordinate the next steps. We could organize a conference call or meet
>> in a IRC channel if you like.
> 
> Yes, sounds like a great Skype call, maybe you can turn your webcam on so I
> can get a view of the Rhein.  I miss it ;)
> 
> Just send me a Calendar invite, whenever it will work best for you. I can
> get up early, although I'd prefer some time during your afternoon or evening
> hours. :)

Will do :)

> 
> Thanks,
> Matt
> 
>> From: Philipp Bärfuss <[email protected]>
>> Reply-To: Magnolia User-List <[email protected]>
>> Date: Wed, 20 Oct 2010 12:05:01 +0200
>> To: Magnolia User-List <[email protected]>
>> Subject: Re: [magnolia-user]  Re: new module
>> 
>> 
>> Hi,
>> 
>>> Yes, that sounds good.  I was actually wondering how much work has already
>>> been done in this regard, since it was on the list of items for STK 1.4, and
>>> it seems that at least there's a Twitter integration paragraph (e.g. On the
>>> Magnolia CMS homepage)
>>> 
>>> Greg, can you shed some light on this?  I looked in Jira, but there wasn't a
>>> Roadmap or Release group for 1.4 yet.
>> We are currently co-ordinating the work for STK 1.4 and we will bundle this
>> release with Magnolia 4.4. As the timeframe is very short, this will be a
>> maintenance release and mainly bring updates for the javascript libraries 
>> like
>> jquery, ...
>> 
>> More features might be developed in STK 1.5/STK 2.0. The roadmap is very 
>> vague
>> and room for collaboration is definitely given.
>> 
>> Anyway I appreciate the approach you are taking. I see the STK main module as
>> the framework on which other more independent/agile modules will base on.
>> 
>>>> I would like to extract these features from a project already implemented.
>>> 
>>> That makes sense.  I'd love to see them.  If you'd like to release them
>>> first in a different module, I understand.
>>> 
>>> Greg, do you have any opinions?
>> 
>> We could also bundle various sub modules (twitter, youtube, ...) under the
>> main project - twigs in that case.
>> 
>> Lets co-ordinate the next steps. We could organize a conference call or meet
>> in a IRC channel if you like.
>> 
>> Cheers
>> - Philipp 
>> 
>> 
>> 
>> ----------------------------------------------------------------
>> 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