Re: [onap-discuss] RTD and wiki

[GLOVER, GREG L]

Thanks Frank,

Great question, I’ve copied ONAP discuss list since the answer pertains to all 
ONAP documentation:

Wiki: Is for informal content.  That would include general community interest 
(welcome, membership, announcements, meetings), and project work in progress 
(e.g. team members, new topics being proposed, draft notes, discussion threads, 
etc.).  The wiki is intended as an “open” community-based mechanism for anyone 
to provide input, questions, suggestions, etc. on any topic .

Readthedocs:  Is for approved, release-based change controlled content. The 
Beijing artifacts can be found here:  http://onap.readthedocs.io/en/beijing/.  
The categories of documentation in readthedocs includes formal release notes, 
architecture, development guidelines, and user guides.  Templates for all these 
sections can be found here:  
http://onap.readthedocs.io/en/beijing/guides/onap-developer/how-to-use-docs/include-documentation.html#templates-and-examples.
  RTD is intended as a more formal mechanism to house “official” ONAP 
artifacts. As such changes or additions to documentation requires review and 
approval via the formal commit process.

Regarding links to the wiki, generally there should not be a need to link from 
RTD. Most likely the links you are seeing are primarily accessing original seed 
content (pre-Amsterdam) that the Doc team is still in the process of converting 
to ReStructured text and migrating to RTD.


From: Frank Sandoval 
Sent: Thursday, June 14, 2018 12:36 PM
To: GLOVER, GREG L ; BENNETT, RICH ; 
PUZHAVAKATH NARAYANAN, SHANKARANARAYANAN 
Subject: RTD and wiki

Hi Greg, Rich,

I’ve been working on OOF documentation and I’d like to clarify the relationship 
between RTD and wiki, as I sometimes come across links into the wiki from RTD.

What is the intended audiences for each set of material?
Are there guidelines for when to direct a reader of RTD to the wiki?

Thanks


Frank Sandoval
frank.sando...@oamtechnologies.com<mailto:frank.sando...@oamtechnologies.com>
OAM Technologies, representing Arm
OOF committer



___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] ONAP Beijing Documentation

[GLOVER, GREG L]

ONAP PTLs,

As of end of day today (Monday, 6 pm ET) all ONAP documentation on readthedocs 
will be pointed to the Beijing branch.  If you happened to made changes to your 
documentation since Thursday, June 7 in the Master branch, please cherry pick 
those into the Beijing branch.

If you have any questions / concerns please contact myself or Rich Bennett.
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] ONAP Documentation for Beijing

[GLOVER, GREG L]

ONAP PTLs / Doc repo committers:

As the Beijing release approaches we want to insure all repositories with 
documentation are being updated and ready to be officially published. Here's 
what you need to do:

  1.  If your Beijing documentation is still not complete and you haven't 
created a separate Beijing branch in repos containing documentation:

 *   Continue to update the master branch of your repo(s)
 *   When finished with your Beijing updates, create a Jira issue on the 
doc project providing the "doc" project team with a commit hash or tag 
reference of the Master branch to be used for Beijing.  (Note - this will 
create a static "snapshot" of your documentation, any future changes to the 
master branch will not update the Beijing branch published on Read The Docs)


  1.  If you want to get started right away on Casablanca you will need to 
create a separate Beijing branch for documentation - Note this is NOT required, 
however this option will provide an automated update to Beijing on Read The 
Docs if you continue to make changes

 *   If you have already created a Beijing branch, just keep contributing 
changes to it as needed
 *   If you plan to create one, make sure you also create a Jira issue on 
the doc project to automatically track the head of your Beijing branch

If you have additional questions please contact myself or Rich Bennett 
@BENNETT, RICH


