On infrastructure@, there is some preliminary talk of maybe autocommitting Confluence content to Subversion. Of course, we expect that material checked into the ASF SVN to be covered by a CLA, even if it originated on a wiki.
All of the S2 documentation is in the Confluence wiki. Except for a bridge page, the autoexported Confluence space is our one-and-only web site for Struts 2. The situation is unlike the way we use moin-moin for S1. In this case, it is clear where the "official" web site ends and the "casual" wiki site begins. For S2, it's all wiki, all the time. The S2 situation begs the question of whether everyone with write access to the S2 documentation wiki should be required to have CLA on file. Otherwise, if we want to check the content in later, we may be hamstrung by tracking down CLAs for contributors of new content. Of course, we don't want to loose the benefit of a wiki space to which anyone can easily contribute. The S2 wiki space already includes the notion of a "vault". * http://cwiki.apache.org/confluence/display/WW/The+Vault We might want move the "vault" content to create a separate "s2wiki" space, that would be open to any registered Confluence user. We could then require a CLA for edit priviledges to the main""WW" space but leave the "s2wiki" space open to any registered user. A big difference between that two woud be that the ""ww" space is bundled with the distribution, but the "s2wiki" space would not be. (Just as we do not bundle the moin-moin space with Struts 1 today.) -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
