Hello Team,

When are you going to share the next approved talks? It's already the 11th
of July.

Don't you think you guys are taking so much time? Please update asap.

Thanks.

<https://about.me/rowdymehul?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=gmail_api&utm_content=thumb>




<https://about.me/rowdymehul?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=gmail_api&utm_content=thumb>





Mehul Patel
about.me/rowdymehul
<https://about.me/rowdymehul?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=gmail_api&utm_content=thumb>
https://www.linkedin.com/in/rowdymehul

On Mon, Jul 9, 2018 at 12:49 AM, Gunnar Wolf <gw...@debian.org> wrote:

> Taowa dijo [Thu, Jul 05, 2018 at 08:00:03PM -0400]:
> > Hello,
> >
> > I understand that these kinds of answers are frustrating, but the
> > content team, as with every other team, is made up of
> > volunteers. There are only a small number of people who make them up
> > and they are all trying their best to do so as fast as possible.
>
> Thanks a lot, Taowa.
>
> Thing is: Yes, we wanted to send out the schedule at least by July
> 1st. But all of the Content Team members have been very busy. I (as
> the content team lead - Ultimately, I took the responsability to get
> this job done!) had set out as my goal for last week to build the
> schedule, and I have a *partial* advance. But I am not in Mexico City,
> and won't return before tomorrow night. I will try to work on it
> during Tuesday, and with great luck, by Wednesday we will have
> something to show to the world.
>
> But I also have a life and a real-life job. And we also have (small
> but needed) family vacations. And everything. So, please, be patient.
>
> I'm sorry not to accept help from just about anybody - Building a
> schedule is a process that seems easy, but requires a bit of expertise
> and to consider several issues you only get from experience... So I'm
> only asking for the Content Team (or, at most, the broader
> organization team) for help.
>

Reply via email to