On Thu, Dec 19, 2013 at 02:16:31PM -0700, Kevin Fenzi wrote:
I meant to send this out sooner, but with the Fedora 20 release things
have been crazy. :) Now that we are nearing the end of 2013, I think it
might be a nice time to think ahead to next year.
What would you love to see happen? What would you like to work on
(even if it's not practical resource wise or logistically)
Here's a list of some of mine:
* 0 downtime upgrades. By this I mean we can update and reboot all our
servers (probibly in some specific order with specific actions
between) and not have to schedule any downtime or notify users
anything is going on. This means at least that we have db
replication/failover working and 2 of everything.
* Migration to ansible fully done, with all hosts moved over and
rebuilt and working.
* Migration to RHEL7. :)
* Ticket queue down to a very small set. When I first started it was
gigantic, then I closed/fixed/redirected a lot of the ticket and we
started going down in number, but over the last year or so we have
hovered between 140-150.
* Migration to hyperkitty/mailman3 complete with all lists moved.
* All hosts selinux enforcing. :)
* No "app" servers left. All applications split out to their own (at
least pair) of instances.
* Logging from every app/server goes to a known place and we process
them all looking for problems.
Here is my list (in no particular order):
- We need to port FAS to a new(er) framework
- Move the user auth completely out of FAS?
- Integrate w/ announces -> new election, new deadline...
* Develop a 0Auth server?
- A number of changes and enhancements are required and I started a little
bit on this already :)
- We are already close, but we need to push it to production
and fix the bugs that will be encountered
* Port our webapp to 2FA
- Toshio started some work on this but we need to continue it
- This makes our product so much more robust that we really
should keep writing them
* Fedmsg-Notifications (FMN)
- Already quite advanced, we need to push it to production and
add new notification options.
* Cnucnu web
- Basis is there but it would be nice to add to the database more
mapping of the project in more linux distribution than just Fedora
- Kick the package review-request out of bugzilla
- Tight(er) integration with koji
- Run fedora-review on each changes
- Run scratch build on each changes
- Provide a temporary git repo for each review that could then be
merged into the official git repo after the review
- This seems to interest the dev and stack group, see third point at:
- We may want to see with tflink and the QA if there are tools in addition to
fedora-review that could be included
- It would be nice to re-work the election application to build in some
sort of plugin systems allowing different votes
- Eventually it would be very nice to merge nuancier into election as
=> I have no real idea yet on how to do so, I just think it would be nice
to have it :)
- With FAS it is probably the oldest application that we have that does not
have a new version coming. We need to update it (new db scheme (?), new
- Using fedmsg or koji directly we are able to retrieve the date of the last
successful build of any packages in our collections. This way we could trigger
an automatic rebuild to check FTBFS of every package every X time (6 month?).
* Auto-rebuild of broken deps
- When we detect a broken deps we should try to rebuild all the dependency and
propose the change to the packager if the build succeeded
Some of these are duable, other are more in the range of thinking out loudly but
all in all, this is what I have in mind for 2014 at the moment :)