I think this more correctly captures the discussion and intent. So I’ve updated the text as follows
Was: The time has come to transition ArchNav out of the lab an into a production environment for the Architecture Subcommittee. NOW: There were discussions underway to transition ArchNav out of the lab an into a production environment for the Architecture Subcommittee. Was: The potential exists for ArchNav to also play a role in ONAP's documentation, education and marketing efforts, but there are alternatives, integrations and alignment that the Doc team also may want to pursue instead. NOW: The Doc team also wants to pursue ArchNav like functionality however they feel there is no need for it to be a separate application. Instead they believe the same functionality can be implemented directly in ReadtheDocs which is the platform we use for our official documentation. Also I changed/rearranged the outcomes to read: * Open Source Project Management: Consensus is reached on the most practical approach for the community: 1. ArchNav will not be migrated and a solution will be implemented in ReadTheDocs infrastructure. 2. ArchNav will be migrated to infrastructure managed by the Linux Foundation as a shared resource for the Doc Team and Subcommittee 3. ArchNav will be migrated to infrastructure managed by the Linux Foundation as a stand-alone solution for the Subcommittee * Technical: Regardless of the three possible project management outcomes above there will be tooling and scripting required throughout the course of this internship either as proof points, implementation and deployment or migration tasks to deliver the agreed upon solution. I will mark this as approved for the purpose of getting the listing submitted. The finer details we can work through in the coming days. Thanks! -kenny From: Lefevre, Catherine <[email protected]> Sent: Friday, April 9, 2021 2:16 PM To: [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; 'Chaker Al-Hakim' <[email protected]> Subject: RE: [onap-discuss] Revised Intern proposal #doc #tsc Importance: High Thanks Timo and Kenny ! @Timo – My understanding is aligned with yours a.k.a. we sort of agreed in TSC yesterday studying and potentially starting to implement ArchNav functionality in RTD was part of this proposal. @Kenny – today is the deadline for TSC approval. My understanding from yesterday’s call was that if we implement functionalities offered by ArchNAV into RTD then TSC was approving the internship proposal. Is everything good now? Many thanks & regards Catherine From: [email protected] <mailto:[email protected]> <[email protected] <mailto:[email protected]> > On Behalf Of Perala, Timo (Nokia - FI/Espoo) Sent: Friday, April 9, 2021 2:51 PM To: [email protected] <mailto:[email protected]> ; [email protected] <mailto:[email protected]> ; [email protected] <mailto:[email protected]> ; [email protected] <mailto:[email protected]> ; 'Chaker Al-Hakim' <[email protected] <mailto:[email protected]> > Subject: Re: [onap-discuss] Revised Intern proposal #doc #tsc Thanks Kenny! I went through the proposal and started to edit, but then decided to write this comment instead. Well, did some non-native writer edits though, nits 😉 The portion of the text I got stuck with and considered to modify was these two paragraphs at the end: ======= 8< ======== 8< ========= The time has come to transition ArchNav out of the lab an into a production environment for the Architecture Subcommittee. This is a pretty straight forward technical effort for anyone with the "Must Have" skills listed below. The potential exists for ArchNav to also play a role in ONAP's documentation, education and marketing efforts, but there are alternatives, integrations and alignment that the Doc team also may want to pursue instead. So what is the right thing to do? ======= 8< ======== 8< ========= I guess the first one describes the original intent, and likely is a good idea still to improve the tool from demo to more robust “production grade”. I believe what the Doc team aspiration has been and is, is to implement the same in RTD. And I thought we sort of agreed in TSC yesterday studying and potentially starting to implement ArchNav functionality in RTD was part of this proposal. Maybe even the primary target? The reason I decided not to edit the proposal to reflect the above was that I was not sure if this indeed was the agreement, or if I just thought it was the agreement because that’s what I wanted to hear (well, after all, I’m a Doc committer). I assume once we have successfully recruited an intern, a more specific task description needs to be worked out by the three mentors listed in the proposal. Maybe at that time we can consider how exactly we want to formulate the task to study (and implement) ArchNav on RTD. With that assumption I entered my “OK” to the proposal wiki page. cheers Timo From: [email protected] <mailto:[email protected]> <[email protected] <mailto:[email protected]> > On Behalf Of Kenny Paul via lists.onap.org Sent: Friday, April 9, 2021 2:20 AM To: [email protected] <mailto:[email protected]> ; [email protected] <mailto:[email protected]> ; 'Chaker Al-Hakim' <[email protected] <mailto:[email protected]> > Cc: [email protected] <mailto:[email protected]> Subject: [onap-discuss] Revised Intern proposal #doc #tsc Dear TSC and Doc team members; I’ve reworked the proposal based upon today’s discussion. https://wiki.lfnetworking.org/x/twIyAw <https://urldefense.com/v3/__https:/wiki.lfnetworking.org/x/twIyAw__;!!BhdT!09WaeKC6m_AiE0M_E0mMItg1_NKZDL36ilrVHM4frm37e3_gOeUy5746y0avptx6XnA-Arw$> Please read through it and feel free to make suggestions. If you think it is OK please add a comment to the page saying so. Thanks! -kenny -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#23127): https://lists.onap.org/g/onap-discuss/message/23127 Mute This Topic: https://lists.onap.org/mt/81956187/21656 Mute #doc:https://lists.onap.org/g/onap-discuss/mutehashtag/doc Mute #tsc:https://lists.onap.org/g/onap-discuss/mutehashtag/tsc Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
