[opnfv-tech-discuss] opnfv-tech-discuss] [opnfvdocs] [release] MS9 Documentation completed

Hello everyone, MS9 documentation completed is scheduled to May 8. Projects are expected to self-report their final result on the documentation compliance page. Please note, New projects or projects that hasn’t delivered a

[opnfv-tech-discuss] FW: [opnfv-project-leads] MS6 - Preliminary documentation - March 15 #hunter #release #documentation

t 18:29 To: OPNFV , "opnfv-project-le...@lists.opnfv.org" Cc: BIN HU , Sofia Wallin , James Baker Subject: [opnfv-project-leads] MS6 - Preliminary documentation - March 15 #hunter #release #documentation Team, MS6 is scheduled for one week from today (March 15). Please

[opnfv-tech-discuss] [release] Documentation updates for Gambia 7.2

Hi everyone, A reminder that documentation updates for Gambia 7.2 need to be ready by this week, Thursday the 24th. And don’t forget to update your release notes. Example, Release Data +--+--+ | **Project**

[opnfv-tech-discuss] [release] Documentation updates for Gambia 7.1

Hi everyone, A reminder that documentation intended for Gambia 7.1 need to be ready by tomorrow. And don’t forget to update your release notes. Example, Release Data +--+--+ | **Project**

[opnfv-tech-discuss] [opnfvdocs] Update: Submodule Transition

e will help you! BR, Sofia From: Sofia Wallin Date: Wednesday, 5 September 2018 at 11:40 To: "opnfv-project-le...@lists.opnfv.org" Cc: "tim.irn...@gmail.com" , "dmcbr...@linuxfoundation.org" , "tbramw...@linuxfoundation.org" , Heather Kirksey Su

Re: [opnfv-tech-discuss] [release] Final documentation updates

Hi Bin, No, you do not have to add “repo” before the “tag”. //Sofia From: BIN HU Date: Wednesday, 7 November 2018 at 15:30 To: Sofia Wallin , OPNFV Subject: RE: [opnfv-tech-discuss] [release] Final documentation updates Regarding: **Repo/tag** | opnfv-7.0.0 Do we

[opnfv-tech-discuss] [release] Final documentation updates

Hi everyone, Prior to the release Friday, please make sure that you * Update your release notes (see example below) * Self-report your compliance on the documentation compliance page BR, Sofia Example,

[opnfv-tech-discuss] [release] FYI: docs build is failing

Hello everyone, The RTD builds are currently failing. Aric and Trevor are supporting to fix the issue. Regards, Sofia -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#5): https://lists.opnfv.org/g/opnfv-tech-discuss/message/5 Mute This Top

[opnfv-tech-discuss] [release] [docs] Checklist for upcoming MS10

Hi everyone, MS10 documentation completed is scheduled to October 31st. Prior to this please make sure that you, * Updated relevant content, if no major additions or updates don’t forget to change from Fraser to Gambia where needed. * Update your release notes (see example below) * E

[opnfv-tech-discuss] [release] [gambia] Reminder MS6 - preliminary documentation

We are still missing around half of the requirements for MS6 – preliminary documentation. For most of the remaining projects it is just a matter of reporting your status on the documentation compliance page New projects a

[opnfv-tech-discuss] Docs hacking event next week

Hi everyone, You are all welcome to attend the Docs hacking event next week! Starting September 5th at 10AM PDT (please have a look at the wiki for your local time zone) Agenda and logistics can be found here

[opnfv-tech-discuss] [opnfvdocs] [release] Documentation updates for Fraser 6.2

Hi everyone, Don’t forget to update the release data in your release notes. This should be done no later than this Thursday June 28. Repo tag = opnfv-6.2.0 Release designation = Fraser 6.2 Release date = June 29 2018 Example, Release Data +-

[opnfv-tech-discuss] [opnfvdocs] [release] Documentation for Fraser 6.1

Hi everyone, Don’t forget to update the release data in your release notes. This should be done no later than Thursday May 24. Repo tag = opnfv-6.1.0 Release designation = Fraser 6.1 Release date = May 25 2018 Example, Release Data +

Re: [opnfv-tech-discuss] [Docs] Missing links for StorPerf docs

Hi Mark, From what I can see the StorPerf project doesn’t have a reference added in any of these two documents. I’ll fix it and add you as reviewer. BR, Sofia From: on behalf of "Beierl, Mark" Date: Wednesday, 9 May 2018 at 16:28 To: OPNFV Subject: [opnfv-tech-discuss] [Docs] Missing links f

[opnfv-tech-discuss] [opnfvdocs] [release] MS9 Documentation completed

Hi everyone, MS9 documentation completed is scheduled to Wednesday this week. Projects are expected to self-report their final result on the documentation compliance page. Don’t forget, New projects or projects that hasn’t

Re: [opnfv-tech-discuss] [docs] Cross Community Documentation effort

+1 //Sofia From: Charles La Voy Date: Tuesday, 17 April 2018 at 20:49 To: Jessica Wagantall Cc: Thanh Ha , Casey Cain , Gregory Glover , DEBEAU Eric IMT/OLN , Sofia Wallin , Anil Belur , Trevor Bramwell , "WELCH, LORRAINE A" , Kit Lou , Daniel Farrell , Luis Gomez Palacios , Ja

Re: [opnfv-tech-discuss] [docs] Cross Community Documentation effort

have other ways to communicate and follow up I think it's good to start with monthly. Happy to hear others options! Regards, Sofia From: Thanh Ha Date: Friday, 6 April 2018 at 00:05 To: Casey Cain , Gregory Glover , DEBEAU Eric IMT/OLN , Sofia Wallin , Anil Belur , Jessica Wagantall , T

[opnfv-tech-discuss] [opnfvdocs] [release] opnfvdocs meeting

BEGIN:VCALENDAR METHOD:REQUEST PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:W. Europe Standard Time BEGIN:STANDARD DTSTART:16010101T03 TZOFFSETFROM:+0200 TZOFFSETTO:+0100 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T02

[opnfv-tech-discuss] [opnfvdocs] [release] opnfvdocs meeting

BEGIN:VCALENDAR METHOD:REQUEST PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:W. Europe Standard Time BEGIN:STANDARD DTSTART:16010101T03 TZOFFSETFROM:+0200 TZOFFSETTO:+0100 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T02

[opnfv-tech-discuss] opnfvdocs session at ONS

Hi, There will be a docs hacking session during the developer forum at ONS. Everyone is welcome to help out with current backlog items and join ongoing discussions on how we can improve how we work. Docs JIRA tickets Regar

[opnfv-tech-discuss] [opnfvdocs] [release] Reminder - MS6 Preliminary documentation completed

ne6-PreliminaryDocumentation>. Thanks, Sofia From: Sofia Wallin Date: Friday, 23 February 2018 at 08:41 To: OPNFV Cc: "dmcbr...@linuxfoundation.org" Subject: [opnfv-tech-discuss] [opnfvdocs] [release] MS6 Preliminary documentation completed Hi, Please be aware of MS6 ‘Preliminary documentation co

Re: [opnfv-tech-discuss] [OPNFV Documentation, opnfvdocs] submodule for Auto project

Hi Gerard, I’ve added the Auto project as submodule. https://gerrit.opnfv.org/gerrit/#/c/53087/ BR, Sofia From: on behalf of "gerard.d...@wipro.com" Date: Monday, 5 March 2018 at 02:36 To: OPNFV Subject: Re: [opnfv-tech-discuss] [OPNFV Documentation, opnfvdocs] submodule for Auto project I’

[opnfv-tech-discuss] [opnfvdocs] [release] MS6 Preliminary documentation completed

Hi, Please be aware of MS6 ‘Preliminary documentation completed’ that is upcoming March 16. Projects are expected to have their document structure in place. This also includes placehold

[opnfv-tech-discuss] Docs hacking event this Thursday!

Hi everyone, This is a reminder that the Docs hacking event is this Thursday! Please add your location to allow others nearby to join. Also, please add any wanted topics to facilitate the discussion. https://wiki.opnfv.org/display/EVNT/Docs+Hacking Thanks, Sofia From: on behalf of Raymond Pai

[opnfv-tech-discuss] Docs hacking event this Thursday!

Hi everyone, This is a reminder that the Docs Hacking event is this Thursday! Please add your location to allow others nearby to join. Also, please add any wanted topics to facilitate the discussion. https://wiki.opnfv.org/display/EVNT/Docs+Hacking Thanks, Sofia From: on behalf of Raymond Pai

Re: [opnfv-tech-discuss] CI job 'docs-verify-rtd-master' failed

Hi Xudan, Thanks for letting me know! Fatih has opened a ticket at helpdesk. Regards, Sofia From: "xudan (N)" Date: Tuesday, 23 January 2018 at 07:38 To: Sofia Wallin Cc: OPNFV Subject: [opnfv-tech-discuss] CI job 'docs-verify-rtd-master' failed Hi Sofia, I found that

[opnfv-tech-discuss] Canceled: opnfvdocs project meeting

BEGIN:VCALENDAR METHOD:CANCEL PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:W. Europe Standard Time BEGIN:STANDARD DTSTART:16010101T03 TZOFFSETFROM:+0200 TZOFFSETTO:+0100 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T020

Re: [opnfv-tech-discuss] [opnfv-project-leads] [opnfvdocs] Agenda for tomorrow's meeting

othan (ahothan)" Date: Tuesday, 12 December 2017 at 21:34 To: "dmcbr...@linuxfoundation.org" , Sofia Wallin Cc: "opnfv-project-le...@lists.opnfv.org" , OPNFV Subject: Re: [opnfv-project-leads] [opnfv-tech-discuss] [opnfvdocs] Agenda for tomorrow's meeting Just a no

[opnfv-tech-discuss] [opnfvdocs] Agenda for tomorrow's meeting

Agenda, * Documentation for Euphrates 5.1 Welcome, Sofia ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Canceled: opnfvdocs project meeting

BEGIN:VCALENDAR METHOD:CANCEL PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:W. Europe Standard Time BEGIN:STANDARD DTSTART:16010101T03 TZOFFSETFROM:+0200 TZOFFSETTO:+0100 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T020

[opnfv-tech-discuss] Canceled: opnfvdocs project meeting

BEGIN:VCALENDAR METHOD:CANCEL PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:W. Europe Standard Time BEGIN:STANDARD DTSTART:16010101T03 TZOFFSETFROM:+0200 TZOFFSETTO:+0100 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T020

[opnfv-tech-discuss] [opnfvdocs] F-release planning for opnfvdocs

Hi everyone, As communicated projects should have their Fraser release planning done by November 3rd. So, next week’s docs project meeting will be allocated for this topic. I encourage everyone with ideas and suggestions for improvements to call in. Meeting info - https://wiki.opnfv.org/display/

[opnfv-tech-discuss] [opnfvdocs] [release] Don't forget to cherry pick your documentation

Hi everyone, Please don’t forget to cherry pick your documentation to stable/euphrates. Thanks, Sofia ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [opnfvdocs] Question on font size and page width

Date: Wednesday, 18 October 2017 at 14:16 To: Sofia Wallin , OPNFV Subject: RE: [opnfv-tech-discuss] [opnfvdocs] Question on font size and page width Hi Sofia, thanks for the clarification. I just realized that there are changes e.g. on the font size and font type for Euphrates compared to

Re: [opnfv-tech-discuss] [opnfvdocs] Question on font size and page width

at 10:51 To: Sofia Wallin , OPNFV Subject: RE: [opnfv-tech-discuss] [opnfvdocs] Question on font size and page width Hi Sofia, the docs.opnfv.org seems to contain the official release documentation. What about other development documentation under /docs/development/ ? Do I have to do some

