On Wed, 8 Jan 2014 19:10:43 +0100 Pierre-Yves Chibon <pingou@xxxxxxxxxxxx> wrote: > Here is my list (in no particular order): > > * FAS3 > - We need to port FAS to a new(er) framework > - Move the user auth completely out of FAS? How would that work? ...snip all good stuff... > * Review-server > - 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: > https://fedoraproject.org/wiki/User:Mmaslano/Draft:Env_and_Stack_PRD#Automation > - We may want to see with tflink and the QA if there are tools in > addition to fedora-review that could be included Interesting idea. Note that we also need to keep a record of all the work done there. By that I mean I often go back and look at a package review to see if something was missed or addressed or noted. We would need to make sure people could go back and look at the history easily. > * Elections > - 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 a plugin > => I have no real idea yet on how to do so, I just think it would > be nice to have it :) > * MirrorManager > - 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 framework, unit-tests...) > * Auto-rebuild > - 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?). This could tie in with the taskotron efforts I would think. > * 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 Not at all easy to do, but yeah... Speaking of auto rebuilding... * autorebuild infra instances In particular buildvm's would be nice to reap and rebuild automatically, but this could extend to other things. Just take out of production, rebuild and readd. > 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 :) Good stuff. ;) kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/infrastructure
