Yes, it should be Dec 14 according to the rule we set.

Most time it is the second meeting of each month, but in Dec, the third. So
I was afraid some people may not notice the tiny difference.

Anyway, let's discuss it in tomorrow's meeting.
--
Yujun

On Tue, Nov 8, 2016 at 6:26 PM <[email protected]> wrote:

> Hi
>
> no problem, I put Bottleneck update instead
>
> regarding the meeting, let' discuss 5 minutes tomorrow.
> I do not know if the second meeting of the month would be easier than the
> rule the second wednesday of the month.
> so for me in December the APAC slot should be the 14th of December (not
> the 1st of December...)
>
> Maybe an alignment on the day (always Thursday) would also a good idea...
>
> /Morgan
>
>
> Le 08/11/2016 à 10:23, Yujun Zhang a écrit :
>
> Hi, all
>
> Thank Morgan for bringing QTIP to the agenda.
>
> May I propose to postpone it to next week? I haven't get the presentation
> ready yet :-(. It is too hurry for tomorrow.
>
> About the APAC slot, it is even more confusing for Dec because Dec 1st is
> Thursday.
>
> How about modifying the rule as *2nd meeting* of each month for APAC
> meeting. What do you think?
> --
> Yujun
>
> On Tue, Nov 8, 2016 at 5:14 PM <[email protected]> wrote:
>
> Hi
>
> the next weekly meeting APAC slot is not clear. We indicate 2 dates in the
> wiki: https://wiki.opnfv.org/display/meetings/TestPerf
>
> According to the calendar it is on the 9th but the agenda is declared for
> the 10th...
>
> I assume it is the 9 8UTC => I modified the wiki
>
> if so for the moment we do not have chair/minutes and the agenda is
> limited to the discussion on priority for Danube (I assume I will introduce
> the topic during the TSC meeting today see attached "Building a TSC vision
> for Danube" deck )
>
> I also created some slides to illustrate what we have discussed in
> Barcelona on the some aggregation actions to provide a consistent Testing
> reporting view as well as web pages to allow scenario owner/user to select
> their list of cases among all the test cases...
>
> I can present it but I have a constraints at 8h25 so I may not be able to
> attend all the meeting
>
> Suggested agenda (do not hesitate to amend it on the wiki...)
>
>    - Testing community Danube release landing page + scenario selection
>    proposals(15')
>    - Test community common goals (20')
>    https://etherpad.opnfv.org/p/TestCommunityGoals
>    - QTIP presentation (15')
>    - AoB (5')
>
> /Morgan
>
> _________________________________________________________________________________________________________________________
>
> 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.
>
>
>
> --
> Morgan Richomme
> Orange/ IMT/ OLN/ CNC/ NCA/ SINA
>
> Network architect for innovative services
> Future of the Network community member
> Open source Orange community manager
>
>
> tel. +33 (0) 296 072 106
> mob. +33 (0) 637 753 [email protected]
>
> _________________________________________________________________________________________________________________________
>
> 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.
>
>
_______________________________________________
opnfv-tech-discuss mailing list
[email protected]
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Reply via email to