[Insight] Calendar idea
Paul W. Frields
stickster at gmail.com
Wed Jun 8 14:07:35 UTC 2011
On Wed, Jun 01, 2011 at 09:48:04AM -0400, Máirín Duffy wrote:
> Hi Paul,
>
> On Tue, 2011-05-31 at 21:25 +0000, Paul W. Frields wrote:
> > * I want to attend the next Fedora Infrastructure team meeting on
> > IRC -- when does it happen?
>
> > * I want to know when the #fedora-meeting room is free, and put in
> > a reservation when I find an open time.
>
> > * I want to see a list of important dates like string and feature
> > freezes for the next release.
>
> > * I want to add an event to the Fedora events calendar and have
> > that entry kick off other things like an eventbox or media
> > request in a Trac.
>
> > * I want to know when the next Fedora release comes out.
> >
> > * I want to know what Fedora events are happening in my geographic
> > region next month.
>
> These use cases are great. The comparison between the status quo and
> shiny future are also great and the shiny futures are a good point to
> start rough prototype sketches from and run them by users to see if they
> make sense. If the users like them, then the step after that would be to
> take a look and see how close the technology could get us to them.
>
> > Note that some of these start shading into the areas that Hiemanshu
> > wants to cover in his GSoC project. So I'd REALLY, REALLY like it if
> > he and/or Juan (nushio) could be at one of our meetings to discuss, or
> > we can set up a special time to do that. Just need some word back
> > from them...
>
> Hiemanshu, if you want some help with prototype sketches of the shiny
> future ideas, just let me know and I'm happy to crank some out for you.
>
> I'm also happy to join the meeting, Paul, if you think it would be
> helpful but you do seem off to a great start as-is.
Hi Mo,
Sorry for the late reply -- since we're still in early stages I didn't
want to use up an hour of your time. But I was thinking the next
stage should be figuring out what technically needs to happen for each
of the above processes to work from a user perspective.
For example, just starting with the very first bullet, if I want to
attend the next Infra team meeting, a few things have to be present on
the system:
* The ability for someone to put in a meeting time
* The ability for someone to edit an existing meeting time, perhaps
based on their group membership (to prevent goofs)
* A view that presents upcoming meeting times in a calendar
(what kind of view would this be? biweekly?), with filters
If we go through this process for all of the use cases, we have a
pretty good idea of the work requirements. We can prioritize them by
how big the win is, and then start to figure out our scope/what we can
finish.
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
Red Hat Summit/JBossWorld -- Register now! http://.theredhatsummit.com
More information about the logistics
mailing list