Here are the 66 repositories contributing documentation:
aaf/authz
aaf/sms
aai/aai-common
aai/esr-gui
aai/esr-server
aai/event-client
aai/sparky-be
appc
appc/deployment
ccsdk/dashboard
ccsdk/distribution
ccsdk/parent
ccsdk/platform/blueprints
ccsdk/platform/nbapi
ccsdk/platform/plugins
ccsdk/storage/esaas
ccsdk/storage/pgaas
ccsdk/utils
clamp
cli
dcaegen2
dmaap/datarouter
dmaap/dbcapi
dmaap/messagerouter/messageservice
externalapi/nbi
holmes/engine-management
holmes/rule-management
integration
integration/devtool
logging-analytics
modeling/modelspec
modeling/toscaparsers
msb/apigateway
msb/discovery
msb/java-sdk
msb/swagger-sdk
multicloud/framework
music
music/distributed-kv-store
oom
optf/has
optf/osdf
policy/engine
portal
sdc
sdc/jtosca
sdc/sdc-distribution-client
sdc/sdc-docker-base
sdc/sdc-titan-cassandra
sdc/sdc-tosca
sdc/sdc-workflow-designer
sdnc/oam
so
so/libs
ui/dmaapbc
usecase-ui
vfc/nfvo/driver/vnfm/svnfm
vfc/nfvo/lcm
vid
vid/asdcclient
vnfrqts/guidelines
vnfrqts/requirements
vnfrqts/testcases
vnfrqts/usecases
vnfsdk/model
vvp/documentation

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] ONAP RST Errors/Warnings, Link check, and Spell check

[GLOVER, GREG L]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Central Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0500
TZOFFSETTO:-0600
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0600
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="GLOVER, GREG L":MAILTO:gg2...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="BENNETT, R
 ICH":MAILTO:rb2...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='onap-disc
 u...@lists.onap.org':MAILTO:'onap-discuss@lists.onap.org'
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=eric.debea
 u...@orange.com:MAILTO:eric.deb...@orange.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="HARFFY, MA
 TTHEW":MAILTO:mhar...@amdocs.com
