Maintainers?

[alrra]

Although, I'm not found of the idea of just adding people to the repository in the hope that things will get done, I think it would be nice (and speed the development a little bit) if this repository had at least one maintainer for every server config.

Right now, we do not have anyone for:

• gae
• iis (@ChrisMcKee offered)
• lighttpd

Other proposals:

• nginx (@aitte ?)

Any thoughts / proposals ?

Cc: @h5bp/server-configs, @AD7six, @necolas @paulirish @xonecas

[necolas]

Added @ChrisMcKee. I think he messaged me or someone or Twitter about IIS? Dunno, it got lost in the noise and I couldn't find where I read the request.

[ChrisMcKee]

Ha! thanks. To celebrate I've closed the issues I resolved over a year ago.

Enjoy the rest of your easter :)

Tara

[necolas]

Let's leave this open for a bit, to find out if there are other people we should add.

[necolas]

Perhaps @aitte - seems to have helped a lot recently with nginx.

[AD7six]

I thought I was supposed to be the nginx maintainer =) - Though I'm not as active as I should be and have no problem yielding to someone else.

I don't think there's anything wrong with being more liberal with commit access (and revoking when necessary) if there's a clear understanding of what's expected. My constant concern has simply been the risk of each server config diverging into an inconsistent, mess of features. Along the same lines, this post gives an interesting perspective on how inviting pull-requesters to take responsibility for a code base can work out pretty well, and be self-managing to boot.

[alrra]

I thought I was supposed to be the nginx maintainer

@AD7six oops, sorry about that, I've updated the info after @necolas's comment and I forgot about the do not have anyone part.

[necolas]

I thought I was supposed to be the nginx maintainer =)

Doesn't have to be just one person if it would help to have others. Your call.

My constant concern has simply been the risk of each server config diverging into an inconsistent, mess of features.

Yep. I think there was some past talk about a common spec or something to avoid such a problem.

[ChrisMcKee]

It would be handy if the spec made it clear which bits were mandatory as there will be some things that aren't best practice within .net (joys of the stack) and would ideally sit within the wiki & markdown file.

[alrra]

It would be handy if the spec made it clear which bits were mandatory

@ChrisMcKee I'll try to come with some proposals in about 2 weeks (sorry for the delayed answer, I'm quite busy at the moment).

Closing this issue for now.