Introduction Fedocal
by Pierre-Yves Chibon
Hi all,
Kevin asked me to present Fedocal a little bit.
Fedocal is a web-application aiming at providing a central place for
Fedora calendar related data.
My first thoughts while doing this was the #fedora-meeting{,-1,-2} IRC
channels, but I do think it could work as well for any other calendar
related information (releases?, infra?).
== What does it do?
* Admin can create calendar(s)
* Calendar are managed by a FAS group
* People within this FAS group can create meetings on this calendar
* While creating meeting, the creator can specify co-managers for the
meeting.
* Only the manager(s) can edit and delete meetings (and only in the
future)
* Meetings have a date, starting and stopping time and a free text field
which can contain any information (agenda, introduction...).
* Meetings can be recursive until the end of time == 2121-12-31*, or
until a specified time and their frequency can be every 7 or 14 days.
* Meetings can have a reminder.
* Reminder are sent 12h, 24h, 48h or 168h (7days) before the meetings[2]
* Reminders can be sent to several email address (comma separated)[2]
* Meetings can be deleted/edited either a single meeting, or all the
future meetings of a recursive meeting.
* The calendars have a weekly view which can be browsed
* The calendars can also be pointed to a single date, it will then
return the view of the week
ie: /#fedora-meeting2/2012/9/25 will return the week view of the 25h of
September, same for /#fedora-meeting2/2012/9/28
== Future plans?
* The first is for sure, see if this application can be useful
* Finish up what needs to be
* Take into account the timezone returned by the FAS for the user to
display the calendar. Maybe having two columns one with UTC one with the
local time.
* Provide a iCal/Caldav output so that we can couple it to a calendar
client [3]
* See with Mizmo to give Fedocal a nicer look :)
* Testing!
Fedocal is still work in progress but there is already some things
nicely working. It will requires some more work but I think it is duable
to have something basic quikly there.
The big question is then: do we consider this useful or should we try to
move to a real calendar solution with the reminder function added ?
Best regards,
Pierre
[1] Why 2121-12-31? Because 21+21=42
[2] This work is still to be done (probably a script to run via a
cronjob at first)
[3] This will require quite some work and probably more than I can put
in during my free time
PS: I am opening now the discussion but I'll be away for 10 days
starting on Wednesday (morning, US time)
11 years
i have cloud
by Matthew Miller
I launched a F17 instance in our Eucalyptus system.
It works. (Awesome!)
I have not done anything to try and break it. Let me know if I should. :)
--
Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ <mattdm(a)fedoraproject.org>
11 years, 1 month
Introduction
by Onalenna Junior Makhura
Hi,
I have been a member of this list for a few years now but due to some
constraints I have not been able to actively participate. I would now
like to start be active in Fedora development. I have been using fedora
as my 1st choice OS since Fedora Core 6.
I would be very glad to have someone who can show me the ropes.
Regards,
Onalenna Junior Makhura
11 years, 1 month
A small step towards for solving Ticket 1084
by vipin kumar
Hi Team!
This mail is regarding Ticket
1084<https://fedorahosted.org/fedora-infrastructure/ticket/1084>
As I already informed in Infrastructure weekly meeting that I'm proposing a
slight change in
page<https://fedoraproject.org/wiki/Infrastructure/Architecture>layout
as mentioned below -
1 Global Presence
< this section is about either showing fedora servers in
geographical map or just listing server locations as suggested by
'abadger1999'.>
2 Network Topology
< this section shows how our severs are interconnected or
connected to the outside world. I guess this section will make more sense
if we are just listing the server locations in section 1.>
3 Network Architecture
< this section will show overall network architecture with
protocol stacks >
3.1 Front end
< similar to present section but with more detail >
3.2 Proxy view
< similar to present section but with more detail >
3.3 Application layer
< similar to present section but with more detail >
4 Helping Out (or Help Us ?)
< this section will target two type of contributors, one who can
improve the quality of information present in page
<https://fedoraproject.org/wiki/Infrastructure/Architecture>and another who
can provide resources.>
This is the overall structure and type of content the page will have.
Please let me know about any additions, deletions or Improvements.
Thanks & Regards,
--
Vipin K.
IRC ID: _love_hurts_
11 years, 1 month
OT: block an email domian
by Frank Murphy
Need some help.
How do I block an email address\domain from posting to list.
noreply+3889835834(a)badoo.com
Have put: *(a)badoo.com
Privacy >
List of non-member addresses whose postings will be automatically discarded.
> Discard.
Is the widcard correct method?
--
Regards,
Frank
"Jack of all, fubars"
11 years, 2 months
Plan for tomorrow's Fedora Infrastructure meeting (2012-09-27)
by Kevin Fenzi
The infrastructure team will be having it's weekly meeting tomorrow,
2012-09-27 at 18:00 UTC in #fedora-meeting on the freenode network.
Suggested topics:
#topic New folks introductions and Apprentice tasks.
If any new folks want to give a quick one line bio or any apprentices
would like to ask general questions, they can do so in this part of the
meeting. Don't be shy!
#topic Applications status / discussion
Check in on status of our applications: pkgdb, fas, bodhi, koji,
community, voting, tagger, packager, dpsearch, etc.
If there's new releases, bugs we need to work around or things to note.
#topic Sysadmin status / discussion
Here we talk about sysadmin related happenings from the previous week,
or things that are upcoming.
#topic Private Cloud status update
#topic Security FAD update
#topic Upcoming Tasks/Items
#info 2012-10-09 to 2012-10-23 F18 Beta Freeze
#info 2012-10-23 F18 Beta release
#info 2012-11-13 to 2012-11-27 F18 Final Freeze
#info 2012-11-20 FY2014 budget due
#info 2012-11-22 to 2012-11-23 Thanksgiving holiday
#info 2012-11-26 to 2012-11-29 Security FAD
#info 2012-11-27 F18 release.
#info 2012-11-30 end of 3nd quarter
#info 2012-12-24 to 2013-01-01 Red Hat Shutdown for holidays.
#info 2013-01-18 to 2013-01-20 FUDCON Lawrence
#topic Open Floor
Submit your agenda items, as tickets in the trac instance and send a
note replying to this thread.
More info here:
https://fedoraproject.org/wiki/Infrastructure/Meetings#Meetings
Thanks
kevin
11 years, 2 months
Ticket #2931
by vipin kumar
On Mon, Sep 24, 2012 at 12:47 AM, vipin kumar <vipinkumar41(a)gmail.com>wrote:
> Hi Team!
>
> Maybe I can start working on Ticket #2931<https://fedorahosted.org/fedora-infrastructure/ticket/2931>if anyone provide some details on that.
>
> thanks & regards,
>
> --
> Vipin K.
> Research Engineer,
> C-DOTB, India
>
--
Vipin K.
Research Engineer,
C-DOTB, India
11 years, 2 months
Web App Accessibility
by Toshio Kuratomi
Accessibility of Web Apps
For a while we've been striving to write web apps that would be usable by
screen readers for people who have visual impairment. Fedora Community was a
solitary exception to this as it was seen as merely aggregating apps that were
provided elsewhere. However, this year, we've had more apps start to rely on
javascript that manipulates the DOM (tagger comes to mind). This is a problem
for screen readers as there are no open source screen readers that I know of
that enable this functionality reliably (elinks is the closest. It links to
spidermonkey for a javascript interpreter. However, it only implements bits
and pieces of the DOM it's extremely unlikely to work with anything useful.)
I think it's time to re-evaluate what we want to strive for in terms of
accessibility. Here's the options I've come up with. Feel free to come up
with other options :-)
* Stop worrying about accessibility
- We can use whatever works in our standard graphical browsers since we
no longer target people who cannot use them with (up to) all five senses.
* Continue to target screen readers for things we write
- Unless someone can find some better news than I've been able to, this
means, among other things, having fallbacks for pages in apps that use
javascript, imagemaps, or other things that don't work in text-mode browsers so
people using screen readers have a method of accessing the same functionality.
This is usually implemented by rendering the fallback as the html page. Then
having javascript replace the contents of the page with whatever is needed to
implement the more dynamic view.
* Continue to target screen readers but only for things we consider in "the
critical path"
- Critical path has been loosely defined as things that are used to build
and push out packages. pkgs.fp.o, koji, bodhi, fas are the obvious ones. pkgdb
and tagger are currently in a grey area of
we'll-survive-without-but-they-probably-should-be-included. wiki (editing) and
mirrormanager (admining mirrors, not downloading via) are examples of things
that are not in the critical path.
* Discard accessibility for screen readers in the WebUI where we provide a
terminal-app that does the same thing.
- This would assume that people using these web apps are using Fedora.
Then again, there might be other methods besides screen readers to access web
pages with javascript on other platforms?
* Assume that blind users can use standard desktop apps (like firefox and
webkit based browsers) to access our web apps as long as the apps provide
keyboard navigation.
- I don't know if this is a reasonable expectation on Fedora. Need to
talk to someone who works on accessibility to know if this is a viable option
for blind users, for a subset that are vision impaired but not totally blind,
or of no use at all.
- We'll also need to think about how to make keyboard navigation
discoverable and perhaps settle on some standard keybindings.
I haven't checked the current state of all our applications in elinks recently
but I did just do a spot check. pkgdb and tagger and both are currently unusable
for their editing functions (tagger I couldn't even log in). FAS worked. koji
I suspect will work for read-only views. For read-write it may work if there's
a way to have elinks use the fedora client-side certificate.
-Toshio
11 years, 2 months