DESCRIPTION;LANGUAGE=en-US:Purpose:\n\n\n  1.  Discuss errors / warnings th
 at all ONAP projects should review/correct (e.g. at a minimum links and sp
 elling for “standard” (U.S.) English\n  2.  Guidelines for code blocks
 \n\n  *   Example: Every word between  ``  `` or * * should be not conside
 red as a word: ``odl-bgpcep-bgp-all`` for code or component\, using *seria
 lize()*\n\nODL guidelines:  http://docs.opendaylight.org/en/stable-carbon/
 developer-guide/bgp-developer-guide.html<https://urldefense.proofpoint.com
 /v2/url?u=http-3A__docs.opendaylight.org_en_stable-2Dcarbon_developer-2Dgu
 ide_bgp-2Ddeveloper-2Dguide.html=DwMFAw=LFYZ-o9_HUMeMTSQicvjIg=hFukw
 2tKoSir9RviUoS0RA=Ig6RtOQiik34sTv0xuh3cEN2eVLToekuWFdvVNZuW9c=HIYk5gtW
 T-Wnc9N4Msw1ltu8rAoYQR6XcipqG4kXLlQ=>\n\n  *   Many languages are suppor
 ted in code blocks  http://pygments.org/languages/<https://urldefense.proo
 fpoint.com/v2/url?u=http-3A__pygments.org_languages_=DwMFAw=LFYZ-o9_HU
 MeMTSQicvjIg=29RzhndOzOy7OCr_UVgPcw=QO82c05rtnDKUo4jaSojKsxRvYh7MMtuaC
 7AarrLn3s=zBqdwuXmibj2dBubOnN9_mDVSpXnHVO58jg6ONLaiiI=>\n  *   There a
 re also tools for analyzing code block styles https://coala.io/#/home 
 that have plugins (known as Bears) for different languages.   https://gith
 ub.com/coala/coala-bears<https://urldefense.proofpoint.com/v2/url?u=https-
 3A__github.com_coala_coala-2Dbears=DwMFAw=LFYZ-o9_HUMeMTSQicvjIg=29R
 zhndOzOy7OCr_UVgPcw=QO82c05rtnDKUo4jaSojKsxRvYh7MMtuaC7AarrLn3s=YfhzFW
 2Y55-RSVhKUyf-9uc5HZG5pGtB-RoJFgJKwpo=>\n\n.
 ..
 ..\n--> Join Skype Meeting<https://join.at
 t.com/meet/gg2147/LJ88LWYK>\nTrouble Joining? Try Skype Web App<https://jo
 in.att.com/meet/gg2147/LJ88LWYK?sl=1>\nJoin by phone\n\n8443439499\, acces
 s code: 24468606 (USA\, Global)   English (United States)\
 n8443439505\, access code: 24468606 (USA\, Global)   Engli
 sh (United States)\n8444331206\, access code: 24468606 (USA\, Global) 
   English (United States)\n8447870853\, access code: 24468606 
 (USA\, Global)   English (United States)\n+1 (205) 517-400
 0\, access code: 24468606 (USA\, Global)English (U
 nited States)\n\nFind a local number<https://join.att.com/dialin?id=244686
 06>\n\nConference ID: 24468606 (same as access code above)\nForgot your di
 al-in PIN?<https://join.att.com/dialin> |Help<https://o15.officeredir.micr
 osoft.com/r/rlidLync15?clid=1033=5=2009>\n\n[!OC([1033])!]\n
 ..
 ...\n\n
SUMMARY;LANGUAGE=en-US:ONAP RST Errors/Warnings\, Link check\, and Spell ch
 eck 
DTSTART;TZID=Central Standard Time:20180511T08
DTEND;TZID=Central Standard Time:20180511T09
UID:04008200E00074C5B7101A82E0081039E85A98E7D301000
 01000A26A2EE74A7A5446A8FC3E79E638D7CC
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20180509T183032Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:Skype Meeting
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:-1924573214
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
END:VCALENDAR
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] ONAP Wiki migration Issue

[GLOVER, GREG L]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Central Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0500
TZOFFSETTO:-0600
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0600
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="GLOVER, GREG L":MAILTO:gg2...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-discu
 s...@lists.onap.org:MAILTO:onap-discuss@lists.onap.org
DESCRIPTION;LANGUAGE=en-US:Discuss interim proposal for https://jira.onap.o
 rg/browse/DOC-264\n...
 ..
 \n--> Join Skype Meeting<https://join.att.com/meet/gg2147/LJ88LWYK
 >\nTrouble Joining? Try Skype Web App<https://join.att.com/meet/gg2147/LJ8
 8LWYK?sl=1>\nJoin by phone\n\n8443439499\, access code: 24468606 (USA\, Gl
 obal)   English (United States)\n8443439505\, access code:
  24468606 (USA\, Global)   English (United States)\n844433
 1206\, access code: 24468606 (USA\, Global)   English (Uni
 ted States)\n8447870853\, access code: 24468606 (USA\, Global)
English (United States)\n+1 (205) 517-4000\, access code: 24468606 
 (USA\, Global)English (United States)\n\nFind a lo
 cal number<https://join.att.com/dialin?id=24468606>\n\nConference ID: 2446
 8606 (same as access code above)\nForgot your dial-in PIN?<https://join.at
 t.com/dialin> |Help<https://o15.officeredir.microsoft.com/r/rlidLync15?cli
 d=1033=5=2009>\n\n[!OC([1033])!]\n..
 ..
 .\n\n
