Re: [oll-user] Call for initial feedback

[Joseph R. W. <jos...@we...>]

On 03/18/2013 01:06 PM, Urs Liska wrote:
> I have completed a first working version of our site www.openlilylib.org 
> and would like to ask you for feedback before I proceed.

These are still somewhat superficial impressions as I have not had a lot of
brain time free due to work :-(  But here goes:

  -- I would like to see a better clarification of the relationship between
     OLLib and Lilypond proper.  In particular where usability/technical
     tools are provided, why aren't they being pushed directly into LP proper?
     Will they be in future?  How is the development relationship seen for the
     future, e.g. will OLLib be for LP something like what Boost is for C++, a
     testing and review ground where concepts and tools can be refined before
     being standardized?

  -- In respect of the above, how is the rationale different between the toolbox
     and the documentation?

  -- I think it's worth separating out the toolbox and documentation aspects of
     OLLib into separate projects.  Or rather: I would separate tools and their
     immediate documentation, from larger-scale tutorials and manuals.  Separate
     "books" and tutorials should probably be separate Git branches, which
     might be grouped together using submodules.

     Example reason: suppose you have some tutorials which contain in-copyright
     material, and a downstream user wants to easily excise them.  It's MUCH
     easier if they can simply delete a pointer to a submodule, rather than
     having to inherit a complete project history including the copyrighted
     material.

     That could also be a protection for OLLib itself, because in the event of
     a publisher dispute we could just remove the individual git repo of the
     disputed material, rather than having to do messy rewrites of a large
     amount of git history.

  -- Bear in mind that separating as much as possible into separate repos or
     branches is also good because many git commands scale with overall project
     size, hence grouping projects into modules as small as possible helps
     improve the developer experience and the ability of the project to expand.

  -- What's the status of lilyglyphs on CTAN?  Would be good to get it there
     quickly and add a link accordingly.

  -- Ditto musicexamples.