Max Horn wrote: <snip>> The important bits are others, and they need comments and actions > by Erik and Rich.Ralph maybe? My current understanding is that we intend to keep the web site on flac.sf.net and have a mirror on xiph.org/flac. On flac.sf.net, we probably don't have SSI, so that's a vote for a static site. I am however all in favor of whatever can be done to make updating and maintenance of the site easier. Erik -- ---------------------------------------------------------------------- Erik de Castro Lopo http://www.mega-nerd.com/
Hi Erik, On 27.12.2012, at 12:28, Erik de Castro Lopo wrote:> Max Horn wrote: > > <snip> > >> The important bits are others, and they need comments and actions >> by Erik and Rich. > > Ralph maybe?Yes, my mistake, sorry!> > My current understanding is that we intend to keep the web site > on flac.sf.net and have a mirror on xiph.org/flac.Either is fine, just somebody has to do it, and apparently Ralph is the one with the access rights to do it. Ralph, if you need any assistance or further information for this, I am happy to help.> > On flac.sf.net, we probably don't have SSI,We do, actually, see http://sourceforge.net/apps/trac/sourceforge/wiki/Project%20web and more specifically http://sourceforge.net/apps/trac/sourceforge/wiki/Project%20web%20and%20developer%20web%20platform Moreover, there is also PHP, Perl, Python, Ruby and Tcl.> so that's a vote for > a static site. I am however all in favor of whatever can be done > to make updating and maintenance of the site easier.Sure. This is a relatively simple website, and I'd prefer to follow the KISS principle there. Supposing we do go with static website generator: Do you have a preference for a language that generator should be written in? In the sense that it should ideally be something you are ideally familiar. The primary choices are Python and Ruby, but Perl and (to a much lesser extent) shell script are also options. Cheers, Max
Max Horn wrote:> Supposing we do go with static website generator: Do you have > a preference for a language that generator should be written in?I am familar with but not fond of Python. Would also be able to handle Ruby but would prefer to avoid Perl. Cheers, Erik -- ---------------------------------------------------------------------- Erik de Castro Lopo http://www.mega-nerd.com/
On 12-12-27 3:28 AM, Erik de Castro Lopo wrote:> My current understanding is that we intend to keep the web site > on flac.sf.net and have a mirror on xiph.org/flac.I was thinking about it the other way around, but that was the default plan.> On flac.sf.net, we probably don't have SSI, so that's a vote for > a static site. I am however all in favor of whatever can be done > to make updating and maintenance of the site easier.With the other Xiph websites we used SSI together with the svn:externals directive to automatically incorporate the latest version of shared resources in the live website. Git doesn't have an equivalent of svn:externals, so we're talking about having to run some script and push the output anyway. I agree the doxygen pages should be generated from the live (and release tag) versions of the code, not checked in. So some kind of generator, even if it's just a hacky script seems the way to go. I also don't see an easy way to automatically pull the sf.net website from the repository the way with do with xiph.org/flac. Sourceforge still has shell accounts, but apparently doesn't support cron, so I'll either have to set up a bot account to push updates, or just replace flac.sf.net with a redirect page. In the meantime, I've replaced the live version of flac.sf.net with the contents of the flac-website repo. I'll update that manually for now. If anyone can write patches, the highest priority bits are to add a news item about maintainership moving to xiph.org, and updating the developers page to point to the new git repository and this list. -r
On 01-01-13 06:51, Ralph Giles wrote:> So some kind of generator, even if it's just a hacky script seems the > way to go.I'm really willing to help as soon as we've settled this matter.> In the meantime, I've replaced the live version of flac.sf.net with the > contents of the flac-website repo. I'll update that manually for now.Well, that's a good start for 2013.> If anyone can write patches, the highest priority bits are to add a news > item about maintainership moving to xiph.org, and updating the > developers page to point to the new git repository and this list.I'm on it, but have a few questions: will the CVS repository (which is not updated anymore I guess?) be closed to avoid confusion? Is the Sourceforge bug and feature request tracker still used? The Sourceforge-stuff has to be updated as well. Anyway, after some hassle, I finally got format-patch working as it should. I've updated the sourceforge tracker links, changed all cvs-links to link to the current git and added some news. -------------- next part -------------- A non-text attachment was scrubbed... Name: news-added-cvs-to-git-tracker-links.patch Type: text/x-patch Size: 0 bytes Desc: not available Url : http://lists.xiph.org/pipermail/flac-dev/attachments/20130101/2ca40f70/attachment.bin