SUMMARY;LANGUAGE=en-US:ONAP Wiki migration Issue
DTSTART;TZID=Central Standard Time:20180507T14
DTEND;TZID=Central Standard Time:20180507T143000
UID:04008200E00074C5B7101A82E0082026540BF7E2D301000
 01000ADD503EA0C64BE428E7161CDCB6396CA
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20180507T120416Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:2
LOCATION;LANGUAGE=en-US:Skype Meeting
X-MICROSOFT-CDO-APPT-SEQUENCE:2
X-MICROSOFT-CDO-OWNERAPPTID:1732466658
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
END:VCALENDAR
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Doc Project Team - 11/20 Agenda

[GLOVER, GREG L]

Doc Team,

Here is the agenda so far for tomorrow's meeting.  
https://wiki.onap.org/display/DW/2017-11-19+Doc+Project+Meeting.

The general topics are below.  Also note the JIRA Issues for each 
https://jira.onap.org/secure/RapidBoard.jspa?rapidView=37=DOC

  *   Wiki Migration
  *   Structure Clean-Up
  *   Carrier Grade
  *   API's
  *   Glossary
  *   Tools / Utilities

Let me know if you have anything additional to discuss:

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Updated Documentation Tutorial

[GLOVER, GREG L]

All PTLs,

An updated tutorial for ONAP documentation can be found here: Documentation 
Tutorial.  
It includes a live presentation with minute markers for easy reference, as well 
as additional reference links.

The complete end to end steps and guidelines for creating your documentation 
can be found here: Creating 
Documentation
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] "permission denied" for accessing referenced documents by Document project demo

[GLOVER, GREG L]

Thanks for the catch!  Those URLs have been updated, I’ll publish a new version 
ASAP.

From: JI, LUSHENG
Sent: Thursday, September 14, 2017 7:57 PM
To: GLOVER, GREG L <gg2...@att.com>
Cc: onap-discuss@lists.onap.org
Subject: "permission denied" for accessing referenced documents by Document 
project demo

Greg,

Sorry I could not attend your demo due to schedule conflict.  And today I 
finally got the chance to view the video.  Thanks for the effort.

When I was trying to access the pages referenced from your project wiki page, 
M4 template, and recorded demo.  But I get “Permission Denied You don't have 
the proper permissions to view this page. Please contact the owner of this 
project to request permission.” on ALL of them.  I registered an account on 
readdocs, that did not help either.

Any suggestions on how to actually see these documents?

Thanks,
Lusheng Ji
DCAE PTL



___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Doc Tutorial recording

[GLOVER, GREG L]

All,

Here is a link to today's audio recording and associated PowerPoint.  
https://wiki.onap.org/display/DW/2017-09-13+Documentation+Tutorial

Again I'll plan on scheduling a follow up session for both audio and visuals.


___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] 答复： Invitation: ONAP Documentation Tutorial @ Wed Sep 13,2017 6am - 7am (PDT) (onap-discuss@lists.onap.org)

[GLOVER, GREG L]

All,

The recording from today’s ONAP documentation review came out as audio only.  
Unfortunately I didn’t realize until after words there is a separate command if 
you want to capture screen sharing AND audio (ughh!)

However on the plus side you all brought up many good questions / suggestions, 
so I’ll plan on scheduling at least one more live session where we can create 
an even better recording (this time with visuals).  Thanks again for all your 
input!


From: LANDO, MICHAEL
Sent: Wednesday, September 13, 2017 12:24 PM
To: fu.guangr...@zte.com.cn; kp...@linuxfoundation.org
Cc: BENNETT, RICH <rb2...@att.com>; onap-discuss@lists.onap.org; GLOVER, GREG L 
<gg2...@att.com>; DRAGOSH, PAM <pdrag...@research.att.com>
Subject: RE: 答复：[onap-discuss] Invitation: ONAP Documentation Tutorial @ Wed 
Sep 13,2017 6am - 7am (PDT) (onap-discuss@lists.onap.org)

The same goes for me…





BR,

Michael Lando
Opensource TL , SDC
AT Network Application Development · NetCom
Tel Aviv | Tampa | Atlanta | New Jersey |Chicago
···
Office: +972 (3) 5451487
Mobile: +972 (54) 7833603
e-mail: ml6...@intl.att.com<mailto:ml6...@intl.att.com>

