UPDATED 1 November 2017 - 

ARCHIVED


Below are some quick links to storing files and traditional contributions.

- Using JIRA to Manage Contributions – wiki page explaining how to use CONTRIB

- CONTRIB Project – contribution repository

- JIRA system showing all projects

- LIAISE Project – for liaisons and tracking liaisons

- SANDBOX Project – for learning and trying out how to upload a contribution before using CONTRIB

  1. if you wish to contribute using a wiki page (e.g., Project Initiation), please feel free to start a page under the relevant R&T PS or the Work Area. (feel free to reach out to me for precise location for the page you want to create)  I would ask that any files associated with the wiki page be posted to CONTRIB and referenced from the wiki page. (vs. attaching them to the wiki page)  Exceptions to this would be images (e.g., .png, .jpg, etc) and other files needed for the wiki page.
  2. If you wish to contribute via MS Office file (i.e., .doc(x), .ppt(x), etc) please use the new CONTRIB project.  Please be sure to set the fields on the CONTRIB Jira entry so that your contribution is associated with the R&T Work Area and the relevant R&T Project Stream. 
  3. If you have a Liaison contribution, please discuss with me and we will use the LIAISE Jira project to create and track the liaison.


Notes for migration:

  • Note: Use of the R&T Files and Contributions page for submitting files and MS Office contributions is discontinued.  Please use CONTRIB.
  • if you have a contribution or work in progress in ARO, please upload it to CONTRIB (or LIAISE) and cross reference the two via URL in the Jira Description. 
  • If you have a contribution or work in progress uploaded to the R&T Files and Contributions page, please upload it to CONTRIB (or LIAISE) and cross reference the two via URL in the Jira description


UPDATED 1 September 2017 - PLEASE READ.  Working methods have changed.

Hi All,

I hope that you were able to attend one of the webinars and have had a chance to use CONTRIB or try out the new JIRA system using the SANDBOX project.  I’ve been using the new CONTRIB tool for a couple of months and, coupled with the wiki, it will allow more dynamic and flexible collaboration both offline and during meetings.

During the webinars and on the Using JIRA to Manage Contributions page it is noted:

Status and planned roll-out

  • The LIAISE JIRA project was created a couple of months ago
    • It’s already being used for incoming and outgoing liaisons
  • CONTRIB and SANDBOX JIRA projects have been created
    • CONTRIB will be used for contributions that currently use ARO
    • SANDBOX can be used for experimentation
  • CONTRIB will go live on 24th/25th August
    • Both ARO and CONTRIB can be used for Q3 contributions
    • After the Q3 meeting, the ARO contribution site will become read-only
  • CONTRIB currently contains a few existing ARO contributions
    • These will be cleared out before it goes live
    • After the Q3 meeting, ARO contributions for active projects will be moved to CONTRIB
    • Any ARO contributions that are not moved to CONTRIB will remain available and searchable

To give us the maximum time to prepare for the freeze of ARO, for the Q3 meeting I would discourage the use of ARO and ask the following:

  1. if you wish to contribute using a wiki page (e.g., Project Initiation), please feel free to start a page under the relevant R&T PS or the Work Area. (feel free to reach out to me for precise location for the page you want to create)  I would ask that any files associated with the wiki page be posted to CONTRIB and referenced from the wiki page. (vs. attaching them to the wiki page)  Exceptions to this would be images (e.g., .png, .jpg, etc) and other files needed for the wiki page.
  2. If you wish to contribute via MS Office file (i.e., .doc(x), .ppt(x), etc) please use the new CONTRIB project.  Please be sure to set the fields on the CONTRIB Jira entry so that your contribution is associated with the R&T Work Area and the relevant R&T Project Stream.
    1. (Note: To keep things simple, consistent and minimize the number of places to contribute, I would like to discontinue use of the R&T Files and Contributions page for submitting files and MS Office contributions.  Please use CONTRIB.)
  3. If you have a Liaison contribution, please discuss with me and we will use the LIAISE Jira project to create and track the liaison.
  4. if you have a contribution already uploaded into ARO, I would ask you also upload it to CONTRIB (or LIAISE) and cross reference the two via URL in the Jira Description. 
  5. If you have a contribution uploaded to the R&T Files and Contributions page, I would ask that you upload it to CONTRIB (or LIAISE) and cross reference the two via URL in the Jira description

 

Below are some links to get you started:

- Using JIRA to Manage Contributions – wiki page explaining how to use CONTRIB

- JIRA system showing all projects

- SANDBOX Project – for learning and trying out how to upload a contribution before using CONTRIB

- CONTRIB Project – contribution repository

- LIAISE Project – for liaisons and tracking liaisons

Please feel free to reach out to me with questions or if you need help with the new tools.

Thanks!
Dave




***THE REST OF THIS PAGE IS OBSOLETED.  See the Using JIRA to Manage Contributions page and the CONTRIB JIRA Project***


Prior File and Contribution Instructions

