Meeting Information


Date Monday August 29, 2011
Time 09:00 AM Central
Telephone Number 866-740-1260
Teleconference ID 9030201



Not Attending


Time Agenda Item
09:00 - 09:30 Review agenda
09:30 - 10:30 Develop complete plan and schedule for transition from Pacman to RPM based documentation.
10:30 - 12:00 Copy over WN and VOMS install documents and work on RPM changes
12:00 - 12:30 Lunch in
12:30 - 01:30 Compare notes on RPM changes and refine RPM plan and approach.
01:30 - 02:00 Review Navigation
02:00 - 03:00 Develop plan to complete navigation and preparation for release.
03:00 - 05:00 TBD

Document Areas and Status

Area Coordinator Documents Reviewed Tested Released Completed
General? RobertEngel 89 85 8/8 85 96%
Compute Element? RobertEngel 70 55(+2) 21/26 52(+1) 74%
Storage? TanyaLevshina 45 35 20/23 36 80%
Security? JamesBarlow 35 35 10/10 35 100%
Tier3? MarcoMambelli 26 11 4/6 19 73%
VO? TerrenceMartin 22 14(+1) 7/8 18(+1) 81%
User? BrianBockelman 21 19 11/12 20 95%
Operations? ElizabethChism 14 14 12/12 14 100%
Integration? SuchandraThapa 4 4 1/1 4 100%
All   322 267(+3) 94/106 285(+2) 89%

Functional Units and Document Dependencies

The Document Finder? supports arbitrary tags that can be used to tag documents of importance in the transition process. Please use the following tags to find these documents:

Functional Unit TAG Name TAG Value
ComputeElement PM2RPM_TASK CE

See here? to learn more about document tagging. Functional units refers to Alain's Plan.

New Documentation Structure

After a conference with Rob Q. and Kyle, the team developed a structure for the documentation to be implemented with the RPM release. This structure was designed to have the following characteristics:
  • Maintains the current conventions for the current 1.2 release in ReleaseDocumentation
  • Reduces the number of top level webs which is too large for easy understanding
  • Has a natural way to develop documentation for major (extensive) new releases
  • Integrates the current archive mechanism while removing Trash/ArchivedDocumentation as a top level web
  • Results in a single place (web) for all official OSG documentation
  • Maintains the logic of collecting documents that don't change between releases into one place

TWiki Web Structure

Documentation (web)

  • Directly contains all documents that don't change between releases (e.g. Glossary, User documents, general descriptions)
  • Release3 (subweb) - contains all release documentation for the RPM release (equivalent to the current ReleaseDocumentation web)
  • Current (link) - Actually just a pointer to the current release (after the RPM release is out, it will point to Release3)
  • Archived (subweb) - The current top level Trash/ArchivedDocumentation Web that contains old releases using OSGx.y. The current ReleaseDocumentation Web will be moved here when the Release 3 is released. The ITBx.y also resides here as it does now.

Internal (web - new)

  • Documentation (subweb) - temporarily will contain all the documents currently in the Documentation web that are not part of the official documentation. These will be moved to the DocumentationTeam subweb below or deleted if no longer relevant.
  • Team (subweb) - current DocumentationTeam info

The result will be the elimination of the top level ReleaseDocumentation and Trash/ArchivedDocumentation webs and the addition of Internal as a top level web. ALL official documents will be found in the top level Documentation web only.

New common documents for Release 3

A small set of common documents are needed to explain YUM and RPM to system administrators and to collect common information that can be referred to (or included) in installation documents. Our first pass cut at these documents are: Note the Rel3 part of the name is temporary and will be removed when the documents are moved to the Release3 subweb.

Early Installation Documents

Documents of Interest

The Document Finder? has been updated to support searching for arbitrary strings (content) in documents withing a specified web. The search can be limited to project documents only which means documents that are managed by the document process. Try searching for:

-- RobertEngel - 27 Aug 2011

Topic revision: r11 - 18 Oct 2016 - 15:25:27 - KyleGross
Hello, TWikiGuest


TWiki | Report Bugs | Privacy Policy

This site is powered by the TWiki collaboration platformCopyright by the contributing authors. All material on this collaboration platform is the property of the contributing authors..