Respectful Git mailing list readers. I was encouraged to "Ask the Git community directly" as is writtein the www.git-scm.com site. == Disclaimer This is not a trolling post or suggestion of something that is not finished. The technology that I'm "lightly" referring as industry breakthrough exists. I just happened to find out that Git (alongside with social coding sites such as Gitorious and GitHub) already fills up the repository and distribution technology that the "abstractions" require. Please do not let the current platform examples fool you; our technology base was on Microsoft's stack, yet this technology is totally platform agnostic. This however means that the material is nonexistent on Linux technology demos (although there are solid demonstrations available for Microsoft's stack). I have tried to approach Linux community (through Linux Foundation, LDN and finally www.linux.com, but I have failed to meet any centralized point to help us figure out Linux development - we know our technology, but we need help getting reference implementations on Linux common languages to be able to abstract them). == End of Disclaimer. Now in brief; I claim that software development can be trivialized (and its efficiency boosted) to absolute maximum. The technology is ridiculously simple stack on top of existing technologies (it's moreover a methodology). It is by its very nature completely open and completely free, platform agnostic. Usable by anyone; learning curve is really simple (considering the learning includes understanding how to define the architectural design and include reference implementation within it). The thing that Git solves perfectly is described in this visualization: http://abstraction.codeplex.com/wikipage?title=Subscribing%20to%20Reference%20Abstractions&referringTitle=Documentation The full technology case theory, key differentiators and examples (although light with videos) can be found: http://abstraction.codeplex.com/documentation The absolutely trivialized software development is presented in the documentation's first link's video followed by visualization of multilevel abstraction stack - I know this does not open properly without any hands-on experience on abstractions. I am very willing and happy to discuss how this can be applied to Linux (both applications and kernel) development, as it is applicable to anything that needs documentation and structured implementation of any size. This technology brings Linux in-par and way beyond of Windows in end-developer experience; and allows huge advantage in Linux because of its versatility (that no longer needs to be sacrificied for solid-base for developer experience). However in this post I am simply asking help to understand Git properly, so that I can design the distribution mechanism (updating both ways) and for example understand the way of making statistical calculations (so that any individual abstraction-provider can be ranked in terms of follow-up "repository forks"). Please apologize my newbieness in mailing lists and groups, as I have just entered the world of open-source-development. Happy spring from Helsinki, Finland, Kalle Launiala -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html