Hi Rich：
Thanks for reminding, and I fill some key comments in that matrix. And
I am preparing a sliders for the meeting, I will show you all why I think
Markdown file is better than RST.
发件人: BENNETT, RICH [mailto:[email protected]]
发送时间: 2017年6月27日 14:42
收件人: Yangliu (E) <[email protected]>; HU, JUN NICOLAS <[email protected]>;
[email protected]; GLOVER, GREG L <[email protected]>; SCAGGS, KEVIN
<[email protected]>; WRIGHT, STEVEN A <[email protected]>; [email protected];
[email protected]; [email protected]
抄送: [email protected]; ANDERSON, ANDREA <[email protected]>; BUJA,
JOHN <[email protected]>; FRAZER, BERNARD <[email protected]>;
LOEWEN, SHAWN <[email protected]>; [email protected];
[email protected]; Zhouzheng (A) <[email protected]>;
Majingfeng <[email protected]>; Wuhuanghua (coco) <[email protected]>;
Linan (Alain Lee) <[email protected]>; Zhouyang (Eric)
<[email protected]>; Zhaojuan (nora) <[email protected]>
主题: RE: [doc] ONAP Documentation Project Start
Hi James,
Nicholas and I provided more detail on the readthedocs approach in the form of
a comparison matrix here
https://wiki.onap.org/display/DW/Comparison+and+Recommendation+of+Document+Tool+Chain.
Feel free to comment or add more columns or rows to compare with what you
have proposed below.
Thank you.
Rich
From: Yangliu (E) [mailto:[email protected]]
Sent: Friday, June 16, 2017 12:12 AM
To: BENNETT, RICH <[email protected]<mailto:[email protected]>>; HU, JUN NICOLAS
<[email protected]<mailto:[email protected]>>;
[email protected]<mailto:[email protected]>; GLOVER, GREG L
<[email protected]<mailto:[email protected]>>; SCAGGS, KEVIN
<[email protected]<mailto:[email protected]>>; WRIGHT, STEVEN A
<[email protected]<mailto:[email protected]>>;
[email protected]<mailto:[email protected]>;
[email protected]<mailto:[email protected]>;
[email protected]<mailto:[email protected]>
Cc: [email protected]<mailto:[email protected]>; ANDERSON, ANDREA
<[email protected]<mailto:[email protected]>>; BUJA, JOHN
<[email protected]<mailto:[email protected]>>; FRAZER, BERNARD
<[email protected]<mailto:[email protected]>>; LOEWEN, SHAWN
<[email protected]<mailto:[email protected]>>;
[email protected]<mailto:[email protected]>;
[email protected]<mailto:[email protected]>; Zhouzheng (A)
<[email protected]<mailto:[email protected]>>; Majingfeng
<[email protected]<mailto:[email protected]>>; Wuhuanghua (coco)
<[email protected]<mailto:[email protected]>>; Linan (Alain Lee)
<[email protected]<mailto:[email protected]>>; Zhouyang (Eric)
<[email protected]<mailto:[email protected]>>; Zhaojuan (nora)
<[email protected]<mailto:[email protected]>>
Subject: 答复: [doc] ONAP Documentation Project Start
RICH：
I have create a demo for our ONAP with my team. I think you can have
a look:
https://pnpdjie.github.io/docs/home/<https://urldefense.proofpoint.com/v2/url?u=https-3A__pnpdjie.github.io_docs_home_&d=DwMFbw&c=LFYZ-o9_HUMeMTSQicvjIg&r=hFukw2tKoSir9RviUoS0RA&m=DU1eyr4nEoVyibHj-Zk4t_hbk15YojJA6fY1l8Gqn4g&s=Qv7rJnbSlq4XjcMR7YV2s9an5SvFAvnHeN743mjtc4Q&e=>
We have finished 5 key feature:
1\Source file managed by Github and published as website
2\Edit the webpage will jump to github project and pull a request for the
change. Then the code will be modify and confirm by the system. Also it will
support for anyone to contribute.
[cid:[email protected]]
3\ We have design a solution to support the Markdown file to edit, check and
publish for local. That means we can create markdown file in PC and contribute
a new page for the website. We use Jekyll.
4\ We have developed a tool for checking the Markdown file’s error like links
broken and blank content. What’s far, we make the markdown published into PDF,
and support to publish by topics as you choose.
5\ For the markdown developers, we have design a tool to fork a completed
developing source such as menu tree\md file template. Those source will
generate due to your option.
My team has a completed experience for the whole things: Website build\ github
management\ contribution system\Markdown runtime environment and something else.
I suggest we can use markdown file as our basic documents developing file, BTW.
BR
James
发件人: BENNETT, RICH [mailto:[email protected]]
发送时间: 2017年6月14日 23:01
收件人: BENNETT, RICH; HU, JUN NICOLAS;
[email protected]<mailto:[email protected]>; GLOVER, GREG L; SCAGGS,
KEVIN; WRIGHT, STEVEN A; Yangliu (E);
[email protected]<mailto:[email protected]>;
[email protected]<mailto:[email protected]>;
[email protected]<mailto:[email protected]>
抄送: [email protected]<mailto:[email protected]>; ANDERSON, ANDREA; BUJA,
JOHN; FRAZER, BERNARD; LOEWEN, SHAWN;
[email protected]<mailto:[email protected]>;
[email protected]<mailto:[email protected]>
主题: [doc] ONAP Documentation Project Start
To: Committers on the
Documentation<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_x_UYwx&d=DwMFbw&c=LFYZ-o9_HUMeMTSQicvjIg&r=hFukw2tKoSir9RviUoS0RA&m=DU1eyr4nEoVyibHj-Zk4t_hbk15YojJA6fY1l8Gqn4g&s=XkOCJWa__gkGPwxAq3BDgYCWdnoGwOv7xPxNQGAk7tI&e=>
project,
You should have or will be receiving in email…
(1) A doodle poll on available times for a first project meeting. Some
topics for the meeting:
* Introductions
* PTL candidates and selection
* How to work together … regular meeting times, mailing list, wiki, doc
source structure, etc
* Project as approved and best practice documentation tool chain
* Release plan and near term deliverables that need to be
completed/finalized
(2) Invite to the committer access control list for the gerrit top level doc
project
If you have suggestion on the topics to include in the first meeting let me
know and I will confirm the logistics with a follow-up email / meeting invite.
Thanks
Rich
Cc: Contributors listed on the Documentation project proposal,
[email protected]<mailto:[email protected]>
_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss
