[RFC] teamGIT bonjour support

[Abhijit Bhopatkar <bain@devslashzero.com>]

Hi,

After a long pause in the development, i am back to drawing boards for teamGit.

Ever since i adopted git as my preferred version control system for my
teams, I had this tough time keeping up with every one. Of course this
is a GoodThing(TM) since this means pace of development is rather
good. But it has its usual problems of forcing everyone to religiously
publish _AND_ keep rebasing on main branch every so often. Also my
major problem is that we discover conflicts only _after_ a developer
tries to rebase his work, typically (by design) after he has fully
coded and tested a feature.

The current way to get around this is shouting aloud before you start
working on a new feature/file/section.
However    a. this is not scalable
                b. pron to human errors
               c. pron to inhumane erros and after fights ;).

So in this regards, I have on my drawing boards a rough design to
1. Publish the current selected topic trees info on local lan.
2. Keep track of interesting topic branches and add alerts when
conflicts bet. selected trees reach alarming levels.
3. Possibly later add authentication mechanism to restrict access.

I plan to do this on LAN using bonjour service discovery, and rest
completely being handled inside teamGIT running as a daemon(may be in
widely abused systray?). (Git will handle actual fetch/conflict
checking etc.)
On a side note i also plan to generate daily reports and configurable
notifications.

So I ask you people, is there a solution already cooking someplace?
may be something i can integrate with teamGIT? (e.g. bonjour plugin
for git dameon)
Any thoughts or comment?
Am i just too stupid to not manage it with documented company wide policies?

BAIN