Re: [ANNOUNCE] Cheetah Community Edition v2.1.0

Apologies for top-posting on this ancient thread.

It has come to my attention that my Abandoned Project Take-over request
with SourceForge.net has been approved and as of now I have
administrator access to the "cheetahtemplate" project on SourceForge.

I'm on the fence about how to handle the distinction between SourceForge
and GitHub, and I certainly wouldn't mind some suggestions.

Currently I'm thinking development continues via GitHub, and "release"
level stuff is pushed to SourceForge where files and the mailing list
are maintained. I'm not the most active SourceForge user so I'm not sure
what all it has to offer and whether we need it :-P

Suggestions welcome, 2009 is looking like a good year for Cheetah :)

On Tue, Mar 17, 2009 at 03:56:12PM -0400, Michael DeHaan wrote:
> R. Tyler Ballance wrote:
>> On Mon, Mar 16, 2009 at 10:55:03AM -0400, Mike Bonnet wrote:
>>   
>>> R. Tyler Ballance wrote:
>>>     
>>>> I've had a fork of the Cheetah CVS for some time, but this weekend I got
>>>> fed up with a number of outstanding patches not being released into the
>>>> mainline release of Cheetah, so I went ahead and forked it :)
>>>>       
>>> Have you tried contacting Tavis directly, perhaps requesting commit   
>>> access to CVS?  I'd hate to see the project get unnecessarily forked.
>>>
>>>     
>>
>> No I've not emailed Tavis directly, I've not actually seen much trace of
>> him online or in the developer community since early 2008
>> (damnsimple.com still shows a lovely Apache 1.3 install page).
>>
>> If he comes back around and permits me access, I'll certainly merge my
>> changes back into the mainline tree, but I'd likely continue working in
>> GitHub (CVS rots your brane, not even FreeBSD uses it for active
>> development anymore ;)).
>>
>> I don't view forking as a bad thing either, I don't intend to create the
>> "Puma Template Engine" or some other large cat, I only intend on pushing
>> the project along to keep up to date with all the community
>> contributions I've seen over the past year or so (let along 2 years
>> since the last formal release).
>>
>>
>> Open source is supposed to be about the bazaar model of development, and
>> I figure at the very least a Community release of Cheetah will be able
>> to take advantage of that :)
>>
>>
>> I understand your concern, my plans are in the vein of improvement and
>> not fragmentation.
>>   
>
> Ditto what Mike said.   I've added him to this email to save time.
>
> Tavis's last post to the list was 11/08, in general, going missing for  
> that time without a post to the list is not a good thing, and I would  
> like to see Cheetah moving forward.    Hope everything is ok.
>
> (Not sure if the Python 2.6 deprecation warnings got corrected yet --  
> but that's one example of us needing something -- so we can't simply  
> just stop taking updates).
>
> If a fork means bugfixes, great, but let's also make sure things remain  
> backwards compatibile and we have a good answer to list and domain  
> ownership -- where the community needs to migrate if needed -- once we   
> figure out the situation.
>
> --Michael
>
>
>

-- 
-R. Tyler Ballance
Slide, Inc.

------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensign option that enables unlimited
royalty-free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects

_______________________________________________
Cheetahtemplate-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cheetahtemplate-discuss

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAkn2AhUACgkQFCbH3D9R4W//SQCfSfOJyeit+XDLf4h8cunKRRBz
C3gAnRLZsyXbaYHL38rpp9ybWVJc5bc7
=u5Pm
-----END PGP SIGNATURE-----