On 29/10/06, Upayavira <[EMAIL PROTECTED]> wrote:
Martijn Dashorst wrote:
> On 10/29/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
>> ok, i didnt realize confluence was going to be our cms, so is our site
>> going
>> to be done in confluence as well?
>
> That is the idea... I'm downloading confluence now, and trying to get
> it running locally as I don't know how to tweak the templates @apache.
> And it wouldn't be a great idea to do it on our live space as well
> either I figure.
>
>> in that case what we should do is take all that we have now and move
>> it into
>> the public space. start fresh on our documentation space.
>
> Yep. and I suggest creating a good site structure as well.
We can create an additional space if that would help, e.g. WICKET_DOCS,
and use that for the website, keeping the wiki as it is. We then are
careful who we give write access to the WICKET_DOCS but make the wiki
more publicly writeable.
Make sense?
That's the way I was expecting we'd do it, although the 'standard'
short name for the site would be "WICxSITE" or "WICKETxSITE".
(See http://cwiki.apache.org/confluence/dashboard.action)
I'm running with the first on my 'local' Confluence though.
Martijn, you won't be able to tweak the Confluence templates directly
at Apache (although we could probably create a 'theme' & get that
installed if we /really/ wanted to, but the template that you will
want to tweak will be the one used by the AutoExport plugin
(http://could.it/autoexport/) - See the attachment for the 'default'
one. Might be worth seeing if any of the existing xSITE projects have
any comments/tips?
Note that the latest version of the Confluence (which Apache have just
upgraded too) appears to need a build of the plugin from it's source.
/Gwyn
Regards, Upayavira
>> > On 10/29/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
>> > > we dont bundle the wiki with our release do we? so is this an
>> issue for
>> > us?
>> > >
>> > > -igor
>> > >
>> > >
>> > > On 10/29/06, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
>> > > >
>> > > > I've been reading up on confluence, and it seems that if we are
>> going
>> > > > to use the confluence wiki for our documentation purposes, we
>> *need*
>> > > > to get CLA's from the contributors.
>> > > >
>> > > > As we don't have those for the current wiki, we need to move the
>> > > > current content to a separate space, which can be public (the
>> way we
>> > > > work now), and we need to create documentation spaces for the
>> > > > projects.
>> > > >
>> > > > From [1]
>> > > > > Projects do not typically bundle a copy of moin-moin into a
>> release.
>> > If
>> > > > you do plan
>> > > > > to bundle a copy of the Confluence space into a release, then the
>> > > > expectation would
>> > > > > be that a Contributors License Agreement would be on file from
>> > everyone
>> > > > who
>> > > > > contributed anything greater than an incidental patch, to
>> either the
>> > > > code or the
>> > > > > documentation.
>> > > >
>> > > > And:
>> > > > > One strategy is to allow confluence-users Comment Create
>> rights. In
>> > this
>> > > > way,
>> > > > > someone can at least leave a note about changes that could be
>> made
>> > to a
>> > > > > particular page. Incidental comments about a page would not
>> require
>> > that
>> > > > a CLA
>> > > > > to be on file.
>> > > > >
>> > > > > Projects can also setup multiple Spaces. One Space, open to all
>> > users,
>> > > > can
>> > > > > be used as a conventional wiki. Then another Space with
>> restricted
>> > > > editing
>> > > > > permissions can be used to create the Project documentation.
>> > > >
>> > > > The most important quote from [1]:
>> > > > > (!) But, do not bundle a copy of a Space into an official
>> > distribution
>> > > > unless all of
>> > > > > the content has been donated to the ASF and we have the
>> appropriate
>> > CLAs
>> > > > on
>> > > > > file!
>> > > >
>> > > > Any ideas on how to progress with this?
>> > > >
>> > > > Martijn
>> > > >
>> > > > [1] http://cwiki.apache.org/confluence/display/CWIKI/Index
--
Download Wicket 1.2.2 now! - http://wicketframework.org
