Committer list [was: Re: NOTICE: Gitolite migration is complete.]

[Austin Seipp]

Sounds good to me. I've found the same info useful. In fact, just
yesterday I had added the list of committers I assembled to the
Contributors page:

http://ghc.haskell.org/trac/ghc/wiki/Contributors

I've gone ahead and created a Committers page with more info. It also
lets people know who to contact (me) if they would like access, and
should help people find out who to talk to when they need help.

http://ghc.haskell.org/trac/ghc/wiki/Committers

I went ahead and filled out most of the details on the people I'm
aware of, except for email. I'm not sure what you'd like to publicly
put out there on Trac.

Developers - If you'd like, please take the time to fill in your email
and amend anything I got wrong (e.g. I just put pretty much everyone's
"committer date" as this month.)

(Also, forgive me for looking into most peoples affiliations and
listing them here, but it does help individual identification - and
it's a decently diverse set of places, which is neat in its own
right!)

On Fri, Aug 16, 2013 at 5:54 AM, Simon Peyton-Jones
<simonpj at microsoft.com> wrote:
>
> Herbert, Austin, Simon
>
> Thanks for taking charge of our git repos.  Very very helpful!
>
> On the question of committers, there's always the danger that we give people commit permission, and several years later they've gone silent and we can barely remember who or why.  I wonder if we should have a "Committers" wiki page, with a bullet for each person in this format:
>
> * Simon Peyton Jones, Microsoft Research, Cambridge, UK.  Trac: simonpj; email: simonpj at microsoft.com.  Added as a committer June 2013.  Main areas of interest: renamer, type checker, optimiser.
>
> I often have trouble connecting people's Trac identity with their email; and it's quite helpful to know which country people are in and where they work.
>
> Do you think that would make sense?  We could also establish the convention that if you don’t commit for a year you'll lose commit access; though it can be re-activated on request.
>
> Simon
>
> | -----Original Message-----
> | From: ghc-devs [mailto:ghc-devs-bounces at haskell.org] On Behalf Of Austin
> | Seipp
> | Sent: 09 August 2013 23:20
> | To: ghc-devs at haskell.org
> | Subject: NOTICE: Gitolite migration is complete.
> |
> | All,
> |
> | Push access is now restored and Gitolite is in place! This brings some
> | nice updates:
> |
> |  * There's now access to the 'git' protocol for cloning anonymously.
> | This lets you clone even the biggest repos extremely quickly, and is
> | the fastest method for getting a copy of the tree.
> |  * Firewalled? Cloning over HTTP now uses Smart HTTP support for Git,
> | meaning it should be faster too!
> |  * We will soon have Gitweb available, once our git.haskell.org CNAME
> | is in place. Eventually we'd like something akin to
> | https://git.kernel.org/cgit/ possibly.
> |  * None of you have shell access to ghc.haskell.org anymore (well,
> | this is a nice update for us administrators :)
> |
> | The following people have had their keys re-added, and should be able
> | to push and pull from the new setup.
> |
> |  * Andreas Voellmy
> |  * Austin Seipp
> |  * Ben Lippmeier
> |  * Iavor Diatchki
> |  * David Terei
> |  * David Waern
> |  * Dimitrios Vytiniotis
> |  * Duncan Coutts
> |  * Edsko de Vries
> |  * Erik de Castro Lopo
> |  * Edward Yang
> |  * Geoffrey Mainland
> |  * Gabor Greif
> |  * Herbert Valerio Riedel
> |  * Ian Lynagh
> |  * Ilya Sergey
> |  * Johan Tibell
> |  * José Pedro Magalhães
> |  * Jan Stolarek
> |  * Manuel Chakravarty
> |  * Max Bolingbroke
> |  * Nicholas Frisby
> |  * Paolo Capriotti
> |  * Richard Eisenberg
> |  * Roman Leshchinskiy
> |  * Ross Patterson
> |  * Simon Hengel
> |  * Simon Marlow
> |  * Simon Peyton Jones
> |  * Thomas Schilling
> |
> | The following people still have shell access for any administrative
> | needs:
> |
> |  * Austin Seipp (and the remaining haskell.org infrastructure team.)
> |  * Herbert Valerio Riedel
> |  * Ian Lynagh
> |
> | I have undoubtedly missed some people. Please talk to me and we'll get
> | you set up!
> |
> | If you're a developer, please read about developer changes here:
> |
> |  * http://ghc.haskell.org/trac/ghc/wiki/GitolitePlan#Developerchanges
> |
> | TL;DR: if you have an old tree, run the following four commands from
> | the root to fix the push/pull URLs.
> |
> | $ git checkout master
> | $ git pull https://github.com/ghc/ghc.git master
> | $ ./sync-all -r ssh://git@ghc.haskell.org remote set-url origin
> | $ ./sync-all -r ssh://git@ghc.haskell.org remote set-url --push origin
> |
> | The reason you must get the latest-copy of ./sync-all is because
> | Herbert made some last minute bug fixes. Technically, you could just
> | download the latest copy and run it directly, but this is easier and
> | fairly straight forward.
> |
> | Please direct any concerns to me, like if you need something off the
> | server, need your shell account back, or need commit access. Over the
> | next few days, I'll be cleaning up the wiki - updating references and
> | guides on how to check out the source for users and developer. I also
> | might be sending out some emails with questions while we refine the
> | new setup in the next few days (there were some Trac integration
> | changes.)
> |
> | Also, a gigantic applause for Herbert, who did a lot of the work here!
> |
> | --
> | Regards,
> | Austin - PGP: 4096R/0x91384671
> |
> | _______________________________________________
> | ghc-devs mailing list
> | ghc-devs at haskell.org
> | http://www.haskell.org/mailman/listinfo/ghc-devs




-- 
Regards,
Austin - PGP: 4096R/0x91384671