Re: [onap-tsc] Zoom Recording Retention Policy

[Swaminathan via Lists.Onap.Org]

Hi Kenny, All,

The suggestion is reasonable, however, I have 1 comment: sometimes in the 
weekly calls, demos of specific components’ functionality, or use case demos 
are also shown. In my view, they should be retained for much longer (forever?).

Perhaps we should also find a good mechanism of providing easy-to-find 
reference/links so that community folks can better benefit from such recordings.

Regards,

Swami.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5613): https://lists.onap.org/g/onap-tsc/message/5613
Mute This Topic: https://lists.onap.org/mt/54381323/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] Status of Frankfurt M1 Approval #frankfurt #m1

[David McBride]

*UPDATE:*

*Approved ready to go:*
AAI, APPC, CLAMP, CCSDK, DCAE, DMaaP; ExtAPI, Integration,  Modeling,
MutliCloud, OOM, Policy, SNDC, SDC, SO, VF-C, VID, VNFReqs, VVP, VNFSDK

*Conditionally approved:*
MSB

*No go:*
AAF, CLI, HOLMES, MUSIC, OOF, PORTAL, UUI

*Not participating in Frankfurt:*
Logging

David



On Fri, Nov 8, 2019 at 4:32 PM David McBride 
wrote:

> Team,
>
> I neglected to include APPC in the list of conditionally approved
> projects. Sorry for any confusion.
>
> David
>
> On Fri, Nov 8, 2019 at 3:17 PM David McBride 
> wrote:
>
>> Team,
>>
>> During the TSC call earlier this week, I said that I would provide an
>> update on M1 approval by the end of this week.
>>
>> We have two projects that will likely not be participating in the
>> release:  Logging, Holmes; although we are continuing to reach out to
>> them.  I've sent mail to the release mailing list and to the integration
>> team requesting feedback on how this may impact other projects and the
>> release.  We will discuss this in future PTL meetings.
>>
>> Currently, the following projects are considered to be compliant with M1
>> requirements:
>>
>>- CLAMP,
>>- Integration,
>>- OOM,
>>- VID,
>>- VNFReqs,
>>- VVP
>>
>> In addition, the following projects are conditionally approved:
>>
>>- AAI,
>>- CCSDK,
>>- DCAE,
>>- SDNC
>>
>> All other projects are in the process of responding to gaps in their M1
>> compliance.  Therefore, at this time, I can't recommend approving M1.
>>
>> We have also followed up with SECCOM regarding the completion of the M1
>> scorecard for SECCOM related requirements.  This is a gating item for M1
>> approval.
>>
>> For additional information on M1 status, see the Milestone Status page
>> . Take note
>> of the feedback to projects below the JIRA summary table.  You may also see
>> the status of components, by requirement on this page
>> 
>> .
>>
>> David
>>
>> --
>> *David McBride*
>> Release Manager
>> Linux Foundation Networking (LFN)
>> Mobile: +1.805.276.8018
>> Email/Google Talk: dmcbr...@linuxfoundation.org
>> IRC: dmcbride
>>
> --
> *David McBride*
> Release Manager
> Linux Foundation Networking (LFN)
> Mobile: +1.805.276.8018
> Email/Google Talk: dmcbr...@linuxfoundation.org
> IRC: dmcbride
>


-- 
*David McBride*
Release Manager
Linux Foundation Networking (LFN)
Mobile: +1.805.276.8018
Email/Google Talk: dmcbr...@linuxfoundation.org
IRC: dmcbride

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5612): https://lists.onap.org/g/onap-tsc/message/5612
Mute This Topic: https://lists.onap.org/mt/48306517/21656
Mute #frankfurt: https://lists.onap.org/mk?hashtag=frankfurt=2743226
Mute #m1: https://lists.onap.org/mk?hashtag=m1=2743226
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] Zoom Recording Retention Policy

[Perala, Timo (Nokia - FI/Espoo)]

Hello,

I would like to understand first
1) What's the current cost and what is the savings potential e.g. if we 
implement policy along the lines outlined below.
2) What's the volume split between projects/TSC & SubCs/DDFs.
3) Assuming the TSC & SubC meeting recordings and DDF recordings constitute 
minority, I have inclination to keep them longer (e.g. indefinitely to start 
with).
4) Project recordings to stay there for the full release. I guess that would in 
practice mean 6 moths + small delta.

cheers
Timo


From: onap-tsc@lists.onap.org  On Behalf Of Chaker 
Al-Hakim via Lists.Onap.Org
Sent: Tuesday, November 12, 2019 6:01 PM
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Zoom Recording Retention Policy


Hi Kenny,

sounds like a reasonable approach to me.

Regards,
Chaker



From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Kenny 
Paul via Lists.Onap.Org
Sent: Tuesday, November 12, 2019 10:54 AM
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] Zoom Recording Retention Policy

Hello TSC,

One of the areas that has been identified as an area to save costs in on the 
storage associated with our Zoom recordings.
Currently there is no set policy so everything stays around forever.  That 
probably doesn't make much sense; it is unlikely someone will go back and 
listening to a meeting on Casablanca topics for example.

I'd like to propose the following policy framework for Zoom recording retention:


  *   Project meetings: 6 months
  *   TSC and Subcommittee meetings: 9 months
  *   Developer Forums: 12 months

