> On Sep 12, 5:38 am, Bartosz R <radaczyn...@gmail.com> wrote: >> Some claim (http://beta.stackoverflow.com/questions/47801) that it is >> not. And so it seems that the last commit was 2 months ago... Can >> anyone clarify?
Cc'ing James Gardner, AuthKit's maintainer. The main problem with AuthKit has been the documentation rather than the code, so I think he's been working mainly on that. The Pylons Book, which he's also writing, contains the latest documentation:
> On Sep 12, 8:38 am, Bartosz R <radaczyn...@gmail.com> wrote: >> Some claim (http://beta.stackoverflow.com/questions/47801) that it is >> not. And so it seems that the last commit was 2 months ago... Can >> anyone clarify?
> a lot of projects have moved to git for active development and just do > an occasional svn commit for a public tagging
I assume you mean mercurial? As for svn as far as I know no one commits there anymore, in fact links are giving 404. if you want to follow all commits the best place will be the RSS from http://knowledgetap.com/hg/
> i don't know that status of authkit itself, but i wouldn't judge a > project by svn activitity anymore
I'm also interested on the status, as far as I know authkit is "complete" but the lack of documentation makes it a big issue as it's such a complex package.
i was just talking about open source projects in general...
a lot of people seem to be leaving subversion for git, or mercurial,
or other more distributed apps, and only syncing to the main svn repo
on a major release
nothign bad about that -- it just makes some projects look inactive
when they're quite active
2 months without an update isn't necessarily a bad thing either. it
often means projects are just being maintained for bug fixes, because
they don't need new features or major reorganizing.
On Fri, Sep 12, 2008 at 1:50 PM, Jonathan Vanasco <jonat...@findmeon.com> wrote:
> i was just talking about open source projects in general...
> a lot of people seem to be leaving subversion for git, or mercurial, > or other more distributed apps, and only syncing to the main svn repo > on a major release
Pylons has moved to Mercurial for Pylons, Routes, WebHelpers, and Ben's other projects. Several other Python packages have also moved to Mercurial because it's really convenient to commit to your local repository, share a tentative patch with somebody for testing, and then push it to the main repository if it's good. The ability to clone repositories during development is also useful; e.g., to test a feature/refactoring which may turn out to be a dead end.
I have stayed away from git because Mercurial is Python, its command syntax is modeled after Subversion, while git is written in C and has a reputation for being uebergeek/hard to use. I don't know of any Python projects using git.
In the Pylons repositories, people do check in minor changes just like they do in Subversion. When enough changes accumulate or the BDFL considers one of them is critical, a release is cut. But note that some packages have multiple repositories:
On Fri, Sep 12, 2008 at 3:45 PM, Mike Orr <sluggos...@gmail.com> wrote:
> On Fri, Sep 12, 2008 at 1:50 PM, Jonathan Vanasco <jonat...@findmeon.com> wrote:
>> i was just talking about open source projects in general...
>> a lot of people seem to be leaving subversion for git, or mercurial, >> or other more distributed apps, and only syncing to the main svn repo >> on a major release
my bad, I though it was a remark regarding pylons.
> Pylons has moved to Mercurial for Pylons, Routes, WebHelpers, and > Ben's other projects. Several other Python packages have also moved > to Mercurial because it's really convenient to commit to your local > repository, share a tentative patch with somebody for testing, and > then push it to the main repository if it's good. The ability to > clone repositories during development is also useful; e.g., to test a > feature/refactoring which may turn out to be a dead end.
Also fast, there is a very nice discussion about this on the turbogears-trunk mailing list, as TG is also moving. If you care to read all the good reasons.
> I have stayed away from git because Mercurial is Python, its command > syntax is modeled after Subversion, while git is written in C and has > a reputation for being uebergeek/hard to use. I don't know of any > Python projects using git.
plus it has (had) a bad integration into Windows, which some people still use :)
> In the Pylons repositories, people do check in minor changes just like > they do in Subversion. When enough changes accumulate or the BDFL > considers one of them is critical, a release is cut. But note that > some packages have multiple repositories:
AuthKit is still being actively developed and still being used. As Mike says, the documentation is the main problem rather than the code. I'll be addressing that after I've completed the Pylons book.
> Cc'ing James Gardner, AuthKit's maintainer. The main problem with > AuthKit has been the documentation rather than the code, so I think > he's been working mainly on that. The Pylons Book, which he's also > writing, contains the latest documentation:
