Noel J. Bergman ha scritto: > We have a suggestion from Sam Ruby for how we could do this today: > > Sam Ruby wrote: >> Things that exist on people.apache.org:/www/james.apache.org/ get >> rsynched to james.apache.org once an hour. >> >> Now, how do we get static html there? Well, a cron job with wget >> would do the trick. Doesn't matter if externally hosted roller >> generates the html statically or dynamically, all that matters is >> that it provides it in response to a get. >> >> Alternately, I have some code that can take one or more feeds and >> produce HTML from it. That code is well documented, but I'm even >> willing to set it up. >> >> Short term, either approach solves the immediate need, modulo some >> minor propagation delays. Doesn't require anybody to move any >> mountains. Doesn't put a strain on our infrastructure. >> >> Once in place, it can be optimized at our leisure. No "Make it >> happen!" fire drills required. > > As I understand it, the gist of it seems to be that we'd have a generated > file based on our feed and a template we provide, and we'd pick up the > current feed content to merge with our static content. Sam will maintain > the "interesting" side for us until it can move to ASF Infrastructure, and > the public visible stuff will serve right off our site. I believe that he's > saying that the template which he will populate could be our main news page, > minus the news to be inserted into it. Periodically, we'd pick up a > potentially new copy containing the latest news merged into that page, which > would then be synched with the live site. > > How would that work for everyone? > > --- Noel
It is a good idea to generate html from a blog feed (and that's what Confluence already do this for us automatically if you use it as a blog). This solution help us removing the "feed reader javascript" from the home page in Danny solution, but this does not fix the fact that we need a way to create and keep the feed updated/reviewed. Please correct me if I'm wrong, but I see the following way for us to mantain the feed: 1) external blog service. cons: it is not inside the ASF. 2) internal mailing list feed. cons: it does not provide after-post editing and we would need a preview post to be approved and one to publish (means few days in delay for each change, at minumum) 3) ASF managed Roller. cons: we have to wait until this service will be available 4) ASF managed Confluence space. cons: we have to ask Infra team some more work for us (is it really so much more work 1 space on a confluence instance that already manage 20 spaces?) Have I missed any option? Stefano
