[onap-tsc] Confirmed: LFN Developer & Testing Forum, Prague, Jan 13-16

2019-10-22 Thread Brandon Wick 
ONAP, OPNFV, and CNTT Communities:

We're pleased to inform you that the next LFN technical event, the LFN
Developer & Testing Forum, has been confirmed for Prague, January 13-16,
2020. *Learn More and Register here*

.

In addition to our regular technical DDF and plugfest activities across
ONAP, OPNFV, and CNTT, we will also be hosting a VNF hacking track to
encourage VNF developers to participate in the compliance and verification
program. Please pass on this invitation to those groups within your
companies or partners who focus in this area.

Logistics can be found on the registration site; we will be in the Prague
Congress Center. We don't have an official room block, but there are a
number of nearby hotels, and we'll be adding some suggestions to the reg
page shortly.

As always, there is no cost to attend, but space could fill up quickly. We
encourage you to register early. Link to the schedule will be added to the
website as the technical communities solidify their agendas.

We know that this particular developer event has been a bit more
logistically challenging for all of us than normal, so we appreciate your
patience, and we're excited to see you in Prague!

Please send any event related questions to: eve...@linuxfoundation.org.

Best,

Brandon Wick
Senior Integrated Marketing Manager
The Linux Foundation
bw...@linuxfoundation.org
+1.917.282.0960

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

View/Reply Online (#5510): https://lists.onap.org/g/onap-tsc/message/5510
Mute This Topic: https://lists.onap.org/mt/36449780/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] ONAP El Alto license exceptions - Slides and backup for TSC

2019-10-22 Thread Eric Debeau via Lists.Onap.Org 
Hello

I notice that a huge number of files (41k out of 91k) still does not have 
license. I believe that it is normal for many files (eg .gitignore, INFO.yaml 
files…), but we should correct other files such as js or go files.

We should improve the process and probably include some verification when 
patching some code to verify that all files include some licenses.

I also strongly advice to get rid of all “Proprietary / restricted” notices.

Best Regards

Eric

De : onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] De la part de Jim 
Baker
Envoyé : jeudi 17 octobre 2019 23:49
À : onap-tsc
Objet : [onap-tsc] ONAP El Alto license exceptions - Slides and backup for TSC

Steve Winslow provided the below information as followup to today's TSC 
meeting. Please review and we will need the TSC decision (aka vote) on whether 
to adopt the license waivers as recommended herein. This vote will need to 
close before sign-off. I will work with Catherine to request a vote. Please 
review and express any concerns before 2019-10-22 EOD.
Thanks, Jim



In anticipation of the upcoming El Alto release, attached please find the 
following materials:

  *   summary slide deck regarding the license scan report and analysis; and
  *   .zip file containing the backup data and materials used to produce the 
slides.
Under the ONAP technical charter [1] ONAP uses the Apache-2.0 license for its 
source code and CC-BY-4.0 for documentation. The TSC can approve exceptions to 
this policy by a vote of at least 2/3 of the full TSC. As with prior ONAP 
releases, this approval vote is taken shortly prior to the release.

The attached slides are intended to assist with this, by documenting the 
various licenses that were found in the ONAP codebases and in certain of the 
third party dependencies that are included at build- or install-time.

These slides have been shared with the ONAP Legal Subcommittee and were 
discussed on a call with subcommittee members on October 17. Unfortunately 
there was not a sufficient quorum for the Legal Subcommittee to make a formal 
recommendation to the TSC. However, the attached slides reflect the 
recommendation of the participants who attended the call.

In a very few instances that are noted in the report, license exceptions were 
not recommended, and for those items we have been working with the participants 
to address the findings prior to the release.

Otherwise, the participants who attended the Legal Subcommittee call recommend 
that the TSC adopt exceptions for the license findings documented in the 
report. Slide 34 includes proposed resolution text in case the TSC would like 
to use this as a formal resolution.

[1] 
https://www.onap.org/wp-content/uploads/sites/20/2018/01/ONAP-Project-a-Series-of-LF-Projects-LLC-Technical-Charter-12-22-2017-FINAL.pdf,
 section 7

--
Steve Winslow
Director of Strategic Programs
The Linux Foundation
swins...@linuxfoundation.org


--
Jim Baker
Linux Foundation Networking - Technical Program Manager
mobile: +1 970 227 6007


_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.


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

View/Reply Online (#5507): https://lists.onap.org/g/onap-tsc/message/5507
Mute This Topic: https://lists.onap.org/mt/34914574/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] [Onap-release] Releases not matching intended versions

2019-10-22 Thread Jim Baker 
It's great when we can systematically remove a whole class of errors
automatically! Thanks Jessica!!

On Tue, Oct 22, 2019 at 1:46 PM Jessica Wagantall <
jwagant...@linuxfoundation.org> wrote:

> Sorry for the delay, my filter filtered out this thread.
>
> Yes, this merge job was resolved Oct12.
> I am in another thread explaining the issues with the released versions
> too with Guangrong
>
> Global-jjb has a fix now to flag these occurrences and we will plan for an
> upgrade of global-jjb soon.
>
> I can bring this topic up in the TSC.
>
> On Thu, Oct 17, 2019 at 3:19 AM Lefevre, Catherine <
> catherine.lefe...@intl.att.com> wrote:
>
>> Good morning Guangring, Jessica,
>>
>>
>>
>> Can you please confirm that this issue has been solved ?
>>
>>
>>
>> Many thanks & regards
>>
>> Catherine
>>
>>
>>
>> *From:* onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] *On
>> Behalf Of *Guangrong Fu
>> *Sent:* Saturday, October 12, 2019 2:28 AM
>> *To:* jwagant...@linuxfoundation.org
>> *Cc:* onap-rele...@lists.onap.org; onap-tsc@lists.onap.org;
>> jba...@linuxfoundation.org; kp...@linuxfoundation.org;
>> dmcbr...@linuxfoundation.org
>> *Subject:* Re: [onap-tsc] [Onap-release] Releases not matching intended
>> versions
>>
>>
>>
>> Hi Jess,
>>
>>
>>
>> Thanks for your information.
>>
>>
>>
>> I was trying to fix it by bumping the version number, but the merge job
>> raised a 401 problem (
>> https://jenkins.onap.org/view/holmes/job/holmes-common-master-merge-java/146/console
>> ).
>> Could you please take a look?
>>
>>
>>
>> Thanks,
>>
>> Guangrong
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> 原始邮件
>>
>> *发件人：*jwagant...@linuxfoundation.org 
>>
>> *收件人**：*onap-release ;onap-tsc <
>> onap-tsc@lists.onap.org>;James Baker ;Kenny
>> Paul ;David McBride <
>> dmcbr...@linuxfoundation.org>;
>>
>> *日 **期 * *：*2019年10月12日 05:27
>>
>> *主 **题 **：[Onap-release] Releases not matching intended versions*
>>
>> Dear ONAP team.
>>
>> I wanted to give you a heads up that today we have flagged 3 releases
>> files that were created
>>
>> with the wrong versions. This is caused from the releases files where
>> teams define a "version"
>>
>> variable but the build they are selecting as a candidate has a different
>> version.
>>
>> For example:
>>
>>
>>
>> *https://gerrit.onap.org/r/#/c/demo/+/96967/1/releases/1.5.0.yaml
>> 
>> -> the release candidate*
>>
>> *is 1.6.0 not
>> 1.5.0: https://jenkins.onap.org/job/demo-maven-stage-master/151/console
>> *
>>
>>
>>
>> *https://gerrit.onap.org/r/#/c/cli/+/96781/2/releases/5.0.0-maven.yaml
>> 
>> -> the release candidate*
>>
>> *is 4.0.0 not 5.0.0
>> -> https://jenkins.onap.org/job/cli-maven-stage-master/113/console
>> *
>>
>>
>>
>> *https://gerrit.onap.org/r/#/c/holmes/common/+/96870/1/releases/maven-1.2.12.yaml
>> 
>> ->*
>>
>> *the release candidate is 1.2.11 not 1.2.12
>> -> https://jenkins.onap.org/job/holmes-common-maven-stage-master/162/console
>> *
>>
>>
>>
>> Please make sure to double check your pom and version.properties that
>> they match the version
>>
>> your team is working on.
>>
>>
>>
>> *Comitters:* please double check releases files and make sure the
>>

