https://fedoraproject.org/wiki/User:Herlo/Fedora_Calendar_Project_Desired_Features_(Draft)#Solution_requirements
Which has no "must have" requirements and no "Should have" requirements.
From reading through this email thread it is clear that not just "any" calendar solution will do.
Before seeing if the list of calendars on the page meet the requirements it would be helpful to know what the requirements are so each calendar solution could be evaluated fairly.
I appreciate that it may not be known what exactly is required but at the least you have some things highlighted here...
It must be able to store events, recurring events, send out reminders, allow people to plug it in to their mail client, allow it to be viewed from a web page, support CalDav / iCalendar etc etc
With these requirements listed it would be easier and fairer to evaluate the solution needed, I imagine then the Infrastructure team would be able to work out the "how" to make it happen or if it is even possible to meet all requirements, or to suggest alternatives.
Hope that helps explain what I was thinking in my head.
2009/2/10 Adam Williamson <awilliam@xxxxxxxxxx>
On Tue, 2009-02-10 at 08:10 +0000, Matthew ... wrote:That's what Clint's page is about - it's a list of candidates we can
> Would it be possible to get a features list that is "ideal" I
> understand what you want but, do we know of anything that supports
> that and is able to run within our environment?
evaluate to see if they meet our needs.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
_______________________________________________
Fedora-infrastructure-list mailing list
Fedora-infrastructure-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
_______________________________________________ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