From: fu.guangr...@zte.com.cn<mailto:fu.guangr...@zte.com.cn> 
[mailto:fu.guangr...@zte.com.cn]
Sent: Wednesday, September 13, 2017 5:15 PM
To: kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>
Cc: BENNETT, RICH <rb2...@att.com<mailto:rb2...@att.com>>; Lando,Michael 
<ml6...@intl.att.com<mailto:ml6...@intl.att.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; GLOVER, GREG L 
<gg2...@att.com<mailto:gg2...@att.com>>; DRAGOSH, PAM 
<pdrag...@research.att.com<mailto:pdrag...@research.att.com>>
Subject: 答复：[onap-discuss] Invitation: ONAP Documentation Tutorial @ Wed Sep 
13,2017 6am - 7am (PDT) 
(onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>)

Hi Kenny,

I'm so sorry that I missed the call because I mistook the time.

Do you have any record on the meeting? I'll look it through.

Thanks.
Guangrong
原始邮件
发件人:kp...@linuxfoundation.org
收件人:onap-discuss@lists.onap.org;rb2...@att.com;gg2...@att.com;ml6...@att.com;pdrag...@research.att.com;
日期:2017-09-12 11:37:35
主题:[onap-discuss] Invitation: ONAP Documentation Tutorial @ Wed Sep 13,2017 6am 
- 7am (PDT) (onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>)

more details 
»<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.google.com_calendar_event-3Faction-3DVIEW-26eid-3DNmNxZW8zcnF0NjZ0MGpxMWhoamZvZ3JnN3Ugb25hcC1kaXNjdXNzQGxpc3RzLm9uYXAub3Jn-26tok-3DNzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tZTM5NTAzZGZkYWRkOWRkM2Y1OTMxZDg2Y2ZjZjJkZjY3ZTc5MGVmMA-26ctz-3DAmerica_Los-5FAngeles-26hl-3Den=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=RynqW2q8pkELnIhPvHEWeQ=iftN2KrW_B7anKp7jESn54H5imKIok6rRCTXz6I7kSY=zJSbrySzlGTnrDVMTZVHBk2TEzekbXNLFyIoIx66Y0Q=>
ONAP Documentation Tutorial
When

Wed Sep 13, 2017 6am – 7am Pacific Time

Where

https://zoom.us/j/484932260<https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_j_484932260=DwQGaQ=LFYZ-o9_HUMeMTSQicvjIg=RynqW2q8pkELnIhPvHEWeQ=iftN2KrW_B7anKp7jESn54H5imKIok6rRCTXz6I7kSY=VfmC0a0OIDbXOq3Jov5y6T9pIChXO821uM0jM1v2Dfo=>
 
(map<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.google.com_url-3Fq-3Dhttps-253A-252F-252Fzoom.us-252Fj-252F484932260-26sa-3DD-26usd-3D2-26usg-3DAFQjCNFJPGYjrbEdVAkjs1GCuX5Gqm51qw=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=RynqW2q8pkELnIhPvHEWeQ=iftN2KrW_B7anKp7jESn54H5imKIok6rRCTXz6I7kSY=7MXtsx1a9P87f-b9GRNX1Vck4BUITlwcoiYHpXBD_ho=>)

Calendar

onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>

Who

•

kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org> - creator

•

onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>

•

rb2...@att.com<mailto:rb2...@att.com>

•

gg2...@att.com<mailto:gg2...@att.com>

•

ml6...@att.com<mailto:ml6...@att.com>

•

pdrag...@research.att.com<mailto:pdrag...@research.att.com>


Hi there,

ONAP Meeting 1 is inviting you to a scheduled Zoom meeting.

