Return-Path: X-Original-To: apmail-community-dev-archive@minotaur.apache.org Delivered-To: apmail-community-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8C149172BD for ; Fri, 10 Apr 2015 21:27:44 +0000 (UTC) Received: (qmail 28779 invoked by uid 500); 10 Apr 2015 21:27:44 -0000 Delivered-To: apmail-community-dev-archive@community.apache.org Received: (qmail 28522 invoked by uid 500); 10 Apr 2015 21:27:44 -0000 Mailing-List: contact dev-help@community.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@community.apache.org Delivered-To: mailing list dev@community.apache.org Received: (qmail 28509 invoked by uid 99); 10 Apr 2015 21:27:44 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Apr 2015 21:27:44 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of pierre.smits@gmail.com designates 209.85.217.178 as permitted sender) Received: from [209.85.217.178] (HELO mail-lb0-f178.google.com) (209.85.217.178) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Apr 2015 21:27:40 +0000 Received: by lbcga7 with SMTP id ga7so22785544lbc.1 for ; Fri, 10 Apr 2015 14:27:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=MmIN6Ed55q7tMjl1A6G+/mm7OI4g6fCPJsyyYH2C5y8=; b=O9TTnczzYBKsDqLwDJyurMito9x40roGQ1LHg2tqTynYr3+2H1AnvoMkAI11+lxl1d lZ8sF+6N2a6qWq0IQoP+zgyvEJKU8HpZRq507+I7M9/HLX2zw1AC922afcy2iNUdCKqq /5qoD6CVS2WI49GPIgKWUHouXPXDvfAi7e0rUzu24kA7VVQUrHZbHmoVkukQWPrepoqO R0DIJSf6DwOtU5wHvcPKzZ+onIQh8KVKLXQuV1UyzWaZc69SaiAuO2DeMwHNNRM4mcs5 CIymGrAIoFU0r8UZC88P9YoF4QGIgx3d6YdHiu2DZNNc+F0GrfpRtaoPq2RDBhr0Wf/e FH8Q== MIME-Version: 1.0 X-Received: by 10.112.167.228 with SMTP id zr4mr3051986lbb.113.1428701239143; Fri, 10 Apr 2015 14:27:19 -0700 (PDT) Received: by 10.25.170.143 with HTTP; Fri, 10 Apr 2015 14:27:19 -0700 (PDT) In-Reply-To: References: <55283A10.4000103@rcbowen.com> Date: Fri, 10 Apr 2015 23:27:19 +0200 Message-ID: Subject: Re: Events calendar From: Pierre Smits To: "dev@community.apache.org" Content-Type: multipart/alternative; boundary=001a11c2432ad9723c0513656dfe X-Virus-Checked: Checked by ClamAV on apache.org --001a11c2432ad9723c0513656dfe Content-Type: text/plain; charset=UTF-8 The question is surely important, and can't be circumvented for a organisation that spends a load of money on furthering the projects and their works. Not only do we need mid and long term plans from every office, but we also need the supporting and governing processes and procedures written down and made available to the ASF community. That way we al can see what needs to be done when it needs to be done. For example, recent mails regarding the various activities executed for the ACNA 15 event pointed out that things got forgotten (like presentation templates). For such events we need scripts, and such scripts need to evaluated and improved after the event. That way we don't make the mistakes when doing a new event like we did in the past. Most importantly, Offices need to take ownership. Best regards, Pierre Smits *ORRTIZ.COM * Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com On Fri, Apr 10, 2015 at 11:09 PM, Ross Gardler (MS OPEN TECH) < Ross.Gardler@microsoft.com> wrote: > To get people involved we need to provide value. Today, we offer no value. > So, if I may, I would like to answer a slightly different question. The one > I want to answer is "how can we provide value so that PMCs will proactively > maintain a central events calendar?" Here's my starting answer, more ideas > very welcome... > > VP Brand has added a clause to the events policy that requires avoidance > of event date clashes. > > Marketing is ramping up on a quarterly report that, once we are in the > swing of things, will be broadly distributed (and thus provide visibility > for events listed in the calendar). > > We have a budget for stickers and other such giveaways at community > events, we won't ship those unless it's on the calendar. > > More?.... > > -----Original Message----- > From: Rich Bowen [mailto:rbowen@rcbowen.com] > Sent: Friday, April 10, 2015 2:01 PM > To: dev > Subject: Events calendar > > Today I found out about yet another Apache event that is almost here and I > hadn't heard about before. > > I also noticed that http://www.apache.org/events/ is ... kinda > embarrassing. > > This, in conjunction with Jan's question a week ago about who managed the > calendar on people.a.o, which is completely a separate thing from the > calendar I thought he was talking about - the Google calendar, at > http://community.apache.org/calendars/conferences.html - makes me wonder > why this is so hard for us. > > So, two questions: > > 1) What other calendars are out there, and what can we do to consolidate > them? > > 2) How can we get PMCs to put their events in that consolidated calendar, > once it exists, so that we don't have all of these last-minute event > surprises, and, also, so that we can help in promoting our communities' > events? > > Suggestions welcome. > > I, for one, am a fan of nuking every calendar we come across, and > publishing the above Google Calendar all over the place, and then making a > google form for people to submit events. > > --Rich > > -- > Rich Bowen - rbowen@rcbowen.com - @rbowen http://apachecon.com/ - > @apachecon > --001a11c2432ad9723c0513656dfe--