yup, sorry erik - I didn't realize it defaulted to private (used to
github I guess).  It is now public.



Jarrett Chisholm
Prylynx Corporation
/IT should be this simple/

[email protected]
www.prylynx.com
T: (519) 895-0600

On 05/10/12 03:27 AM, Erik Janssens wrote:
> I think your repo is private ?  because I have no permission to
> view it.
>
> On Thu, Oct 4, 2012 at 8:57 PM, Jarrett Chisholm <[email protected]> 
> wrote:
>> oh also, the repo is at:
>>
>> https://bitbucket.org/jarrettchisholm/elixir
>>
>> I pulled from here for the camelot code (hopefully it's the latest...):
>> http://gitorious.org/camelot
>>
>> Also, the url on your camelot site to get the source code doesn't work
>> (at least not for me)...needs to be
>> 'git://gitorious.org/camelot/camelot.git' and not
>> '[email protected]:camelot/camelot.git'. (I think the later requires you
>> to have your ssh public key registered with the project).
>>
>> cheers
>>
>> Jarrett Chisholm
>> Prylynx Corporation
>> IT should be this simple
>>
>> [email protected]
>> www.prylynx.com
>> T: (519) 895-0600
>>
>> On 04/10/12 02:55 PM, Jarrett Chisholm wrote:
>>> Hey Erik,
>>>
>>> Thanks for the reply.
>>>
>>> Yeah that sounds cool.  I'm going to have my local copy point to both
>>> the bitbucket and github repos (I'll push/pull to/from both).
>>>
>>> For getting elixir 'updated' with the camelot code, is it mostly the
>>> stuff in the 'orm' directory that I want to be looking at?
>>>
>>> cheers
>>>
>>> Jarrett Chisholm
>>> Prylynx Corporation
>>> IT should be this simple
>>>
>>> [email protected]
>>> www.prylynx.com
>>> T: (519) 895-0600
>>>
>>> On 02/10/12 01:18 AM, Erik Janssens wrote:
>>>> Hello Jarrett,
>>>>
>>>> Camelot as a whole project is GPL.
>>>>
>>>> However the orm module as it is now in gitorious (not yet released), should
>>>> not be GPL.
>>>>
>>>> I originally started with writing some GPL code to mimic Elixir behavior, 
>>>> and
>>>> later on copied parts of the original BSD code of elixir into them.
>>>>
>>>> The code now more looks like the original Elixir code with some additions 
>>>> of
>>>> mine.  I have no issues with releasing those additions as BSD of course.
>>>>
>>>> So if you want to go ahead with this, simply let me know, and we'll sort it
>>>> out.
>>>>
>>>> Erik
>>>>
>>>> PS : may I suggest bitbucket for cooperation ?  I've used it in some recent
>>>> projects and am happy with it.  Especially the posibility to work with 
>>>> subrepos
>>>> is handy for integration purposes.
>>>>
>>>> On Sun, Sep 30, 2012 at 5:04 AM, Jarrett Chisholm
>>>> <[email protected]> wrote:
>>>>> Hi Eric,
>>>>>
>>>>> I'm sifting through some of the orm code for Camelot (with the intention 
>>>>> of
>>>>> maybe merging some of it into Elixir).  However, I've stopped due to the
>>>>> copyright - it's GPL, not MIT.  I'm not entirely sure about how licenses
>>>>> work and such, but is this kosher?  i.e. with the 2 licenses, is it ok to
>>>>> copy your changes from Camelot into the elixir core?
>>>>>
>>>>> For anyone interested, I put a copy of the elixir source onto github (got
>>>>> the latest version from SVN a couple months ago):
>>>>> https://github.com/jarrettchisholm/elixir
>>>>>
>>>>>
>>>>> Cheers
>>>>>
>>>>> Jarrett Chisholm
>>>>> Prylynx Corporation
>>>>> IT should be this simple
>>>>>
>>>>> [email protected]
>>>>> www.prylynx.com
>>>>> T: (519) 895-0600
>>>>>
>>>>> On 12/09/12 04:48 AM, Erik Janssens wrote:
>>>>>
>>>>> Hello Gaetan,
>>>>>
>>>>> Good to hear from you. It's a pity that you don't do any more
>>>>> database work, we would all benefit from it ;)
>>>>>
>>>>> About the copyright/thanks, those will be added should I release
>>>>> the code of course.  It was my original intention to simply write
>>>>> a compatibility layer for Elixir code to Declarative, but when diving
>>>>> into it I saw the added value Elixir still provides on top of Declarative,
>>>>> and then started to copy/paste parts and unit tests, and it evolved
>>>>> to a modified copy.
>>>>>
>>>>> The original documentation would indeed only need some changes.
>>>>> I've removed things that were marked as deprecated and changed
>>>>> to setup steps a little bit (but those were not documented).
>>>>>
>>>>> Regards,
>>>>>
>>>>> Erik
>>>>>
>>>>> On Wed, Sep 12, 2012 at 10:26 AM, Gaėtan de Menten <[email protected]>
>>>>> wrote:
>>>>>
>>>>> On Wed, Sep 5, 2012 at 10:13 AM, [email protected] <[email protected]>
>>>>> wrote:
>>>>>
>>>>> Hello,
>>>>>
>>>>> As part of the Camelot project http://www.python-camelot.com/,
>>>>> and to migrate our existing applications from Elixir to Declarative,
>>>>> I've reworked Elixir to be a layer on top of Declarative.  Most
>>>>> of the existing Elixir unit tests pass with the new code.
>>>>>
>>>>> Ah! You've done what I dreamed to do but never found the
>>>>> time/motivation to do it (since I don't use Elixir or any database
>>>>> stuff for work, Elixir now competes with many other activities for my
>>>>> free time). My ultimate goal was in fact to clean it up enough to
>>>>> propose it for inclusion into SQLAlchemy.
>>>>>
>>>>> Elixir is still very useful in that way because it's much easier to
>>>>> define relationships with Elixir than with pure Declarative.  Also,
>>>>> it's a good basis to implement custom usage patterns. (which
>>>>> was the original purpose of Elixir)
>>>>>
>>>>> Indeed.
>>>>>
>>>>> This code is now part of the Camelot codebase, but it could be
>>>>> useful for non gui projects as well.
>>>>>
>>>>> So if somebody is prepared to take this code and release it
>>>>> as Elixir 0.8 and do the project maintenance (packages,
>>>>> documentation, etc), I'm willing to cooperate and split this code
>>>>> out of Camelot.
>>>>>
>>>>> Packages is no big deal. Documentation can be but most of the current
>>>>> Elixir documentation should apply. I can't commit any time to Elixir
>>>>> these days for various reasons but I could have some in the future.
>>>>> I'll come back to you if that is ever the case. I had also a few
>>>>> features in my local copy waiting for cleanup and commit but well...
>>>>> no time.
>>>>>
>>>>> If nobody steps in, the code will just remain where it is now.
>>>>>
>>>>> That's a bit sad but perfectly understandable.
>>>>>
>>>>> Any thoughts or ideas ?
>>>>>
>>>>> Just a small deception: I found no trace of any copyright or even
>>>>> "thanks" to the original Elixir developers on your code/modified
>>>>> version of Elixir.
>>>>>
>>>>> --
>>>>> Gaėtan de Menten
>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google Groups
>>>>> "SQLElixir" group.
>>>>> To post to this group, send email to [email protected].
>>>>> To unsubscribe from this group, send email to
>>>>> [email protected].
>>>>> For more options, visit this group at
>>>>> http://groups.google.com/group/sqlelixir?hl=en.
>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google Groups
>>>>> "SQLElixir" group.
>>>>> To post to this group, send email to [email protected].
>>>>> To unsubscribe from this group, send email to
>>>>> [email protected].
>>>>> For more options, visit this group at
>>>>> http://groups.google.com/group/sqlelixir?hl=en.
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "SQLElixir" group.
>> To post to this group, send email to [email protected].
>> To unsubscribe from this group, send email to 
>> [email protected].
>> For more options, visit this group at 
>> http://groups.google.com/group/sqlelixir?hl=en.
>>

-- 
You received this message because you are subscribed to the Google Groups 
"SQLElixir" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sqlelixir?hl=en.

Reply via email to