Re: [opnfv-tech-discuss] [docs] Fuel and Armband merged documentation

: Alexandru Avadanii Cc: Sofia Wallin , "dmcbr...@linuxfoundation.org" , OPNFV , Cristina Pauna , Bob Monkman Subject: Re: [docs] Fuel and Armband merged documentation Hi Alex, I think it makes sense for Armband team to have a separate documentation if you are going have suppor

[opnfv-tech-discuss] Canceled: opnfvdocs project meeting

BEGIN:VCALENDAR METHOD:CANCEL PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:W. Europe Standard Time BEGIN:STANDARD DTSTART:16010101T03 TZOFFSETFROM:+0200 TZOFFSETTO:+0100 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T020

Re: [opnfv-tech-discuss] [opnfvdocs] Question on font size and page width

Hi Bryan and Gerald, The artifact urls doesn’t give you complete fair view of the rendering in comparison to the actual result on docs.opnfv.org. We currently have the old toolchain running which give you a somewhat reasonable idea on the final result. This is unfortunately not possible to do w

[opnfv-tech-discuss] [opnfvdocs] Topic for tomorrow's docs meeting

Topic, * Dovetail documentation Welcome, Sofia ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [opnfvdocs] [opnfv-project-leads] Documentation updates for Euphrates

Hi all, Please help me review this patch to make sure that necessary documentation updates are done for the Euphrates release. Installer projects/PTLs and scenario owners Should review the installation instruction to make sure that relevant documentat

[opnfv-tech-discuss] Canceled: opnfvdocs project meeting

BEGIN:VCALENDAR METHOD:CANCEL PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:W. Europe Standard Time BEGIN:STANDARD DTSTART:16010101T03 TZOFFSETFROM:+0200 TZOFFSETTO:+0100 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T020

Re: [opnfv-tech-discuss] [opnfvdocs] Tracking work discussed at the OPNFV summit

Thanks a lot Trevor – This is a great start! I will have a closer look and see if I have anything that should be added (this goes for everyone not just the ones that attended the discussion in Beijing). We can then at the next docs meeting discuss how we can work on these items in the best way

[opnfv-tech-discuss] [opnfvdocs] Topic for today's docs call

MS6 - Preliminary documentation done Welcome, Sofia ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Canceled: opnfvdocs project meeting

BEGIN:VCALENDAR METHOD:CANCEL PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:W. Europe Standard Time BEGIN:STANDARD DTSTART:16010101T03 TZOFFSETFROM:+0200 TZOFFSETTO:+0100 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T020

Re: [opnfv-tech-discuss] [releng][opnfvdocs]document verify rtd job failed

Mark Beierl > SW System Sr Principal Engineer > Dell EMC | Office of the CTO > mobile +1 613 314 8106 > mark.bei...@dell.com<mailto:mark.bei...@dell.com> > > On Jul 19, 2017, at 05:20, Sofia Wallin mailto:sofia.wal...@ericsson.com>> wrote:

Re: [opnfv-tech-discuss] [releng][opnfvdocs]document verify rtd job failed

ll manage to help. //Sofia From: Lijun Date: Wednesday, 19 July 2017 at 09:45 To: Aric Gardner , "tbramw...@linuxfoundation.org" , Sofia Wallin , "julien...@gmail.com" , "shang.xiaod...@zte.com.cn" Cc: OPNFV Subject: [opnfv-tech-discuss][releng][opnfvdocs]document

Re: [opnfv-tech-discuss] [opnfvdocs] OPNFV doc workflow for E release

;. BR, Sofia From: "Alec Hothan (ahothan)" Date: Tuesday, 11 July 2017 at 22:37 To: Sofia Wallin , OPNFV Subject: Re: [opnfv-tech-discuss] [opnfvdocs] OPNFV doc workflow for E release Hi Sofia, Can you provide a quick status on the documentation workflow for the E release. Is it same

