As suggested on Trac, here is a thread letting us discuss more
about this idea.
* People send reminder manually, sometimes late, sometimes wrong
* People forget sometimes to send the reminder.
* Many teams are doing that.
* It takes time.
* Sender need to subscribe to mailing lists
* If there is a new wiki page for each meeting (agenda), we can't find
the last one easily!
Letting teams registering events on a cron will improve that.
We could use the meeting page (which would need to be updated!) to
get the meeting info.
* Meeting time
* How far should the reminder be sent (in days?)
* Meeting frequency, schedule
* To which list the reminder should be sent
* Static link to meeting details.
For example (as we already do in the French team):
This mail is a reminder for today's meeting for the French speaking community.
2011-11-28 / 18:30 UTC
The agenda is located at:
As kevin said, including the time could be wrong because of daylight
Hence the static meeting page is really important.
Lots of meeting follow a generic agenda, there is no need to create a
new page each time (take a look at ), the wiki history keep the old
meeting agenda for us. Therefor the meeting agenda should also be
included in the static meeting page.
Of course, if this is implemented, all teams (amba, infra, docs…)
should use it, else this is not really useful.
What do you think?
At the moment while checking if a password is valid FAS does not check
how many characters are present.
Thus it allows things like: "aaaaaaaaaaaaaaaaaaaa" as password.
One solution is of course checking how many different characters are
present in the password and I have a quick patch which does that.
However while discussing about this with Kevin and Toshio on IRC we did
not find what would be an optimal number of character different in the
password which would be:
- high enough to make the password strong(er)
- low enough so that in case of brute force the number of possibilities
for each character added remain high.
So, do you have an opinion on the minimal amount of different characters
a password should have ?
The infrastructure team will be having it's weekly meeting tomorrow
2011-12:01 at 1900 UTC in #fedora-meeting on the freenode network.
Suggested topics (suggested by whom):
* New folks introductions and Apprentice tasks.
* Password / ssh key reset status and retrospective.
* serverbeach / collab / hosted status
* ibiblio machines status
* Upcoming Tasks/Items
2011-12-01 Flag day for password reset/new ssh keys.
2011-12-01 nag fi-apprentice folks for december
2011-12-08 - Fedora 14 end of life.
2011-12-23 to 2012-01-02 - rh shutdown week.
2012-01-13 to 2012-01-15 - FUDCON blacksberg
2012-02-14 to 2012-02-28 - F17 Alpha Freeze
* Meeting tagged tickets:
* Open Floor
Submit your agenda items, as tickets in the trac instance and send a
note replying to this thread.
More info here:
My name is Jacinto Batoon or jac1bat0 at freenode. I've been working on a
degree in Network Systems Administration which got me interested in Linux.
I'm quite comfortable writing bash scripts as well as python. Right now,
I'm learning to use puppet and nagios to administer and monitor a network
of virtual hosts running on my server. It's a very limited setup and I'm
looking forward to discovering how these tools are used in a real world
With the work recently done on fedora-review , I started to wonder if
it would be interesting to work on an app dedicated to review RPM
package for Fedora.
I got myself day dreaming about:
- One goes to this new website
- Login using FAS credential
- Click on the "create new review"
- Provide name/summary/source rpm
- Upload source rpm (check that it is a source rpm)
- The ticket gets created
- Unpack the source rpm
- Put the tarball/zip into the dedicated directory
- Create a Git repo
- Add all the other files from the source rpm into the git repository
- fedora-review runs against this new package.
- Reporter adapts his spec file in the git repo
- fedora-review runs for each new version and print out the changes (?
- Reviewer works from the git
- Reviewer declares the review:
- git gets move and rename to become the official git repository
- invalid (for license/bundled lib...)
- git get removed from the filesystem
- close (stalled reporter/any other reason)
- git get removed from the filesystem
I was wondering if it could rely on a similar infrastructure than what
we are using via fedpkg/pyrpkg (a reviewpkg ?).
I was curious if that would be interesting and since an example is worth
many words, I tried to work on a small proof of concept . The
README.txt contains the information on how to set it up for testing.
It needs still a lot of changes:
- All parts regarding the review itself (changing the status, adding one
in cc, mail comments added...) is to be done
- The design needs to be done (this has to be done, what's there atm is
just good enough for testing :-))
but as I said, it's more a PoC for the moment to collect
I am starting the conversation here on the infra list to get the first
reactions, it'll be opened to the devel list later on if worth it.
So please shoot :-)
Just to bring folks up to date with the current status of our migration
of collab and hosted machines to new hardware:
Last week serverbeach10 died. It was the host that was running the
hosted03 test instance. (So, if you have been wondering why you
have not be able to get to it, thats why). In the process of them
looking at it, it was found that the hardware was end of life and
they didn't have any spares/replacements.
After discussions, the miscommunication was cleared up and they are
going to re-replace our new serverbeach machines with supported/newer
So, those new machines should hopefully be provisioned this week, and
serverbeach06-10 will go away.
Of course this throws a wrench into our timeframe for migrating things,
as we are set back waiting for new machines and re-provisioning them
and then may run into holidays. ;)
I'll update our timetable as soon as I know more about the new
machines. Possibly we can get in some of the migration before holidays,
On the plus side the RHEL6 test instance for hosted was looking pretty
ok from all the testing feedback I got, so I think we are good to
migrate over to 6 on it in any case.
I'm planning on attending FUDCon Blacksburg  towards the end of
January. I see Kevin and Toshio already listed a few FI hackfests.
I added a MirrorManager hackfest, and am curious if anyone else will
be there to join. My goal is to get the TG2 transition complete so we
can start moving forward on new MM features on the TG2 base.
Dell | Office of the CTO
As we recently announced, we are working on migrating fedorahosted.org
over to a newer instance or instances. We announced and held a activity
Which resulted in the following plans:
Per those plans, we have setup a RHEL6 test instance of
fedorahosted.org and would like to ask people to test against it for
issues or problems.
How to test:
edit your local /etc/hosts file and add:
Then your requests will go against the new instance.
Simply use trac, your scm and anything else as normal and note any
issues or problems. The only thing that is disabled on this test
instance is email. Please note any changes you make will be LOST. This
instance is just for testing and will be resynced to real content from
time to time.
If you could collect results and mail them to this list
(infrastructure) that would be best for now.
Please do remember to remove the /etc/hosts entry when you are going to
go back to the live/production instance.
If we don't see any nasty issues by monday, I will announce more widely
for more testing. Then, hopefully by next wed we can decide if moving
to rhel6 is going to be easy/feasable in the time we have.
Thanks in advance for any testing.
On Fri, Nov 18, 2011 at 5:56 AM, Richard E. van der Luit
> Hi all,
> i can not select dutch as locale for FAS (left at website), though
> translating it in Transifex.
> Anyway to fix this?
Hi, the FAS is an infra web app.
It was planned to be updated yesterday…
@infra do dutch was added? Do the FAS as already been updated?