Re: Tuscany wiki strategy, was :Re: Website - Consistent navigation menus
Hi, I have migrated all content (or atleast most - folks who have added something to the main wiki in the last 24 hrs, please check and copy over the changes to TUSCANYWIKI). I have provided all 'create' permissions to confluence-users. So, if somebody is having trouble creating pages, please let me know. As for contributing content to this wiki here is what comes to my mind... - committers and non-committers may create content on the TUSCANYWIKI. - committers can copy over the contents to TUSCANY after they are done with TUSCANYWIKI to ensure that the two are in sync. I am yet to figure out an automated way to do this. - non committers, when they are done with some content, can post a JIRA to the ML with a link to the TUSCANYWIKI page that needs to be synchronized with TUSCANY - committers looking into a JIRA can go over to TUSCANYWIKI and review the changes and simply copy over the page to TUSCANY Thats all I can think about at the present moment and please feel free to suggest better alternatives to this. Thanks - Venkat On 6/14/07, haleh mahbod [EMAIL PROTECTED] wrote: Can you please also outline what are the steps that a contributor can follow to provide updates to the website through this wiki? Thanks, Haleh On 6/13/07, Venkata Krishnan [EMAIL PROTECTED] wrote: Hi, I have created the Tuscany Wiki space now on confluence - http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Index. Mike, I need help with copying the pages over from TUSCANY and then stubbing the autoexport for TUSCANYWIKI. Right now I just about see export and import of spaces. Thanks - Venkat On 6/13/07, Mike Edwards [EMAIL PROTECTED] wrote: Venkat, +1 from me. How to migrate content? I assume that you mean how do we control the process? The steps in actually moving content are reasonably straightforward - but the process for deciding to do it must mirror that for placing code into trunk, as mentioned on some other emails... Yours, Mike. Venkata Krishnan wrote: Hi, I have the admin access now. I am able to see the 'Create Space' option on the dashboard now. Before I go ahead let me conform the following - We are going to create a space named 'Tuscany Wiki' with key 'TUSCANYWIKI' - All contents of the present wiki space 'TUSCANY' will be copied over to this new space - We will disable the html autoexport for TUSCANYWIKI as we really don't need this. - TUSCANYWIKI will be open to all confluence users. Please let me know if any of you have concerns about all of this. Also, are we clear about how we are going to migrate content submitted on TUSCANYWIKI over to TUSCANY? Thanks - Venkat On 6/12/07, Simon Laws [EMAIL PROTECTED] wrote: Ok, thanks Venkat for looking into this. Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tuscany wiki strategy, was :Re: Website - Consistent navigation menus
Hi, a couple of points in line... On 6/14/07, Venkata Krishnan [EMAIL PROTECTED] wrote: Hi, I have migrated all content (or atleast most - folks who have added something to the main wiki in the last 24 hrs, please check and copy over the changes to TUSCANYWIKI). I have provided all 'create' permissions to confluence-users. So, if somebody is having trouble creating pages, please let me know. As for contributing content to this wiki here is what comes to my mind... - committers and non-committers may create content on the TUSCANYWIKI. Also, for site updates, anyone can copy existing pages from the current web site by cut and pasting the source from the TUSCANY space into the TUSCANYWIKI space. - committers can copy over the contents to TUSCANY after they are done with TUSCANYWIKI to ensure that the two are in sync. I am yet to figure out an automated way to do this. I don't think we need an automated way of doing this as it would remove the human oversight that we are introducing by having two spaces. - non committers, when they are done with some content, can post a JIRA to the ML with a link to the TUSCANYWIKI page that needs to be synchronized with TUSCANY We need people to attach the source rather than a link 1/ With a link the linked page may change and what they intented to submit may not be what gets reviewed. 2/ People attaching content to JIRA are checking a box to say that they are contributing it to Apache. Difficult to audit this if a link is attached. - committers looking into a JIRA can go over to TUSCANYWIKI and review the changes and simply copy over the page to TUSCANY Thats all I can think about at the present moment and please feel free to suggest better alternatives to this. Thanks - Venkat On 6/14/07, haleh mahbod [EMAIL PROTECTED] wrote: Can you please also outline what are the steps that a contributor can follow to provide updates to the website through this wiki? Thanks, Haleh On 6/13/07, Venkata Krishnan [EMAIL PROTECTED] wrote: Hi, I have created the Tuscany Wiki space now on confluence - http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Index. Mike, I need help with copying the pages over from TUSCANY and then stubbing the autoexport for TUSCANYWIKI. Right now I just about see export and import of spaces. Thanks - Venkat On 6/13/07, Mike Edwards [EMAIL PROTECTED] wrote: Venkat, +1 from me. How to migrate content? I assume that you mean how do we control the process? The steps in actually moving content are reasonably straightforward - but the process for deciding to do it must mirror that for placing code into trunk, as mentioned on some other emails... Yours, Mike. Venkata Krishnan wrote: Hi, I have the admin access now. I am able to see the 'Create Space' option on the dashboard now. Before I go ahead let me conform the following - We are going to create a space named 'Tuscany Wiki' with key 'TUSCANYWIKI' - All contents of the present wiki space 'TUSCANY' will be copied over to this new space - We will disable the html autoexport for TUSCANYWIKI as we really don't need this. - TUSCANYWIKI will be open to all confluence users. Please let me know if any of you have concerns about all of this. Also, are we clear about how we are going to migrate content submitted on TUSCANYWIKI over to TUSCANY? Thanks - Venkat On 6/12/07, Simon Laws [EMAIL PROTECTED] wrote: Ok, thanks Venkat for looking into this. Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tuscany wiki strategy, was :Re: Website - Consistent navigation menus
Hi, I have the admin access now. I am able to see the 'Create Space' option on the dashboard now. Before I go ahead let me conform the following - We are going to create a space named 'Tuscany Wiki' with key 'TUSCANYWIKI' - All contents of the present wiki space 'TUSCANY' will be copied over to this new space - We will disable the html autoexport for TUSCANYWIKI as we really don't need this. - TUSCANYWIKI will be open to all confluence users. Please let me know if any of you have concerns about all of this. Also, are we clear about how we are going to migrate content submitted on TUSCANYWIKI over to TUSCANY? Thanks - Venkat On 6/12/07, Simon Laws [EMAIL PROTECTED] wrote: Ok, thanks Venkat for looking into this. Simon
Re: Tuscany wiki strategy, was :Re: Website - Consistent navigation menus
On 6/13/07, Venkata Krishnan [EMAIL PROTECTED] wrote: Hi, I have the admin access now. I am able to see the 'Create Space' option on the dashboard now. Before I go ahead let me conform the following - We are going to create a space named 'Tuscany Wiki' with key 'TUSCANYWIKI' - All contents of the present wiki space 'TUSCANY' will be copied over to this new space - We will disable the html autoexport for TUSCANYWIKI as we really don't need this. - TUSCANYWIKI will be open to all confluence users. Please let me know if any of you have concerns about all of this. Also, are we clear about how we are going to migrate content submitted on TUSCANYWIKI over to TUSCANY? That all sounds ok to me. For the migrate how about we just ask people to use JIRAs as is done with code changes. Then for non-trivial changes we're moving to the main website we can start making sure users either have an ICLA on file and/or tick the JIRA box granting rights to the ASF. ...ant
Re: Tuscany wiki strategy, was :Re: Website - Consistent navigation menus
Sounds good to me. Let's get this started and refine the process as we go along and learn what's most effective. Simon Venkata Krishnan wrote: Hi, I have the admin access now. I am able to see the 'Create Space' option on the dashboard now. Before I go ahead let me conform the following - We are going to create a space named 'Tuscany Wiki' with key 'TUSCANYWIKI' - All contents of the present wiki space 'TUSCANY' will be copied over to this new space - We will disable the html autoexport for TUSCANYWIKI as we really don't need this. - TUSCANYWIKI will be open to all confluence users. Please let me know if any of you have concerns about all of this. Also, are we clear about how we are going to migrate content submitted on TUSCANYWIKI over to TUSCANY? Thanks - Venkat On 6/12/07, Simon Laws [EMAIL PROTECTED] wrote: Ok, thanks Venkat for looking into this. Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tuscany wiki strategy, was :Re: Website - Consistent navigation menus
Venkat, +1 from me. How to migrate content? I assume that you mean how do we control the process? The steps in actually moving content are reasonably straightforward - but the process for deciding to do it must mirror that for placing code into trunk, as mentioned on some other emails... Yours, Mike. Venkata Krishnan wrote: Hi, I have the admin access now. I am able to see the 'Create Space' option on the dashboard now. Before I go ahead let me conform the following - We are going to create a space named 'Tuscany Wiki' with key 'TUSCANYWIKI' - All contents of the present wiki space 'TUSCANY' will be copied over to this new space - We will disable the html autoexport for TUSCANYWIKI as we really don't need this. - TUSCANYWIKI will be open to all confluence users. Please let me know if any of you have concerns about all of this. Also, are we clear about how we are going to migrate content submitted on TUSCANYWIKI over to TUSCANY? Thanks - Venkat On 6/12/07, Simon Laws [EMAIL PROTECTED] wrote: Ok, thanks Venkat for looking into this. Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tuscany wiki strategy, was :Re: Website - Consistent navigation menus
Hi, I have created the Tuscany Wiki space now on confluence - http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Index. Mike, I need help with copying the pages over from TUSCANY and then stubbing the autoexport for TUSCANYWIKI. Right now I just about see export and import of spaces. Thanks - Venkat On 6/13/07, Mike Edwards [EMAIL PROTECTED] wrote: Venkat, +1 from me. How to migrate content? I assume that you mean how do we control the process? The steps in actually moving content are reasonably straightforward - but the process for deciding to do it must mirror that for placing code into trunk, as mentioned on some other emails... Yours, Mike. Venkata Krishnan wrote: Hi, I have the admin access now. I am able to see the 'Create Space' option on the dashboard now. Before I go ahead let me conform the following - We are going to create a space named 'Tuscany Wiki' with key 'TUSCANYWIKI' - All contents of the present wiki space 'TUSCANY' will be copied over to this new space - We will disable the html autoexport for TUSCANYWIKI as we really don't need this. - TUSCANYWIKI will be open to all confluence users. Please let me know if any of you have concerns about all of this. Also, are we clear about how we are going to migrate content submitted on TUSCANYWIKI over to TUSCANY? Thanks - Venkat On 6/12/07, Simon Laws [EMAIL PROTECTED] wrote: Ok, thanks Venkat for looking into this. Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tuscany wiki strategy, was :Re: Website - Consistent navigation menus
Can you please also outline what are the steps that a contributor can follow to provide updates to the website through this wiki? Thanks, Haleh On 6/13/07, Venkata Krishnan [EMAIL PROTECTED] wrote: Hi, I have created the Tuscany Wiki space now on confluence - http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Index. Mike, I need help with copying the pages over from TUSCANY and then stubbing the autoexport for TUSCANYWIKI. Right now I just about see export and import of spaces. Thanks - Venkat On 6/13/07, Mike Edwards [EMAIL PROTECTED] wrote: Venkat, +1 from me. How to migrate content? I assume that you mean how do we control the process? The steps in actually moving content are reasonably straightforward - but the process for deciding to do it must mirror that for placing code into trunk, as mentioned on some other emails... Yours, Mike. Venkata Krishnan wrote: Hi, I have the admin access now. I am able to see the 'Create Space' option on the dashboard now. Before I go ahead let me conform the following - We are going to create a space named 'Tuscany Wiki' with key 'TUSCANYWIKI' - All contents of the present wiki space 'TUSCANY' will be copied over to this new space - We will disable the html autoexport for TUSCANYWIKI as we really don't need this. - TUSCANYWIKI will be open to all confluence users. Please let me know if any of you have concerns about all of this. Also, are we clear about how we are going to migrate content submitted on TUSCANYWIKI over to TUSCANY? Thanks - Venkat On 6/12/07, Simon Laws [EMAIL PROTECTED] wrote: Ok, thanks Venkat for looking into this. Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tuscany wiki strategy, was :Re: Website - Consistent navigation menus
Ok, so can our Confluence admins tell us if we need to create a JIRA with infra to make this happen or whether they can action this? Simon
Re: Tuscany wiki strategy, was :Re: Website - Consistent navigation menus
I was wanting to take Luciano's help to make my id admin. Since he is not available I've just about posted to infra to add my id as confluence admin. As mentioned on the IRC last night I'd like to check up after I get admin privelges, if this can be done by us or should have to only go thro infra. I my local confluence I can see how to get this done and remains to be seen if the same can be done on the Apache Confluence. - Venkat On 6/12/07, Simon Laws [EMAIL PROTECTED] wrote: Ok, so can our Confluence admins tell us if we need to create a JIRA with infra to make this happen or whether they can action this? Simon
Re: Tuscany wiki strategy, was :Re: Website - Consistent navigation menus
Ok, thanks Venkat for looking into this. Simon
Re: Tuscany wiki strategy, was :Re: Website - Consistent navigation menus
I'd like an additional space that non-committers can use to preview proposed updates to the Web site. I suggest granting access control permission to edit this space by request on the dev list. Anyone who wants to contribute to the Web site could make such a request. The structure (e.g., menus) and page names in the preview space would be identical to the Web site space (TUSCANY). The preview space would not be exactly in sync with the Web site space and would contain only a subset of the content. See discussion in [1] about how it would be used. The name of the preview space could be TUSCANY-preview. Simon [1] http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg18763.html Luciano Resende wrote: Should we have a discussion around our wiki strategy and make sure we do the right thing? We could use the Geronimo wiki strategy [1] as an example and start point. I think we should consider the following things: - Naming Convention - Access Control List for the wiki spaces - Scope for contents - What goes where.. - What is going to be available on the website space - What is going to be available on the other wiki spaces - Navigation on defined scopes - Maintainability If we come up with a scheme that would have multiple spaces, that is going to be transparent for the end user, we may have couple advantages : - Easy content administration - We could apply the Left Navigation Template, similar to the one used at OSOA.org and then we would maintain sub-space look and feel more consistent without having to use page templates that will be hard to maintain in the future. - Small spaces are easier to maintain and organize - Separate spaces can make it easy to track web traffic to specific sub projects - etc Well, I'm not convinced we need the same amount of spaces Geronimo have, but we might take advantages of having multiple spaces, and I wanted to throw the idea and would like to hear back your thoughts and feedback. Herman, could also share little more about your experience with Confluence in the Geronimo project, and how multiple spaces made life easier for you guys ? [1] http://cwiki.apache.org/geronimo/geronimo-cwiki-documentation-architecture.html On 6/6/07, Hernan Cunico [EMAIL PROTECTED] wrote: I would suggest you guys use lower case for the space names, at least for the one with the highest hierarchy. Remember the URL is case sensitive and it is based on the space ID. Ideally http://cwiki.apache.org/tuscany should take you to a page consolidating pointers to all the other Tuscany spaces. This would be the tuscany space. Then you could have shorter names to identify project name and space. Long time ago when all the Confluence thingy was just starting we came out with the following convention, AAAxBBB. That is 3 cap letters for identify the project and 2 or more to identify the specific space, all separated by a lower case x. Hence the names used in the Geronimo spaces (http://cwiki.apache.org/geronimo/geronimo-cwiki-documentation-architecture.html) However not all the projects are following this convention so, ultimately, it's up to you guys. The idea is to make your like easier when you get to the point when you need to start spanning to more and more spaces. HTH Cheers! Hernan Simon Laws wrote: OK so, I'll raise a JIRA against infrastructure asking for a new space to act as our wiki: Name: Apache Tuscany Wiki Key: TUSCANYWIKI Is everyone happy with this name? Venkat, when you say administrator privileges I assume you mean confluence admin privileges? Wouldn't this be a separate request? If so can you go ahead with this also. Regards Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Simon C Nash IBM Distinguished Engineer Hursley Park, Winchester, UK [EMAIL PROTECTED] Tel. +44-1962-815156 Fax +44-1962-818999 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tuscany wiki strategy, was :Re: Website - Consistent navigation menus
Should we have a discussion around our wiki strategy and make sure we do the right thing? We could use the Geronimo wiki strategy [1] as an example and start point. I think we should consider the following things: - Naming Convention - Access Control List for the wiki spaces - Scope for contents - What goes where.. - What is going to be available on the website space - What is going to be available on the other wiki spaces - Navigation on defined scopes - Maintainability If we come up with a scheme that would have multiple spaces, that is going to be transparent for the end user, we may have couple advantages : - Easy content administration - We could apply the Left Navigation Template, similar to the one used at OSOA.org and then we would maintain sub-space look and feel more consistent without having to use page templates that will be hard to maintain in the future. - Small spaces are easier to maintain and organize - Separate spaces can make it easy to track web traffic to specific sub projects - etc Well, I'm not convinced we need the same amount of spaces Geronimo have, but we might take advantages of having multiple spaces, and I wanted to throw the idea and would like to hear back your thoughts and feedback. Herman, could also share little more about your experience with Confluence in the Geronimo project, and how multiple spaces made life easier for you guys ? [1] http://cwiki.apache.org/geronimo/geronimo-cwiki-documentation-architecture.html On 6/6/07, Hernan Cunico [EMAIL PROTECTED] wrote: I would suggest you guys use lower case for the space names, at least for the one with the highest hierarchy. Remember the URL is case sensitive and it is based on the space ID. Ideally http://cwiki.apache.org/tuscany should take you to a page consolidating pointers to all the other Tuscany spaces. This would be the tuscany space. Then you could have shorter names to identify project name and space. Long time ago when all the Confluence thingy was just starting we came out with the following convention, AAAxBBB. That is 3 cap letters for identify the project and 2 or more to identify the specific space, all separated by a lower case x. Hence the names used in the Geronimo spaces (http://cwiki.apache.org/geronimo/geronimo-cwiki-documentation-architecture.html) However not all the projects are following this convention so, ultimately, it's up to you guys. The idea is to make your like easier when you get to the point when you need to start spanning to more and more spaces. HTH Cheers! Hernan Simon Laws wrote: OK so, I'll raise a JIRA against infrastructure asking for a new space to act as our wiki: Name: Apache Tuscany Wiki Key: TUSCANYWIKI Is everyone happy with this name? Venkat, when you say administrator privileges I assume you mean confluence admin privileges? Wouldn't this be a separate request? If so can you go ahead with this also. Regards Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tuscany wiki strategy, was :Re: Website - Consistent navigation menus
You pretty much summarized the advantages of having multiple spaces
From Admin point of view, there are all benefits from having multiple spaces, you have
more control on everything, it is more granular and the maintenance is
lighter-weight.
From the user perspective it is transparent, however they get improved HTML
render speed.
From development perspective it's just matter of getting used to the architecture. Have a good understanding
what goes where and why. You can also have multiple templates for
exporting the spaces (well, still limited to one per space), this give you some additional flexibility. You
could manage all the menus directly at template level so there would not be the need for the {include} on
every single page anymore.
As for planning I would start doing a breakdown planning for the current
content trying to maximize reusability within those spaces; come up with some
grouping criteria. Then work on what would be the relation between those
spaces. You'll also need to outline a hierarchy and naming convention. Separate
wiki content from website content. Define user groups and roles.
Using themes as you pointed out from OSOA.org did not work for us. It
required lot of template customization at Confluence level plus we would still have to
use the AE plugin template to export to HTML. We rather used the later that in addition
supported css and we were more independent from infra to make these changes. Changes made
to the AE plugin template do not affect Confluence.
HTH
Cheers!
Hernan
Luciano Resende wrote:
Should we have a discussion around our wiki strategy and make sure we
do the right thing?
We could use the Geronimo wiki strategy [1] as an example and start point.
I think we should consider the following things:
- Naming Convention
- Access Control List for the wiki spaces
- Scope for contents
- What goes where..
- What is going to be available on the website space
- What is going to be available on the other wiki spaces
- Navigation on defined scopes
- Maintainability
If we come up with a scheme that would have multiple spaces, that is
going to be transparent for the end user, we may have couple
advantages :
- Easy content administration
- We could apply the Left Navigation Template, similar to the
one used at OSOA.org and then we would maintain sub-space look and
feel more consistent without having to use page templates that will be
hard to maintain in the future.
- Small spaces are easier to maintain and organize
- Separate spaces can make it easy to track web traffic to specific
sub projects
- etc
Well, I'm not convinced we need the same amount of spaces Geronimo
have, but we might take advantages of having multiple spaces, and I
wanted to throw the idea and would like to hear back your thoughts and
feedback.
Herman, could also share little more about your experience with
Confluence in the Geronimo project, and how multiple spaces made life
easier for you guys ?
[1]
http://cwiki.apache.org/geronimo/geronimo-cwiki-documentation-architecture.html
On 6/6/07, Hernan Cunico [EMAIL PROTECTED] wrote:
I would suggest you guys use lower case for the space names, at least
for the one with the highest hierarchy. Remember the URL is case
sensitive and it is based on the space ID.
Ideally http://cwiki.apache.org/tuscany should take you to a page
consolidating pointers to all the other Tuscany spaces. This would be
the tuscany space.
Then you could have shorter names to identify project name and space.
Long time ago when all the Confluence thingy was just starting we came
out with the following convention, AAAxBBB. That is 3 cap letters for
identify the project and 2 or more to identify the specific space, all
separated by a lower case x. Hence the names used in the Geronimo
spaces
(http://cwiki.apache.org/geronimo/geronimo-cwiki-documentation-architecture.html)
However not all the projects are following this convention so,
ultimately, it's up to you guys. The idea is to make your like easier
when you get to the point when you need to start spanning to more and
more spaces.
HTH
Cheers!
Hernan
Simon Laws wrote:
OK so,
I'll raise a JIRA against infrastructure asking for a new space to
act as
our wiki:
Name: Apache Tuscany Wiki
Key: TUSCANYWIKI
Is everyone happy with this name?
Venkat, when you say administrator privileges I assume you mean
confluence
admin privileges? Wouldn't this be a separate request? If so can you go
ahead with this also.
Regards
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
