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 457C56969 for ; Fri, 20 May 2011 13:46:02 +0000 (UTC) Received: (qmail 30660 invoked by uid 500); 20 May 2011 13:46:02 -0000 Delivered-To: apmail-community-dev-archive@community.apache.org Received: (qmail 30598 invoked by uid 500); 20 May 2011 13:46:02 -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 30590 invoked by uid 99); 20 May 2011 13:46:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 May 2011 13:46:02 +0000 X-ASF-Spam-Status: No, hits=-1.6 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [129.67.1.165] (HELO relay1.mail.ox.ac.uk) (129.67.1.165) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 May 2011 13:45:56 +0000 Received: from smtp0.mail.ox.ac.uk ([129.67.1.205]) by relay1.mail.ox.ac.uk with esmtp (Exim 4.75) (envelope-from ) id 1QNQ1G-0008PH-59 for dev@community.apache.org; Fri, 20 May 2011 14:45:34 +0100 Received: from dhcp29.oucs.ox.ac.uk ([129.67.103.29]) by smtp0.mail.ox.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1QNQ1G-00043T-0L for dev@community.apache.org; Fri, 20 May 2011 14:45:34 +0100 Message-ID: <4DD6707E.7010508@apache.org> Date: Fri, 20 May 2011 14:45:34 +0100 From: Ross Gardler User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: dev@community.apache.org Subject: Re: Shared Calendars References: <6CEC5AAC-02C4-4333-99EB-89D9B14E5CB1@apache.org> <4DD65423.7060003@apache.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Oxford-Username: oucs0040 On 20/05/2011 14:26, Christian Grobmeier wrote: >>> But why not having a Calendar for all projects. One might be able to >>> filter for a specific project or event type, be it "release", "dinner" >>> or whatever. Other events would become a better visibility, like >>> Apache CON or a retreat >> >> I think this would be really good. However, I don't think we need to dictate >> where projects keep their calendar stuff. The starting point is for projects >> to select a solution that suits them and make us aware of an iCAL feed. >> >> ComDev can then create a calendar that imports these various feeds. Moving >> forwards we might provide a funky front end that allows feeds of certain >> types to be aggregated into a personal feed - but lets not get ahead of >> ourselves ;-) > > Yes, sounds better. > Finally we "simply" would need an iCAL feed aggregator maybe similar > to planet.apache.org > Is the code for planet somehow extensible for this task? Might be a start The python code behind PlanetApache is open source: http://www.intertwingly.net/code/venus/ A search for "ical aggregator" turned up a simple looking python script: https://github.com/mhagander/icalaggregator (untested) Ross > > Christian > >> So who is going to create the comdev feed and add Grants Lucene feed as a >> first one. I know ComDev have discussed having a calendar of events in the >> past, if we provide some visibility for it maybe we can actually make it >> worthwhile. >> >> Ross >> >> >> >>> >>> Christian >>> >>> On Fri, May 20, 2011 at 12:44 PM, Grant Ingersoll >>> wrote: >>>> >>>> I'm curious, do any projects have shared calendars? For instance, the >>>> thought occurred to me that I might put up a Google Calendar for Lucene or >>>> Mahout that is public read-only, but committers have write control on it. >>>> On the calendar, we could put things like potential release dates, >>>> reminders for PMC actions (such as review potential committers or do board >>>> reports). Community members could submit "patches" for community related >>>> events such as conferences, meetups, hackathons, etc. >>>> >>>> -Grant >>> >>> >>> >> >> >> -- >> rgardler@apache.org >> @rgardler >> > > > -- rgardler@apache.org @rgardler