Hello,
I have two students interested in diploma thesis called Yum plugin for
suggesting packages based on usage:
http://bit.ly/18hrHbL
TL;DR - from anonymized access log, create a database of suggested
packages using data mining techniques and provide a Yum plugin that
would suggest "Users of vim also installed: ctags, git, ..."
I am gonna create a Fedora Feature wiki page shortly describing this in
more detail. Our goal is to offer this project for integration into
Fedora later on, at least provide Fedora packages for it.
To do that, we need good source of data. It would be best to collect
access logs from one or two main Fedora mirrors. We would provide short
script in Python that would parse access logs and anonymize the data (IP
address hash-salted) and filtered only relevant data (RPM files from
latest Fedora release or updates repositories). That would be phase one
which should give us a sample data.
Phase two would be to integrate this script with logrotate and for one
Fedora release cycle (Fedora 19) the script would collect relevant
anonymized data into a file. Final suggested package database would be
created from this file (or maybe files to allow us to move them on the
fly out of the stat directory).
The big (legal) question is if we are able to provide this anonymized
data to public, or if we want to sign NDA with all people involved. I am
CCing Tom for this question.
I need your help with connecting to relevant people. Any comments are
appreciated.
Many thanks and I hope this effort will lead to improving user
experience with Fedora packaging.
--
Later,
Lukas "lzap" Zapletal
irc: lzap #theforeman

The infrastructure team will be having it's weekly meeting tomorrow,
2013-05-30 at 19: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 / discussion
#topic Upcoming Tasks/Items
https://apps.fedoraproject.org/calendar/list/infrastructure/
#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

I was asked (with my Red Hat hat on) to put together a little report on
areas in Fedora which could be improved with an investment in better
automation. From what I'm working on myself, I'm aware of the gigantic need
in the cloud images production process, and I've been keeping an eye on Tim
Flink's autoqa revamp ideas. I expect there are others, because I know from
my previous jobs that there's always a balance between building
condiment-passing machines and just _passing the salt_. [1] Are there other
things which could be made better if only someone came up with the spare
time and resources to do the work?
1. http://xkcd.com/974/
--
Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ <mattdm(a)fedoraproject.org>

Hello,
IRC handle: kc4zvw
I have been using Linux since Redhat 4 and am a contractor that does
Linux admin work for a large aerospace company.
Can write scripts in Bash, Python and Ruby.
Have installed a copy of Fedora 18 on a dedicated machine to learn and
work on embedded controller projects.
regards,
David
--
David Billsbrough (KC4ZVW) Chuluota, Florida Grid Loc: EL98kp
Web: http://www.kc4zvw.us --- Blog: http://kc4zvw.wordpress.com
AMSAT * AVR * FreeBSD * Linux * PICmicro * QRP * Raspi * TAPR

Greetings.
we are now in the infrastructure freeze leading up to the Fedora 19
Beta release. This is a pre-release freeze.
You can see a list of hosts that do not freeze by checking out the
ansible repo and running the freezelist script:
git clone http://infrastructure.fedoraproject.org/infra/ansible.git
scripts/freezelist -i inventory/inventory
Anything listed as freezes is frozen until 2013-05-28 (or later if Beta
slips). Frozen hosts should have no changes made to them without a
signoff on the change from at least 2 sysadmin-main or rel-eng members.
Thanks,
kevin

Hi all,
Yesterday I announced an idea that I've had of using datagrepper to
announce package ownership changes [1].
The feedback seem positive, so I change the script [2] to send the email
directly, so basically we can run it via a cron job easily.
Do we want to have this script as a cron job in the infrastructure?
All it needs to run is argparse and requests.
The following question is how often should the cron run, this is opened
for discussion.
Regards,
Pierre
[1] http://lists.fedoraproject.org/pipermail/devel/2013-May/182783.html

As I recall, one of the claimed advantages of using github over
fedorahosted is the ease with which people can submit code - the idea
being that new contributors are more likely to have a github account
than a FAS account.
I'm curious whether anyone has observed an uptick in external
contributions since the switch over to github, does anyone have any
numbers or opinions on that?
Tim

Please forgive me if this isn't the right format for this request; it's
been a long time since I've done one of these.
I need to push the following change to the review-stats code through
puppet:
diff --git a/modules/review-stats/files/review-stats.py b/modules/review-stats/files/review-stats.py
index 2c59752..e494168 100755
--- a/modules/review-stats/files/review-stats.py
+++ b/modules/review-stats/files/review-stats.py
@@ -205,7 +205,7 @@ def run_query(bz):
bugdata[bug.id]['hidden'] = 1
# Get the status of each "interesting" bug
- for i in seq_max_split(alldeps, 500):
+ for i in seq_max_split(alldeps, 100):
for bug in filter(None, bz._proxy.Bug.get_bugs({'ids':i, 'permissive': 1})['bugs']):
interesting[bug['id']] = bug
RHBugzilla is pretty broken right now, and I'm working on fixing this
code upstream in a better way which I will push once we unfreeze, but
this is the minimal fix that appears to at least get the script to
complete without throwing proxy errors. It takes ages to run but it
does eventually finish.
- J<

db01 is low on disk space again.
This is due to us keeping transaction logs for a long long time.
I would like to delete jan and feb transaction logs to free up space
for now. After the freeze, we should fix this with a proper tmpwatch
setup.
+1s?
kevin