Date: Thu, 28 Mar 2024 11:03:16 +0000 (UTC)
Message-ID: <204812639.3291.1711623796019@aws-us-west-2-tungsten-confluence-1.web.codeaurora.org>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_3290_579908166.1711623796018"
------=_Part_3290_579908166.1711623796018
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
2020-11-19 Docs Project Meeting
2020-11-19 Docs Project Meeting
Attendees
- Prefix the topic name with the following tags, if applicable:
- [idea] - the topic owner introduces a new idea to be discussed
- [information] - the topic owner only provides information<=
/li>
- [decision wanted] - the topic owner is looking for a decision
- [discussion] - a general discussion
- [question] - the topic owner is looking for an answer
- Add the topic owner name in parentheses at the end of the line
Agenda
- Progress on the structure - WIP: Documentation structure (Szymon Golebiewski)
- Documentation for R2011:
- wait and copy
- ask for docs and merge them after the migration is finished
- Plan for the next week (Szymon Golebie=
wski)
- Document where to store specs and blueprint?
- Document how to create API documentation and API docs generator
Minutes
- Juniper provided information on which part of Contrail documentation ca=
n be copied to Tungsten Fabric
- As R2011 is coming to finish we need to decide if we are moving the doc=
umentation now or should we wait with that step until Junipers R2011. This =
way we won't need another sync of documentation
- We need to figure out how to incorporate documentation update in the Ju=
nipers process or how to automatically check Contrail documentation for upd=
ates
- Transfer of documentation will require to answer some of the questions =
regarding used names:
- Contrail- prefix if used in source code very often. Should documentatio=
n follow that naming convention or should it be de-contrailized?
- We should construct a dictionary of contrail names that should or shoul=
d not be de-contrailzed. For example, Contrail Controller should be TF cont=
roller while Contrail Command should not be translated.
- During a transfer of documents, there might be a problem with screensho=
ts. Contrail uses Contrail Command while TF uses WebUI. We need to figure o=
ut how to flag such pages.
Action items
------=_Part_3290_579908166.1711623796018--