Re: How to *hide* a page from the website (and manuals)?
On 02/12/14 16:00, Urs Liska wrote: Am 02.12.2014 16:58, schrieb Paul Morris: Urs Liska wrote I just stumbled over http://lists.gnu.org/archive/html/lilypond-devel/2013-12/msg00187.html and http://lilypond.org/website/gsoc-2012.html I still think it would be best to convert it into a generic GSOC page and start the process of updating it for the next round which will arrive soon enough. Having a persistent page on the website about GSOC signals to any potential future GSOCoders that we're interested (not just for one year but every summer). Sound reasonable but is definitely more work than simply hiding or deleting it. We could ask the mentors listed on that page if they would still be interested in mentoring for 2015, and/or possibly remove their names and replace them with Mentor: to be determined. Just my $0.02 -Paul Added as: https://code.google.com/p/lilypond/issues/detail?id=4215 James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
How to *hide* a page from the website (and manuals)?
Hi folks, I just stumbled over http://lists.gnu.org/archive/html/lilypond-devel/2013-12/msg00187.html and http://lilypond.org/website/gsoc-2012.html I think my first sentence in the thread starter is even more true today. I thought we could *hide* that GSoC 2012 page from the website instead of completely removing it (making it easier to create something new someday). Any opinions? And how would one hide a page instead of deleting it? In any case, I think we can't leave it online in its current state. Best Urs ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: How to *hide* a page from the website (and manuals)?
On 02/12/14 14:28, Urs Liska wrote: Hi folks, I just stumbled over http://lists.gnu.org/archive/html/lilypond-devel/2013-12/msg00187.html and http://lilypond.org/website/gsoc-2012.html I think my first sentence in the thread starter is even more true today. I thought we could *hide* that GSoC 2012 page from the website instead of completely removing it (making it easier to create something new someday). Any opinions? And how would one hide a page instead of deleting it? We could simply put the text in a comment within the TexInfo code that the page is built from. Assuming that is the best way forward, create a tracker and label it accordingly and I'll look at doing that. James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: How to *hide* a page from the website (and manuals)?
Urs Liska wrote I just stumbled over http://lists.gnu.org/archive/html/lilypond-devel/2013-12/msg00187.html and http://lilypond.org/website/gsoc-2012.html I still think it would be best to convert it into a generic GSOC page and start the process of updating it for the next round which will arrive soon enough. Having a persistent page on the website about GSOC signals to any potential future GSOCoders that we're interested (not just for one year but every summer). We could ask the mentors listed on that page if they would still be interested in mentoring for 2015, and/or possibly remove their names and replace them with Mentor: to be determined. Just my $0.02 -Paul -- View this message in context: http://lilypond.1069038.n5.nabble.com/How-to-hide-a-page-from-the-website-and-manuals-tp169135p169142.html Sent from the Dev mailing list archive at Nabble.com. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: How to *hide* a page from the website (and manuals)?
Am 02.12.2014 16:58, schrieb Paul Morris: Urs Liska wrote I just stumbled over http://lists.gnu.org/archive/html/lilypond-devel/2013-12/msg00187.html and http://lilypond.org/website/gsoc-2012.html I still think it would be best to convert it into a generic GSOC page and start the process of updating it for the next round which will arrive soon enough. Having a persistent page on the website about GSOC signals to any potential future GSOCoders that we're interested (not just for one year but every summer). Sound reasonable but is definitely more work than simply hiding or deleting it. We could ask the mentors listed on that page if they would still be interested in mentoring for 2015, and/or possibly remove their names and replace them with Mentor: to be determined. Just my $0.02 -Paul ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
