>> Long live 1.x branch (with a possible fork using an extra-mega-cool brand 
>> name)!
>
> I'm sorry but that seems like an argument of someone that only takes
> from open source.

This was intended to be a humorous way of saying that I will continue
to use the 1.x branch. Sorry if it was not funny :) Anyway, the
friendly fork possibility was raised by Mark and I see nothing wrong
with it (hence the name: friendly).

> why don't YOU go ahead and add support for so in tg2? you have the
> good to go as an external package, lots of TG1 components are now like
> this, tw, catwalk2, repoze.what, etc.

Believe me, if I would have time, I would do it. I know this is the
lousy excuse everyone would give and I don't expect you to take me
seriously at all.

> Your last remark is really bad, the only reason 1.x is present is for
> CP3, in fact I don't think SO is even part of the goals of 1.5

Ouch. That would be really sad, would force me to reconsider my
options. Of course if SO support is dropped also from the 1.x branch,
I'll bite the bullet and migrate to SA (although I see no technical
reason for it for myself, SO works 100% for me).

> That said please stop the FUD, TG on CP people do not want to fork,
> they just want to keep their old apps running.

Again, the forking possibility was raised by Mark and in general a
fork is nothing bad, negative, evil, undesirable, backward, hostile,
etc per se.

I must admit you did manage to get me thinking about this bloody SO ->
SA transition again, even though I decided about 10 times that I won't
do it :)

Cheers,
Daniel




-- 
Psss, psss, put it down! - http://www.cafepress.com/putitdown

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears" 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/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to