On Thu, Feb 03, 2011 at 06:37:05PM +0100, Andrea Veri wrote:
Il giorno 03/feb/2011, alle ore 15.38, Paul W. Frields ha scritto:
> On Wed, Feb 02, 2011 at 11:09:40PM +0100, Andrea Veri wrote:
>> Il giorno 02/feb/2011, alle ore 22.37, Paul W. Frields ha scritto:
>>> We'll meet in #fedora-meeting at the usual time, 1900 UTC (2pm US
>>> Eastern, 11am US Pacific) to talk about Insight. We'll look at how
>>> the migration of data has gone for Peter and Andrea, and what is
>>> needed still for staging.
>> I would like to add another point to the discussion, which is the
>> deployment of a calendar system linked to drupal where all Fedora
>> system will be able to post their meeting's time and date. (like The Fridge
>> in Ubuntu )
>> Peter pointed me to a great module for doing this, which is available at .
>> Any suggestion or idea will be welcome about this!
> I wouldn't mind seeing this in the *next* phase of Insight. At this
> time we shouldn't be adding requirements to what we're doing, though.
> Let's concentrate on getting this phase done. You can add this to the
> project plan under phase 2 for consideration:
Don't see it as a requirement, but such thing is definitely needed
into Fedora. We currently miss a calendar and all teams do have to
organize themselves using other software outside the project. (this
is causing problems in the other teams I've been contributing)
I agree it's needed. This is the *definition* of a requirement,
Anyway it is up to you to have the last word, so I'll just /hide
Thanks Andrea. I would like to see us offering more useful service
through this Drupal CMS to the project as a whole. A project-wide
calendar would be a very helpful addition. However, there was at
least one recent calendar system recently put into testing already --
Zarafa, stood up by the Infrastructure team. Therefore we shouldn't
be independently adding this (or other functions) to Insight without
consulting with other people who might have worked, or be working, on
such a system.
Beyond all that, until we get to a production state with the functions
we've already planned, I'm not in favor of extending ourselves even
further. Adding a calendar to Drupal is a fairly simple operation.
Configuring it to a set of project requirements so it can be used by
everyone is less simple, but still manageable. Installation and
configuration, though, are the smaller part of our responsibilities.
This system by definition isn't a "set and forget" operation. We are
all going to be responsible for its maintenance for the foreseeable
future. So it behooves us to be thoughtful about what we take on.
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
- - - - http://pfrields.fedorapeople.org/
Where open source multiplies: http://opensource.com