I am new to the fedora infrastructure group. I am going throug few of the links in the site to get a feel of the work. I have submitted my .ssh_rsa_key.pub from the site. I think I will get some intimation on this. Please someone can let me know further proceedings from here onwards.
Regards & Thanks Prabir Senapati mailto: senapati2001(a)yahoo.com
AFAIK the build hosts are RHEL5 (or maybe F10 by now?). At any rate
the rpm used in rawhide is quite different than the ones from the
hosts, how has this been solved in the build hosts? Has the hosting OS
upgraded its rpm to be compatible to all hosted chroots? Or is the rpm
within the chroot used?
I'm asking in a double context: First I'd like to understand if smart
can properly handle chroots of rawhide/F11 on F10/RHEL5 hosts. Anders
Björklund (in the Cc, please keep him there on replies) has put a
great deal of effort to have smart working on F10 and F11, and a smart
version for managing F11 and later chroots on F10 or earlier would be
And second I'd like to know how to setup a build environment for F11
for getting some ATrpms packages out.
Axel.Thimm at ATrpms.net
I've been lurking on the mailing list for a while and I finally
registered for my fedora account today (username: chrisj)
I'm interested in helping out as time permits. I got on irc once
(lurking again) and haven't really logged in since. I'll try to make a
few meetings after the holidays
I'm planning to get my personal test systems setup soon. I just moved
and still getting things straight at home. Bought a 750GB drive last
night and will be installing F10 over the weekend. I had been running
the U... distro and it's time to get back to the fedora/RH rpm way of
doing things :-)
I've used RedHat since before Fedora existed (I think 6 was the first
one). Started as a hobbyist, 2 years. Then got a job as an admin and
have been doing Linux admin and Cisco networks for the last 5 years.
My current employer is a Win shop so I just get to run the DNS,
email, and network, but the network is 50 remote offices and 3
different data centers in the midwest. I don't mind the Windows too
much and can find my way around them, it's also kinda fun to get the
Linux and MS products to play nice together. I've worked with a lot of
different linux and OSS software products including: postfix,
openldap, apache, bind, samba, mailman, pam, built some custom rpm's,
etc. I use RHEL mostly at work and some fedora and Cent for testing
(some suse, deb, and slackware in the past). I used to do lots of
security firewall apliances with various linux distros (I was a big
fan of LRP when it would fit on a floppy), most of this is now done
with Cisco in my world. I can shell script pretty well and I've
written several perl scripts in the last few years (dabbled in php but
not enough to know it well). I've always been interested in python but
don't have much if any exp with it. I also don't have much experience
with SQL/DB or source control.
I was looking at the FIGs and would be interested in the base sysadmin
and sysadmin-noc for now while I figure out where everything is and
what it does. I'm also interested in more info on the sysadmin-tools
and sysadmin-web FIG.
So, next just apply for the FIGs, keep lurking, ask some questions,
show up for IRC meetings?
I'm not sure if we have any memcached experience on the list but I thought
I'd ask. Can anyone explain this:
Notice how memcached1 has a much higher hit rate and memcached2 has a much
lower hit rate?
I will eventually want to use a bugzilla account for a certain service. To
make it easier for someone else to reclaim this account in case i vanish, I
would like to use a Fedora mail alias for this.
Is there some type of bot account type in FAS that I can use to create the
additional mail alias or some other procedure for this?
Today we added the transif user to the packager group because transifex
lost the ability to add translations for comps. At the moment, this
doesn't affect much -- packager group only gives you the ability to
commit to comps and what packages you are given explicit rights to.
However, it may become bigger in the future since we may allow people to
specify that anyone in packager can commit to their packages.
transif's last commit to the comps files was around the 17th of July.
If anyone can recall some action or config change that they might have
performed that would have changed whether transif could commit to comps
between 17th of July and today or can think of a better way to give
transif access to the comps cvs repo please speak up! it would be
better long-term if transif was not in the packager group.
The only solution we've come up with that doesn't use the packager group
so far requires that we do two things:
1) add cvs acls for transif to commit to comps.
2) set filesystem acls so transif can commit to comps.
Doing #2 isn't that great an idea as it's a one-off doing something not
readily apparent (we don't use fs acls anywhere else in cvs). But if it
could be puppet managed it might not be too bad.
Okay, We've got to do some work for AGPL compliance with moksha.
First, a few restrictions that we'll have to live with until we can
figure out a legal way to do them better:
* We cannot do development work directly fedoracommunity/moksha on
staging for now. All fedoracommunity/moksha changes must be deployed to
staging in the form of an rpm.
* lmacken has confirmed that staging is currently deployed from rpm.
* **The same for the publictest instances**
* If legal approves of using Apache Basic Auth to fix this, we can use
that to allow use of the publictest boxes again. Note, though, that
that approval will still restrict us (for instance, ianweller is using
pt7 to demo his fedora community stats branch. He won't be able to demo
it to people outside of sysadmin-test with the Apache Basic Auth
solution in place).
Some things we need to code into Fedora Community:
* We need to be able to customize the footer or front page of
fedoracommunity to point to infrastructure.fedoraproject.org for the
sources and to trac for hotfixes.
* Note that for certain uses of publictest/staging, this can work as
well. For instance, ianweller could run his demo strictly from a git
checkout and the configuration can point people to that *specific* revision.
* Upstream moksha/fedoracommunity might want to change their default
footer/frontpage to point to the upstream tarballs as legal says the
project page isn't good enough for people running it to be compliant.
For those of you who haven't no idea what "Fedora Community" is, its our
newest Fedora web application, providing a window into the Fedora
distribution, and leveraging the power of Fedora's Account System,
Bodhi, Bugzilla, Koji, and PackageDB into a single user-friendly
website. It is built entirely with Free Software, such as Moksha and
Turbogears 2. Fedora Community is designed to simplify Fedora workflows
and bring transparency to Fedora processes:
What you see on that URL is our 1.0 milestone, but we already have lots
of ideas on improvements and new functionality that we'd like to develop
for our 2.0 release. So, we're going to have a public brainstorming
session on Monday, August 3rd, 2009:
* The session will be held at 1500 UTC (11 AM Eastern)
(In addition, if there are enough interested international folks who
cannot attend the session due to their timezone, please let me know, and
we will try to schedule a future session that works for you)
We're going to use a variety of ways to be involved:
* IRC: #moksha on irc.freenode.net (we'll be watching and taking
questions from the channel)
* Gobby: We're going to keep our notes in Gobby, an open source
The name of our document is "Fedora Community Brainstorm", see
http://fedoraproject.org/wiki/Communicate/GobbyHowTo for information on
how to connect
* Telephone: This is where we'll be doing the talking.
US Toll-Free: 800-451-8679
Conference Code: 22717 79826
(If you need an international dial-in number, please email me with your
country, and I may be able to provide it.)
Please be kind and mute your line if you're not asking a question. If
the noise on the call becomes unbearable, I will mute everyone. :)
Questions about the meeting? Email me. Questions about Fedora Community
2.0? Come to the brainstorming session! Can't make it to the session and
want to suggest something? Login to Gobby and add it to our notes before
Tom "spot" Callaway, Fedora Community Cat Herder