Re: [onap-tsc] [Onap-release] Releases not matching intended versions

2019-10-22 Thread Jessica Wagantall 
Sorry for the delay, my filter filtered out this thread.

Yes, this merge job was resolved Oct12.
I am in another thread explaining the issues with the released versions too
with Guangrong

Global-jjb has a fix now to flag these occurrences and we will plan for an
upgrade of global-jjb soon.

I can bring this topic up in the TSC.

On Thu, Oct 17, 2019 at 3:19 AM Lefevre, Catherine <
catherine.lefe...@intl.att.com> wrote:

> Good morning Guangring, Jessica,
>
>
>
> Can you please confirm that this issue has been solved ?
>
>
>
> Many thanks & regards
>
> Catherine
>
>
>
> *From:* onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] *On
> Behalf Of *Guangrong Fu
> *Sent:* Saturday, October 12, 2019 2:28 AM
> *To:* jwagant...@linuxfoundation.org
> *Cc:* onap-rele...@lists.onap.org; onap-tsc@lists.onap.org;
> jba...@linuxfoundation.org; kp...@linuxfoundation.org;
> dmcbr...@linuxfoundation.org
> *Subject:* Re: [onap-tsc] [Onap-release] Releases not matching intended
> versions
>
>
>
> Hi Jess,
>
>
>
> Thanks for your information.
>
>
>
> I was trying to fix it by bumping the version number, but the merge job
> raised a 401 problem (
> https://jenkins.onap.org/view/holmes/job/holmes-common-master-merge-java/146/console
> ).
> Could you please take a look?
>
>
>
> Thanks,
>
> Guangrong
>
>
>
>
>
>
>
>
>
> 原始邮件
>
> *发件人：*jwagant...@linuxfoundation.org 
>
> *收件人**：*onap-release ;onap-tsc <
> onap-tsc@lists.onap.org>;James Baker ;Kenny
> Paul ;David McBride <
> dmcbr...@linuxfoundation.org>;
>
> *日 **期 * *：*2019年10月12日 05:27
>
> *主 **题 **：[Onap-release] Releases not matching intended versions*
>
> Dear ONAP team.
>
> I wanted to give you a heads up that today we have flagged 3 releases
> files that were created
>
> with the wrong versions. This is caused from the releases files where
> teams define a "version"
>
> variable but the build they are selecting as a candidate has a different
> version.
>
> For example:
>
>
>
> *https://gerrit.onap.org/r/#/c/demo/+/96967/1/releases/1.5.0.yaml
> 
> -> the release candidate*
>
> *is 1.6.0 not
> 1.5.0: https://jenkins.onap.org/job/demo-maven-stage-master/151/console
> *
>
>
>
> *https://gerrit.onap.org/r/#/c/cli/+/96781/2/releases/5.0.0-maven.yaml
> 
> -> the release candidate*
>
> *is 4.0.0 not 5.0.0
> -> https://jenkins.onap.org/job/cli-maven-stage-master/113/console
> *
>
>
>
> *https://gerrit.onap.org/r/#/c/holmes/common/+/96870/1/releases/maven-1.2.12.yaml
> 
> ->*
>
> *the release candidate is 1.2.11 not 1.2.12
> -> https://jenkins.onap.org/job/holmes-common-maven-stage-master/162/console
> *
>
>
>
> Please make sure to double check your pom and version.properties that they
> match the version
>
> your team is working on.
>
>
>
> *Comitters:* please double check releases files and make sure the
> candidate being proposed
>
> in the "log_dir" variable is the actual version you want to release.
>
>
>
> Also, please please please do not overwrite Jenkins failures. Please
> report them instead since
>
> fixing bad merge changes are difficult to fix.
>
>
>
> Thanks a ton
>
> Jess
>
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all