"Nick Sabalausky" <seewebsitetocontac...@semitwist.com> wrote in message news:jp3oq2$2esa$1...@digitalmars.com... > "Nick Sabalausky" <seewebsitetocontac...@semitwist.com> wrote in message > news:jp3ocp$2e1c$1...@digitalmars.com... >> >> 2. The protocols (ie. either git/hg/etc or better yet a standard >> extension that handles both git and hg) would then incorporate the things >> that github/bitbucket have proven to be commonly useful and franky >> *expected*, like fork-tracking, pull requests, issue tracking, etc. I'd >> imagine this would likely involve special extentions to the git/hg/etc >> repo format. But no matter how this is actually implemented, this would >> be like "libpng" (although it would likely have a standard cmd line and >> web-based interfaces, too - which wouldn't make sence for libpng, but it >> would be essential here). >> > > Sorry, what I meant there was "it would likely have standard cmd line and > web ***API*** interfaces". Ie, not actual web pages, but a web service > protocol, like a REST API, or SOAP (minus the XML, preferably) or whatever > the hell the popular equivalent is these days. ;) >
Or hell, doesn't even have to be web, could be SCGI or a new thing or whatever, just some standardized network protocol.
