Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Members directory #137

Closed
maddhruv opened this issue May 17, 2018 · 9 comments
Closed

Members directory #137

maddhruv opened this issue May 17, 2018 · 9 comments

Comments

@maddhruv
Copy link
Contributor

What?

  • Building a members directory of all the current NF members that shall contain - team they are members of, contact info, employee/student at, he/she, member since, etc

Why?

  • Help find members/team contacts, info and other details
  • NF can have a centralized place to find people/members

How?

  • A simple markdown table

Who will do it?

  • Self made PRs adding their own details

Where?

  • Inside members repo, so that everyone inside the org will have access to the same and not publicly available
  • DIRECTORY.md
@Trott
Copy link
Member

Trott commented May 17, 2018

Who will do it?

  • Self made PRs adding their own details

If this can't be automated, it's likely to be little more than an exercise in herding cats. (I won't stop you or anyone else from trying. Happy to be proven wrong.)

@WaleedAshraf
Copy link
Contributor

WaleedAshraf commented May 17, 2018

Related issue: nodejs - members directory
Node.js People Everywhere (npe)

@maddhruv I believe this can be very helpful. But as @Trott said, the process should be either automated or very easy (just filling a simple google form) to carry in long term. I'm available if any kind of help is needed for this task.

@maddhruv
Copy link
Contributor Author

A Google form or typeform can be done, else I don't find a better automated way of doing it

@Trott can you tell me some of the details I should ask from the members other than:

  • Name
  • Email
  • GitHub handle
  • Twitter handle
  • LinkedIn handle
  • Employment/University
  • member since
  • teams
  • he/she
  • current address(timezones)

@Trott
Copy link
Member

Trott commented May 18, 2018

@maddhruv I would ask for as little information as you can while still making the thing useful. The more information you ask for, the less likely people are to finish filling out a form. "Member since" seems gratuitous and also suggests that the longer you've been a member, the more credibility you have. I would discourage listing that if it's not necessary for some purpose.

I wouldn't be surprised if @nodejs/automation could come up with a way of pulling out all the GitHub handles for people in the nodejs/members group and some basic information about them.

Since this is a private directory for just nodejs/members, then I wonder if https://github.com/orgs/nodejs/teams/members is sufficient, or at least gets us most of the way there. I'm not sure what non-Owners of the org see when they go to https://github.com/orgs/nodejs/teams/members/members?utf8=%E2%9C%93&query=+membership%3Achild-team, but if members can see all the other members there, that might be a decent start. It will likely never contain pronouns (although people can list them in their own GitHub profiles which people can click through to). And I don't know if people who aren't Owners can see what teams I'm on by going to https://github.com/orgs/nodejs/teams?query=%40Trott. But if they can, that's a good start too.

Aside: It's probably best to call it "pronouns" rather than listing pronoun choice as "he/she" as some people may prefer "they" or other non-binary options.

@richardlau
Copy link
Member

Bear in mind that even if it's automated you need to get consent as this is personally identifiable information. This is especially true for members who are EU citizens in light of the GPDR compliance deadline one week from today.

@richardlau
Copy link
Member

And I don't know if people who aren't Owners can see what teams I'm on by going to https://github.com/orgs/nodejs/teams?query=%40Trott. But if they can, that's a good start too.

I see ten teams at that link.

@Tiriel
Copy link
Contributor

Tiriel commented May 18, 2018

As @WaleedAshraf pointed, some related issues have already emerged from time to time.

I'd be all in favour of such a directory/listing, but I fear it is doomed to fall out of sync. Although the information you want to put in the listing seems pretty stable in time, I think most people will forget to update their information when they change (including myself).

But like others, I would definitely like to see a try anyway!

@joyeecheung
Copy link
Member

You could probably already list all the emails, names and GitHub handles in a markdown using ncu-team but to be honest I think if someone wants to get that information, they can already do that with GitHub GUI by looking up the teams. It feels weird to me to get my personal information listed like that.

@Trott
Copy link
Member

Trott commented Jul 5, 2019

Closing stuff that has been inactive for more than a year in this repo, but if someone plans on picking this up, just go ahead and re-open! No strong opinions from me. Just tidying.

@Trott Trott closed this as completed Jul 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants