18F / hub

DEPRECATED: Documentation hub for the 18F team
https://github.com/18F/handbook
Other
46 stars 33 forks source link

add 18f org chart to /hub #31

Open gbinal opened 9 years ago

gbinal commented 9 years ago

When it's at a good point for it, it'd be great to add to /hub.

@quepol - do you want to ping here when it's to that point? Alternatively, if you're game to post the remaining issues, @mbland or I can keep an eye and check in if it looks like they are addressed.

gbinal commented 9 years ago

Great idea I just heard - yes to posting the structure, but leave off names.

mbland commented 9 years ago

cc: @shawnbot @meiqimichelle

shawnbot commented 9 years ago

I'm a big fan of doing this as YAML data and HTML rather than an image or images. Can I get a what-what?

mbland commented 9 years ago

@shawnbot What are you thinking in terms of YAML implementation? I was thinking of adding title: and supervisor: attributes to items in team.yml, creating the graph that way.

shawnbot commented 9 years ago

@mbland that works for me, as long as we can iterate over those structures in a Liquid template.

meiqimichelle commented 9 years ago

Works for me! Is that you, @shawnbot , I hear volunteering to make said HTML template/static viz?

shawnbot commented 9 years ago

Yep, count me in! Now, where's the data?

meiqimichelle commented 9 years ago

@quepol @aaronsnow Is there an org structure -- divisions, titles, names -- that we can put on the private side of the hub for team reference? @shawnbot is volunteering to get it translated into beauty on the hub, but I'm not sure where the latest info is. Thx! (pinging @aaronsnow as well since I'm guessing HH is a little busy at home right now!)

aaronsnow commented 9 years ago

Yep, I'll email it.

On Tue, Feb 3, 2015 at 8:30 PM, Michelle Hertzfeld <notifications@github.com

wrote:

@quepol https://github.com/quepol @aaronsnow https://github.com/aaronsnow Is there an org structure -- divisions, titles, names -- that we can put on the private side of the hub for team reference? @shawnbot https://github.com/shawnbot is volunteering to get it translated into beauty on the hub, but I'm not sure where the latest info is. Thx! (pinging @aaronsnow https://github.com/aaronsnow as well since I'm guessing HH is a little busy at home right now!)

— Reply to this email directly or view it on GitHub https://github.com/18F/hub/issues/31#issuecomment-72773508.

Aaron Snow 18F https://18f.gsa.gov/ Deputy Executive Director Director of Client Services aaron.snow@gsa.gov

meiqimichelle commented 9 years ago

@shawnbot More info for the org chart yml:

I was asking about org codes and #teamops and...

office code translator. XFA = PIF, XFB = Operations (aka non-billable staff), XFB = billable staff. It's how your classified when hired. @mhz you're XFB. Fun part is this all may change as we re-org based off the new org-structure.

and

to give you more context there is a 'box' on the OCSIT org structure with Greg in it; that's XF. Branching off of that; XFA, XFB, XFC.

Recording here in case this will be incorporated into our org chart.

mbland commented 9 years ago

@meiqimichelle I take it it was supposed to read: XFC = billable staff?

meiqimichelle commented 9 years ago

Ha. I read too quickly, didn't see the double. No, I think the XFB is correct. Perhaps operations was meant to be XFC. I say this because looking in my email, the delivery folks all seem to have XFB.

mbland commented 9 years ago

109 underway.