Re: tweet or http://lilypond.org/productions.html

[James]

Hello,

On 15/12/13 13:43, David Kastrup wrote:
> James <address@hidden> writes:
>
> > Hello,
> >
> > I tried to look back on the old discussions when we set up the
> > Pondings and I am not sure where the tweet/web line should be drawn
> > (if it should be drawn at all).
> >
> > That is the tweet is I assume going to be rather ephemeral whereas the
> > website is going to be around for a while in terms of being
> > search-able. So for example David K added a Ponding recently:
> >
> > http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=49eb1b3eab84975c67613986c65f60f731c9818b
> >
> > Which is great but I see no reason why this would not be better served
> > in the 'productions' part of the website.
> Basically it was to avoid making a more definite decision.  It may well
> be that it belongs in some of the more permanent sections ultimately.
>
> I'm trying not to drop too many balls, so I decided to do at least
> something.

Well I am starting to go back through this kind of doc/tracker stuff and 
get back to committing. So you don't have to worry.

My only issue with the pondings is it looked like there was some more 
'syntax' I had to learn for the xml stuff. I can handle tags but the 
other special character stuff looked tiresome.

> > Are there any strong opinions?
> Well, my strongest opinion is that anything I need not bother with helps
> me focus on things I am better at.
Quite.

> We have some rules due to our being
> a GNU project: we don't want to advertise non-free software or services
> based on similar lock-ins.  So anything deserves a close look before it
> is placed in our more permanent sections.  Also one should try not
> having too many dead links...
Normally I check all the links each time I visit this page (I did a load 
of link clear up last time) so that shouldn't be a problem. They will 
get caught.

I guess my own take is it can be on both, but for things 'books' that 
are really published that other people can get to (possibly many years 
later) that they are better served long term in the productions section.

However I can see now why your commit was made into a Ponding and why 
Phil suggested it for

http://code.google.com/p/lilypond/issues/detail?id=3657

Than productions.

James