Comment 20 for bug 174672

Revision history for this message
In , Dmose (dmose) wrote :

(In reply to comment #19)
>
> B: dmose and I have also both started discussing the need for greater ease of
> access to calendar files that are publicly available on the internet.

I would actually go so far as to say that even "search known calendar collections" is really just part of a higher level goal of providing useful integration with stuff on the web (eg existing ICS resources, calendaring sites, mapping sites for locations, etc).

> In this respect, I believe the ultimate solution is to introduce a 'or search
> known calendar collections' option to the URL page of remote calendar
> creation in the wizard.

It could make sense to have an entry point there. I would argue that in the short term, it would make sense to simply have a menu item that links to a web page of Internet calendaring resources, and one of the things on that page would be a link to another "search for a holiday calendar" page.

> Many of the comments and criticisms that I've heard about this seem to be
> arguing more from the point of view that this patch does not go far enough.
> (Comment #17 especially). The points made there are all perfectly relevant,
> but I'm of the belief that trying to address them would be taking too large of
> a step at once (at least given available development resources).

Yes, I completely agree. Right now, in both the Sunbird and Lightning worlds, the important goal is to "ship something that is usable by users and based on the refactored back-end". If we can do something easily now to support holiday stuff, great.

> What needs to be decided then is: Is this patch an acceptable first step along
> the paths to the two above goals? It certainly is not the final answer to
> either of them. If we decide that this is not an acceptable solution, then
> perhaps this bug needs to be closed as invalid, and a new bug with a more
> clearly established goal needs to be filed.

This sounds to me like an excellent framing of what we need to sort out now, although I think just adding a menu item as described above would be another possible simple solution.

> One of the things I'd propose would be to try to develop some common use cases
> for holiday files, probably via a blog post.
> -What percentage of users subscribe to a holiday file?
> -What percentage of our users subscribe to more than 1 holiday file?
> -What percentage know holiday files exist/ where to find them?
> -What percentage use the holiday file directly corresponding to their locale?
>
> If we can get answers to these questions, it might help indicate how
> appropriate this patch is.

Its not clear to me how blogging is likely to result in us having believable answers to this questions, but perhaps Im not understanding exactly what youre proposing.