Stefano,
> 1) external blog service. cons: it is not inside the ASF.
AIUI, Sam would provide this as an interim solution until we have one within
the ASF, itself.
> 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)
And separately, you've said:
> > Simple solution: post the announcement as a draft to the dev@ list
> > for review.
> This would make the workflow even more complex than now IMHO.
How so? You are talking about a few days delay for each change. I have no
idea why, except that in your:
> 1) commit to an xml in svn
> 2) build the m2 site
> 3) commit the generated site to svn
> 4) svn up on minotaur
you seem to be implying that the news items would be committed without
review, and then changed if necessary. I'm not considering that to be a
proper practice, even if we can change them later.
I have separately asked Sam if he can syndicate directly from SVN content,
which would merge the blog and SVN based solutions, although I am also
asking if in the wider feed community, changing news items is a valid
practice. Even if it isn't, I'm not sure that matters for our purposes.
Nor do I believe we want to CTR our news items. At the least, commit for
review, and then move to an approved URL for publication after review.
As I understand Sam, once the one-time setup would be performed, the
workflow would be:
- commit news item to svn
- wait for it to appear on the web site
But as Danny said, Sam knows more about this than any of us, so let's see
what he says.
--- Noel
