Skip to content
This repository has been archived by the owner on Nov 5, 2019. It is now read-only.

Create and document an onboarding resource #13

Open
patcon opened this issue Jul 11, 2017 · 9 comments
Open

Create and document an onboarding resource #13

patcon opened this issue Jul 11, 2017 · 9 comments

Comments

@patcon
Copy link
Member

patcon commented Jul 11, 2017

Intending to adapt from this: https://trello.com/b/FCGGEaQq/edgi-web-monitoring-project-onboarding

Related: #9

@patcon patcon self-assigned this Jul 11, 2017
@b5
Copy link
Member

b5 commented Jul 12, 2017

Thanks for getting the jump on this @patcon! First & foremost, I think it's worth scoping which audience we're talking about onboarding here, and correct me if I'm wrong, but this would be for on boarding dev-contributors, correct? The other onboarding would be users, who may or may not be comand-line-inclined, and I think we could set aside as a separate set of documents to be worked into the platform itself.

To get things rolling, I think there are a few tasks that would help in the trello-for-datatogether:

  • Update the list of services document in this repo. I've updated the diagram in this repo, but the services list is out of date. If someone could PR this repo with an update to that list, I'd be grateful. The services in the diagram that are translucent are "planned" (meaning they haven't hit production yet). Details about each service should be at least remotely listed in each repo on datatogether.
  • Create a "Language guide": Currently we have great projects for Go, Javascript & Python devs, it'd be great to have a "I program this language, where should I start?". I think that'd be a huge addition to the trello board for this project.
  • Do some Quality Assurance for setup instructions for each service
  • Open issues on this repo for:
    • Picking a GitHub issue labelling strategy
    • Improving readme's across the board to match the quality of @mhucka's (research repo)[https://github.com/datatogether/research]
    • Getting our roadmap into place & establishing conventions.
    • Picking between this GitHub project & Waffle.io for current work overviews. ( @flyingzumwalt is a fan of waffle.io, and apparently people outside the datatogether org can't see the project!?)

@b5
Copy link
Member

b5 commented Jul 12, 2017

Quick update to make things easier: I've gone through all of the repos on the @datatogether and added topics for all of them, making sorting a little easier:

@patcon
Copy link
Member Author

patcon commented Jul 12, 2017

this would be for on boarding dev-contributors, correct?

👍

@patcon
Copy link
Member Author

patcon commented Jul 12, 2017

Created DataTogether trello org, and properly permissioned template board:
https://trello.com/b/ET8wNxE9/datatogether-dev-onboarding

I'll start copying cards later

@b5 I've sent you a trello invite on the org, and will admin you after

@patcon
Copy link
Member Author

patcon commented Jul 12, 2017

Really love the idea of language guides as something to make that bit immediately legible to newcomers!

@patcon
Copy link
Member Author

patcon commented Jul 12, 2017

fwiw, can search by lang without manually tagging :) (though perhaps this might fail in some edge-cases)
https://github.com/search?utf8=%E2%9C%93&q=language%3Apython+org%3Adatatogether&type=

@patcon
Copy link
Member Author

patcon commented Jul 12, 2017

The access doc seems important to let people know which services and tools we use to glue this community together. Thoughts on breezing by that in this onboarding?

@dcwalk
Copy link
Member

dcwalk commented Feb 15, 2018

Can we revisit this? Do we want to focus on developing an onboarding resource for DT potential devs? It seems like there will be a more general orientation/onboarding about the project as well. I'd argue that is different and I'm not sure whether trello is the best implementation.

@dcwalk
Copy link
Member

dcwalk commented Feb 16, 2018

ping @patcon :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants