mlhim-owners team mailing list archive

[Luciana Tricai Cavalini <lutricav@xxxxxxxxx>]

What's funny about it is that that idea goes back to the idea of a
pure-python implementation that was abandoned in 2008.
But that's the way things are - sometimes the knowlegde needs some
cycles to move forward.

Lu

Em 06/02/2011 08:33, Tim Cook escreveu:
> On Sat, 2011-02-05 at 23:28 -0200, Joao S. O. Bueno wrote:
>> hI Tim --
>> I am personally +1 for LGPL - it is the license I've been using on my
>> personall other projetcts lately.
>> However, if Oship 2 is built to be used with Plone, we should attempt
>> to Plone's license which is pure GPL.
>> (If it can be factored in an independent Egg which can be used outside
>> Plone as well - that should not matter, though) .
> 
> Hi Joao,
> 
> Thanks for the comments.  I believe that in MLHIM python projects, the
> reference model, will be very framework agnostic.  Though I have started
> with BlueBream to create a template, just to test and exercise the
> classes.  The RM itself shoudl work within any framework that uses
> buildout.  It seems that there is a recipe on PyPI for just about
> everything.  Including various persistence solutions such as MySQL,
> MongoDB and CouchDB ...
> 
> So my plan (always subject to suggestions) is to use only the ZTK
> components required to provide core functionality.  Release the RM as an
> egg and then build OSHIPpy out of the RM and one of the frameworks. 
> 
> This way the RM will work with Plone for HKCR which I believe is a
> logical choice.  
> 
> Thoughts?
> 
> Tim
> 
> 
> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~mlhim-owners
> Post to     : mlhim-owners@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~mlhim-owners
> More help   : https://help.launchpad.net/ListHelp

-- 
Esta mensagem foi verificada pelo sistema de antivírus e
 acredita-se estar livre de perigo.