Re: moving LilyPond blog to our website
Hi Janek, all, this blog is a very good idea! I will follow it regularly. I also like your approach: Just do it, now. The discussion coming up here is quite expected, I would say, and it is also what prevented such a blog to be created before. If there is a chance to integrate it in the LP website, that would be nice. But if it was my time and energy, I would skip the discussion, keep the enthusiasm and go for an independent setup - with a link or some forward mechanism from the main website, if possible. (Just one more opinion in this thread.) The possibility to comment is nice. This blog was a missing part in the LP world, imho. Once I can find some more time, I would like to write an article. But unfortunately not this summer. Btw, there seems to be a syntax highlighter for wordpress: http://speckyboy.com/2009/02/19/12-wordpress-plugins-to-display-and-highlight-code-within-your-blog/ Cheers, Joram ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: moving LilyPond blog to our website
2013/6/5 Shevek s...@saultobin.com: Have you considered using a Jekyll based CMS? I've heard about Jekyll but i have no experience with it. If there's someone familiar with Jekyll who thinks that it'd be a better choice (and would help with transition), we can discuss it. As for now i see that Wordpress provides everything i need and seems to work. (sorry if that sounds brusque - i'd love to have time to discuss and consider everything, but alas, i'm too busy :( ) best, Janek ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: moving LilyPond blog to our website
On Wed, Jun 05, 2013 at 11:19:01PM +0200, Janek Warchoł wrote: As for now i see that Wordpress provides everything i need and seems to work. I have no personal experience with wordpress, but I heavily recommend wordpress / google blogger / identi.ca / any pre-made blog-hosting system, rather than trying to handle the technical sutff manually. - Graham ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: moving LilyPond blog to our website
Hi Joram, 2013/6/5 Noeck noeck.marb...@gmx.de: Hi Janek, all, this blog is a very good idea! I will follow it regularly. I also like your approach: Just do it, now. The discussion coming up here is quite expected, I would say, and it is also what prevented such a blog to be created before. thanks, that's very encourageing! If there is a chance to integrate it in the LP website, that would be nice. But if it was my time and energy, I would skip the discussion, keep the enthusiasm and go for an independent setup - with a link or some forward mechanism from the main website, if possible. (Just one more opinion in this thread.) It seems there may be an easy way to handle this. I'll write about it in another email, to keep things separate. The possibility to comment is nice. This blog was a missing part in the LP world, imho. Once I can find some more time, I would like to write an article. But unfortunately not this summer. Great! Of course, you're invited to write short, informal posts as well if you'd like (for example, your cheat sheet is a very good topic for a blog post, short or long). Btw, there seems to be a syntax highlighter for wordpress: http://speckyboy.com/2009/02/19/12-wordpress-plugins-to-display-and-highlight-code-within-your-blog/ i'll try to check it in a free moment. The plugin i tried had support for highlightning several languages but not lilypond, and i didn't see an option to add custom rules. thanks! Janek ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: moving LilyPond blog to our website
- Original Message - From: Janek Warchol janek.lilyp...@gmail.com To: Federico Bruni fedel...@gmail.com; LilyPond Users lilypond-user@gnu.org; Jacques Menu jacques.m...@tvtmail.ch; Paul Morris p...@paulwmorris.com; Jan Nieuwenhuizen jann...@gnu.org; David Kastrup d...@gnu.org Sent: Tuesday, June 04, 2013 9:55 AM Subject: moving LilyPond blog to our website Hi all, it seems to be decided that we're moving the blog to our website (i.e. to be hosted on lilypond.org), and we're doing it asap, because as Paul said: I don't think we've agreed anything of the sort. People have requested it, but nothing more. Who is going to get admin permission on lilypond.org to administer this? -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: moving LilyPond blog to our website
Am 04.06.2013 10:55, schrieb Janek Warchoł: Hi all, it seems to be decided that we're moving the blog to our website (i.e. to be hosted on lilypond.org), Makes sense to move away from a commercial provider. and we're doing it asap, because as Paul said: Installing WordPress is a one click operation. Don't forget to remove install.php and readme.html for security when it's done. To backup the site, export the database structure and data, which is easily done with cron, and rsync the folder contents elsewhere. Please discuss! Janek ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user 2013/6/4 Paul Morris p...@paulwmorris.com: people will link to it, and the longer you wait to move it, the more broken links you create +1. There already are links which will be broken. As i see it, there are a few decisions we have to make: 1) are we going to use WordPress or something else, for example Mezzaine: 2013/6/3 Federico Bruni fedel...@gmail.com: Another option could be Mezzanine, a CMS based on Django which has many built-in features (including blogging). Considering that many lilypond developers know python, it could be a wise choice in case we need to hack on it. Mezzanine has some scripts to import from other CMS (Wordpress included): http://mezzanine.jupo.org/docs/blog-importing.html ? (my vote is with Wordpress, but i really have no experience apart from last few days) The fundamental question is whether to host the blog on a 'live' (i.e. php based) system or with a static site generator. What are the capabilities on the lilypond.org server (wrt installed programs and performance)? lilypond.org is (currently) a statically served web site. I think using a static site generator isn't really an option because any update would have to be compiled and uploaded by someone with the necessary write access. But we first should know whether lilypond.org actually can serve a Django or PHP based site. WordPress seems to be a quite 'big' application so there would be much overhead. OTOH the fact that it is quite comfortable to use makes it a good choice when we actually want to use it (and not to be busy configuring and maintaining it). Of course Python would be a good thing, but PHP isn't hard to hack either. 2) what the precise address/location should be? Paul suggests: 2013/6/4 Paul Morris p...@paulwmorris.com: Ideally it could be at www.lilypond.org/blog/ on the lilypond.org domain and to some extent integrated into the main LilyPond website. (i.e. make it easy to navigate back and forth between the two sites seamlessly) (another option could probably be blog.lilypond.org, but i have no idea whether that's a purely cosmetical choice or has some implications.) I think I'd prefer lilypond.org/blog because it's consistent with the other menu entries. But a subdomain could be more straightforward when it comes to running a live web application. A subdomain can also be transparently mapped to another service provider if the lilypond.org server doesn't provide the necessary infrastructure. As for the integration, i think that the blog should be accessible as an item in the top menubar (I.e. next to Introduction, Manuals, Download and Community). +1 We could also modify the Pondings box to point to the newest or a random blog post (of the 'productions' category). (That's a redundancy anyway, and if we host the blog on lilypond.org we should sort it out). If we go for WordPress, Jacques Menu showed a starting point. Jacques, i count on your help as well! :) There is no way i could do this alone. 2013/6/3 Jacques Menu jacques.m...@tvtmail.ch: Hello, I've switched from CMS Made Simple (lives up to its name) to WordPress for its power and rich set of plugins. Using 3.5.1 and a child of the new twentytwelve template makes browsing on phones and templates much more practical (you can check with http://gioiacantar.ch). You'll need: - write FTP access to the folder hosting the site; - a dedicated MySQL database; - PHP activated; - ability to run cron tasks. As mentioned above this would be crucial. So someone involved in the hosting should check and clarify . Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: moving LilyPond blog to our website
Am 04.06.2013 11:24, schrieb Urs Liska: I think I'd prefer lilypond.org/blog because it's consistent with the other menu entries. But a subdomain could be more straightforward when it comes to running a live web application. A subdomain can also be transparently mapped to another service provider if the lilypond.org server doesn't provide the necessary infrastructure. Am 04.06.2013 11:21, schrieb Phil Holmes: Who is going to get admin permission on lilypond.org to administer this? Mapping blog.lilypond.org to another server/provider could also be useful for this issue. Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: moving LilyPond blog to our website
Hi, 2013/6/4 Phil Holmes m...@philholmes.net: - Original Message - From: Janek Warchol it seems to be decided that we're moving the blog to our website (i.e. to be hosted on lilypond.org), and we're doing it asap, because as Paul said: I don't think we've agreed anything of the sort. People have requested it, but nothing more. I apologize if that sounded like i'm trying to enforce something. That's not my intention; i'd just like to get things done asap (and i don't imagine why anyone would oppose moving the blog to our website). Who is going to get admin permission on lilypond.org to administer this? I can if that's necessary. How do i get them, and is there anyone who has them already? best, Janek ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: moving LilyPond blog to our website
- Original Message - From: Janek Warchoł janek.lilyp...@gmail.com To: Phil Holmes m...@philholmes.net Cc: Federico Bruni fedel...@gmail.com; LilyPond Users lilypond-user@gnu.org; Jacques Menu jacques.m...@tvtmail.ch; Paul Morris p...@paulwmorris.com; Jan Nieuwenhuizen jann...@gnu.org; David Kastrup d...@gnu.org Sent: Tuesday, June 04, 2013 12:33 PM Subject: Re: moving LilyPond blog to our website Hi, 2013/6/4 Phil Holmes m...@philholmes.net: - Original Message - From: Janek Warchol it seems to be decided that we're moving the blog to our website (i.e. to be hosted on lilypond.org), and we're doing it asap, because as Paul said: I don't think we've agreed anything of the sort. People have requested it, but nothing more. I apologize if that sounded like i'm trying to enforce something. That's not my intention; i'd just like to get things done asap (and i don't imagine why anyone would oppose moving the blog to our website). Who is going to get admin permission on lilypond.org to administer this? I can if that's necessary. How do i get them, and is there anyone who has them already? best, Janek I have them, because I need them to upload the website. However, I honestly don't think it's a case of just asking someone and admin being given. As others have said, what about the load on the server? Will there be any other effect. I'd suggest trying to involve GP before assuming this will automatically happen. -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: moving LilyPond blog to our website
Am 04.06.2013 10:55, schrieb Janek Warchoł: If we go for WordPress, Jacques Menu showed a starting point. Jacques, i count on your help as well! :) There is no way i could do this alone. 2013/6/3 Jacques Menu jacques.m...@tvtmail.ch: Hello, I've switched from CMS Made Simple (lives up to its name) to WordPress for its power and rich set of plugins. Using 3.5.1 and a child of the new twentytwelve template makes browsing on phones and templates much more practical (you can check with http://gioiacantar.ch). You'll need: - write FTP access to the folder hosting the site; - a dedicated MySQL database; - PHP activated; - ability to run cron tasks. Installing WordPress is a one click operation. Don't forget to remove install.php and readme.html for security when it's done. To backup the site, export the database structure and data, which is easily done with cron, and rsync the folder contents elsewhere. In theory I can offer to host that on my webspace. I (still) have enough storage available, can set up a ftp access point restricted to the blog, have PHP and MySQL and also can run cron jobs. I can't guarantee this to be a permanent offer, but as it seems it should be possible to move the site if necessary. I'm not sure though if/how it's possible to transparently redirect the browsers from lilypond.org so it looks like being hosted on lilypond.org/blog or blog.lilypond.org. Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: moving LilyPond blog to our website
Janek wrote: 1) are we going to use WordPress or something else, for example Mezzaine: I have no experience with Mezzanine, but I found this helpful comparison with WordPress from a Mezzanine users forum: http://grokbase.com/t/gg/mezzanine-users/12byf39adw/wordpress-vs-mezzanine It sounds like Mezzanine is great if you have a Python/Django developer who can administer it and especially if you want to do more than blogging with your site (i.e. web applications). On the other hand, WordPress requires less developer effort, has fewer dependencies, and works well if you just want to do a blog site (i.e. _not_ web applications). (another option could probably be blog.lilypond.org, but i have no idea whether that's a purely cosmetical choice or has some implications.) One consequence here is that subdomains like blog.lilypond.org are treated as separate sites by search engines, and so they are ranked separately. So this splits your site content into two sites, rather than putting it all under one site. I think the latter is generally better from a doing-well-in-search-results (SEO) perspective. As for the integration, i think that the blog should be accessible as an item in the top menubar (I.e. next to Introduction, Manuals, Download and Community). Another possibility is to have it as a sublink/subheading under Community and maybe also have a link from the home page where Pondings is. Maybe as Urs mentioned have a few recent posts listed there (possibly from a particular category?). This would be a more conservative approach. Depending on how things go, later a link to the blog could move up into the top-level navigation menu (while keeping the URLs the same). Going the other direction, you could have the top level navigation/menubar appear on all the blog pages, making it easy to get from the blog back to the rest of the site. This just requires tweaking your WordPress theme (using a child theme of the twentytwelve theme you're now using). That's something I've done and could help with. (I'm less help with installing PHP and the MySQL database, but I'm pretty handy customizing a WordPress site once it's up and running.) Urs Liska wrote: The fundamental question is whether to host the blog on a 'live' (i.e. php based) system or with a static site generator. What are the capabilities on the lilypond.org server (wrt installed programs and performance)? This is a good question. For a blog where people can post comments and then immediately see them appear, that means dynamic rather than static. However, there are caching plugins for WordPress[1] that help with this by automatically storing a static html copy of each page and then just sending that to the web browser[2]. When a new post or comment is made, the changed pages are removed from the cache and the new version of those pages gets stored again. [1] I've used HyperCache: http://wordpress.org/plugins/hyper-cache/ http://www.satollo.net/plugins/hyper-cache [2] How it works, from one of the links above: On each request, the cache engine is called by WordPress. It checks if the html for this request is in cache and is still valid. If so the html page is returned and everything stops. WordPress calls the cache engine BEFORE any other kind of operations, so no plugins are activated, no database connection established, no queries executed. If the page requested is not in cache, the cache engine “captures” the html produced by WordPress and puts it on file. Phil Holmes wrote: However, I honestly don't think it's a case of just asking someone and admin being given. As others have said, what about the load on the server? Will there be any other effect. I'd suggest trying to involve GP before assuming this will automatically happen. I think this is a good idea. -Paul Morris ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: moving LilyPond blog to our website
Janek wrote: 1) are we going to use WordPress or something else, for example Mezzaine: I have no experience with Mezzanine, but I found this helpful comparison with WordPress from a Mezzanine users forum: http://grokbase.com/t/gg/mezzanine-users/12byf39adw/wordpress-vs-mezzanine It sounds like Mezzanine is great if you have a Python/Django developer who can administer it and especially if you want to do more than blogging with your site (i.e. web applications). On the other hand, WordPress requires less developer effort, has fewer dependencies, and works well if you just want to do a blog site (i.e. _not_ web applications). (another option could probably be blog.lilypond.org, but i have no idea whether that's a purely cosmetical choice or has some implications.) One consequence here is that subdomains like blog.lilypond.org are treated as separate sites by search engines, and so they are ranked separately. So this splits your site content into two sites, rather than putting it all under one site. I think the latter is generally better from a doing-well-in-search-results (SEO) perspective. As for the integration, i think that the blog should be accessible as an item in the top menubar (I.e. next to Introduction, Manuals, Download and Community). Another possibility is to have it as a sublink/subheading under Community and maybe also have a link from the home page where Pondings is. Maybe as Urs mentioned have a few recent posts listed there (possibly from a particular category?). This would be a more conservative approach. Depending on how things go, later a link to the blog could move up into the top-level navigation menu (while keeping the URLs the same). Going the other direction, you could have the top level navigation/menubar appear on all the blog pages, making it easy to get from the blog back to the rest of the site. This just requires tweaking your WordPress theme (using a child theme of the twentytwelve theme you're now using). That's something I've done and could help with. (I'm less help with installing PHP and the MySQL database, but I'm pretty handy customizing a WordPress site once it's up and running.) Urs Liska wrote: The fundamental question is whether to host the blog on a 'live' (i.e. php based) system or with a static site generator. What are the capabilities on the lilypond.org server (wrt installed programs and performance)? This is a good question. For a blog where people can post comments and then immediately see them appear, that means dynamic rather than static. However, there are caching plugins for WordPress[1] that help with this by automatically storing a static html copy of each page and then just sending that to the web browser[2]. When a new post or comment is made, the changed pages are removed from the cache and the new version of those pages gets stored again. [1] I've used HyperCache: http://wordpress.org/plugins/hyper-cache/ http://www.satollo.net/plugins/hyper-cache [2] How it works, from one of the links above: On each request, the cache engine is called by WordPress. It checks if the html for this request is in cache and is still valid. If so the html page is returned and everything stops. WordPress calls the cache engine BEFORE any other kind of operations, so no plugins are activated, no database connection established, no queries executed. If the page requested is not in cache, the cache engine “captures” the html produced by WordPress and puts it on file. Phil Holmes wrote: However, I honestly don't think it's a case of just asking someone and admin being given. As others have said, what about the load on the server? Will there be any other effect. I'd suggest trying to involve GP before assuming this will automatically happen. I think this is a good idea. -Paul Morris ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: moving LilyPond blog to our website
On Tue, Jun 04, 2013 at 12:52:17PM +0100, Phil Holmes wrote: - Original Message - From: Janek Warchol it seems to be decided that we're moving the blog to our website (i.e. to be hosted on lilypond.org), and we're doing it asap, because as Paul said: wait, what? I don't think we've agreed anything of the sort. People have requested it, but nothing more. Yes. I have them, because I need them to upload the website. However, I honestly don't think it's a case of just asking someone and admin being given. As others have said, what about the load on the server? Will there be any other effect. I'd suggest trying to involve GP before assuming this will automatically happen. If the blog posts are being written in texinfo, then these posts would just be news items. Nothing strange. Write a doc patch, test with make website, git-cl, review, etc. Or we could even skip the review and push straight to staging as long as you test with make doc first. If you want to write the posts in rst or markdown, then you'd want to look at a static site generator, like pelican or nikola. I've been experimenting with nikola for my own website (not uploaded yet). While you investigate those programs, you should check that they can integrate nicely with the existing website. If you don't have experience with static site generators and our website build process, ETA 20 hours to get a decent hello world. This time includes responding to patch reviews. - Graham ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: moving LilyPond blog to our website
On Tue, Jun 04, 2013 at 10:55:38AM +0200, Janek Warcho?? wrote: (my vote is with Wordpress, but i really have no experience apart from last few days) Be prepared to make frequent security upgrades to WordPress/PHP if you are concerned about the security of the hosting server. In 2012, 23 Wordpress issues were reported, although some of those are disputed. http://www.cvedetails.com/vulnerability-list/vendor_id-2337/product_id-4096/ ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: moving LilyPond blog to our website
Have you considered using a Jekyll based CMS? -- View this message in context: http://lilypond.1069038.n5.nabble.com/moving-LilyPond-blog-to-our-website-tp146656p146679.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
