python-kid on buildsys server
by Michael Schwendt
$ rpm -q python-kid
python-kid-0.9-2.centos4
on buildsys.fedoraproject.org would benefit from an update to 0.9.5 which
includes xml related fixes and makes it possible to create pages that
don't fail in the w3c validator.
$ rpm -q --whatrequires python-kid
repoview-0.5.1-1.centos4
17 years, 1 month
Multiple CLA Implementation
by Warren Togami
I just talked with Ken Reilly, one of RH's engineering managers. We are
trying to solve the CLA problem, where legal surprised us by allowing
Red Hat contributors to Fedora under Red Hat's CLA instead of Fedora's
CLA. We both realize there are potential problems in this, but there is
urgency to allow Red Hat CLA very soon because this blocks many Red Hat
engineers from creating Fedora Accounts as we approach the merge.
Below is an initial simple implementation to enable this very quickly.
Luckily however, the groups shouldn't get in our way to further improve
this process later.
One Time Changes
================
1) Existing cla_done is cloned to fedora_cla.
2) dell_cla group is created, Matt adds whoever he wants. Remove
dell_cla members from fedora_cla.
3) redhat_cla group is created, populated through various means.
4) Modify existing Fedora CLA signing process to join fedora_cla instead
of cla_done.
Automatic Changes Thereafter
============================
fedora_cla auto adds to cla_done
redhat_cla autoadds to cla_done
dell_cla autoadds to cla_done
Toshio's cvsextras -> fedorabugs code should work in these cases too?
redhat_cla Management
=====================
1) (one time) Dump dist-fc7 package owners, match e-mail addresses with
FAS accounts, add all those to redhat_cla.
2) (one time) Add everyone else that we know about who currently doesn't
match e-mail addresses.
3) Give kreilly admin access to the redhat_cla group, so he can
add/remove members in an interim.
4) Later give RH GIS access, so they can make it part of their standard
"new employee" or "remove employee" process.
See any problems in this? Please comment.
We need this implemented REAL SOON, hopefully by tomorrow.
Warren Togami
wtogami(a)redhat.com
17 years, 2 months
xen1
by Mike McGrath
Xen1 is going to be offline for the next few days. I'm going to upgrade
it to RHEL5. We can do our evaluations to see if its time to upgrade
the rest of our environment. Ironically we're still not done upgrading
everything to RHEL4 yet :-)
Anywho, those interested in testing their apps on RHEL5 please contact
me or the list so we can coordinate.
-Mike
17 years, 2 months
Introduction
by Peter van der Does
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi people,
A quick introduction as I'm new here.
My name is Peter van der Does and I'm 36 years old, born and raised in
the Netherlands but since a couple of years living in NJ, USA, so yes
I'm bilingual (Dutch and English). I have been in the computer industry
for close to 17 years now of which about 10 years as a systems
administrator and of those 10 years about 4 years as a Linux/Unix admin.
I have been managing mostly Redhat servers but also other flavors, like
Mandriva, CentOS (OK, that is Redhat), HP-UX. I've been managing a wide
variety of software (Apache, MySQL, Postfix etc) as well as network
configurations (DHCP, DNS, routers, switches). Tools I have been using
are Nagios, Cacti, OpenView as well writing my own Perl/Shell scripts to
help with the administration tasks.
At the moment I'm a stay home dad, which means I've got quite some time
on my hand and I have been looking for something I can do from home and
give me the ability to keep in touch with the industry. My biggest
hobbies currently are photography and with spring coming I hope to pick
up golfing again.
Currently I'm working on a DNS audit for the group.
Don't hesitate to drop me an email if you want to ask something or need
something.
Peter van der Does
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGC9EA/vSRAed+jpgRAvc0AJ4gCsX50FP3Urp9u3ysoCvsk8KGPQCgiG/c
N+zlujnrkySpqZwKqCVANog=
=lwdl
-----END PGP SIGNATURE-----
17 years, 2 months
Metrics: Ideas of Data Sources
by Warren Togami
Just jotting down some ideas for additional Fedora Metrics. Data over
time and graphs would be very useful in media to show using actual
numbers the growth of Fedora in activity, contributors and packages.
These graphs would also be very useful in making business cases to RH in
showing the success of Fedora investment, as we try to justify more
targeted investments.
Data Sources
============
1) cvsextras-sponsors(a)fp.org receives all of the notices where people
request and are granted access to the cvsextras group. We have no
official mail archive of this. Does anyone personally have an archive
of cvsextras-sponsors mail going back to the beginning when Sopwith
launched the system?
Harvesting that mail archive would allow us to graph absolute # of
Fedora package contributors over time. This however tells us nothing
about activity.
2) Check-in activity on the two commits lists could tell us:
- how many contributors were active in a given month
- how active was package activity in general
- how many new packages
- how many actively maintained packages
3) Metadata within CVS could tell us similar information as above.
Any other ideas for potential statistics grabbing opportunities?
Warren Togami
wtogami(a)redhat.co
17 years, 2 months
Meeting on Thursday
by Mike McGrath
I'll be in training on Thursday and will be unable to attend the meeting.
-Mike
17 years, 2 months
Re: Wiki slownessThat
by Toshio Kuratomi
On Mon, 2007-03-26 at 08:29 -0500, Mike McGrath wrote:
> Thorsten Leemhuis wrote:
> > BTW, did anybody ask the moin moin developers for their plans? I suppose
> > other projects hit the same bottleneck, too...
> >
> Yeah, I've talked to them a bit. Toshio is actually working with them
> to submit a patch.
>
... but I am short of time. So if someone wants to work on this first,
the basics are that we want to maintain a list of subscribed pages. One
list will be per page and have all the normal subscriptions which target
one specific page. The other list will be global to moin and hold all
the regular expression using subscriptions. These lists only have to be
updated when the user updates their subscription preferences. The Moin
code will then be able to quickly assemble a list of people that are
subscribed to the page from the per-page-list and sequentially trying to
match the regexes.
(The Moin devs tell me the current method scans every subscription
request of every user to see if it matches the page that has been
modified. 8000+ users of which 1000+ have subscriptions. In the new
scheme we only have to sequentially scan 180+ regular expressions.)
I don't think I'll be able to work on this until post-F7. So you guys
have nearly 2 months to get fed up enough with the delay to get to this
first ;-)
-Toshio
17 years, 2 months
