Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Confluence is the main way WGs interact with internal and external parties. The WG pages are used to report updates for the TSC meetings, and every RISE-funded/prioritized project must have an up-to-date page listing that helps answer what is being done, why it's important, how is it going to be done and when it will be complete:

  • Clear definition of work being done
  • Timelines
  • Components, repositories, stakeholdersAbout
    • Introduce the context behind the work.
  • Project Scope and Timelines
    • Define the requirements, the work being done, and by when the work ought to be completed.
  • Components and Repos
    • Identify repos and components that work will include. Include any proof-of-concepts and existing patchwork as well.
  • Stakeholders and Partners

    • Who needs to be included in design, implementation, review or testing? Include here RISE contacts (using @PersonName) and external parties (other partners, key upstream project contacts) 
  • Dependencies
    • Do you depend on something being done in another WG? Do you need some spec work?
  • Measure of success
    • How will the Board know the project succeeded?
  • RISE Requirements
    • What do you need from
    RISE (if any)
  • Dependencies, including any RVI specification dependencies.
  • Periodic Updates, including
    • the RISE Board?
  • Periodic Updates
    • Add key updates here, using heading 2 with the update date as the title. 
    • Include:
      • Relevant technical decisions that are impacting the project
      • Delays
      • Links to important technical discussions (on upstream channels, of course)
      • References to patches.

Confluence is viewed as the single source of truth. No entries == no progress. Anyone should be able to view the page and get at least a rough sense of what's going on. This has implications on the quality of how the information is presented.

Projects that are not written up are not RISE projects - there's no deduplication and collaboration possible in an environment where companies silently do work.

Confluence is not an engineering log or an attic for obsolete information. Pages need to be maintained and revised to reflect reality. All in all, this enables passive updates of RISE progress to all interested parties.

...