Thoughts?

Thanks!
-kenny



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5611): https://lists.onap.org/g/onap-tsc/message/5611
Mute This Topic: https://lists.onap.org/mt/54381323/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] Zoom Recording Retention Policy

[Chaker Al-Hakim]

Hi Kenny,

sounds like a reasonable approach to me.

Regards,
Chaker



From: onap-tsc@lists.onap.org  On Behalf Of Kenny Paul 
via Lists.Onap.Org
Sent: Tuesday, November 12, 2019 10:54 AM
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] Zoom Recording Retention Policy

Hello TSC,

One of the areas that has been identified as an area to save costs in on the 
storage associated with our Zoom recordings.
Currently there is no set policy so everything stays around forever.  That 
probably doesn't make much sense; it is unlikely someone will go back and 
listening to a meeting on Casablanca topics for example.

I'd like to propose the following policy framework for Zoom recording retention:


  *   Project meetings: 6 months
  *   TSC and Subcommittee meetings: 9 months
  *   Developer Forums: 12 months

Thoughts?

Thanks!
-kenny



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5610): https://lists.onap.org/g/onap-tsc/message/5610
Mute This Topic: https://lists.onap.org/mt/54381323/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] Zoom Recording Retention Policy

[Kenny Paul]

Hello TSC,

 

One of the areas that has been identified as an area to save costs in on the
storage associated with our Zoom recordings.

Currently there is no set policy so everything stays around forever.  That
probably doesn't make much sense; it is unlikely someone will go back and
listening to a meeting on Casablanca topics for example.

 

I'd like to propose the following policy framework for Zoom recording
retention:

 

*   Project meetings: 6 months
*   TSC and Subcommittee meetings: 9 months
*   Developer Forums: 12 months

 

Thoughts?

 

Thanks!

-kenny

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5609): https://lists.onap.org/g/onap-tsc/message/5609
Mute This Topic: https://lists.onap.org/mt/54381323/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] CCSDK Committer promotion requests : Kapil Singal and Kevin Smokowski

[TIMONEY, DAN]

TSC

The CCSDK project would like to recommend the following 2 developers for 
promotion to committer:

Kapil Singal : 
https://wiki.onap.org/display/DW/Committer+Promotion+Request+for+CCSDK+-+Kapil+Singal
Kevin Smokowski : 
https://wiki.onap.org/display/DW/Committer+Promotion+Request+for+CCSDK+-+Kevin+Smokowski

Both of them have a strong record of contributions to our project and have the 
support of our existing committers.I would greatly appreciate your approval 
to promote them to committers.

Thanks!
Dan

Dan Timoney
Principal Technical Staff Member
AT
Email : dtimo...@att.com
Office : +1 (732) 420-3226
Mobile : +1 (201) 960-1211
200 S Laurel Ave, Rm E2-2A03
Middletown, NJ 08873

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5608): https://lists.onap.org/g/onap-tsc/message/5608
Mute This Topic: https://lists.onap.org/mt/54324215/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] Meetings, Lists and Community Self-management

[Davide Cherubini]

Done 

From:  on behalf of Kenny Paul 

Reply to: "onap-tsc@lists.onap.org" 
Date: Monday, 11 November 2019 at 18:22
To: "onap-tsc@lists.onap.org" 
Subject: Re: [onap-tsc] Meetings, Lists and Community Self-management

Hmm…  ~1300 potential voters and only 9 votes on this.
Vote here if you care.  https://www.surveymonkey.com/r/53WFQD9

Thanks!
-kenny

From: kp...@linuxfoundation.org 
Sent: Wednesday, November 6, 2019 5:42 PM
To: onap-tsc@lists.onap.org
Subject: Meetings, Lists and Community Self-management

(Bcc’d to onap-release and onap-discuss)

If you’ve been around the ONAP project for a couple of years you probably know 
that we made a decision to have a large general discussion list with tags 
rather than going with independent lists.  Y’all are also probably well aware 
of the fact that calendar management has been “a challenge”  from the very 
beginning.

These issues aren’t unique to us. Within the LF today there was a rather long 
Slack thread on these topics.  The prevailing wisdom is that one mailing list 
per project/subcommittee whereby each list has it’s own dedicated groups.io 
calendar is the best way to give the respective community control of their own 
destiny.

Upsides to such an arrangement:

  *   The PTL or subcommittee Chair would be the default list owner and 
responsible for maintain the groups.io calendar for their list.

Downsides:

  *   Potential for creating cross-communication silos
  *   Cross posts being rejected if someone isn’t subscribed to both lists

Must haves:

  *   There would still need to be at least 2 other moderators for each list.
  *   The way we use Zoom accounts bridge management would probably need to be 
adjusted at some point, but for now we should be able to get by with our 
current “Bridge Manager” model.

We can have a discussion here but the link here will take you to a non-binding 
“interest” poll to gauge if this is desirable to the community or not.
I’ll leave it up for a few days and then based upon the results I’ll put 
together a proposal.

https://www.surveymonkey.com/r/53WFQD9



Thanks!
-kenny



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5605): https://lists.onap.org/g/onap-tsc/message/5605
Mute This Topic: https://lists.onap.org/mt/44911787/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-