If you don't make the meeting then works for me because: I have same probleme with my ticket and I comment on track. If somebody has problems with ticket then can give you one mail. Thank you. Regards. 2016-08-17 19:39 GMT+03:00 Sylvia Sánchez <lailahfsf@xxxxxxxxx>: > > Mmm... If it has any use for you, I can try as I'm usually awake late at > night, but I can't promise. > > > Cheers, > Sylvia > > > On 17 August 2016 at 14:18, Máirín Duffy <duffy@xxxxxxxxxx> wrote: >> >> Hi folks, >> >> I can't make this meeting due to a prior commitment, and it'll be hard for >> Sirko bc it's 1 AM his time. Can anybody make this meeting? Basically you >> just speak up and give our status. >> >> ~m >> >> ----- Forwarded Message ----- >> From: "Justin W. Flory" <jflory7@xxxxxxxxx> >> To: "Fedora + Community + Operations = Fedora CommOps" >> <commops@xxxxxxxxxxxxxxxxxxxxxxx> >> Sent: Monday, August 15, 2016 1:07:48 PM >> Subject: [commops] Fwd: Fedora 25 Alpha Release Readiness Meeting, >> Thursday, August 18 @ 19:00 UTC >> >> Coming up this week! >> >> >> -------- Forwarded Message -------- >> Subject: Fedora 25 Alpha Release Readiness Meeting, Thursday, August 18 >> @ 19:00 UTC >> Date: Mon, 15 Aug 2016 15:32:13 +0200 >> From: Jan Kurik <jkurik@xxxxxxxxxx> >> Reply-To: logistics@xxxxxxxxxxxxxxxxxxxxxxx >> To: Fedora Logistics List <logistics@xxxxxxxxxxxxxxxxxxxxxxx>, >> ambassadors <ambassadors@xxxxxxxxxxxxxxxxxxxxxxx>, Fedora Design Team >> <design-team@xxxxxxxxxxxxxxxxxxxxxxx>, docs >> <docs@xxxxxxxxxxxxxxxxxxxxxxx>, Fedora Marketing team >> <marketing@xxxxxxxxxxxxxxxxxxxxxxx>, For testing and quality assurance >> of Fedora releases <test@xxxxxxxxxxxxxxxxxxxxxxx>, Paul W. Frields >> <pfrields@xxxxxxxxxx>, Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx>, dennis >> <dennis@xxxxxxxx>, Fedora Websites Team >> <websites@xxxxxxxxxxxxxxxxxxxxxxx>, Fedora Translation Project List >> <trans@xxxxxxxxxxxxxxxxxxxxxxx>, devel-announce@xxxxxxxxxxxxxxxxxxxxxxx >> >> Join us on irc.freenode.net in #fedora-meeting for the Fedora 25 Alpha >> Release Readiness Meeting meeting. >> >> The meeting is going to be held on Thursday, August 18, 2016 19:00 >> UTC. Please check the [FedoCal] link for your time zone. >> >> We will meet to make sure we are coordinated and ready for the Alpha >> release of Fedora 25 on Tuesday, August 23nd, 2016. Please note that >> this meeting is going to be held even if the release is delayed at the >> Go/No-Go meeting on the same day two hours earlier. >> >> You may received this message several times, but it is by purpose to >> open this meeting to the teams and to raise awareness, so hopefully >> more team representatives will come to this meeting. This meeting >> works best when we have representatives from all of the teams. >> >> [FedoCal] https://apps.fedoraproject.org/calendar/meeting/4486/ >> >> More information available at: >> https://fedoraproject.org/wiki/Release_Readiness_Meetings >> >> Thank you for your support and Regards, Jan >> -- >> Jan Kuřík >> Platform & Fedora Program Manager >> Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic >> _______________________________________________ >> logistics mailing list >> logistics@xxxxxxxxxxxxxxxxxxxxxxx >> >> https://lists.fedoraproject.org/admin/lists/logistics@xxxxxxxxxxxxxxxxxxxxxxx >> >> >> _______________________________________________ >> Fedora Community Operations (CommOps) mailing list >> commops@xxxxxxxxxxxxxxxxxxxxxxx >> >> https://lists.fedoraproject.org/admin/lists/commops@xxxxxxxxxxxxxxxxxxxxxxx >> >> _______________________________________________ >> design-team mailing list >> design-team@xxxxxxxxxxxxxxxxxxxxxxx >> >> https://lists.fedoraproject.org/admin/lists/design-team@xxxxxxxxxxxxxxxxxxxxxxx >> > > > _______________________________________________ > design-team mailing list > design-team@xxxxxxxxxxxxxxxxxxxxxxx > https://lists.fedoraproject.org/admin/lists/design-team@xxxxxxxxxxxxxxxxxxxxxxx > _______________________________________________ design-team mailing list design-team@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/design-team@xxxxxxxxxxxxxxxxxxxxxxx
