py3k is not that  important to current users
Mike Orr is pretty responsive 
and he answers cheetah queries immediately so i m ccing
good work on the patches they are running well in our production so far
thanks
On Tue, Mar 17, 2009 at 11:21 PM, R. Tyler Ballance <tyler@slide.com> wrote:
On Wed, Mar 18, 2009 at 12:12:23AM -0400, Michael DeHaan wrote:
>>
>> The one nice thing about GitHub in this case is that the Cheetah CE
>> repository is public and anybody can fork (it's encouraged!) off of it
>> in order to create patches. GitHub provides a nice interface for
>> upstream project maintainers to properly incorporate downstream patches
>> from individuals (http://github.com/blog/270-the-fork-queue)
>>
>> That said, I do think it's helpful to post patches to the mailing list
>> for general code review and discuss, but also so everybody is aprised on
>> the specifics of bugs and their fixes as the project moves forward.
>>
>
> Github's calling that "forking" is a bit weird in terms of technology
> (I'd call that a remote branch), but I do love git and
> github does make it easy.
>
> It still does help to have one official "upstream" tree.

I agree, I don't think there's any problem with making my GitHub repo
the "upstream" repository (as opposed to hosting something elsewhere).
The new SourceForge git support is interesting, but GitHub definitely
has made a lot of nice stuff and in short order.

> So sourceforge does have a project takeover process if we need it?

The only thing I found was this:
http://apps.sourceforge.net/trac/sourceforge/wiki/Abandoned%20Project%20Takeovers

I don't intend on pinging SourceForge Support for at least a couple
weeks (not sure what a good wait time is).


I updated the _SiteTemplate.tmpl in www/ and pushed it to the gh-pages
branch which is responsible for this content:
http://rtyler.github.com/cheetah/ (awesome Gimp skill on the logo huh? :))
(I also updated the credits.html to include recent patch contributors)

I've lost motivation for the night to figure out how to generate a new
set of docs for all the TeX files that are responsible for the Cheetah
docs, not knowing TeX has something to do with that I presume. I'd
welcome any help on that from you guys :)


I feel like we should be coming up with an agenda, or at least some
semblance of a list of bugs that need resolving, etc; projects with
goals and TODOs tend to do well. The only two things on my list are
updated/more tests and starting some speed optimizations (we spend some
amount of time filling templates). Other things like Py3k come to mind,
but is Python 3000 even necessary at this point?


Ideally I'd like to get a point release per-month if possible (if there
are changes there to be released).


Cheers
--
-R. Tyler Ballance
Slide, Inc.

------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Cheetahtemplate-discuss mailing list
Cheetahtemplate-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cheetahtemplate-discuss




--
Bidegg worlds best auction site
http://bidegg.com