CWIKI -> SVN

[Ted Husted <hu...@apache.org>]

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: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org

Re: CWIKI -> SVN

[Ted Husted <hu...@apache.org>]

Pursuant to this discussion, and others on infrstructure@,  there is
now a "asf-cla" group on our Confluence site. The role of the
"asf-cla" group is to identify people that we know have CLAs on file
with the foundation.

The asf-cla group has create and edit permissions to the S2
Documentation space (WW), but not remove or delete. If there is
someone who would like to help edit the documentation, we should ask
him or her to file a CLA. When it goes on record, a Confluence
Administrator can add that person to the "asf-cla" group.

The "struts-admin" group is now the "struts-committers" group to
better indicated its role. This group has all rights to the WW space.

There is no "struts-user" group, since that would overlap with the
"asf-cla" group.

To encourage contributions from everyone, there is now a "Struts 2
Wiki" space (S2WIKI).

* http://cwiki.apache.org/confluence/display/S2WIKI/Home

This area is akin to the moin-moin wiki. Any Confluence user can
create or edit pages. (Though, ATM, we still reserve delete and remove
to struts-committers.)

I moved the "Vault" page from the WW space over to S2WIKI, to give us
a starting point.

-Ted.


On 8/28/06, Ted Husted <hu...@apache.org> wrote:
> 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.
>


-- 
HTH, Ted.
* http://www.husted.com/struts/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org

Re: CWIKI -> SVN

[Ted Husted <hu...@apache.org>]

On 8/28/06, Martin Cooper <ma...@apache.org> wrote:
> However we achieve it, having a wide open space and a controlled space makes
> sense to me. I haven't been paying attention to the thread on infra@, but I
> assume the plan would be that the controlled space would be checked in to
> SVN, while the wide open space would not? (Otherwise we wouldn't be solving
> the problem...)

Yes.


> (Aside: I wish we could lose the 'WW' bit, renaming it to STRUTS or
> something. It doesn't make sense any more, and it's really going to confuse
> people as we get further from the WebWork roots.)

It's possible, though not trivial, to change the space name in
Confluence. In JIRA, it's even more difficult, and in that case,
there's a trail of issue tickets leading back through the WW releases.
So, at least the WW is consistent between the docs and the issue
tracker :)

I think that when we are ready for the next major version, we may want
to create a new space anyway, and we can use a new Confluence space
name and corresponding new JIRA project name at that time.

-Ted.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org

Re: CWIKI -> SVN

[Martin Cooper <ma...@apache.org>]

On 8/28/06, Ted Husted <hu...@apache.org> wrote:
>
> 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.


You mean 'lose'. Loosing the benefit would be just fine. ;-)

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.


However we achieve it, having a wide open space and a controlled space makes
sense to me. I haven't been paying attention to the thread on infra@, but I
assume the plan would be that the controlled space would be checked in to
SVN, while the wide open space would not? (Otherwise we wouldn't be solving
the problem...)

(Aside: I wish we could lose the 'WW' bit, renaming it to STRUTS or
something. It doesn't make sense any more, and it's really going to confuse
people as we get further from the WebWork roots.)

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.)


Makes sense to me.

--
Martin Cooper


-Ted.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>