Contact Info

[Jonskichov]

A thought: we should have a "do you want to be involved? Contact us!" link. We (or others with appropriate admin rights) don't have a means for randoms to join up.

Can GitHub do this?

Should we offer an email address?

Should we let those who want to join in create a GitHub account and create an Issue (that requests membership)?

Etc :)

How should this work?

[amis92]

Now I'm writing tutorial it hit me too. If someone wants to be admin/dev, how should he ask for permission.

I think creating Issue is enough. Any non-member can comment on issue. Then we can add him, knowing his GitHub nickname.

Thing is, do we add everyone who asks? (I think yes, we need it as easy to get involved for people as possible)

E-mail would be hard to maintain (who has access to it, password etc. leaving it to one person isn't best practice for open-source like this).

I thought about Google+ Group we already have, but that's only for people with Google account. And if one wants to be admin/dev here, one has to create GitHub account anyway.

[dattanchu]

Can't you log into github with a Google+ account?
On Mar 23, 2014 6:57 AM, "Amadeusz Sadowski" notifications@github.com
wrote:

Now I'm writing tutorial it hit me too. If someone wants to be admin/dev,
how should he ask for permission.

I think creating Issue is enough. Any non-member can comment on issue.
Then we can add him, knowing his GitHub nickname.

Thing is, do we add everyone who asks? (I think yes, we need it as easy to
get involved for people as possible)

E-mail would be hard to maintain (who has access to it, password etc.
leaving it to one person isn't best practice for open-source like this).

I thought about Google+ Group we already have, but that's only for people
with Google account. And if one wants to be admin/dev here, one has to
create GitHub account anyway.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/22#issuecomment-38380406
.

[amis92]

Nay. Surely not.

[Jonskichov]

Well remember that people can fork/pull request, so most people don't need to be admins.

We shouldn't have a billion admins deciding what to accept and when to release. It'd be a mess... Depending on how active the admins are and how busy the particular repo is, we'd probably only need a couple of admins per repo. The current admins for a repo could decide if they want to add someone

I'm more concerned with someone coming along with some new game system that they want to host with us. We need to create a repo, admin group for it blah blah. Where do they contact us?

That said I'm sporadically reaching out to people atm to get them on board, so I suspect we'll have a decent base of repos with admins soon enough. Then we can leave it up to them to accept additional admins :)

[amis92]

Well personally I think it'll be easier for everyone if developers/maintainers (who "often" visit us here) are part of organisation, even just in a single team for single repo.

Because forking/pull requesting is a tad bit more complicated than doing it as a member. Bear in mind I feel most people should be just devs (push+pull), and only few would be admins(push, pull, pull requests, dev team management). With that in mind, I created the wiki - for devs. Additional pages will be for admins.

[Jonskichov]

@amis92 Agreed - I've closed this one in favour of: #21