Join from PC, Mac, Linux, iOS or Android: 
https://zoom.us/j/484932260<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.google.com_url-3Fq-3Dhttps-253A-252F-252Fzoom.us-252Fj-252F484932260-26sa-3DD-26usd-3D2-26usg-3DAFQjCNFJPGYjrbEdVAkjs1GCuX5Gqm51qw=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=RynqW2q8pkELnIhPvHEWeQ=iftN2KrW_B7anKp7jESn54H5imKIok6rRCTXz6I7kSY=7MXtsx1a9P87f-b9GRNX1Vck4BUITlwcoiYHpXBD_ho=>

Or iPhone one-tap :
US: +16465588656,,484932260#  or +16699006833,,484932260#
Or Telephone：
Dial(for higher quality, dial a number based on your current location)：
US: +1 646 558 8656  or +1 669 900 6833  or +1 855 880 1246 (Toll Free) 
or +1 877 369 0926 (Toll Free)
Meeting ID: 484 932 260
International numbers ava

[onap-discuss] [Doc] Documentation project meeting and email reminders

[GLOVER, GREG L]

To all Documentation project participants:


  *   A reminder that the weekly Documentation Project meeting starting next 
Tuesday July 11 has been moved UP two hours to 9-10 am ET, 3-4 pm UK, 9-10 pm 
Asia.


Also two notes on Emails:


  *   As a general rule most communications about the Documentation project 
should use onap-discuss@lists.onap.org


  *   So everyone can more easily filter out Documentation-related discussions, 
please type [Doc] before the rest of your subject in the HEADER of your emails

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [DOC] Documentation Meeting changes

[GLOVER, GREG L]

Two schedule changes for the Documentation project:


  1.  The weekly Documentation project meeting has been cancelled for July 4.  
We will resume on Tuesday July 11



  1.  Starting July the weekly Documentation project meeting will be moved up 
two hours, starting at 9 am ET (U.S.).  This is to better accommodate 
participants in Asia and Europe.


___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] ONAP Meeting Placeholder

[GLOVER, GREG L]

All,

This is a placeholder notice for an ONAP Documentation project meeting on 
Thursday, June 29 from 7-8 ET (Friday morning in Asia).  Here is the Zoom info:

ONAP Doc Weekly
Hi there,
ONAP Meeting 1 is inviting you to a scheduled Zoom meeting.
Join from PC, Mac, Linux, iOS or Android: 
https://zoom.us/j/981212600
Or iPhone one-tap (US Toll): +14086380968,,981212600# or 
+16465588656,,981212600#
Or Telephone:
Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)
+1 855 880 1246 (US Toll Free)
+1 877 369 0926 (US Toll Free)
Meeting ID: 981 212 600
International numbers available: 
https://zoom.us/zoomconference?m=It_2aPlwgUYRY3iJ3WI5BkHop6nEsGgx

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] ONAP Documentation scope

[GLOVER, GREG L]

All,

Attached is a first cut at mapping the ONAP topics (Developer wiki) to the 24 
approved projects.  Note the following:


  *   The topics are listed down the side and are separated into three tabs:  
Technical, Project Mgt and Community
  *   The projects are listed across the top (project descriptions are in the 
row below)
  *   The topics and projects are highlighted in red if they have at least one 
intersection ("X").  Note there are a few of each that aren't highlighted.

Some questions we'll need to answer:

  *   Should we organize ourselves by topic, by project, or some other 
structure?
  *   Is our team responsible for overseeing every topic (insuring 
documentation is accurate, timely and comprehensive)?  I would think for 
Technical topics absolutely yes, but what about Project Mgt and Community topics
  *   Will every topic have documentation updates driven by a scheduled 
release?   If not how should we handle
  *   Are there topics and/or projects that are missing?  I didn't include the 
list of proposed projects - they may help fill in some gaps


ONAP Documentation Scope 6-19-2017.xlsx
Description: ONAP Documentation Scope 6-19-2017.xlsx
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss