Create an org chart

[iancrowther]

Should we create an Org chart?

For example:

• Who do I speak to regarding ti.to
• Who do I speak to regarding our email london@nodeschool.io

[max-mapper]

IMO we shouldn't have a shared ti.to or email because it makes it difficult to manage (because its all centralized). My opinion is I think it would be easier for everyone if chapters had their own tito and email.

However @brianloveswords controls the nodeschool.io DNS, and there are apparently 25 people on the /nodeschool ti.to account and it looks like if you get invited you can create events under /nodeschool

[iancrowther]

@brianloveswords - what are your thoughts on the admin?

[SomeoneWeird]

Yeah, I think separate ti.to accounts for chapters is probably a good idea, makes everything easier to manage because you don't have to wait for a person who has admin to do stuff.

[iancrowther]

so i agree on the ti.to front..

what about email?

[max-mapper]

I don't know an easy way to run email for a group. I've done Google Apps For Your Domain in the past but that requires a similar additional centralized management layer. If someone has an idea on how to set up nodeschool emails without a central bottleneck then that would solve it, otherwise I'm not sure how to make it maintainable

[martinheidegger]

Nodeschoolbot?

[brianloveswords]

@iancrowther @maxogden The main issue for me with Google Apps for us is scale. It costs $5/mo per email address. I'm fine to eat the cost for a few addresses, but if we're talking an email for every org, that becomes more problematic.

[RichardLitt]

We could host our own mail server, and not use Gmail at all. That should allow us to have somewhat limitless mailboxes, with aliases for each one; one per org shouldn't be a problem.

[mikeal]

You should do what Node.js is doing now.

https://github.com/nodejs/email

Basically, @rvagg wrote some code to configure mailgun and we point the DNS for email there. Then there's just a big json config in a repo that people can send pull requests to in order to get listed :)

[SomeoneWeird]

@brianloveswords Yeah, we really don't want to do that :) @RichardLitt highly advise against running our own mail server @mikeal that is v. cool :)

[brianloveswords]

Oh this is awesome @mikeal. I'm gonna try to set this up.

[brianloveswords]

Okay @iancrowther @maxogden I think nodeschool/email solves the email problem in a sufficiently decentralized way.

Steps to add an email address:

1. Requester submits a pull request that adds an alias to nodeschool/aliases.json
2. Everybody ensures pull request passes Travis (json linting).
3. Core team member merges pull request.

Anything that hits the master branch will be automatically deployed.

We can send 10,000 free emails on the mailgun free tier. I'll raise a new thread if we start getting close to that with legitimate use.

[SomeoneWeird]

I just enabled status check requirements for master on nodeschool/email - now travis has to pass, before you can merge stuff :)

[iancrowther]

@brianloveswords - feel free to delete london@nodeschool.io from google apps @mikeal - danke

[iancrowther]

lol - so back to the org chart?

I never actually got much insight into my original question. I think it would be useful

[max-mapper]

IMO ideally the org chart would be a small group of people (more than 1 to increase "hit by a bus factor", but small enough group to eliminate any bureaucracy, maybe 10?). The job of the small group of people would be to manage passwords and administrative duties that should hopefully be few and far between (like redeploying nodeschoolbot when it breaks).

The rest of the org chart would just be chapters :)

[iancrowther]

ah yeah, I have not thought to include the chapters. I think thats overkill and becomes a "thing" to admin.

what tasks do people oversea?

• email
• nodeschoolbot
• newsletter
• website ci
• tito (which I assume will just become a placeholder movinf forward)
• domain
• ...?

[RichardLitt]

Those sound about right to me. Can we start with those, and add to it as needed?

It doesn't seem like there is a burning need for an org chart, @iancrowther. Unless I am missing something, as this ticket is a bit stale.

[SomeoneWeird]

I don't see this as a pressing need.