On Monday 03 Jun 2013 15:35:37 Steve Dougherty wrote: > On 06/01/2013 08:39 AM, Matthew Toseland wrote: > >> SomeDude mentions that the Fossil SCM has things like a wiki and > >> bug tracking already, and asks that the Fred plugin be > >> VCS-agnostic. [2] This is a good thing to do - it would mean adding > >> a layer of semantic abstraction, though it introduces a danger of > >> overengineering. Any easy part of this is adding a "vcs" property > >> in published repository entries. I'm reluctant to try to develop an > >> extension for Fossil SCM instead of patching Infocalypse because: > >> > >> 1) Mercurial already has a Freenet transport through Infocalypse. > >> 2) my mentor ArneBab has experience with Mercurial, Infocalypse, > >> and b. [3] > > > > I suspect it would be difficult, because they work in different ways. > > OTOH Fred is likely to continue using git for the foreseeable future. > > No opinion really. > > SeekingFor may have that covered - see Gitocalypse, which intends to > allow using Infocalypse repos as git remotes. [0]
Maybe so, but they are different enough that for example signed commits, and even signed tags, probably won't work? IMHO signing both commits and tags is especially important on in-Freenet repo's. > >> > >> My proposed design for the first set of changes: > >> > >> Someone's WoT identitiy has "vcs" context. USK@WoT-ID/vcs/ holds an > >> XML file containing in part: > >> > >> <repository > >> vcs="Infocalypse">USK@WoT-ID/reponame/edition/</repository> > >> <repository > >> vcs="Infocalypse">USK@key/reponame/edition/</repository> > >> > >> Pull requests are at USK@WoT-ID/vcs-pull/ > >> > >> <pull vcs="Infocalypse" to="USK@key/reponame/">CHK@key</pull> > >> > >> where fetching the key gives something like a collection of > >> email-formatted diffs. It would be nice for Infocalypse to allow > >> checking this with "hg incoming" or similar. > > > > I hope there will be proper bundles etc. We want this to be > > efficient. > > Ah, yes! This should point to the repo and revision to pull instead. How > about > > <pull vcs="Infocalypse" to="USK@" from="USK@">hg revision hash</pull> > > Instead of full keys maybe it could be a USK hash. Infocalypse already > uses it to refer to repos: SHA1 hash of edition 0 of the USK. That said, > using it would require that the repo be known, so maybe it'd be better > to use full keys for both.
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Devl mailing list [email protected] https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