[opnfv-tech-discuss] [opnfvdocs] Agenda for tomorrow's meeting

Agenda, · Danube 3.0 – Any issues or questions? · Clarify the responsibilities between the docs team and release manager · MS6 Preliminary documentation completed – Any clarification needed? Welcome, Sofia ___ opnfv-tech-disc

[opnfv-tech-discuss] opnfvdocs project meeting

BEGIN:VCALENDAR METHOD:REQUEST PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:W. Europe Standard Time BEGIN:STANDARD DTSTART:16010101T03 TZOFFSETFROM:+0200 TZOFFSETTO:+0100 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T02

[opnfv-tech-discuss] Canceled: opnfvdocs project meeting (updated GoToMeeting link)

BEGIN:VCALENDAR METHOD:CANCEL PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:W. Europe Standard Time BEGIN:STANDARD DTSTART:16010101T03 TZOFFSETFROM:+0200 TZOFFSETTO:+0100 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T020

[opnfv-tech-discuss] Canceled: opnfvdocs project meeting (updated GoToMeeting link)

BEGIN:VCALENDAR METHOD:CANCEL PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:W. Europe Standard Time BEGIN:STANDARD DTSTART:16010101T03 TZOFFSETFROM:+0200 TZOFFSETTO:+0100 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T020

[opnfv-tech-discuss] Canceled: opnfvdocs project meeting (updated GoToMeeting link)

BEGIN:VCALENDAR METHOD:CANCEL PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:W. Europe Standard Time BEGIN:STANDARD DTSTART:16010101T03 TZOFFSETFROM:+0200 TZOFFSETTO:+0100 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T020

[opnfv-tech-discuss] Canceled: opnfvdocs project meeting (updated GoToMeeting link)

BEGIN:VCALENDAR METHOD:CANCEL PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:W. Europe Standard Time BEGIN:STANDARD DTSTART:16010101T03 TZOFFSETFROM:+0200 TZOFFSETTO:+0100 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T020

[opnfv-tech-discuss] opnfvdocs project meeting (updated GoToMeeting link)

BEGIN:VCALENDAR METHOD:REQUEST PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:W. Europe Standard Time BEGIN:STANDARD DTSTART:16010101T03 TZOFFSETFROM:+0200 TZOFFSETTO:+0100 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T02

[opnfv-tech-discuss] opnfvdocs project meeting (updated with agenda)

BEGIN:VCALENDAR METHOD:REQUEST PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:W. Europe Standard Time BEGIN:STANDARD DTSTART:16010101T03 TZOFFSETFROM:+0200 TZOFFSETTO:+0100 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T02

Re: [opnfv-tech-discuss] [opnfv-project-leads] [release][danube] Intent-to-Release for Danube scenarios

And please don’t forget that scenarios intended for release need to be documented. Templates can be found under opnfvdocs/docs/templates/release/scenarios/scenario.name/ Scenario descriptions for Colorado can be found here

Re: [opnfv-tech-discuss] [opnfvdocs] About docs CI jobs

. I don’t know if it’s possible to increase the number of executors, if this could be an easy solution. I happily welcome all feedback and potential improvements for the E release. Regards, Sofia From: Julien [mailto:julien...@gmail.com] Sent: den 10 mars 2017 10:30 To: Sofia Wallin ; TECH

[opnfv-tech-discuss] opnfvdocs project meeting (updated with agenda)

BEGIN:VCALENDAR METHOD:REQUEST PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:W. Europe Standard Time BEGIN:STANDARD DTSTART:16010101T03 TZOFFSETFROM:+0200 TZOFFSETTO:+0100 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T02

Re: [opnfv-tech-discuss] [opnfvdocs] Feedback wanted on docs.opnfv.org

