Merging XMPP SoC branch

Ethan Blanton elb at pidgin.im
Sat Jul 14 11:42:49 EDT 2007


Evan Schoenberg spake unto us the following wisdom:
> On Jul 14, 2007, at 1:21 AM, Ethan Blanton wrote:
> >I think there's a conceptual gap here -- this part of the process
> >isn't something which needs to be documented as "this is how Pidgin
> >development works", at all.
> 
> This is indeed a conceptual gap -- one which most of the Adium crowd,  
> as a subset of the legacy version control crowd, share.

Several of the regular Pidgin developers seem to share it, too; I have
always been of the belief that learning to use your tools properly
pays off many times over in the long run, but not all share my
beliefs.

> I've been following the monotone transition since day 1 on the pidgin  
> (then-gaim) cabal list, and have been using it since the official  
> pidgin transition to monotone.  I have no idea whatsoever how Augie  
> and Andy would go about setting up the distributed-but-shared  
> versioning you describe.  Can you please recommend some reading  
> (preferably more specific than "read the monotone wiki!") for how  
> this works conceptually and practically?

From the monotone tutorial:

http://monotone.ca/docs/Basic-Network-Service.html

and the next page:
http://monotone.ca/docs/Synchronising-Databases.html

These are a good, trivial introduction to getting a netsync server up
and running.  For interaction of only two or three developers,
monotone also supports an ssh method (similar to cvs :ext:), where
someone could just pop up a group-readable database on a shared server
someplace.  (For information about this, see
http://monotone.ca/docs/Other-Transports.html .)

Not to be a smartass, but note that all of these pages are from the
monotone manual, available on monotone.ca and via 'info monotone'.
The first two are in the new-user tutorial.  I *highly* recommend
reading through that tutorial; it's only a few pages, and it will help
start to break down the scars of years using crappy VCS systems.

> (All that said, I have no desire for Adium to become a specialty  
> distributor of libpurple.  I'm willing to have it track im.pidgin.soc. 
> 2007.xmpp temporarily so long as we're propagating from  
> im.pidgin.pidgin regularly and maintaining a soon-goal of a merge of  
> that branch to im.pidgin.pidgin, but in general it, like, Pidgin and  
> Finch, should track libpurple releases.)

I completely agree; we should be endeavoring to make sure that Adium
can use a shipping libpurple.

Ethan

-- 
The laws that forbid the carrying of arms are laws [that have no remedy
for evils].  They disarm only those who are neither inclined nor
determined to commit crimes.
		-- Cesare Beccaria, "On Crimes and Punishments", 1764
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://pidgin.im/pipermail/devel/attachments/20070714/f0dd5e89/attachment.sig>


More information about the Devel mailing list