Re: [oll-user] Call for initial feedback

[Urs L. <ul...@op...>]

Am 20.03.2013 12:41, schrieb Janek Warchoł:
> Hi Urs,
>
> 2013/3/18 Urs Liska <ul...@op... <mailto:ul...@op...>>
>
>     Hi all,
>
>     I have completed a first working version of our site
>     www.openlilylib.org <http://www.openlilylib.org>
>     and would like to ask you for feedback before I proceed.
>
>
> Congratulations!
> I have to admit i'm a bit confused as to what goes where:
I think it actually _is_ somewhat confusing, as I've always found that 
somewhat confusing with SourceForge project that I just visited.
So I'll try to clarify as best as I can:

I have set up three projects on *_SourceForge_*:

  * *openLilyLib* (http://sourceforge.net/projects/openlilylib/)
    This contains OLLib (the 'LilyPond library' part) and the tutorials
    library
  * *musicexamples* (http://sourceforge.net/projects/musicexamples/)
    LaTeX package to manage music examples
  * *lilyglyphs* (http://sourceforge.net/projects/lilyglyphs/)
    LaTeX package to include notational elements in LaTeX documents

Initially I had set up the second and third project as 'subprojects' to 
the first one, but that didn't really work - I have the impression this 
is quite buggy on SourceForge's part.
Actually I didn't even seem to succeed deleting these subprojects, so 
they are still there in the main navigation of the openLilyLib project.

I have separated the three parts in separate Git repositories because a) 
I found that development of them is quite separate and b) someone 
interested in cloning one of the parts doesn't have to get everything.
The downside is that there are dependencies, especially for 
collaborators authoring LaTeX documents: Everyone who wants to compile 
any of the documents with the openLilyLib document class has to have all 
three packages installed.
So it might be more consistent to have everything in one Git repository 
after all. Then everybody who clones that repository has everything 
available he needs (and only has to configure some paths/symlinks).
Unfortunately I don't know how to merge Git repositories. I have read a 
few guides on how to do it, but it seems quite non-trivial to preserve 
the history and not to run into path conflicts (commits pointing to 
wrong file locations).
If that would be possible, we could have one SourceForge project only, 
which would be less confusing probably.

######################

Each of the current projects has the following menu items on its project 
page:

  * *Summary*
    Overview, Screenshots, Features
    -> SourceForge's entry page for any project
  * *Files*
    Download area (although only 'musicexamples' has a file release here
    so far)
  * *Reviews* (automatic and not influencable)
    Structure for user reviews
  * *Support* (automatic)
    (Details below)
  * *Code*
    Access to the Git repository

*openLilyLib*, the main project, has the following menu items in addition:

  * *Blog*
    I'm not sure if we really need one, but SourceForge strongly
    encourages that in order to expose a project's activity and make it
    more visible to the SourceForge community
  * *Tickets*
    The issue tracking system.
    It is quite configurable, but I don't have understood it fully yet.
    Tickets for all part-projects are collected here, with a field to
    assign the ticket to one of the projects.
  * *Mailing Lists*
    Currently there is only this one (openlilylib-user).
    I'm not sure if we should have separate public and private (-dev)
    lists, or separate lists for the subprojects. But probably there
    won't be too much traffic in the foreseeable future anyway, so we
    might stick with the existing single list.
    (-> Thoughts and suggestions welcome)
  * *Discussion*
    Configurable forums.
    I'm not sure if we need this or should concentrate the communication
    on the mailing list.
    The advantage I see with forums is that it significantly reduces the
    step for externals to actually expose themselves and post something.
    And it is more likely for interested people to browse a forum than
    the archives of a mailing list.
    The disadvantage is that it might be somewhat dissociated to have
    information partly in forums and a mailing list.
    (-> Thoughts and suggestions welcome)

*musicexamples* and *lilyglyphs* only have:

  * *Wiki* (with only one page)
    This states the relation between the (sub) project and the whole
    family and provides links to the relevant information.
    Maybe I should also add such a single Wiki page to openLilyLib?

#######################

Any SourceForge project has a *Project Web* space that can be populated 
individually through file upload. Until now they offered "Hosted Apps", 
a selection of Wiki or CMS application, but that is right now being 
discontinued.

I use "stacey", a tiny PHP framework, to manage the content in this web 
space.
Content can be edited in text files, using Markdown for formatting, HTML 
if that isn't sufficient, and some variables that are implemented 
through stacey.

I only use the project web space for openLilyLib and have configured it 
so that the domain www.openlilylib.org points to that project web space.
So we have a web site with our own domain that is actually hosted at 
SourceForge.
This web site contains an introduction to the project and an overview of 
the different subprojects.
For file downloads, tickets and discussion we only link to SourceForge, 
but we provide the current manuals (the 'musicexamples' page is a quite 
good example ATM).
How this web site will evolve we'll see over the time. It might remain a 
kind of 'business card', a mere entry point to the SourceForge project 
pages. Or it could evolve to something bigger, I have no idea so far.
However, the tutorials will be presented here, and this will probably 
the most prominent part of the web site, as it will have a larger number 
of pages (one for each tutorial).

############

So, this was quite lengthy, but I hope i clarifies the context a bit ...

> are the parts (OLL, lilyglyphs, ...) each in a separate git 
> repository; what's the connection between sourceforge and 
> openlilylib.org <http://openlilylib.org> (what can be found where).
> But maybe i just need to use it for some time.
>
>     My next steps would be to personally invite a selection of people to
>     participate in the project and after that send an email to
>     lilypond-user
>     presenting the project and ask for collaboration.
>
>
> +1
And one of the most important issues is to prepare a first file release 
of OLLib, however incomplete this will be.
For that we (I) have to fixate the 'entry point' strategy (I will have a 
closer look at how Jan-Peters lalily (https://github.com/jpvoigt/lalily) 
does this and see how I can apply/transfer the concept. Then that first 
stage has to be documented.
I think it is important to have OLLib as a file release early, even if i 
only contains a small number of functions. But that will enable us to 
show what it actually is (and can become) to attract users, feedback and 
collaborators.

Best
Urs
>
> best,
> Janek

-------------- next part --------------
An HTML attachment was scrubbed...