Jess,
I reviewed the revised repo requests and would like to move ahead with this if
no different opinion is announced. According to Morgan's email, he has created
ticket for that. Please check it
Xinhui
On 12/23/19, 10:17 AM, "Xinhui Li" <lxin...@vmware.com> wrote:
The request is received
Thanks,
Xinhui
On 12/23/19, 12:19 AM, "morgan.richo...@orange.com"
<morgan.richo...@orange.com> wrote:
Hi
I updated the page
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.onap.org%2Fdisplay%2FDW%2FResources%2Band%2BRepositories&data=02%7C01%7Clxinhui%40vmware.com%7C21e838499c8a43607eb908d787d46208%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637127218567816690&sdata=Eq1V4HGXRHDA%2BIIJNhOwKj9WdjF1fcStYxC2PjiAeko%3D&reserved=0
I highlighted the request for the 3 new repositories in Yellow in the
table.
I also
- updated the list of committers/contributors (not done for a while -
I think it would be better to do it dynamically (using INFO.yaml)
rather than using static declaration)
- complete the info (lots of id were missing)
- added a section for the archived repositories (devtool and
benchmarking not active for at least 2 releases have been archived)
- added a column to split committers on all the repositories and thoses
dealing with demo
- created a column component group, as we may have a notion of
groups/subgroups to host the repos - easier to manage the 13
repositories
/Morgan
Le samedi 21 décembre 2019 à 00:32 +0000, Xinhui Li a écrit :
> Morgan,
>
> Thanks for forwarding the first email because I did not receive
> it. pls follow below guide to fill in the required information to
> request a new repo
>
> At the same time, I checked the link you sent over but cannot access
> the content. I will touch Jessica for the base.
>
> "
> For each project the PTL is responsible for updates all the sections
> to support their project accordingly .
>
> The PTL go to the Resources and Repositories section for their
> project
> The PTL fills in the required information for the new repo(s)
> they are requesting in the Release Components Name table. Please
> highlight the newly requested repo using fill colors and/or bold or
> colored font.
> The PTL emails infrastructure-coordina...@onap.org with a
> pointer to the data they just entered. This email must include:
> The LFIDs for the committers for the new repo(s)
> The justification as to why an existing repo cannot be used.
> The Infrastructure Coordinator will review the completeness and
> the accuracy of the information.
> If there are no perceived issues with the request,
> the Infrastructure Coordinator will open a repo creation request via
> support.linuxfoundation.org without engaging the TSC.
> If there are perceived issues
> the Infrastructure Coordinator will contact the PTL for
> clarification.
> If following the conversation between the PTL there are
> still unreconciled issues, the Infrastructure Coordinator will
> escalate the request to the TSC for review and approval.
> "
>
> Thanks,
> Xinhui
>
> On 12/19/19, 11:30 PM, "onap-tsc@lists.onap.org on behalf of Morgan
> Richomme via Lists.Onap.Org" <onap-tsc@lists.onap.org on behalf of
> morgan.richomme=orange....@lists.onap.org> wrote:
>
> Hi
>
> I did not get any feedback on this request (see below). sent on
> the
> 21st of November
> For the next PTL meeting, some projects asked for a status on the
> availability of such images.
> But without repo, we cannot start building dockers.
> With the xmas break, it will be hard to finalize this before 2020
> but
> could you provide a feedback on the request.
>
> Regards
>
> Morgan
>
> -----------------------------------------------------------------
> -----
> Le jeudi 21 novembre 2019, Morgan RICHOMME a écrit :
>
> Hi XinHui
>
> I open a new ticket for the creation of 3 new repositories aiming
> to
> host Dockerfiles to build refeence docker images to be used as
> baseline
> images (Alpine 11 + Java11 and Alpine11 + Python3) by the other
> ONAP
> projects.
> - integration/docker/onap-baseline
> - integration/docker/onap-java11
> - integration/docker/onap-python3.7
>
>
>
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fjira.linuxfoundation.org%2Fservicedesk%2Fcustomer%2Fportal%2F2%2FIT-18325&data=02%7C01%7Clxinhui%40vmware.com%7C21e838499c8a43607eb908d787d46208%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637127218567816690&sdata=TBXMAlbcLs70%2B0T8UpI%2BYPt46onC11pk3N9ld2yrWVg%3D&reserved=0
>
> Could you validate this request?
>
> Regards
>
> Morgan
>
> NB: I did not find neither the infra-coordinator nor XinHui when
> sharing the ticket.
>
> _________________________________________________________________
> ________________________________________________________
>
> 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.
>
>
>
>
>
>
_________________________________________________________________________________________________________________________
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 (#5800): https://lists.onap.org/g/onap-tsc/message/5800
Mute This Topic: https://lists.onap.org/mt/69335793/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]
-=-=-=-=-=-=-=-=-=-=-=-
