What should be added or removed? Remember this is going to be a time
for us to actually sit in a room and get stuff done.
High level goals (Infrastructure Specific):
1) Basic auth/group API for the old Accounting system and the new
one in Python.
2) Update System hacking (lmacken lead)
3) Finalize the new postfix server
4) Discuss the "Fedora Noc" + initial coding / Design
5) Volunteer sponsorship
6) Future of the wiki (Moin)
7) Design and coding of new account system (Try to find something
that is already out there)
8) Hosting (Jkeating lead)
9) Package Database
10) Backup Server (Finalize)
High level goals (general non-infrastructure specific)
1) Lowering the barrier to entry without sacrificing
infrastructure / security
2) Volunteer management (coordination might be a better word)
3) VCS / SCM future (Lead by those in the sig)
I'd also like to get with some of the other dev's to get an idea of whats
important for them to have going forward and whats needed for this
I'm one of the other resident old-farts at Red Hat.
I'm currently the architect for Red Hat's Release Configuration
Management team (aka release engineering). My main focus is on the
infrastructure within Red Hat and RHEL.
I am willing to contribute ideas etc. without being the one to
implement them (again, like Bill).
Architect, Release Configuration Management
Red Hat, Inc.
I'm a resident old fart here at Red Hat, and somewhat of a Fedora
jack-of-all-trades, doing development and helping with testing,
releasing, signing, planning, etc. I've been heavily involved in
the planning of the Great Merger, and the plans for Fedora 7.
I'm also a member of the Fedora Project Board.
Fedora infrastructure plans: I am probably going to be one of
those annoying people coming up with lots of plans along the lines
of "we should do X, Y, and Z, and here are plans for them" without
actually doing the implementation. Whether that makes me useful
or useless remains to be seen.
For all those who haven't been following along because of the Holidays,
we have data in the database! For all those who have been following
along, there's a TurboGears deployment needing some serious UI love!
I've coded a read-only view of the Fedora 1-devel Collections with lists
of packages in each. Making a similar interface for the Packages should
be out later this week. If you want to stare at the horror that is a
project in the middle of birth have a gander here:
There's a lot left to do and I'm anxious to start recruiting others to
work on various aspects of this. I'll post a more formal list of
sub-tasks for this project after the meeting tomorrow but for now, if
anyone wants to give feedback on the database schema, it's still got the
ugly hacks that I'd love someone to point out a more elegant solution
for (schema attached). And anyone that thinks they'd like to take a
stab at using TurboGears and SQLAlchemy, prepare to be recruited!
So, I never got around to sending one of these. Here goes.
I'm a Linux software architect for Dell. I've been administering
Linux systems since 1994 and have been Dell's lead engineer for Linux
products since 1999. My team develops and tests Red Hat Enterprise
Linux and Novell/SuSE Linux Enterprise Server products on Dell
PowerEdge servers and Precision workstations. We use Fedora on our
laptops and desktops, fix bugs, and merge those fixes into all of the
various streams - upstream and various target distros. I also have
the privilage of serving Fedora on the Fedora Project Board. I run
the linux-poweredge(a)dell.com public mailing list (subscribe and read
archives at http://lists.us.dell.com) among others, which has several
thousand Linux sysadmins on it.
I'm a master of many languages and cultures. I blend in. You'll
never find me. oops, wrong movie...
For Fedora Infrastructure, I'm working on the Mirror Management
System. I also want to get gitweb working for anonymous r/o checkouts
from the new project hosting service.
I'm 'mdomsch' on IRC.
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com