Infrastructure
This section contains the discussion happening on the fedora-infrastructure-list
http://fedoraproject.org/wiki/Infrastructure
Contributing Writer: HuzaifaSidhpurwala
static F10 Alpha relnotes page
Karsten Wade writes for fedora-infrastructure-list [1]
Karsten proposed that we turn [2] static. People should also be able to edit that page. Perhaps as part of making it static we can tell people to post changes to the talk page, then we'll do irregular updates of the static content?
[1] https://www.redhat.com/archives/fedora-infrastructure-list/2008-August/msg00013.html
[2] https://fedoraproject.org/wiki/Releases/10/Alpha/ReleaseNotes
Photo gallery
Nicu Buculei writes for fedora-infrastructure-list [3]
The Art team decided to start collecting photos which can be used as desktop wallpapers, make a best-of-breed selection and create one or more packages. The easiest way is to add all of them to the wiki. However Nicu proposed that we use a better solution, either a gallery plug-in for trac or a stand alone gallery or something like that.
[3] https://www.redhat.com/archives/fedora-infrastructure-list/2008-August/msg00028.html
FAS authentication for Red Hat bugzilla
Rahul Sundaram writes for fedora-infrastructure-list [4]
Rahul asked if configuring FAS Auth for Red Hat bugzilla was possible. At which Mike replies saying that it was not our call, and Red Hat will need to decide that.
[4] https://www.redhat.com/archives/fedora-infrastructure-list/2008-August/msg00039.html
RFC: script to run sqlalchemy migrations on the db
Toshio Kuratomi writes for fedora-infrastructure-list [5]
FAS started using the python-migrate package to update its db. This is a good thing for third-parties that want to install their own FAS server as it lets us ship the database changes in a way that is easy for those users to apply to their own production databases.
However, it doesn't work very well in our particular environment because we're a bit more strict about our permissions than the migrate authors envision. In order to perform migrations, you need to have a user that can modify the schema for the db. This is either the owner of the db or the superuser. In our setup, we create the db with the superuser and then run our web apps with another user. This prevents the normal web app from modifying the db schema. Toshio proposed a couple of solutions to this.
[5] https://www.redhat.com/archives/fedora-infrastructure-list/2008-August/msg00059.html