Anuket Project
2022-03-07- [Anuket RA-1]- Workstream Meeting Agenda and Minutes
Meetings Every Monday at 15:30 UTC
Zoom Meeting link: https://zoom.us/j/99279174971?pwd=eWozNENnYkpLSXdRSzZvblNKVU1wdz09
Attendees:
Name (Organisation) | will incorporate Participant report from Zoom.
Name |
|---|
@Pankaj.Goyal(Microsoft) |
@Cédric Ollivier (Orange) |
@Karine Sevilla(Orange) |
As a courtesy to your colleagues please mute yourself when in listen mode. Thanks
Antitrust Policy
https://r.lfnetworking.org/Antitrust%20Slide.pdf and GSMA Anti-Trust Policy Notice
Agenda and Minutes
Agenda Bashing
Release information
rst conversion status
Review of PRs in progress
Creation of detailed issues for Moselle
Next Meetings, vacation plans, daylight saving time
AOB
Release information
Moselle Release milestones
Milestone | Date | Notes |
|---|---|---|
M1 | 2022-02-01 | Release definition |
M2 | 2022-03-22 | Scope freeze |
M3 | 2022-04-19 | Content freeze |
M4 | 2022-05-17 | Proofreading |
M5 | 2022-06-07 | Release readiness |
M6 | 2022-06-14 | Sign off |
Moselle Specification Planning Dashboard - RA1
We are now working to reach M2 milestone(scope freeze). We can start the creation of detailed issues for Moselle.
RST conversion
First step: md files cleaning is done, PR #2766 merged
RST files are generated and uploaded, PR #2799, merged,
RST cleaning following rst conversion:
Ch01 and Ch02, PR#2811: reference links fixed → merged
Ch03, Ch04, PR#2815: reference links fixed , Figures captions, Lines breaks →merged
Ch05, PR#2817: Addition of backslashes to fix cut words → merged
Ch02 , PR#2821: Addition of backslashes to fix cut words → merged
Ch07, PR#2819: duplicated title removed → merged
Ch08, PR#2820: numbering removed for internal link→ merged
Ch06, PR#2818: reference links fixed, tables fixed → merged
Tox issues on RST files: PR#2830 -> merged
Next step: work on .md links, @Cédric Ollivier will start and we can split the work
Writing Links in RST, examples:
For a document ->:doc:`ref_model/chapters/chapter04`
For in internal link ->:ref:`ref_model/chapters/chapter04:profile extensions`
external hyperlink ->`Python<https://www.python.org/>`_
For references used repeatedly, @Pankaj.Goyalproposes to create a reference once with a simple label and use this label in text.
In PR 2487, Georg uses ":ref:`ref_arch/kubernetes/chapters/chapter04:Kubernetes Node`". Since this reference is repeatedly used, can we 1. define ".. _k8sNode: ref_arch/kubernetes/chapters/chapter04:Kubernetes Node" and then 2. use ":ref:k8sNode_".
@Cédric Ollivierwill check if it will be correct for automation tools.
@Cédric Ollivierand @Karine Sevillawill check how to use VScode and tox locally with windows.
Next meetings
The changes for daylight saving is scheduled at different date per country, it will change the meeting time.
What is more convenient for people attending this meeting?
2022-03-14: next meeting
Actions
Name | Action |
|---|---|
Cédric | Check Pankaj proposal of reference creation |
Cédric | Start modifications of internal links into RST files |
Cédric/Karine | Check the use of VScode and tox locally with windows |
Cédric/Karine | RST conversion last step: link to RTD for references (internal and external) in a temporary step and then Sphinx when RM is done |
All | Start providing new content for Moselle |