s and font should be aligned. My intention is that we already for the Danube release will reach some level of agreement and have all teams use a common look and feel. BR, Sofia From: Georg Kunz Sent: den 24 februari 2017 17:05 To: Sofia Wallin ; TECH-DISCUSS OPNFV (opnfv-tech-discuss@lists.opnf

Re: [opnfv-tech-discuss] [OPNFV] [Danube] [Documentation] Organization of testing section

Hi Morgan, Yes – This is consistent with what we decided yesterday. Thank you, Sofia From: morgan.richo...@orange.com [mailto:morgan.richo...@orange.com] Sent: den 1 mars 2017 08:27 To: Sofia Wallin ; David McBride Cc: opnfv-tech-discuss@lists.opnfv.org; Yujun Zhang ; mark.bei...@emc.com

[opnfv-tech-discuss] [opnfvdocs] Feedback wanted on docs.opnfv.org

Hi all, As communicated the docs project has the intention to divide the documentation into three different areas Release documentation, Test documentation and Development documentation [1]. I'm happy to see that we have received feedback around this and we want to broaden the discussion to agre

Re: [opnfv-tech-discuss] [opnfvdocs] [opnfv-project-leads] Update - Migration to readthedocs

Hi Gerald, I think that the best approach is that the docs project creates the first version of this. BR, Sofia From: Kunzmann, Gerald [mailto:kunzm...@docomolab-euro.com] Sent: den 22 februari 2017 14:57 To: Sofia Wallin ; TECH-DISCUSS OPNFV (opnfv-tech-discuss@lists.opnfv.org) ; opnfv

[opnfv-tech-discuss] [opnfvdocs] [opnfv-project-leads] Update - Migration to readthedocs

Hello, As many of you already know, as part of the Danube release we are migrating all our documentation to readthedocs, an online documentation service. There are a few changes with respect to documentation that everyone should be aware of: Distinct release, development and testing documentati

Re: [opnfv-tech-discuss] [opnfv-project-leads] [opnfvdocs] Documentation update for Danube release

den 17 februari 2017 00:24 To: Sofia Wallin ; TECH-DISCUSS OPNFV (opnfv-tech-discuss@lists.opnfv.org) ; opnfv-project-le...@lists.opnfv.org Subject: Re: [opnfv-project-leads] [opnfv-tech-discuss] [opnfvdocs] Documentation update for Danube release Hi Sofia I am attempting to check out the docs too

Re: [opnfv-tech-discuss] [opnfvdocs] Documentation update for Danube release

-discuss-boun...@lists.opnfv.org] On Behalf Of Sofia Wallin Sent: den 7 februari 2017 14:26 To: TECH-DISCUSS OPNFV (opnfv-tech-discuss@lists.opnfv.org) ; opnfv-project-le...@lists.opnfv.org Subject: [opnfv-tech-discuss] [opnfvdocs] Documentation update for Danube release To all projects that plans

Re: [opnfv-tech-discuss] [opnfvdocs] Documentation update for Danube release

