On 13.03.2015 21:55, Richard Hipp wrote:
On 3/13/15, Warren Young <[email protected]> wrote:
Few organizations have the problem that the full power of Git solves.
And yet many organizations voluntarily take on the problems that come
with using Git. Weird.
Аnyway, Github won that game. In fact it is a good thing - consolidation
of majority of the open source code in one collaborative place, 10x more
compelling to the new generation developers than e.g. late 90's
sourceforge is a phenomenon which greatly accelerates moving the world
forward ...
I hope the next big thing will be another Github for versioning, forking
and merging (i.e. collaboration) on (meta) data, along with the text
artifacts.
And it seems natural this thing to be born here - in sqlite/fossil
community - who other has in depth, first hand expertise in both fields
- structural data handling and versioning?
The semi-structural software/deployment artifacts (traditional service
configurations, devops artifacts like Ansible playbooks,
protocols/interfaces definitions, package recipes - RPM, NPM specs, etc,
etc) all have at least the same impact as the code itself, because they
*enable* the deployment and reuse of already perfectly written code at
the site (managed by not-developer users/admins).
But currently we rely on expressing this kind of information as text
(e.g. YAML in the best case), mostly because we do not have real
versioning/forking/merging mechanism, common place and suitable - well
known schemes for tree/graph sqlite databases as a replacement of the
whole insanity.
Kind regards,
Alek
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
