3:30 p.m.
Hi, guys. Uh, quick intro for those who see the redhat.com and wonder
who I am - I'm Adam Williamson. I'm new in the Fedora QA department here
at RH, my job is to drive community involvement in Fedora QA. I came
over from Mandriva where I was the community manager. I'll be working
from my home in Vancouver, Canada.
I'm new on the list so this may have come up before, in which case
apologies :). Something I thought would be nice to have for QA community
is a public calendar system where dates of events like test days can be
published. Obviously it's silly for me personally or the QA team to take
on the job of hosting a calendar server, but it was suggested that it
would be a good project for the infrastructure team, and other groups
within Fedora could probably benefit from it. Does it sound like a good
idea? Anyone want to have a go? Or is there something already, that I
don't know about? Thanks!
--
adamw
3:38 p.m.
On Thu, 5 Feb 2009, Adam Williamson wrote:
Hi, guys. Uh, quick intro for those who see the redhat.com and
wonder
who I am - I'm Adam Williamson. I'm new in the Fedora QA department here
at RH, my job is to drive community involvement in Fedora QA. I came
over from Mandriva where I was the community manager. I'll be working
from my home in Vancouver, Canada.
I'm new on the list so this may have come up before, in which case
apologies :). Something I thought would be nice to have for QA community
is a public calendar system where dates of events like test days can be
published. Obviously it's silly for me personally or the QA team to take
on the job of hosting a calendar server, but it was suggested that it
would be a good project for the infrastructure team, and other groups
within Fedora could probably benefit from it. Does it sound like a good
idea? Anyone want to have a go? Or is there something already, that I
don't know about? Thanks!
--
This is something that has been discussed a few times in the past but no
one has volunteered to put together I'm afraid. It'd be a good project to
have up and going though.
-Mike
3:40 p.m.
On Thu, 2009-02-05 at 15:38 -0600, Mike McGrath wrote:
On Thu, 5 Feb 2009, Adam Williamson wrote:
> Hi, guys. Uh, quick intro for those who see the redhat.com and wonder
> who I am - I'm Adam Williamson. I'm new in the Fedora QA department here
> at RH, my job is to drive community involvement in Fedora QA. I came
> over from Mandriva where I was the community manager. I'll be working
> from my home in Vancouver, Canada.
>
> I'm new on the list so this may have come up before, in which case
> apologies :). Something I thought would be nice to have for QA community
> is a public calendar system where dates of events like test days can be
> published. Obviously it's silly for me personally or the QA team to take
> on the job of hosting a calendar server, but it was suggested that it
> would be a good project for the infrastructure team, and other groups
> within Fedora could probably benefit from it. Does it sound like a good
> idea? Anyone want to have a go? Or is there something already, that I
> don't know about? Thanks!
> --
This is something that has been discussed a few times in the past but no
one has volunteered to put together I'm afraid. It'd be a good project to
have up and going though.
Thanks a lot, Mike. Would it maybe help if I at least do some evaluatin'
of the available software? I'm happy to do one-time stuff like that,
it's the long-term commitment of *maintaining* the running server that I
don't think it makes sense to house over here. Thanks!
--
adamw
2:52 p.m.
Mike McGrath wrote:
> I'm new on the list so this may have come up before, in which
case
> apologies :). Something I thought would be nice to have for QA community
> is a public calendar system where dates of events like test days can be
> published. Obviously it's silly for me personally or the QA team to take
> on the job of hosting a calendar server, but it was suggested that it
> would be a good project for the infrastructure team, and other groups
> within Fedora could probably benefit from it. Does it sound like a good
> idea? Anyone want to have a go? Or is there something already, that I
> don't know about? Thanks!
> --
This is something that has been discussed a few times in the past but no
one has volunteered to put together I'm afraid. It'd be a good project to
have up and going though.
http://trac.calendarserver.org/
Would love to see this packaged up in fedora... I've been meaning to do
it, but just bogged down w/ other things. :)
--Bret
3:53 p.m.
There are a few Calendar modules for Zikula (the CMS I'm setting up to run
docs.fp.o) that might suit your needs - worth considering in the longer term
should the CMS prove to be a success?
Simon
-----Original Message-----
From: fedora-infrastructure-list-bounces(a)redhat.com [mailto:fedora-
infrastructure-list-bounces(a)redhat.com] On Behalf Of Adam Williamson
Sent: 05 February 2009 21:30
To: fedora-infrastructure-list(a)redhat.com
Subject: Calendaring system?
Hi, guys. Uh, quick intro for those who see the redhat.com and wonder
who I am - I'm Adam Williamson. I'm new in the Fedora QA department
here
at RH, my job is to drive community involvement in Fedora QA. I came
over from Mandriva where I was the community manager. I'll be working
from my home in Vancouver, Canada.
I'm new on the list so this may have come up before, in which case
apologies :). Something I thought would be nice to have for QA
community
is a public calendar system where dates of events like test days can be
published. Obviously it's silly for me personally or the QA team to
take
on the job of hosting a calendar server, but it was suggested that it
would be a good project for the infrastructure team, and other groups
within Fedora could probably benefit from it. Does it sound like a good
idea? Anyone want to have a go? Or is there something already, that I
don't know about? Thanks!
--
adamw
_______________________________________________
Fedora-infrastructure-list mailing list
Fedora-infrastructure-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.0.233 / Virus Database: 270.10.18/1935 - Release Date:
02/04/09 16:35:00
4:01 p.m.
On Thu, 2009-02-05 at 21:53 +0000, Simon Birtwistle wrote:
There are a few Calendar modules for Zikula (the CMS I'm setting
up to run
docs.fp.o) that might suit your needs - worth considering in the longer term
should the CMS prove to be a success?
I'll take a look, thanks for the pointer. The needs for us are, I think,
pretty simple. It needs to work as a simple calendaring system - you can
just use it as a calendar, nothing more, nothing less, if you don't want
anything else - into which you can do all the usual calendar stuff,
schedule events. The only other significant requirement for me is that
it support CalDAV, because it's important to allow people to access it
through other clients and calendar systems so that it doesn't become yet
another damn thing they have to look at separately. I would be accessing
the calendar from Evolution, for e.g., along with my personal calendar
and other shared calendars I have going.
--
adamw
7:51 p.m.
On Thu, Feb 5, 2009 at 3:01 PM, Adam Williamson <awilliam(a)redhat.com> wrote:
On Thu, 2009-02-05 at 21:53 +0000, Simon Birtwistle wrote:
> There are a few Calendar modules for Zikula (the CMS I'm setting up to run
> docs.fp.o) that might suit your needs - worth considering in the longer term
> should the CMS prove to be a success?
I'll take a look, thanks for the pointer. The needs for us are, I think,
pretty simple. It needs to work as a simple calendaring system - you can
just use it as a calendar, nothing more, nothing less, if you don't want
anything else - into which you can do all the usual calendar stuff,
schedule events. The only other significant requirement for me is that
it support CalDAV, because it's important to allow people to access it
through other clients and calendar systems so that it doesn't become yet
another damn thing they have to look at separately. I would be accessing
the calendar from Evolution, for e.g., along with my personal calendar
and other shared calendars I have going.
--
adamw
Adam,
Funny thing, I was just mentioning how it would be nice to have a
calendaring solution that would be able to let people pull feeds and
put items on the calendar for Fedora with use in FAS. I think even
though there's currently no solution quite as good as google calendar
(or apple's iCal) in free software, there are alternatives.
Bongo Project - http://bongo-project.org/Main_Page (formerly Hula) (GPLv2)
Bedework - http://www.bedework.org/bedework/ (BSD License)
DAViCal - http://rscds.sourceforge.net/ (GPL)
I'm sure there are others, but I think a self-sustaining calendar that
could integrate with the Fedora Account System (FAS) and make it so
that people can create events that could get pushed to a central
calendar which others might subscribe. Something like this would be
awesome and I'd be happy to help you get it started. Maybe one of the
above programs can meet our needs, or maybe we need to look into
something else.
Cheers,
Clint
1:28 p.m.
On Thu, 2009-02-05 at 18:51 -0700, Clint Savage wrote:
Adam,
Funny thing, I was just mentioning how it would be nice to have a
calendaring solution that would be able to let people pull feeds and
put items on the calendar for Fedora with use in FAS. I think even
though there's currently no solution quite as good as google calendar
(or apple's iCal) in free software, there are alternatives.
Bongo Project - http://bongo-project.org/Main_Page (formerly Hula) (GPLv2)
Bedework - http://www.bedework.org/bedework/ (BSD License)
DAViCal - http://rscds.sourceforge.net/ (GPL)
I'm sure there are others, but I think a self-sustaining calendar that
could integrate with the Fedora Account System (FAS) and make it so
that people can create events that could get pushed to a central
calendar which others might subscribe. Something like this would be
awesome and I'd be happy to help you get it started. Maybe one of the
above programs can meet our needs, or maybe we need to look into
something else.
Thanks a lot, Clint. Actually one of our QA community guys, Jóhann
Guðmundsson, independently suggested Bedework to me and I had a quick
look at the web page and it looks nice. It runs in Java but I guess
that's no problem if it works on OpenJDK, and it looks like it's nice
and self-contained, actively developed, and seems to really work to
implement the latest standards, so it looks like a good candidate to me.
I haven't looked at the others you suggested yet, but I will.
I'm happy to help out as much as I can - I'm no expert in this field -
in the initial set up, my only concern is to make sure that this is
something the infrastructure group will maintain over a sustained
period, I'm just hoping that it won't fall by the wayside and stop
working after a few months or wind up with me having to (try and)
maintain it or something. But I'm certainly happy to help out in getting
it up and running and fit for purpose initially.
--
adamw
3:32 p.m.
Adam Williamson wrote:
On Thu, 2009-02-05 at 18:51 -0700, Clint Savage wrote:
> Adam,
>
> Funny thing, I was just mentioning how it would be nice to have a
> calendaring solution that would be able to let people pull feeds and
> put items on the calendar for Fedora with use in FAS. I think even
> though there's currently no solution quite as good as google calendar
> (or apple's iCal) in free software, there are alternatives.
>
> Bongo Project - http://bongo-project.org/Main_Page (formerly Hula) (GPLv2)
> Bedework - http://www.bedework.org/bedework/ (BSD License)
> DAViCal - http://rscds.sourceforge.net/ (GPL)
>
> I'm sure there are others, but I think a self-sustaining calendar that
> could integrate with the Fedora Account System (FAS) and make it so
> that people can create events that could get pushed to a central
> calendar which others might subscribe. Something like this would be
> awesome and I'd be happy to help you get it started. Maybe one of the
> above programs can meet our needs, or maybe we need to look into
> something else.
Thanks a lot, Clint. Actually one of our QA community guys, Jóhann
Guðmundsson, independently suggested Bedework to me and I had a quick
look at the web page and it looks nice. It runs in Java but I guess
that's no problem if it works on OpenJDK, and it looks like it's nice
and self-contained, actively developed, and seems to really work to
implement the latest standards, so it looks like a good candidate to me.
I haven't looked at the others you suggested yet, but I will.
I'm happy to help out as much as I can - I'm no expert in this field -
in the initial set up, my only concern is to make sure that this is
something the infrastructure group will maintain over a sustained
period, I'm just hoping that it won't fall by the wayside and stop
working after a few months or wind up with me having to (try and)
maintain it or something. But I'm certainly happy to help out in getting
it up and running and fit for purpose initially.
We have kind of a de facto no-Java standard in infrastructure. This is
partially because none of us have had good experiences running apps in
java and partially because we have noone with Java programming
experience to fix things if we need to. If you had some people to give
to us to work on maintaining the server we might be able to work out
something similar to how zikula is being run for the docs deploy. But
that doesn't sound like the case :-(
-Toshio
4:47 p.m.
One Zikula calendar module has a variety of feeds (see
http://code.zikula.org/crpcalendar/attachment/wiki/screenshots/list.png) or
http://jami.cremonapalloza.org/index.php?module=crpCalendar for a live demo. It might
need some template modifications for display, but you could allow users to submit events
and so on by logging in with their FAS ID. However, I am sure there are better standalone
solutions out there, if you're happy to maintain a separate tool.
-----Original Message-----
From: fedora-infrastructure-list-bounces(a)redhat.com [mailto:fedora-
infrastructure-list-bounces(a)redhat.com] On Behalf Of Toshio Kuratomi
Sent: 06 February 2009 21:33
To: Fedora Infrastructure
Subject: Re: Calendaring system?
Adam Williamson wrote:
> On Thu, 2009-02-05 at 18:51 -0700, Clint Savage wrote:
>
>> Adam,
>>
>> Funny thing, I was just mentioning how it would be nice to have a
>> calendaring solution that would be able to let people pull feeds and
>> put items on the calendar for Fedora with use in FAS. I think even
>> though there's currently no solution quite as good as google
calendar
>> (or apple's iCal) in free software, there are alternatives.
>>
>> Bongo Project - http://bongo-project.org/Main_Page (formerly Hula)
>> (GPLv2) Bedework - http://www.bedework.org/bedework/ (BSD License)
>> DAViCal - http://rscds.sourceforge.net/ (GPL)
>>
>> I'm sure there are others, but I think a self-sustaining calendar
>> that could integrate with the Fedora Account System (FAS) and make
it
>> so that people can create events that could get pushed to a central
>> calendar which others might subscribe. Something like this would be
>> awesome and I'd be happy to help you get it started. Maybe one of
>> the above programs can meet our needs, or maybe we need to look into
>> something else.
>
> Thanks a lot, Clint. Actually one of our QA community guys, Jóhann
> Guðmundsson, independently suggested Bedework to me and I had a quick
> look at the web page and it looks nice. It runs in Java but I guess
> that's no problem if it works on OpenJDK, and it looks like it's nice
> and self-contained, actively developed, and seems to really work to
> implement the latest standards, so it looks like a good candidate to
me.
> I haven't looked at the others you suggested yet, but I will.
>
> I'm happy to help out as much as I can - I'm no expert in this field
-
> in the initial set up, my only concern is to make sure that this is
> something the infrastructure group will maintain over a sustained
> period, I'm just hoping that it won't fall by the wayside and stop
> working after a few months or wind up with me having to (try and)
> maintain it or something. But I'm certainly happy to help out in
> getting it up and running and fit for purpose initially.
We have kind of a de facto no-Java standard in infrastructure. This is
partially because none of us have had good experiences running apps in
java and partially because we have noone with Java programming
experience to fix things if we need to. If you had some people to give
to us to work on maintaining the server we might be able to work out
something similar to how zikula is being run for the docs deploy. But
that doesn't sound like the case :-(
-Toshio
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.0.233 / Virus Database: 270.10.18/1936 - Release Date:
02/05/09 11:34:00
4:56 p.m.
On Fri, Feb 6, 2009 at 3:47 PM, Simon Birtwistle <simon(a)zikula.org> wrote:
One Zikula calendar module has a variety of feeds (see
http://code.zikula.org/crpcalendar/attachment/wiki/screenshots/list.png) or
http://jami.cremonapalloza.org/index.php?module=crpCalendar for a live demo. It might
need some template modifications for display, but you could allow users to submit events
and so on by logging in with their FAS ID. However, I am sure there are better standalone
solutions out there, if you're happy to maintain a separate tool.
> -----Original Message-----
> From: fedora-infrastructure-list-bounces(a)redhat.com [mailto:fedora-
> infrastructure-list-bounces(a)redhat.com] On Behalf Of Toshio Kuratomi
> Sent: 06 February 2009 21:33
> To: Fedora Infrastructure
> Subject: Re: Calendaring system?
>
> Adam Williamson wrote:
> > On Thu, 2009-02-05 at 18:51 -0700, Clint Savage wrote:
> >
> >> Adam,
> >>
> >> Funny thing, I was just mentioning how it would be nice to have a
> >> calendaring solution that would be able to let people pull feeds and
> >> put items on the calendar for Fedora with use in FAS. I think even
> >> though there's currently no solution quite as good as google
> calendar
> >> (or apple's iCal) in free software, there are alternatives.
> >>
> >> Bongo Project - http://bongo-project.org/Main_Page (formerly Hula)
> >> (GPLv2) Bedework - http://www.bedework.org/bedework/ (BSD License)
> >> DAViCal - http://rscds.sourceforge.net/ (GPL)
> >>
> >> I'm sure there are others, but I think a self-sustaining calendar
> >> that could integrate with the Fedora Account System (FAS) and make
> it
> >> so that people can create events that could get pushed to a central
> >> calendar which others might subscribe. Something like this would be
> >> awesome and I'd be happy to help you get it started. Maybe one of
> >> the above programs can meet our needs, or maybe we need to look into
> >> something else.
> >
> > Thanks a lot, Clint. Actually one of our QA community guys, Jóhann
> > Guðmundsson, independently suggested Bedework to me and I had a quick
> > look at the web page and it looks nice. It runs in Java but I guess
> > that's no problem if it works on OpenJDK, and it looks like it's nice
> > and self-contained, actively developed, and seems to really work to
> > implement the latest standards, so it looks like a good candidate to
> me.
> > I haven't looked at the others you suggested yet, but I will.
> >
> > I'm happy to help out as much as I can - I'm no expert in this field
> -
> > in the initial set up, my only concern is to make sure that this is
> > something the infrastructure group will maintain over a sustained
> > period, I'm just hoping that it won't fall by the wayside and stop
> > working after a few months or wind up with me having to (try and)
> > maintain it or something. But I'm certainly happy to help out in
> > getting it up and running and fit for purpose initially.
>
> We have kind of a de facto no-Java standard in infrastructure. This is
> partially because none of us have had good experiences running apps in
> java and partially because we have noone with Java programming
> experience to fix things if we need to. If you had some people to give
> to us to work on maintaining the server we might be able to work out
> something similar to how zikula is being run for the docs deploy. But
> that doesn't sound like the case :-(
>
> -Toshio
>
Bret,
I don't know, part of me wants to look at calendarserver, but I can't
find what the licensing is there. It looks like maybe it's a ruby
project? I looked around on the site and there's no clear link to
any good information on its licensing.
Simon,
As far as zikula, while I think the calendaring of Zikula is great, I
wonder if we really need a fully blown CMS to manage our calendaring?
In this case, it seems to me that we need *just* calendaring and not
much else. I'd like an easy way for people to interact with the
calendar from their client applications and update the calendar. I'd
also like it to only do that if they have the rights to modify
calendar events for their particular group(s) in FAS.
Can Zikula do that? My thought is that Zikula is more of a "do it on
the server" type application and can't handle input from a calendar
client using caldav (or others).
Maybe it can do all of the above and more. My theory is that we need
to create a wiki page with the feature set we need and get the thing
that matches closest to our needs. I'd be happy to start that effort
early next week. If anyone else wants to create it first, I'd be
happy to help their page instead of mine.
Cheers,
Clint
6:47 p.m.
On Fri, 2009-02-06 at 15:56 -0700, Clint Savage wrote:
Bret,
I don't know, part of me wants to look at calendarserver, but I can't
find what the licensing is there. It looks like maybe it's a ruby
project? I looked around on the site and there's no clear link to
any good information on its licensing.
calendarserver appears to be a python project, and it appears to be
licensed at least partly under apache 2.0
http://trac.calendarserver.org/browser/CalendarServer/trunk/LICENSE
More clear info at
http://trac.calendarserver.org/browser/CalendarServer/trunk/README
--
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating
8:04 p.m.
On Fri, 2009-02-06 at 15:56 -0700, Clint Savage wrote:
On Fri, Feb 6, 2009 at 3:47 PM, Simon Birtwistle
<simon(a)zikula.org> wrote:
> One Zikula calendar module has a variety of feeds (see
http://code.zikula.org/crpcalendar/attachment/wiki/screenshots/list.png) or
http://jami.cremonapalloza.org/index.php?module=crpCalendar for a live demo. It might
need some template modifications for display, but you could allow users to submit events
and so on by logging in with their FAS ID. However, I am sure there are better standalone
solutions out there, if you're happy to maintain a separate tool.
>
>> -----Original Message-----
>> From: fedora-infrastructure-list-bounces(a)redhat.com [mailto:fedora-
>> infrastructure-list-bounces(a)redhat.com] On Behalf Of Toshio Kuratomi
>> Sent: 06 February 2009 21:33
>> To: Fedora Infrastructure
>> Subject: Re: Calendaring system?
>>
>> Adam Williamson wrote:
>> > On Thu, 2009-02-05 at 18:51 -0700, Clint Savage wrote:
>> >
>> >> Adam,
>> >>
>> >> Funny thing, I was just mentioning how it would be nice to have a
>> >> calendaring solution that would be able to let people pull feeds and
>> >> put items on the calendar for Fedora with use in FAS. I think even
>> >> though there's currently no solution quite as good as google
>> calendar
>> >> (or apple's iCal) in free software, there are alternatives.
>> >>
>> >> Bongo Project - http://bongo-project.org/Main_Page (formerly Hula)
>> >> (GPLv2) Bedework - http://www.bedework.org/bedework/ (BSD License)
>> >> DAViCal - http://rscds.sourceforge.net/ (GPL)
>> >>
>> >> I'm sure there are others, but I think a self-sustaining calendar
>> >> that could integrate with the Fedora Account System (FAS) and make
>> it
>> >> so that people can create events that could get pushed to a central
>> >> calendar which others might subscribe. Something like this would be
>> >> awesome and I'd be happy to help you get it started. Maybe one of
>> >> the above programs can meet our needs, or maybe we need to look into
>> >> something else.
>> >
>> > Thanks a lot, Clint. Actually one of our QA community guys, Jóhann
>> > Guðmundsson, independently suggested Bedework to me and I had a quick
>> > look at the web page and it looks nice. It runs in Java but I guess
>> > that's no problem if it works on OpenJDK, and it looks like it's
nice
>> > and self-contained, actively developed, and seems to really work to
>> > implement the latest standards, so it looks like a good candidate to
>> me.
>> > I haven't looked at the others you suggested yet, but I will.
>> >
>> > I'm happy to help out as much as I can - I'm no expert in this
field
>> -
>> > in the initial set up, my only concern is to make sure that this is
>> > something the infrastructure group will maintain over a sustained
>> > period, I'm just hoping that it won't fall by the wayside and stop
>> > working after a few months or wind up with me having to (try and)
>> > maintain it or something. But I'm certainly happy to help out in
>> > getting it up and running and fit for purpose initially.
>>
>> We have kind of a de facto no-Java standard in infrastructure. This is
>> partially because none of us have had good experiences running apps in
>> java and partially because we have noone with Java programming
>> experience to fix things if we need to. If you had some people to give
>> to us to work on maintaining the server we might be able to work out
>> something similar to how zikula is being run for the docs deploy. But
>> that doesn't sound like the case :-(
>>
>> -Toshio
>>
Bret,
I don't know, part of me wants to look at calendarserver, but I can't
find what the licensing is there. It looks like maybe it's a ruby
project? I looked around on the site and there's no clear link to
any good information on its licensing.
Simon,
As far as zikula, while I think the calendaring of Zikula is great, I
wonder if we really need a fully blown CMS to manage our calendaring?
In this case, it seems to me that we need *just* calendaring and not
much else. I'd like an easy way for people to interact with the
calendar from their client applications and update the calendar. I'd
also like it to only do that if they have the rights to modify
calendar events for their particular group(s) in FAS.
Can Zikula do that? My thought is that Zikula is more of a "do it on
the server" type application and can't handle input from a calendar
client using caldav (or others).
Maybe it can do all of the above and more. My theory is that we need
to create a wiki page with the feature set we need and get the thing
that matches closest to our needs. I'd be happy to start that effort
early next week. If anyone else wants to create it first, I'd be
happy to help their page instead of mine.
Cheers,
Clint
Clint,
I see it a little different. Why support ANOTHER piece of software when
the software we already have will work. We wouldn't be using the CMS
just for calendaring... We'd be using the CMS for everything and it has
a calendar function.
All that being said, I don't know if Zikula can do what we want it to do
for a calendar solution.
Eric
5:32 a.m.
On Fri, 2009-02-06 at 13:32 -0800, Toshio Kuratomi wrote:
We have kind of a de facto no-Java standard in infrastructure. This
is
partially because none of us have had good experiences running apps in
java and partially because we have noone with Java programming
experience to fix things if we need to. If you had some people to give
to us to work on maintaining the server we might be able to work out
something similar to how zikula is being run for the docs deploy. But
that doesn't sound like the case :-(
No, I don't think so. So let's knock Bedework off the list for now,
there do seem to be other viable alternatives. I like Clint's idea of a
wiki page to set the requirements and evaluate alternatives, I will
happily create / contribute to that next week once my brain is working
again :), depending on whether Clint has got around to creating it by
then. Added to my todo.
--
adamw
12:10 a.m.
On Sat, Feb 7, 2009 at 4:32 AM, Adam Williamson <awilliam(a)redhat.com> wrote:
On Fri, 2009-02-06 at 13:32 -0800, Toshio Kuratomi wrote:
> We have kind of a de facto no-Java standard in infrastructure. This is
> partially because none of us have had good experiences running apps in
> java and partially because we have noone with Java programming
> experience to fix things if we need to. If you had some people to give
> to us to work on maintaining the server we might be able to work out
> something similar to how zikula is being run for the docs deploy. But
> that doesn't sound like the case :-(
No, I don't think so. So let's knock Bedework off the list for now,
there do seem to be other viable alternatives. I like Clint's idea of a
wiki page to set the requirements and evaluate alternatives, I will
happily create / contribute to that next week once my brain is working
again :), depending on whether Clint has got around to creating it by
then. Added to my todo.
--
adamw
Hi all,
It's been a day or two since this conversation knocked off, but I
think I have a wiki page[1] up with some good information. It is
still a bit incomplete and we'll need to spend some time specifically
with the features we'd like to see. I've added all of the calendaring
servers listed in this thread, if I missed one, feel free to add it on
the wiki page.
Also, I put together a tentative timeline for when we could have this
calendaring server in place. I assume it's based upon desire and time
so let's see what we can get done!
I'm looking forward to seeing this project a reality.
Cheers,
Clint
1 -
https://fedoraproject.org/wiki/User:Herlo/Fedora_Calendar_Project_Desired...
12:21 a.m.
Adam Williamson wrote:
On Thu, 2009-02-05 at 21:53 +0000, Simon Birtwistle wrote:
> There are a few Calendar modules for Zikula (the CMS I'm setting up to run
> docs.fp.o) that might suit your needs - worth considering in the longer term
> should the CMS prove to be a success?
I'll take a look, thanks for the pointer. The needs for us are, I think,
pretty simple. It needs to work as a simple calendaring system - you can
just use it as a calendar, nothing more, nothing less, if you don't want
anything else - into which you can do all the usual calendar stuff,
schedule events. The only other significant requirement for me is that
it support CalDAV, because it's important to allow people to access it
through other clients and calendar systems so that it doesn't become yet
another damn thing they have to look at separately. I would be accessing
the calendar from Evolution, for e.g., along with my personal calendar
and other shared calendars I have going.
Has anyone given this a try?
http://chandlerproject.org/
http://chandlerproject.org/Projects/ProductTour
It might be a nice fit for Fedora because it is python based and some of
the user stories center around how it has been useful in collaboration
activities.
John
1:36 p.m.
Adam Williamson wrote:
Hi, guys. Uh, quick intro for those who see the redhat.com and
wonder
who I am - I'm Adam Williamson. I'm new in the Fedora QA department here
at RH, my job is to drive community involvement in Fedora QA. I came
over from Mandriva where I was the community manager. I'll be working
from my home in Vancouver, Canada.
I'm new on the list so this may have come up before, in which case
apologies :). Something I thought would be nice to have for QA community
is a public calendar system where dates of events like test days can be
published. Obviously it's silly for me personally or the QA team to take
on the job of hosting a calendar server, but it was suggested that it
would be a good project for the infrastructure team, and other groups
within Fedora could probably benefit from it. Does it sound like a good
idea? Anyone want to have a go? Or is there something already, that I
don't know about? Thanks!
I've not seen anything in this thread yet, so it may have been mentioned
before;
MediaWiki has a couple of calendering plugins that will allow "days" to
be allocated; I looked into this for our meeting schedule but since none
of them include any times for appointments I found it to be useless.
Nonetheless, it could be worthwhile for allocating "Test days" and
"Events" -and things of the sort.
Kind regards,
Jeroen van Meeuwen
-kanarip
1:58 p.m.
On Mon, Feb 9, 2009 at 12:36 PM, Jeroen van Meeuwen <kanarip(a)kanarip.com> wrote:
Adam Williamson wrote:
>
> Hi, guys. Uh, quick intro for those who see the redhat.com and wonder
> who I am - I'm Adam Williamson. I'm new in the Fedora QA department here
> at RH, my job is to drive community involvement in Fedora QA. I came
> over from Mandriva where I was the community manager. I'll be working
> from my home in Vancouver, Canada.
>
> I'm new on the list so this may have come up before, in which case
> apologies :). Something I thought would be nice to have for QA community
> is a public calendar system where dates of events like test days can be
> published. Obviously it's silly for me personally or the QA team to take
> on the job of hosting a calendar server, but it was suggested that it
> would be a good project for the infrastructure team, and other groups
> within Fedora could probably benefit from it. Does it sound like a good
> idea? Anyone want to have a go? Or is there something already, that I
> don't know about? Thanks!
I've not seen anything in this thread yet, so it may have been mentioned
before;
MediaWiki has a couple of calendering plugins that will allow "days" to be
allocated; I looked into this for our meeting schedule but since none of
them include any times for appointments I found it to be useless.
Nonetheless, it could be worthwhile for allocating "Test days" and
"Events"
-and things of the sort.
Kind regards,
Jeroen van Meeuwen
-kanarip
I think the point I'm continuing to make is that it should support
caldav or something similar. The protocol defines a protocol, so the
client applications themselves shouldn't matter, but we do need to
have a way to communicate with the calendar server.
My intention isn't to discount MediaWiki or Zikula as a possible
platform for a calendaring client, but to say that the features you
suggest are not what we're after here. Instead I'd say that those two
applications could push/pull data from the calendar server (using
caldav).
The events listed in the caldav server can be manipulated by these
other applications and probably through an API which could include
Access Control Lists based upon FAS rights. I can see this being a
bit of an undertaking, but it can really benefit the Fedora Project as
a whole.
As I stated in my previous email, I've got a draft up of all the
features we'd like to see (it's pretty empty right now) and I'll
probably go ahead and list some of this email there. But for those of
you who are interested in helping me get that wiki page more complete,
feel free to visit:
https://fedoraproject.org/wiki/User:Herlo/Fedora_Calendar_Project_Desired...
Keep the thoughts coming, I want to see this project succeed!
Cheers,
Clint
2:28 p.m.
Clint Savage wrote:
On Mon, Feb 9, 2009 at 12:36 PM, Jeroen van Meeuwen
<kanarip(a)kanarip.com> wrote:
> Adam Williamson wrote:
>> Hi, guys. Uh, quick intro for those who see the redhat.com and wonder
>> who I am - I'm Adam Williamson. I'm new in the Fedora QA department here
>> at RH, my job is to drive community involvement in Fedora QA. I came
>> over from Mandriva where I was the community manager. I'll be working
>> from my home in Vancouver, Canada.
>>
>> I'm new on the list so this may have come up before, in which case
>> apologies :). Something I thought would be nice to have for QA community
>> is a public calendar system where dates of events like test days can be
>> published. Obviously it's silly for me personally or the QA team to take
>> on the job of hosting a calendar server, but it was suggested that it
>> would be a good project for the infrastructure team, and other groups
>> within Fedora could probably benefit from it. Does it sound like a good
>> idea? Anyone want to have a go? Or is there something already, that I
>> don't know about? Thanks!
> I've not seen anything in this thread yet, so it may have been mentioned
> before;
>
> MediaWiki has a couple of calendering plugins that will allow "days" to be
> allocated; I looked into this for our meeting schedule but since none of
> them include any times for appointments I found it to be useless.
> Nonetheless, it could be worthwhile for allocating "Test days" and
"Events"
> -and things of the sort.
>
> Kind regards,
>
> Jeroen van Meeuwen
> -kanarip
>
I think the point I'm continuing to make is that it should support
caldav or something similar. The protocol defines a protocol, so the
client applications themselves shouldn't matter, but we do need to
have a way to communicate with the calendar server.
My intention isn't to discount MediaWiki or Zikula as a possible
platform for a calendaring client, but to say that the features you
suggest are not what we're after here. Instead I'd say that those two
applications could push/pull data from the calendar server (using
caldav).
The events listed in the caldav server can be manipulated by these
other applications and probably through an API which could include
Access Control Lists based upon FAS rights. I can see this being a
bit of an undertaking, but it can really benefit the Fedora Project as
a whole.
As I stated in my previous email, I've got a draft up of all the
features we'd like to see (it's pretty empty right now) and I'll
probably go ahead and list some of this email there. But for those of
you who are interested in helping me get that wiki page more complete,
feel free to visit:
https://fedoraproject.org/wiki/User:Herlo/Fedora_Calendar_Project_Desired...
Keep the thoughts coming, I want to see this project succeed!
Dude, I'm sorry I even brought it up. Good luck!
-Jeroen
2:46 p.m.
On Mon, 9 Feb 2009, Clint Savage wrote:
On Mon, Feb 9, 2009 at 12:36 PM, Jeroen van Meeuwen
<kanarip(a)kanarip.com> wrote:
> Adam Williamson wrote:
>>
>> Hi, guys. Uh, quick intro for those who see the redhat.com and wonder
>> who I am - I'm Adam Williamson. I'm new in the Fedora QA department
here
>> at RH, my job is to drive community involvement in Fedora QA. I came
>> over from Mandriva where I was the community manager. I'll be working
>> from my home in Vancouver, Canada.
>>
>> I'm new on the list so this may have come up before, in which case
>> apologies :). Something I thought would be nice to have for QA community
>> is a public calendar system where dates of events like test days can be
>> published. Obviously it's silly for me personally or the QA team to take
>> on the job of hosting a calendar server, but it was suggested that it
>> would be a good project for the infrastructure team, and other groups
>> within Fedora could probably benefit from it. Does it sound like a good
>> idea? Anyone want to have a go? Or is there something already, that I
>> don't know about? Thanks!
>
> I've not seen anything in this thread yet, so it may have been mentioned
> before;
>
> MediaWiki has a couple of calendering plugins that will allow "days" to
be
> allocated; I looked into this for our meeting schedule but since none of
> them include any times for appointments I found it to be useless.
> Nonetheless, it could be worthwhile for allocating "Test days" and
"Events"
> -and things of the sort.
>
> Kind regards,
>
> Jeroen van Meeuwen
> -kanarip
>
I think the point I'm continuing to make is that it should support
caldav or something similar. The protocol defines a protocol, so the
client applications themselves shouldn't matter, but we do need to
have a way to communicate with the calendar server.
My intention isn't to discount MediaWiki or Zikula as a possible
platform for a calendaring client, but to say that the features you
suggest are not what we're after here. Instead I'd say that those two
applications could push/pull data from the calendar server (using
caldav).
The events listed in the caldav server can be manipulated by these
other applications and probably through an API which could include
Access Control Lists based upon FAS rights. I can see this being a
bit of an undertaking, but it can really benefit the Fedora Project as
a whole.
As I stated in my previous email, I've got a draft up of all the
features we'd like to see (it's pretty empty right now) and I'll
probably go ahead and list some of this email there. But for those of
you who are interested in helping me get that wiki page more complete,
feel free to visit:
https://fedoraproject.org/wiki/User:Herlo/Fedora_Calendar_Project_Desired...
Keep the thoughts coming, I want to see this project succeed!
Maybe we should mature this a bit and look into full collaboration suites.
For example http://www.opengroupware.org/
I'm poking around at some now, I'm not sure what license restrictions
there are for each.
-Mike
2:55 p.m.
On Mon, Feb 9, 2009 at 3:46 PM, Mike McGrath <mmcgrath(a)redhat.com> wrote:
On Mon, 9 Feb 2009, Clint Savage wrote:
> On Mon, Feb 9, 2009 at 12:36 PM, Jeroen van Meeuwen <kanarip(a)kanarip.com>
wrote:
> > Adam Williamson wrote:
> >>
> >> Hi, guys. Uh, quick intro for those who see the redhat.com and wonder
> >> who I am - I'm Adam Williamson. I'm new in the Fedora QA department
here
> >> at RH, my job is to drive community involvement in Fedora QA. I came
> >> over from Mandriva where I was the community manager. I'll be working
> >> from my home in Vancouver, Canada.
> >>
> >> I'm new on the list so this may have come up before, in which case
> >> apologies :). Something I thought would be nice to have for QA community
> >> is a public calendar system where dates of events like test days can be
> >> published. Obviously it's silly for me personally or the QA team to
take
> >> on the job of hosting a calendar server, but it was suggested that it
> >> would be a good project for the infrastructure team, and other groups
> >> within Fedora could probably benefit from it. Does it sound like a good
> >> idea? Anyone want to have a go? Or is there something already, that I
> >> don't know about? Thanks!
> >
> > I've not seen anything in this thread yet, so it may have been mentioned
> > before;
> >
> > MediaWiki has a couple of calendering plugins that will allow "days"
to be
> > allocated; I looked into this for our meeting schedule but since none of
> > them include any times for appointments I found it to be useless.
> > Nonetheless, it could be worthwhile for allocating "Test days" and
"Events"
> > -and things of the sort.
> >
> > Kind regards,
> >
> > Jeroen van Meeuwen
> > -kanarip
> >
>
> I think the point I'm continuing to make is that it should support
> caldav or something similar. The protocol defines a protocol, so the
> client applications themselves shouldn't matter, but we do need to
> have a way to communicate with the calendar server.
>
> My intention isn't to discount MediaWiki or Zikula as a possible
> platform for a calendaring client, but to say that the features you
> suggest are not what we're after here. Instead I'd say that those two
> applications could push/pull data from the calendar server (using
> caldav).
>
> The events listed in the caldav server can be manipulated by these
> other applications and probably through an API which could include
> Access Control Lists based upon FAS rights. I can see this being a
> bit of an undertaking, but it can really benefit the Fedora Project as
> a whole.
>
> As I stated in my previous email, I've got a draft up of all the
> features we'd like to see (it's pretty empty right now) and I'll
> probably go ahead and list some of this email there. But for those of
> you who are interested in helping me get that wiki page more complete,
> feel free to visit:
>
>
https://fedoraproject.org/wiki/User:Herlo/Fedora_Calendar_Project_Desired...
>
> Keep the thoughts coming, I want to see this project succeed!
>
Maybe we should mature this a bit and look into full collaboration suites.
For example http://www.opengroupware.org/
I'm poking around at some now, I'm not sure what license restrictions
there are for each.
-Mike
_______________________________________________
Fedora-infrastructure-list mailing list
Fedora-infrastructure-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
As a former contributor to OGo I think it's a great project, and it
supports things like CAlDAV. However unless things have changed
recently I'd expect it to be a bear to get packaged and into Fedora.
Not that it should be excluded, just a heads up. That said it's really
email centric and I am not sure we'd want to get in that business.
3:11 p.m.
On Mon, 9 Feb 2009, David Nalley wrote:
On Mon, Feb 9, 2009 at 3:46 PM, Mike McGrath
<mmcgrath(a)redhat.com> wrote:
> On Mon, 9 Feb 2009, Clint Savage wrote:
>
>> On Mon, Feb 9, 2009 at 12:36 PM, Jeroen van Meeuwen <kanarip(a)kanarip.com>
wrote:
>> > Adam Williamson wrote:
>> >>
>> >> Hi, guys. Uh, quick intro for those who see the redhat.com and wonder
>> >> who I am - I'm Adam Williamson. I'm new in the Fedora QA
department here
>> >> at RH, my job is to drive community involvement in Fedora QA. I came
>> >> over from Mandriva where I was the community manager. I'll be
working
>> >> from my home in Vancouver, Canada.
>> >>
>> >> I'm new on the list so this may have come up before, in which case
>> >> apologies :). Something I thought would be nice to have for QA
community
>> >> is a public calendar system where dates of events like test days can
be
>> >> published. Obviously it's silly for me personally or the QA team to
take
>> >> on the job of hosting a calendar server, but it was suggested that it
>> >> would be a good project for the infrastructure team, and other groups
>> >> within Fedora could probably benefit from it. Does it sound like a
good
>> >> idea? Anyone want to have a go? Or is there something already, that I
>> >> don't know about? Thanks!
>> >
>> > I've not seen anything in this thread yet, so it may have been
mentioned
>> > before;
>> >
>> > MediaWiki has a couple of calendering plugins that will allow
"days" to be
>> > allocated; I looked into this for our meeting schedule but since none of
>> > them include any times for appointments I found it to be useless.
>> > Nonetheless, it could be worthwhile for allocating "Test days"
and "Events"
>> > -and things of the sort.
>> >
>> > Kind regards,
>> >
>> > Jeroen van Meeuwen
>> > -kanarip
>> >
>>
>> I think the point I'm continuing to make is that it should support
>> caldav or something similar. The protocol defines a protocol, so the
>> client applications themselves shouldn't matter, but we do need to
>> have a way to communicate with the calendar server.
>>
>> My intention isn't to discount MediaWiki or Zikula as a possible
>> platform for a calendaring client, but to say that the features you
>> suggest are not what we're after here. Instead I'd say that those two
>> applications could push/pull data from the calendar server (using
>> caldav).
>>
>> The events listed in the caldav server can be manipulated by these
>> other applications and probably through an API which could include
>> Access Control Lists based upon FAS rights. I can see this being a
>> bit of an undertaking, but it can really benefit the Fedora Project as
>> a whole.
>>
>> As I stated in my previous email, I've got a draft up of all the
>> features we'd like to see (it's pretty empty right now) and I'll
>> probably go ahead and list some of this email there. But for those of
>> you who are interested in helping me get that wiki page more complete,
>> feel free to visit:
>>
>>
https://fedoraproject.org/wiki/User:Herlo/Fedora_Calendar_Project_Desired...
>>
>> Keep the thoughts coming, I want to see this project succeed!
>>
>
> Maybe we should mature this a bit and look into full collaboration suites.
>
> For example http://www.opengroupware.org/
>
> I'm poking around at some now, I'm not sure what license restrictions
> there are for each.
>
> -Mike
>
> _______________________________________________
> Fedora-infrastructure-list mailing list
> Fedora-infrastructure-list(a)redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
>
As a former contributor to OGo I think it's a great project, and it
supports things like CAlDAV. However unless things have changed
recently I'd expect it to be a bear to get packaged and into Fedora.
Not that it should be excluded, just a heads up. That said it's really
email centric and I am not sure we'd want to get in that business.
Lets say we wanted to use features that were _not_ email storage based.
How feasible is that? For example, if I created an appointment for you
and me, it'd still send an email to your @fp.o email address which would
then just be forwarded to your local MTA.
-Mike
3:23 p.m.
On Mon, Feb 9, 2009 at 4:11 PM, Mike McGrath <mmcgrath(a)redhat.com> wrote:
On Mon, 9 Feb 2009, David Nalley wrote:
> On Mon, Feb 9, 2009 at 3:46 PM, Mike McGrath <mmcgrath(a)redhat.com> wrote:
> > On Mon, 9 Feb 2009, Clint Savage wrote:
> >
> >> On Mon, Feb 9, 2009 at 12:36 PM, Jeroen van Meeuwen
<kanarip(a)kanarip.com> wrote:
> >> > Adam Williamson wrote:
> >> >>
> >> >> Hi, guys. Uh, quick intro for those who see the redhat.com and
wonder
> >> >> who I am - I'm Adam Williamson. I'm new in the Fedora QA
department here
> >> >> at RH, my job is to drive community involvement in Fedora QA. I
came
> >> >> over from Mandriva where I was the community manager. I'll be
working
> >> >> from my home in Vancouver, Canada.
> >> >>
> >> >> I'm new on the list so this may have come up before, in which
case
> >> >> apologies :). Something I thought would be nice to have for QA
community
> >> >> is a public calendar system where dates of events like test days
can be
> >> >> published. Obviously it's silly for me personally or the QA
team to take
> >> >> on the job of hosting a calendar server, but it was suggested that
it
> >> >> would be a good project for the infrastructure team, and other
groups
> >> >> within Fedora could probably benefit from it. Does it sound like a
good
> >> >> idea? Anyone want to have a go? Or is there something already, that
I
> >> >> don't know about? Thanks!
> >> >
> >> > I've not seen anything in this thread yet, so it may have been
mentioned
> >> > before;
> >> >
> >> > MediaWiki has a couple of calendering plugins that will allow
"days" to be
> >> > allocated; I looked into this for our meeting schedule but since none
of
> >> > them include any times for appointments I found it to be useless.
> >> > Nonetheless, it could be worthwhile for allocating "Test
days" and "Events"
> >> > -and things of the sort.
> >> >
> >> > Kind regards,
> >> >
> >> > Jeroen van Meeuwen
> >> > -kanarip
> >> >
> >>
> >> I think the point I'm continuing to make is that it should support
> >> caldav or something similar. The protocol defines a protocol, so the
> >> client applications themselves shouldn't matter, but we do need to
> >> have a way to communicate with the calendar server.
> >>
> >> My intention isn't to discount MediaWiki or Zikula as a possible
> >> platform for a calendaring client, but to say that the features you
> >> suggest are not what we're after here. Instead I'd say that those
two
> >> applications could push/pull data from the calendar server (using
> >> caldav).
> >>
> >> The events listed in the caldav server can be manipulated by these
> >> other applications and probably through an API which could include
> >> Access Control Lists based upon FAS rights. I can see this being a
> >> bit of an undertaking, but it can really benefit the Fedora Project as
> >> a whole.
> >>
> >> As I stated in my previous email, I've got a draft up of all the
> >> features we'd like to see (it's pretty empty right now) and
I'll
> >> probably go ahead and list some of this email there. But for those of
> >> you who are interested in helping me get that wiki page more complete,
> >> feel free to visit:
> >>
> >>
https://fedoraproject.org/wiki/User:Herlo/Fedora_Calendar_Project_Desired...
> >>
> >> Keep the thoughts coming, I want to see this project succeed!
> >>
> >
> > Maybe we should mature this a bit and look into full collaboration suites.
> >
> > For example http://www.opengroupware.org/
> >
> > I'm poking around at some now, I'm not sure what license restrictions
> > there are for each.
> >
> > -Mike
> >
> > _______________________________________________
> > Fedora-infrastructure-list mailing list
> > Fedora-infrastructure-list(a)redhat.com
> > https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
> >
>
> As a former contributor to OGo I think it's a great project, and it
> supports things like CAlDAV. However unless things have changed
> recently I'd expect it to be a bear to get packaged and into Fedora.
> Not that it should be excluded, just a heads up. That said it's really
> email centric and I am not sure we'd want to get in that business.
>
Lets say we wanted to use features that were _not_ email storage based.
How feasible is that? For example, if I created an appointment for you
and me, it'd still send an email to your @fp.o email address which would
then just be forwarded to your local MTA.
-Mike
_______________________________________________
Fedora-infrastructure-list mailing list
Fedora-infrastructure-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
So OGo is (or was) cognizant of other users accounts - and would
create the appointment on the calendar directly rather than sending to
the users MTA. Calendar and other non-mail stuff are all stored in the
DB - while mail is almost an add-on. (In the mail-less environment it
knows about e-mail - and can send items out, but it treats local users
completely separate from e-mail. That might be ok. - esp if we did
iCAL or CalDAV.
I do need to disclaim that I haven't kept up with OGo in quite a while
and things may have changed, but the architecture had been around for
a long time, and I don't think they would have made any dramatic
changes.
4:08 p.m.
On Mon, Feb 9, 2009 at 2:23 PM, David Nalley <david(a)gnsa.us> wrote:
On Mon, Feb 9, 2009 at 4:11 PM, Mike McGrath
<mmcgrath(a)redhat.com> wrote:
> On Mon, 9 Feb 2009, David Nalley wrote:
>
>> On Mon, Feb 9, 2009 at 3:46 PM, Mike McGrath <mmcgrath(a)redhat.com> wrote:
>> > On Mon, 9 Feb 2009, Clint Savage wrote:
>> >
>> >> On Mon, Feb 9, 2009 at 12:36 PM, Jeroen van Meeuwen
<kanarip(a)kanarip.com> wrote:
>> >> > Adam Williamson wrote:
>> >> >>
>> >> >> Hi, guys. Uh, quick intro for those who see the redhat.com and
wonder
>> >> >> who I am - I'm Adam Williamson. I'm new in the Fedora
QA department here
>> >> >> at RH, my job is to drive community involvement in Fedora QA. I
came
>> >> >> over from Mandriva where I was the community manager. I'll
be working
>> >> >> from my home in Vancouver, Canada.
>> >> >>
>> >> >> I'm new on the list so this may have come up before, in
which case
>> >> >> apologies :). Something I thought would be nice to have for QA
community
>> >> >> is a public calendar system where dates of events like test
days can be
>> >> >> published. Obviously it's silly for me personally or the QA
team to take
>> >> >> on the job of hosting a calendar server, but it was suggested
that it
>> >> >> would be a good project for the infrastructure team, and other
groups
>> >> >> within Fedora could probably benefit from it. Does it sound
like a good
>> >> >> idea? Anyone want to have a go? Or is there something already,
that I
>> >> >> don't know about? Thanks!
>> >> >
>> >> > I've not seen anything in this thread yet, so it may have been
mentioned
>> >> > before;
>> >> >
>> >> > MediaWiki has a couple of calendering plugins that will allow
"days" to be
>> >> > allocated; I looked into this for our meeting schedule but since
none of
>> >> > them include any times for appointments I found it to be useless.
>> >> > Nonetheless, it could be worthwhile for allocating "Test
days" and "Events"
>> >> > -and things of the sort.
>> >> >
>> >> > Kind regards,
>> >> >
>> >> > Jeroen van Meeuwen
>> >> > -kanarip
>> >> >
>> >>
>> >> I think the point I'm continuing to make is that it should support
>> >> caldav or something similar. The protocol defines a protocol, so the
>> >> client applications themselves shouldn't matter, but we do need to
>> >> have a way to communicate with the calendar server.
>> >>
>> >> My intention isn't to discount MediaWiki or Zikula as a possible
>> >> platform for a calendaring client, but to say that the features you
>> >> suggest are not what we're after here. Instead I'd say that
those two
>> >> applications could push/pull data from the calendar server (using
>> >> caldav).
>> >>
>> >> The events listed in the caldav server can be manipulated by these
>> >> other applications and probably through an API which could include
>> >> Access Control Lists based upon FAS rights. I can see this being a
>> >> bit of an undertaking, but it can really benefit the Fedora Project as
>> >> a whole.
>> >>
>> >> As I stated in my previous email, I've got a draft up of all the
>> >> features we'd like to see (it's pretty empty right now) and
I'll
>> >> probably go ahead and list some of this email there. But for those of
>> >> you who are interested in helping me get that wiki page more complete,
>> >> feel free to visit:
>> >>
>> >>
https://fedoraproject.org/wiki/User:Herlo/Fedora_Calendar_Project_Desired...
>> >>
>> >> Keep the thoughts coming, I want to see this project succeed!
>> >>
>> >
>> > Maybe we should mature this a bit and look into full collaboration suites.
>> >
>> > For example http://www.opengroupware.org/
>> >
>> > I'm poking around at some now, I'm not sure what license
restrictions
>> > there are for each.
>> >
>> > -Mike
>> >
>> > _______________________________________________
>> > Fedora-infrastructure-list mailing list
>> > Fedora-infrastructure-list(a)redhat.com
>> > https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
>> >
>>
>> As a former contributor to OGo I think it's a great project, and it
>> supports things like CAlDAV. However unless things have changed
>> recently I'd expect it to be a bear to get packaged and into Fedora.
>> Not that it should be excluded, just a heads up. That said it's really
>> email centric and I am not sure we'd want to get in that business.
>>
>
> Lets say we wanted to use features that were _not_ email storage based.
> How feasible is that? For example, if I created an appointment for you
> and me, it'd still send an email to your @fp.o email address which would
> then just be forwarded to your local MTA.
>
> -Mike
>
> _______________________________________________
> Fedora-infrastructure-list mailing list
> Fedora-infrastructure-list(a)redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
>
So OGo is (or was) cognizant of other users accounts - and would
create the appointment on the calendar directly rather than sending to
the users MTA. Calendar and other non-mail stuff are all stored in the
DB - while mail is almost an add-on. (In the mail-less environment it
knows about e-mail - and can send items out, but it treats local users
completely separate from e-mail. That might be ok. - esp if we did
iCAL or CalDAV.
I do need to disclaim that I haven't kept up with OGo in quite a while
and things may have changed, but the architecture had been around for
a long time, and I don't think they would have made any dramatic
changes.
Good call on OGO, I didn't even know it did iCal or caldav stuffs. My
last job was extensively with OGO, but I was just a user. It is
flexible, can handle multiple appointments, scheduling with one
another. If it supports ical/caldav, it could be a very viable choice
as it wouldn't require the use of OGO, but it *could* be used to
schedule activities.
Sounds like we're narrowing our features down to a good list. I'll
add OpenGroupWare onto the list.
Dave, could you expand on why it might be a bear to package?
Cheers,
Clint
4:18 p.m.
On Mon, 2009-02-09 at 12:58 -0700, Clint Savage wrote:
I think the point I'm continuing to make is that it should
support
caldav or something similar. The protocol defines a protocol, so the
client applications themselves shouldn't matter, but we do need to
have a way to communicate with the calendar server.
My intention isn't to discount MediaWiki or Zikula as a possible
platform for a calendaring client, but to say that the features you
suggest are not what we're after here. Instead I'd say that those two
applications could push/pull data from the calendar server (using
caldav).
The events listed in the caldav server can be manipulated by these
other applications and probably through an API which could include
Access Control Lists based upon FAS rights. I can see this being a
bit of an undertaking, but it can really benefit the Fedora Project as
a whole.
As I stated in my previous email, I've got a draft up of all the
features we'd like to see (it's pretty empty right now) and I'll
probably go ahead and list some of this email there. But for those of
you who are interested in helping me get that wiki page more complete,
feel free to visit:
https://fedoraproject.org/wiki/User:Herlo/Fedora_Calendar_Project_Desired...
Keep the thoughts coming, I want to see this project succeed!
Cheers,
Clint
Right, Clint and I are definitely thinking along the same lines here.
I think it's worthwhile outlining the Glorious Future Vision, so you can
see what Clint and I are driving for here. What we'd like to have is a
beautiful calendar system, where all Fedora-related events are stored.
It'd have each team's meetings and test days and so on listed in it, the
dates when Fedora pre-releases and final releases are due out - anything
Fedora-related with a specific date and time on it could be stored here.
And, critically, it needs to support CalDAV so that we can pull that
data into other places. Most usefully for an end user, you could pull
whichever particular project's dates you wanted into Evolution,
Lightning, KDEPIM or whatever, so that you can see the dates in your
regular client, and set alarms based on them and so on. The problem with
a purely web-based system is it becomes yet another damn place to log in
to, and you can't really set alarms on it.
--
adamw
6:40 p.m.
I've not used it in a while, and it is php based (I seem to remember that
being frowned upon) however I believe it supports caldav/ical at least for
publishing and supports numerous other plugins.
Has any one considered Horde and it calender (kronolith?) Plugin, I believe
they are already packaged in fedora.
On 9 Feb 2009, 10:18 PM, "Adam Williamson" <awilliam(a)redhat.com> wrote:
On Mon, 2009-02-09 at 12:58 -0700, Clint Savage wrote: > I think the point
I'm continuing to make i...
Right, Clint and I are definitely thinking along the same lines here.
I think it's worthwhile outlining the Glorious Future Vision, so you can
see what Clint and I are driving for here. What we'd like to have is a
beautiful calendar system, where all Fedora-related events are stored.
It'd have each team's meetings and test days and so on listed in it, the
dates when Fedora pre-releases and final releases are due out - anything
Fedora-related with a specific date and time on it could be stored here.
And, critically, it needs to support CalDAV so that we can pull that
data into other places. Most usefully for an end user, you could pull
whichever particular project's dates you wanted into Evolution,
Lightning, KDEPIM or whatever, so that you can see the dates in your
regular client, and set alarms based on them and so on. The problem with
a purely web-based system is it becomes yet another damn place to log in
to, and you can't really set alarms on it.
--
adamw
_______________________________________________ Fedora-infrastructure-list
mailing list Fedora-infr...
2:10 a.m.
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?
In terms of running Java Apps, Its not that hard, we've been running 3 or 4
jboss clusters here for a couple of years and had absolutely no problems
with anything server side. Nothing major anyway, apache (httpd) issues with
it, but not with Jboss. The only issues we have had has always been
application dependant. And in most cases a bounce of the war file would
resolve the issue (temporarily)
If there isn't enough skill to support that sort of environment then are we
looking more towards a slightly more bespoke solution?
2009/2/9 Adam Williamson <awilliam(a)redhat.com>
On Mon, 2009-02-09 at 12:58 -0700, Clint Savage wrote:
> I think the point I'm continuing to make is that it should support
> caldav or something similar. The protocol defines a protocol, so the
> client applications themselves shouldn't matter, but we do need to
> have a way to communicate with the calendar server.
>
> My intention isn't to discount MediaWiki or Zikula as a possible
> platform for a calendaring client, but to say that the features you
> suggest are not what we're after here. Instead I'd say that those two
> applications could push/pull data from the calendar server (using
> caldav).
>
> The events listed in the caldav server can be manipulated by these
> other applications and probably through an API which could include
> Access Control Lists based upon FAS rights. I can see this being a
> bit of an undertaking, but it can really benefit the Fedora Project as
> a whole.
>
> As I stated in my previous email, I've got a draft up of all the
> features we'd like to see (it's pretty empty right now) and I'll
> probably go ahead and list some of this email there. But for those of
> you who are interested in helping me get that wiki page more complete,
> feel free to visit:
>
>
https://fedoraproject.org/wiki/User:Herlo/Fedora_Calendar_Project_Desired...
>
> Keep the thoughts coming, I want to see this project succeed!
>
> Cheers,
>
> Clint
Right, Clint and I are definitely thinking along the same lines here.
I think it's worthwhile outlining the Glorious Future Vision, so you can
see what Clint and I are driving for here. What we'd like to have is a
beautiful calendar system, where all Fedora-related events are stored.
It'd have each team's meetings and test days and so on listed in it, the
dates when Fedora pre-releases and final releases are due out - anything
Fedora-related with a specific date and time on it could be stored here.
And, critically, it needs to support CalDAV so that we can pull that
data into other places. Most usefully for an end user, you could pull
whichever particular project's dates you wanted into Evolution,
Lightning, KDEPIM or whatever, so that you can see the dates in your
regular client, and set alarms based on them and so on. The problem with
a purely web-based system is it becomes yet another damn place to log in
to, and you can't really set alarms on it.
--
adamw
_______________________________________________
Fedora-infrastructure-list mailing list
Fedora-infrastructure-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
10:12 a.m.
On Tue, 2009-02-10 at 08:10 +0000, Matthew ... wrote:
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?
That's what Clint's page is about - it's a list of candidates we can
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
10:35 a.m.
To clarify what I was after, if you look at the following link:
https://fedoraproject.org/wiki/User:Herlo/Fedora_Calendar_Project_Desired...
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(a)redhat.com>
On Tue, 2009-02-10 at 08:10 +0000, Matthew ... wrote:
> 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?
That's what Clint's page is about - it's a list of candidates we can
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(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
11:38 a.m.
2009/2/10 Matthew ... <soimafreak(a)gmail.com>:
To clarify what I was after, if you look at the following link:
https://fedoraproject.org/wiki/User:Herlo/Fedora_Calendar_Project_Desired...
Which has no "must have" requirements and no "Should have"
requirements.
Add some requirements. It's a wiki and can be edited :)
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.
No argument, that page is a draft and needs editing. I'm hoping we
get a collective of suggestions/requirements.
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.
Those sound somewhat reasonable, let's get them on the wiki page. If
you don't have wiki formatting skills, don't worry, I'll format it
once you've added them to the right section.
I completely agree with your thinking and thus why I created the page.
I'm not the master here, just trying to make it possible for others
to have a say. Getting that information on the wiki page is critical
to determining what calendaring solution we use.
I'll be adding stuff too, but just haven't had time to do so. Anyone,
with a FAS account can edit the wiki.
Cheers,
Clint
5552
days inactive
5557
days old
infrastructure@lists.fedoraproject.org
29 comments
13 participants
participants (13)
-
Adam Williamson -
Bret McMillan -
Clint Savage -
David Nalley -
Douglas Furlong -
Eric Christensen -
Jeroen van Meeuwen -
Jesse Keating -
John Poelstra -
Matthew ... -
Mike McGrath -
Simon Birtwistle -
Toshio Kuratomi