Hi Morgan, Yes – I think this is the best place since it is common for all testing groups. BR, Sofia From: morgan.richo...@orange.com [mailto:morgan.richo...@orange.com] Sent: den 7 februari 2017 16:19 To: Sofia Wallin ; Kunzmann, Gerald ; TECH-DISCUSS OPNFV (opnfv-tech-discuss@lists.opnfv.org

Re: [opnfv-tech-discuss] [opnfvdocs] Documentation update for Danube release

? Please see answer from Chris on this. We have a docs meeting tomorrow where we could have a discussion about this. BR, Sofia From: Kunzmann, Gerald [mailto:kunzm...@docomolab-euro.com] Sent: den 7 februari 2017 14:35 To: Sofia Wallin ; TECH-DISCUSS OPNFV (opnfv-tech-discuss@lists.opnfv.org) ; opnfv

[opnfv-tech-discuss] [opnfvdocs] Documentation update for Danube release

To all projects that plans to contribute with documentation to the Danube release. Hi, As a reminder that documentation is part of the release even this time, following email contains some useful information and links. Since we are moving to read the docs

[opnfv-tech-discuss] opnfvdocs project meeting

BEGIN:VCALENDAR METHOD:REQUEST PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:W. Europe Standard Time BEGIN:STANDARD DTSTART:16010101T03 TZOFFSETFROM:+0200 TZOFFSETTO:+0100 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T02

[opnfv-tech-discuss] [opnfvdocs] opnfvdocs bi-weekly team meeting

BEGIN:VCALENDAR METHOD:REQUEST PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:W. Europe Standard Time BEGIN:STANDARD DTSTART:16010101T03 TZOFFSETFROM:+0200 TZOFFSETTO:+0100 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T02

[opnfv-tech-discuss] Canceled: [opnfvdocs] opnfvdocs bi-weekly team meeting

BEGIN:VCALENDAR METHOD:CANCEL PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:W. Europe Standard Time BEGIN:STANDARD DTSTART:16010101T03 TZOFFSETFROM:+0200 TZOFFSETTO:+0100 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T020

[opnfv-tech-discuss] [opnfvdocs] [opnfv-project-leads] Version control for generated documents

Please note that the same procedure for documentation applies for Colorado 3.0. All links needs to be updated, http://artifacts.opnfv.org/opnfvdocs/colorado/3.0/docs/documentation/index.html Deadline for documentation is November 30. Regards, Sofia From: Sofia Wallin Sent: den 6 oktober 2016

Re: [opnfv-tech-discuss] [opnfv-project-leads] [opnfvdocs] Planning of D release documentation

onal documentation (release notes, test specifications, development etc.) Danube documentation<https://jira.opnfv.org/browse/DOCS-169> has been created to be used as Epic reference. BR, Sofia From: Tahhan, Maryam [mailto:maryam.tah...@intel.com] Sent: den 1 november 2016 10:34 To: Sofia Wa

[opnfv-tech-discuss] [opnfv-project-leads] [opnfvdocs] Planning of D release documentation

Hi everyone, Looking into the D release planning for all projects I've noticed that not all of you have indicated if any documentation is planned for the D release or not. To be able to follow the documentation progress I would appreciate your help in creating a Jira ticket with a cross reference

[opnfv-tech-discuss] Canceled: [opnfvdocs] opnfvdocs bi-weekly team meeting

BEGIN:VCALENDAR METHOD:CANCEL PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:W. Europe Standard Time BEGIN:STANDARD DTSTART:16010101T03 TZOFFSETFROM:+0200 TZOFFSETTO:+0100 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T020

Re: [opnfv-tech-discuss] [opnfv-project-leads] [opnfvdocs] Documentation updates for Colorado 2.0

link updates 2, Cherrypick to Colorado 2.0 3, Tag according to tagging procedure<https://wiki.opnfv.org/display/SWREL/Git+Tagging+Instructions+for+Colorado+Release> 4, Re-merge BR, Sofia From: Jonas Bjurel Sent: den 11 oktober 2016 23:21 To: Sofia Wallin ; opnfv-project-le...@lists.opn

[opnfv-tech-discuss] [opnfv-project-leads] [opnfvdocs] Documentation updates for Colorado 2.0

[mailto:opnfv-project-leads-boun...@lists.opnfv.org] On Behalf Of Sofia Wallin Sent: den 6 oktober 2016 14:16 To: TECH-DISCUSS OPNFV (opnfv-tech-discuss@lists.opnfv.org) ; opnfv-project-le...@lists.opnfv.org Subject: [opnfv-project-leads] [opnfvdocs] [opnfv-tech-discuss] Version control for generated

[opnfv-tech-discuss] [opnfvdocs] [opnfv-project-leads] Version control for generated documents

Hi, In order to preserve the documents released as part of colorado.1.0, the location to store colorado.2.0 documents have been changed. The new location adds version string into the path. For example, the top level colorado.1.0 release documentation was stored and linked as below. http://arti

[opnfv-tech-discuss] [opnfvdocs] Colorado release of opnfvdocs

Hi, Here are the opnfvdocs release artifacts for Colorado. Commit id/SHA-1: 199598501aaf2926fea43ea4cdfe5b2e29c0fd92 Documents, http://artifacts.opnfv.org/opnfvdocs/colorado/docs/installationprocedure/index.html http://artifacts.opnfv.org/opnfvdocs/colorado/docs/userguide/index.html http://arti

Re: [opnfv-tech-discuss] [tech-discuss][docs] What is the final decision on scenario release notes

. But as stated in the email that I sent out, scenario owners and installer PTL's are asked to agree on how to handle this best. BR, Sofia From: Jonas Bjurel Sent: den 16 september 2016 14:24 To: opnfv-tech-discuss@lists.opnfv.org; David McBride ; Christopher Price ; Raymond Paik ; Sofia W

[opnfv-tech-discuss] [opnfvdocs] [opnfv-project-leads] REMINDER - Document links needed for Colorado release

Reminder! We need to have all document links collected no later than Sunday (September 18th). Links can be found here, http://artifacts.opnfv.org/ //Sofia From: Sofia Wallin Sent: den 12 september 2016 15:43 To: opnfv-project-le...@lists.opnfv.org; TECH-DISCUSS OPNFV (opnfv-tech-discuss

[opnfv-tech-discuss] [opnfvdocs] [opnfv-project-leads] Document links needed for Colorado release

To all projects that are expected to provide documentation to the Colorado release. Hi, We need to collect all document links that should be included in the release library. I have created a wiki page to compile this information and I need help to ensure that we cover every project. https://wik

[opnfv-tech-discuss] [opnfvdocs] additional docs meeting

BEGIN:VCALENDAR METHOD:REQUEST PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:W. Europe Standard Time BEGIN:STANDARD DTSTART:16010101T03 TZOFFSETFROM:+0200 TZOFFSETTO:+0100 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T02

[opnfv-tech-discuss] [opnfvdocs] opnfvdocs bi-weekly team meeting

BEGIN:VCALENDAR METHOD:REQUEST PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:W. Europe Standard Time BEGIN:STANDARD DTSTART:16010101T03 TZOFFSETFROM:+0200 TZOFFSETTO:+0100 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T02

Re: [opnfv-tech-discuss] How are Documentation/Reference Projects Published in C release

t point. Thank you all for the responses. Daniel From: David McBride [mailto:dmcbr...@linuxfoundation.org]<mailto:[mailto:dmcbr...@linuxfoundation.org]> Sent: Tuesday, August 30, 2016 2:25 PM To: Daniel Smith mailto:daniel.sm...@ericsson.com>> Cc: Sofia Wallin mailto:sofia.wal..

Re: [opnfv-tech-discuss] [opnfvdocs] Clarification: Update on release documentation

, BIN [mailto:bh5...@att.com] Sent: den 11 augusti 2016 18:21 To: Sofia Wallin; TECH-DISCUSS OPNFV (opnfv-tech-discuss@lists.opnfv.org); TSC OPNFV (opnfv-...@lists.opnfv.org); Christopher Price Subject: RE: [opnfv-tech-discuss] [opnfvdocs] Clarification: Update on release documentation Is the “/docs

[opnfv-tech-discuss] [opnfvdocs] Clarification: Update on release documentation

dure/installation.instruction.rst //Sofia From: Sofia Wallin Sent: den 10 augusti 2016 14:08 To: TECH-DISCUSS OPNFV (opnfv-tech-discuss@lists.opnfv.org); TSC OPNFV (opnfv-...@lists.opnfv.org) Subject: Update release documentation [opnfvdocs] [opnfv-tech-discuss] Hi everyone, After reviewing the status for Colo

[opnfv-tech-discuss] Update release documentation [opnfvdocs]

Hi everyone, After reviewing the status for Colorado we have agreed that: Feature projects should produce a ”user guide” for their feature according to: https://gerrit.opnfv.org/gerrit/#/c/18311/ Scenario’s should also have a brief description provide