NOTE: To make referencing of files/contributions in agendas and minutes easier on the PS Leads and Area Director, we will try using the wiki for file storage as well as minutes and agendas for a select project.  

This page and file repository are for storing files and contributions for the Routing and Transport Work Area and its projects. Please refer to the instructions on tagging files for inclusion into the proper project file lists.

File Naming convention:

<file subject/title>-<authorlastname>-<one word company name>|-<AROContribution#|JIRAIssue#>|.<file extension>

Where: 

<file subject> - *short* description or document title.  e.g., Comments on WT-350 BGP based EVPNs
<authorlastname> - the family or last name of the principal author.  e.g., Sinicrope
<one word company name|> - one word for the principal author's member company name.  Note can be more than one word concatenated together to form a single word where needed.  e.g., Ericsson, Huawei, ChinaUnicom, ChinaMobile
|-<AROContribution#|JIRAIssue#>| - CONDITIONAL - If the file was/is an contribution or file that exists on ARO, provide the ARO contribution number:  e.g., bbf2017.001 
If the file is associated with a JIRA issue, provide the JIRA issue number e.g., LIAISE-2

<file extension> - common three or four letter file extension describing the type of file.  Try to stick to the examples given:  e.g., .doc, .docx,.pdf, .pptx, .ppt, .txt, .html, .xls, .xlsx, .zip

e.g., Comments on WT-350 BGP based EVPNs-Sinicrope-Ericsson-bbf2015.219.docx

NOTE:  When uploading subsequent versions of the same file, the EXACT same filename MUST be used.  
NOTE:  When uploading different file types for the same contribution, e.g., a .ppt to explain a .docx contribution, please use the EXACT same filename for both only changing the file extension.
e.g., 
Comments on WT-350 BGP based EVPNs-Sinicrope-Ericsson-bbf2015.219.docx  for the contribution
Comments on WT-350 BGP based EVPNs-Sinicrope-Ericsson-bbf2015.219.pptx  - for the presentation of the contribution
Comments on WT-350 BGP based EVPNs-Sinicrope-Ericsson-bbf2015.219.pdf  - for the .pdf of the contribution 


Tagging convention:

When uploading the files or contributions, they must be tagged to be shown under the correct projects and on the appropriate agendas.  Any combination of these tags is valid depending on author intent.  
They should always be tagged with at least the work area they are intended for. Please use the tags that come up in the list and try not to create new ones.

R&T TagMeaning
rtRouting and Transport Work Area
rt-plenR&T Work Area Plenary
rt-ciCloud Interconnect PS
rt-mtrMobile Transport & Routing PS
rt-poePacket Optical Evolution PS
wt-#Working Text number e.g., wt-221
md-#Marketing Draft number e.g., md-350
#QyyyyMeeting tag - e.g., 3Q2017, 1Q2016
Other
Tags 
Meaning
wwcWireless-Wireline Convergence
amArchitecture and Migration Work Area
fanFiber Access Networks Work Area
busBroadband User Services Work Area
sdnnfvSDN/NFV Work Area
phytxPHY TX
fttdpFTTDP
cmnyangCommon YANG
itInnovation Track
mktMarketing

e.g.,  If I have an NPIF on new mobile backhaul work I would tag it with:  rt, rt-plen, rt-mtr
e.g., If I have a contribution on EVPN for WT-350, I would tag it with: rt, rt-ci, WT-350
e.g., if I have a contribution for both R&T and WWC on 5G Transport virtualization, where it was presented at the R&T plenary and assigned to the Mobile Transport and Routing PS, I might tag it with: rt, rt-mtr, wwc, sdnnfv, wwc 

e.g., Comments on WT-350 BGP based EVPNs-Sinicrope-Ericsson-bbf2015.219.docx  tagged with: rt, rt-ci, WT-350


How To Tag:
  1. Upload your file to the drag and drop box
  2. Once it’s uploaded it should appear in the file list
  3. Click on the arrow to the left of the file name
  4. Click on the pencil icon to add labels





  File Modified
