On Sat, 14 Mar 2015 14:02:18 +0200 John Found <johnfo...@asm32.info> wrote:
> But, for example fossil can provide some way to connect the stand alone > repositories and developers in some kind of distributed peer-to-peer network > and > to provide some interaction - I don't know - maybe some voting, messaging, > clone tracking, collaborative environment, pull requests, whatever will turn > a > heap of independent repositories into mutually connected developers network. > No one is interested, but I will continue a little. :) The first step towards such achievement is to allow all Fossil users to exists in one common username space. OpenID authentication could help to make this without big effort. Another step is to provide some notification mechanism from the cloned repositories to the parent repository - for example, when the user make commit to the cloned repository, Fossil sends notification message to the parent repository. These automatic notifications are not so useful but may serve as a statistics mechanism and as a indicator of the project development. Of course, if the project leader has informations about the changes, he can choose to pull some/all of these changes without waiting the pull request. Even more useful is if the parent repository, notifies the clones about new commits, because the cloned repository might want to merge these changes. But if the cloned repository is not hosted on a web server this can be not easy task. In this case the notification can be made by request from the cloned repository. The ticket system can be used as a distributed messaging engine between developers. Regards -- http://fresh.flatassembler.net http://asm32.info John Found <johnfo...@asm32.info> _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
