| I can do the former, but the latter needs to be done by a member of the | “ghc” on GitHub. I can do the latter (and keep managing the travis | instance) if someone adds me to the organization... Johachim, you contribute a lot, thank you. You should be a member of the group! Who decides that? I know about GHC committers...is that the same as the ghc group on Github. Anyway I support adding Joachim! Simon | -----Original Message----- | From: ghc-devs [mailto:ghc-devs-bounces@haskell.org] On Behalf Of | Joachim Breitner | Sent: 11 July 2014 11:36 | To: ghc-devs@haskell.org | Subject: Put GHC on travis for real | | Hi, | | with all packages as submodules, ghc-complete (which is basically a git | repository tracking the „fingerprint“ of the main repository) is | obsolete. So we could move the travis-checking of the main line to run | on the ghc repository directly. This would require | | * adding a .travis.yaml based on the contents of | https://github.com/nomeata/ghc-complete/blob/master/.travis.yml | and https://github.com/nomeata/ghc-complete/blob/master/validate.sh to | the repository. | * enabling Travis for this repository. | | I can do the former, but the latter needs to be done by a member of the | “ghc” on GitHub. I can do the latter (and keep managing the travis | instance) if someone adds me to the organization... | | Greetings, | Joachim | | | | -- | Joachim “nomeata” Breitner | mail@joachim-breitner.de • http://www.joachim-breitner.de/ | Jabber: nomeata@joachim-breitner.de • GPG-Key: 0xF0FBF51F | Debian Developer: nomeata@debian.org