Microsoft Word Document Contribution to FlexE White Paper-Cheng-Huawei.docx Please refer to JIRA CONTRIB-20018: https://issues.broadband-forum.org/issues/?jql=text%20~%20%22FlexE%22 Sep 01, 2017 by Dean Cheng
Microsoft Word Document WT-350i2ELineETree.SBCandidate-Sinicrope-RnTWAD.docx Aug 03, 2017 by David Sinicrope
PDF File WT-350i2ELineETree.SBCandidate-Sinicrope-RnTWAD.pdf Aug 03, 2017 by David Sinicrope
Microsoft Word Document WT-350 ELine final Modifications from bbf2016.691.02-Cherukuri-DF-bbf2016.691.docx Updated with note on continuous, nested and stitched LSPs Aug 01, 2017 by David Sinicrope
Microsoft Powerpoint 97 Slideshow wt-350-figures.ppt Figure source for WT-350 Aug 01, 2017 by David Sinicrope
ZIP Archive BBF Liaison Reply to ITU-T Q13SG15 on WT221Amd2-RTArea.zip Final, transmitted version of: Liaison to ITU-T Q13-Yuanlong Jiang-Huawei Jun 13, 2017 by David Sinicrope
PDF File BBF Liaison Reply to ITU-T Q13SG15 on WT221Amd2-RTArea.pdf Final, transmitted version of: Liaison to ITU-T Q13-Yuanlong Jiang-Huawei Jun 13, 2017 by David Sinicrope
Microsoft Word 97 Document BBF Liaison Reply to ITU-T Q13SG15 on WT221Amd2-RTArea.doc Final, transmitted version of: Liaison to ITU-T Q13-Yuanlong Jiang-Huawei Jun 13, 2017 by David Sinicrope
Microsoft Word 97 Document Liaison to ITU-T Q13-Yuanlong Jiang-Huawei.doc Jun 12, 2017 by David Sinicrope
Microsoft Word 97 Document Liaison to ITU-T Q13SG15 on WT-331-Sinicrope-Ericsson.doc May 18, 2017 by Gregory Bathrick
Microsoft Powerpoint Presentation 2Q2017 Closing Plenary WA Highlights.RnT-Sinicrope-RTAD.pptx May 18, 2017 by David Sinicrope
PDF File Liaison to OIF on FlexE-Cheng-Huawei.pdf To be approved and transmitted out of the 2Q2017 meeting May 18, 2017 by David Sinicrope
PDF File Liaison to ITU-T SG15 on FlexE-Cheng-Huawei.pdf To be approved and transmitted out of the 2Q2017 meeting May 18, 2017 by David Sinicrope
PDF File Liaison to IETF CCAMP on FlexE-Cheng-Huawei.pdf To be approved and transmitted out of the 2Q2017 meeting May 18, 2017 by David Sinicrope
PDF File Liaison to IEEE 802.3 on FlexE-Cheng-Huawei.pdf To be approved and transmitted out of the 2Q2017 meeting May 18, 2017 by David Sinicrope
Microsoft Word 97 Document Liaison to MEF on 5G Transport-Yuanlong Jiang-Huawei.doc transmitted on 27 April 2017 May 18, 2017 by David Sinicrope
Microsoft Powerpoint Presentation WT-221a2 Figures-Fabregas-Nokia-bbf2017.484.pptx May 17, 2017 by Guiu Fabregas
Microsoft Word 97 Document Liaison to ITU-T Q10SG15 on WT-350PhaseII-Sinicrope-Ericsson.doc Added placeholder for attachment - Liaison not to be sent until WT-350 Phase II SB text is ready and SB opened May 17, 2017 by David Sinicrope
Microsoft Word 97 Document Liaison to ITU-T SG15 on FlexE-Cheng-Huawei.doc May 17, 2017 by David Sinicrope
Microsoft Word 97 Document Liaison to IETF CCAMP on FlexE-Cheng-Huawei.doc May 17, 2017 by David Sinicrope
Microsoft Word 97 Document Liaison to IEEE 802.3 on FlexE-Cheng-Huawei.doc May 17, 2017 by David Sinicrope
Microsoft Word 97 Document Liaison to OIF on FlexE-Cheng-Huawei.doc May 17, 2017 by David Sinicrope
Microsoft Word 97 Document WT-221a2 resolution of comment N15-Fabregas-Nokia-bbf2017.487.doc May 16, 2017 by Guiu Fabregas
Microsoft Word 97 Document WT-221a2 Seamless MPLS requirements-Fabregas-Nokia-bbf2017.483.doc May 16, 2017 by Guiu Fabregas
Microsoft Word 97 Document WT-221a2 GMPLS considerations-Fabregas-Nokia-bbf2017.486.doc May 16, 2017 by Guiu Fabregas
JPEG File Arrow.jpg May 10, 2017 by David Sinicrope
Microsoft Word 97 Document WT-350 ELine Modifications from bbf2016.691.02-Cherukuri-DF-bbf2016.691.doc Apr 17, 2017 by Rao Cherukuri
Microsoft Powerpoint Presentation 1Q2017 Closing Plenary WA Highlights.RnT-Sinicrope-RTAD.pptx Mar 23, 2017 by David Sinicrope
Microsoft Excel Spreadsheet All Companies Straw Ballot Comments on WT-221Amd2-Yuanlong Jiang-Huawei.xlsx Mar 23, 2017 by Yuanlong Jiang
Microsoft Powerpoint Presentation Flex Ethernet overiewpresentatation - Cheng-Huawei-bbf2017.147.pptx Mar 20, 2017 by Mark Fishburn
Microsoft Excel Sheet Ericsson Straw Ballot Comments on WT-221Amd2-Sinicrope-Ericsson-bbf2017.279.00.xls Mar 20, 2017 by David Sinicrope



1 Comment

  1. All companies' comments (including the comments from ITU-T Q13/SG15 liaison) are incorporated.