Re: Acumos: Moving Wiki Content to LFDL Wiki - Concerns

Jacqueline Serafin
 

Acumos TSC,

After reviewing the concerns submitted and the various options, we have decided to leave the Acumos wiki unchanged. We will link out to the Acumos wiki from the LF DL wiki. 

Thank you,
Jacqueline 

Jacqueline Serafin
Program Manager
The Linux Foundation
+1 (415) 676-1127 (m)
Regular Hours: 6am-3pm PT



On Mon, Feb 11, 2019 at 8:35 AM Jacqueline Serafin <jserafin@...> wrote:
Hi Aimee,

Thanks for the very detailed email which is very helpful and will be shared with our IT team as they review the plan and next steps for the Acumos wiki updates. To be clear, we will not move forward with any changes until more details are reviewed and discussed with the TSC. We have not ruled out linking to individual project wikis from the LF-DL wiki; the initial plan was based on the standard structure that new umbrella projects are following. We will certainly take into consideration the feedback shared and will work on determining with the TSC the best path forward with the least impact possible as the goal. 

Thank you,
Jacqueline 

Jacqueline Serafin
Program Manager
The Linux Foundation
+1 (415) 676-1127 (m)


On Mon, Feb 11, 2019 at 8:11 AM UKASICK, AIMEE L (AIMEE L) <aimeeu@...> wrote:
Acumos TSC, Ibrahim, Jacqueline:

During today's Acumos TSC call, Jacqueline mentioned that the LF wants to migrate the Acumos wiki to a single space on the LF-DL wiki. I have concerns given the way the Acumos wiki is structured.  Confluence does not supported nested spaces [1]. While I appreciate the desire to promote the LF DL projects from a single point, I am concerned that the Acumos wiki's organizational structure and separation of concerns will not be preserved if it is migrated to a single space.

The Acumos wiki currently consists of 23 site spaces and 3 personal spaces [1]. Each project has its own space, as do the TSC committees, Release management, TSC, Events, Meetings, etc. I structured the wiki this way for the following reasons:
  • to have clear organization: the top menu bar (Acumos, Committees, Documentation, Events, Infrastructure, Meetings, Projects, Releases, TSC) contains links to the various spaces, which makes it easy for the end user to find information; each project having its own space also facilitates much shorter page URLs as well as an easily navigable PAGE TREE in the sidebar
  • separation of concerns: the PTL for each project has authorization to add and delete content within the project space, enabling PTLs to keep their project spaces organized and uncluttered without having to submit a Helpdesk ticket to remove content created by mistake or remove content that is no longer needed
  • ability for Acumos to easily add/retire projects over time: a new project can have a new space and menu item; an archived project remains in its own space but the menu item would be moved from Projects to an as-yet-uncreated Archive menu item
  • ability for each space to have its own blog, calendars, space shortcuts, etc

I also worked with the LF Helpdesk (primarily Vanessa) to install plugins: SubSpace (the top menu bar), SonarQube Connector for Confluence, Draw.io, and Git for Confluence.

Also, I noticed that the LF-Networking wiki links to individual project wikis [2]. Out curiosity, would you mind passing along why linking to individual project wikis from the LF-DL wiki doesn't seem to be an option?

Thanks.



-----
Aimee Ukasick
AT&T
IRC: aimeeu

Join acumosai-tsc@lists.deeplearningfoundation.org to automatically receive all group messages.