Hi all, I'm afraid I still haven't read the thread discussing LTS and the clusterf.... resulting from a typical SMW/SF install requiring about 20 independently maintained but interrelated extensions (it's always going to be hard!).
On this topic two ideas came to mind: 1) Would adopting this kind of branching model (if it isn't already) help to improve maintaining stable branches: http://nvie.com/posts/a-successful-git-branching-model/ 2) What can we learn from Drupal development, where multiple modules are integrated via extensive use of APIs? Speaking as a dumb user, can we start a 'developer documentation' page on smw.org? I know it's a pain in the neck, but explaining design decisions to newbs has many long term advantages, not least, forcing the logic to be explicit helps it to be reviewed 'internally' (by the developers concerned) and useful ideas may be generated 'externally' (by the wider community). Making developer documentation should help attract new developers as well as help users to understand dependencies. Cheers, Dan. ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may _______________________________________________ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
