Openstack has it's own CI system that is independent of travis, so I'm not sure the benefit of adding it into horizons repo. If u have a public fork what stops u from putting the file/s in that fork? Seems like u should be able to manipulate your fork however u want. Sent from my really tiny device... On Mar 12, 2014, at 5:09 AM, "Adam Nelson" <adam at kili.io<mailto:adam at kili.io>> wrote: I see that horizon doesn't use Travis CI Is that a political decision? If not, would there be resistance to adding a minimal .travis.yml file to horizon/master so that other people can use travis for their public horizon repos? Travis requires the file to exist on all branches for historical reasons. This wouldn't oblige the use of Travis but it would make it easier for me since we're actively developing on a public fork and use Travis. -Adam -- Kili - Cloud for Africa: kili.io<http://kili.io/> Musings: twitter.com/varud<https://twitter.com/varud> More Musings: varud.com<http://varud.com/> About Adam: www.linkedin.com/in/adamcnelson<https://www.linkedin.com/in/adamcnelson> _______________________________________________ OpenStack-dev mailing list OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140312/832d300f/attachment.html>