Oliver, A proposal is not 'proposed' till an email to the TSC has been sent. There is a two week public comment period *after* that email has been sent before it is eligible for a creation review by the TSC. Once a proposal has been announced to the TSC I would suggest providing comment on that thread via email.
Before the email is sent to the TSC announcing the proposal, comments on the wiki are likely a good vehicle for feedback. Ed On Mon, May 8, 2017 at 12:41 PM, SPATSCHECK, OLIVER (OLIVER) < [email protected]> wrote: > > As I am ready to start commenting on the various proposals I was wondering > what mechanism we should use for that. Should we just use the confluence > comment feature? If we do that we need to make sure that the primary > contacts are responsive in editing the proposal/responding to the comments. > What’s the protocol? > > I know Mazin was pushing for having most proposals ready by Thu so there > is little time left… . > > Thoughts? > > Oliver > > > On May 8, 2017, at 8:47 AM EDT, Ed Warnicke <[email protected]> wrote: > > > > I am agnostic as to which way we resolve it, so long as they are indexed > in one place and it's obvious how to find it :) > > > > Ed > > > > On Mon, May 8, 2017 at 12:01 AM, Kanagaraj Manickam < > [email protected]> wrote: > > There is an another wiki https://wiki.onap.org/display/ > DW/Project+Proposal+Kickoff where most of the projects are proposed. > > > > Should we bring them under the page listed here > https://wiki.onap.org/display/DW/Proposing+A+Project > > > > > > > > Regards > > > > Kanagaraj M > > > > ************************************************************ > *************************** > > 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、 > 复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！********* > ************************************************************ > ***************** > > > > ************************************************************ > *************************** > > This e-mail and its attachments contain confidential information from > HUAWEI, which is intended only for the person or entity whose address is > listed above. Any use of the information contained herein in any way > (including, but not limited to, total or partial disclosure, > reproduction, or dissemination) by persons other than the intended > recipient(s) is prohibited. If you receive this e-mail in error, please > notify the sender by phone or email immediately and delete it! > > ************************************************************ > *************************** > > > > > > > > From: [email protected] [mailto:onap-tsc-bounces@ > lists.onap.org] On Behalf Of Danny Lin > > Sent: Sunday, May 07, 2017 4:14 AM > > To: Ed Warnicke > > Cc: [email protected]; onap-tsc > > Subject: Re: [onap-tsc] [onap-discuss] Projects > > > > > > > > Good suggestion, Ed. I will list multi-VIM project there. Thanks. > > > > > > > > Danny > > > > > > On May 6, 2017, at 3:41 PM, Ed Warnicke <[email protected]> wrote: > > > > I have seen a bunch of proposal wiki pages for projects, but only see a > small number listed in the index for such proposals: > > > > https://wiki.onap.org/display/DW/Proposing+A+Project > > > > > > > > For the folks working on proposals, would you list them there? > > > > > > > > It allows the others who might be interested to see that there is a > project proposal coming together and participate :) > > > > > > > > Ed > > > > > > > > On Sat, May 6, 2017 at 9:08 AM, GILBERT, MAZIN E (MAZIN E) < > [email protected]> wrote: > > > > Team, > > > > First, thank you for spending a week in NJ brainstorming, planning and > architecting our next 4Q17 release. > > Our next step is to have the smaller community teams flush out their > project proposals, fill in gaps, and communicate > > with other teams to consolidate proposals in the case of overlaps. > Please notify us if your proposal is ready to be > > reviewed for feedback. I expect the majority of proposals will be in > that stage before our Thursday TSC meeting > > on May 11th. > > > > Have a wonderful weekend. > > mazin > > > > > > _______________________________________________ > > onap-discuss mailing list > > [email protected] > > https://lists.onap.org/mailman/listinfo/onap-discuss > > > > > > > > _______________________________________________ > > onap-discuss mailing list > > [email protected] > > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists. > onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwICAg&c= > uilaK90D4TOVoH58JNXRgQ&r=3nVF4lkCrih5WqBdByLDuw&m=vlMAtln- > nCY4wHPDZBk3vYGpkIUrdU-nEUWD5J4G7Oo&s=bjIf_nHjEJ9EvLfgMgrX9fIECr_ > GPPLraqE9rWQN8bA&e= > > > > > > _______________________________________________ > > onap-discuss mailing list > > [email protected] > > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists. > onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwICAg&c= > LFYZ-o9_HUMeMTSQicvjIg&r=9iyuArzgyekj47PZSPfIijI2cSHsUJ > tAlcTA0X_udNI&m=0RAg6WGUQczuY_PyZwWICxxhGGt7oGP1B_2NZmNihFc&s=L8gq8Zi-32C- > rfQuRnKL9AOLrSsrKvcfkTkIkVcliLM&e= > >
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
