Well, the title says it all. Fedora Tour, which we recently decided
to make a web application needs web developers. Ironic eh? The thing is:
none of the current Fedora Tour team members have ever done web
development before. We’re learning, but the changes with HTML5, CSS3 and
time, we’d like an established web developer to come in and help us
reduce the learning time and get down to the implementation as soon as
- Are you a web developer?
- Do you have some free cycles?
- Do you want to work on a brand new, *awesome* project?
** Give us a shout today!!
You can either catch us on #fedora-tour on Freenode, or you can ping us
on the mailing list. I’m around on quite a few fedora IRC channels,
so you can also catch me personally if you want. My nick is
The wiki page for fedora tour contains all the info you’d need.
Note: This is only an announcement mail. Please do not reply to it.
Contact us instead!
Is anyone interested in helping lead Ask Fedora? The following tasks
needs to be done on a regular basis:
* Update and test Askbot whenever there is a new upstream release
* Coordinate with Kevin Fenzi (nirik in #fedora-admin) for deploying to
staging instance and test it for regressions, flesh out new features etc
* Deploy to production instance after testing. Having some knowledge of
Puppet would help in doing this task but if not coordinate with Kevin
for this as well
* Developing or coordinating development of new features useful for Ask
Fedora. Python and Django knowledge would be useful for this step but
* Develop policies for moderators, helping out as a admin for Ask Fedora
and keeping an eye on the forum in general, including unanswered
* Last but not the least, participate in the forum itself but asking or
You can delegate some of these tasks and do it as a team. Let me know
if you want to take over. I will still be involved to whatever extend I
can but I would like to hand off primary responsibilities to someone
else and focus on other things at the moment. Thanks.
Of late, APAC has been trying to improve the situation with swag,
funding, reimbursements and the sort. Since Harish is the only Comm Arch
person responsible for all of APAC, we think it's better to open all
tickets at the APAC trac where they can be discussed at the bi-weekly
APAC meetings, and are all at one spot for Harish to review. Keeping
this in mind, I've opened a ticket with FAmSCo requesting the the India
trac be made read only, and all future tickets for *all of APAC* be
opened in the APAC trac. The ticket is here. It'll be discussed in
this APAC meeting this Saturday (again) to make a final decision. I
request you to please post your comments on the ticket, or at the APAC
meeting (which is preferred).
I know a few people are now EPEL maintainers. If you would like to have
a free RHEL subscription, check out the info here
-------- Original Message --------
Subject: REMINDER: RHEL entitlements for EPEL maintainers
Date: Mon, 2 Apr 2012 09:57:25 -0600
From: Kevin Fenzi <kevin(a)scrye.com>
Reply-To: EPEL development disccusion <epel-devel-list(a)redhat.com>
Organization: Scrye, INC
I thought I would drop a reminder here about RHEL entitlements for EPEL
maintainers. If you are a maintainer of packages in EPEL, you can get a
entitlement to run RHEL to help you test and fix your package(s).
for more information and process to request your entitlement.
Hopefully this is useful to some. ;)