I've completed named repository pull support. This means a list of WoT-enabled repositories is inserted under the identity whenever such a repository is created or pushed. For instance, my repo listing is: [0]
<vcs version="0"> <repository vcs="Infocalypse">USK@pxtehd-TmfJwyNUAW2Clk4pwv7Nshyg21NNfXcqzFv4,LTjcTWqvsq3ju6pMGe9Cqb3scvQgECG81hRdgj5WO4s,AQACAAE/wiki_hacking.R1/6</repository> <repository vcs="Infocalypse">USK@pxtehd-TmfJwyNUAW2Clk4pwv7Nshyg21NNfXcqzFv4,LTjcTWqvsq3ju6pMGe9Cqb3scvQgECG81hRdgj5WO4s,AQACAAE/pyProbe.R1/10</repository> </vcs> This means that on LCWoT one could fetch my wiki_hacking repository, set up Mercurial to use its version of Infocalypse, then fetch pyProbe with mkdir pyProbe; cd pyProbe; hg init; hg fn-pull --wot operhiem1/pyProbe. WoT support depends on issue #5729 [1] or implementing a workaround. Next week I plan to work on pull requests. Thoughts: * Freemail is excellent at getting messages between identities. * Pull requests are ideally more widely visible to allow review. * Wide visibility in WoT is hard. (Reading everything does not scale!) Would it be sufficient to allow people to mark identities to follow for pull requests? Should it be easy for repository owners to publicize the existence of a pull request? What about the people making the pull request? From my limited understanding of PSKs it seems like a PSK-per-project would be useful. Too bad they don't exist yet. I'm having oral surgery on Tuesday, and my mentor ArneBab is returning from vacation Wednesday. Eek. Thanks, operhiem1 [0] USK@pxtehd-TmfJwyNUAW2Clk4pwv7Nshyg21NNfXcqzFv4,LTjcTWqvsq3ju6pMGe9Cqb3scvQgECG81hRdgj5WO4s,AQACAAE/vcs/1 [1] https://bugs.freenetproject.org/view.php?id=5729
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Devl mailing list [email protected] https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
