Either way is fine with me. In general 16:00 UTC is a good choice since it seems not to be mid-might for anyone that is involved.

Best regards, Mark

Am 30.08.2014 um 12:53 schrieb Thorben Janssen <thjanssen123@gmail.com>:

Wednesday at the same time is fine for me.
Do you want to shift all meetings or only this one?

Regards,
Thorben

---

Von: Antoine Sabot-Durand
Gesendet: ‎30.‎08.‎2014 12:18
An: John D. Ament
Cc: cdi-dev
Betreff: Re: [cdi-dev] Spec launch meeting and CDI weekly meeting

Hi John,

Sorry to have missed that. According to Pete, French are holidays specialists. I guess I have to improve my expertise in this domain ;).

 Is it ok for everybody to switch the meeting on Wednesday at the same time ? If there ware no objection I will send you an invitation Monday.

Antoine

Le 29 août 2014 à 18:53, John D. Ament <john.d.ament@gmail.com> a écrit :

Could it be pushed to later in the week? Monday's a holiday in the US.

On Fri, Aug 29, 2014 at 9:32 AM, Antoine Sabot-Durand <antoine@sabot-durand.net> wrote:

Hi All,

On CDI 1.1, we use to have a weekly meeting each monday at 16:00 UTC (that’s 9:00 am PDT, 6:00 pm CEST and 9:30 pm  IST). It’s hard to find a time slot that please everybody (from US West Coast to India), so Ir propose we keep this track. Now, if you have issue with this slot (if you live in New Zealand or Australia) say it and we’ll try to figure out a better slot (even if there’s no ideal one).

The meeting place is the IRC channel and last one hour. We use an IRC bot (jbott) to keep track of meeting minutes for the record or people unable to attend the meeting. You can get familiarised with BOT commands here : 

https://wiki.debian.org/MeetBot

So I propose we have our JSR launch meeting next monday (sept 1st) with the following agenda :

- Discussion on the working method and tools used (mainly do we use Google Drive or Github with Asciidoc for working doc)

- Discussion on each workshop I mentioned in my previous post and missing workshop

  * Workshop teams

* Workflow chosen

* estimated deadline (hard to say since we don’t know our workforce, but will be refined later)

- Q & A if we still have time 

Note that It think we should avoid talking about specific content of workshop except if you think things are missing or that we could forgot them.

If you want to see other points in the agenda let me know.

I’m thrilled to start this great project with you guys.

Antoine

_______________________________________________
cdi-dev mailing list
cdi-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/cdi-dev

Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 (http://www.apache.org/licenses/LICENSE-2.0.html). For all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.

_______________________________________________
cdi-dev mailing list
cdi-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/cdi-dev

Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 (http://www.apache.org/licenses/LICENSE-2.0.html). For all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.

_______________________________________________
cdi-dev mailing list
cdi-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/cdi-dev

Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 (http://www.apache.org/licenses/LICENSE-2.0.html). For all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.