Submitting patches to Cheetah (for fun and profit!)

[R. Tyler Ballance-5]

With v2.2.2 out the door, and thoughts ruminating for what a v2.3.0
would look like, I thought it would be an ideal time to send an email
overviewing some ways in which you can contribute to Cheetah (as mikeb@,
abbeyj@ and a number of others have since I started maintaining
Cheetah).


Since we're using Git as our version control system, there are a few
different workflows that can be used, which offer us greater flexibility
as a community.


GitHub-oriented
===============
Since the "primary" Cheetah repository as well as my "development"
repository are both hosted with GitHub, you can use GitHub as the means
of collaborating and submitting patches to Cheetah.

  1. Create a GitHub account: http://www.github.com
  2. Visit http://github.com/rtyler/cheetah and click the "fork" button
  3. Clone your copy of the repository
  4. <holy-patchwork-batman>
  5. Commit your changes
  6. Push your changes back to GitHub
  7. Visit your Cheetah repo on GitHub.com and click the "pull request"
     button.
  8. Profit!



Mailinglist-oriented
=====================
The means in which Linux/Git itself is developed is through a very
decentralized pulling of patches from a large number of sources,
including their primary mailing lists. You can do this with Cheetah as
well, using the git-send-email(1) and git-format-patch(1) commands makes
it fairly easy. I find this git alias to be very helpful (from my
~/.gitconfig)

        [alias]
                ## Usage: git mpatch <hash> [send-email option]
                mpatch = !sh -c 'git format-patch $0...$0~ --suffix=.patch.temp && git send-email *.patch.temp $1 && rm *.patch.temp'

You can use git-format-patch(1) and git-send-email(1) to mail a series
of patches, my typical usecase is just to mail one patch off, but don't
let that dissuade you from mailing a series :)

This mailing list is fine for mailing patches to as far as I'm
concerned, so you could do:

  1. Clone my development repo: git://github.com/rtyler/cheetah.git
     (you likely want to track the "next" branch and work there)
  2. <holy-patchwork-batman>
  3. Commit your changes
  4. git mpatch HEAD (or other format-patch/send-email magickery)
  5. Profit!!

It's worth noting that copying and pasting a patch file into a mail
client will likely break git-am(1)'s ability to apply the patch, so I
really do recommend trying out git-send-email(1).


If you have any other questions, do let me know.


I'll be sending out a list of what I think v2.3.0 should consist of
likely later this week for community review


Cheers,
-R. Tyler Ballance
Slide, Inc.


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Cheetahtemplate-discuss mailing list
Cheetahtemplate-discuss@...
https://lists.sourceforge.net/lists/listinfo/cheetahtemplate-discuss