Hi, Am Dienstag, den 15.07.2014, 08:38 +0000 schrieb Simon Peyton Jones: > This is all fantastic, thank you Joachim. But how would a new GHC dev > find out this information? Could it please be documented on the wiki?
Yes, I plan to do it once it settles, there are still a view things to observe and to decide. (E.g. we’d like to make travis send mails about breakage to the commiter directly, but for that it needs to be more reliable). With other projects in the pipeline, I want to add a new wiki page, linked from the sidebar https://ghc.haskell.org/trac/ghc/wiki/Infrastructure that gives an overview of all tools that a developer should at least know that they exist. It will mostly link to the corresponding wiki page, and possibly list a responsible person. This will include: * git repository * trac itself (wiki + issue tracker) * mailing lists (note the s! – I didn’t know about ghc-builds for a long time) * Phab * Builders * Travis * The yet to announce performance dashboard It could also host links to external tools such as https://www.ohloh.net/p/ghc Anyways, please keep bleating about such things! Greetings, Joachim -- Joachim “nomeata” Breitner [email protected] • http://www.joachim-breitner.de/ Jabber: [email protected] • GPG-Key: 0xF0FBF51F Debian Developer: [email protected]
signature.asc
Description: This is a digitally signed message part
_______________________________________________ ghc-devs mailing list [email protected] http://www.haskell.org/mailman/listinfo/ghc-devs
