Community Meeting (March 16) - Community Onboarding

Justin Obara obara.justin at
Mon Mar 21 12:47:40 UTC 2016

Hi Taliesin,

Thanks for your feedback, I left some comments below.


On March 20, 2016 at 1:50:00 PM, Taliesin Love Smith (ts14hh at wrote:

Hi Justin,
Great article about on-ramping. I agree the 6 steps look like a good recipe for getting people involved and helping them stay involved. 

Sorry I missed the Community Meeting on this topic.
Just wondering if the topic of on-ramping inclusive design students came up?
We sort of talked more generally about onboarding with some specifics about GSoC students. I don’t believe that the Inclusive design students came up as a specific point. If you have more thoughts on this, please feel free to let us know. 

I think the Community Meeting is such a valuable platform for making connections, especially in the first year of the program.

I've only come to a few meetings, but I've enjoyed them, and would like to join in more often.
Thanks, glad you’ve enjoyed them. Hope you can make it to more. They are open so feel free to come whenever you like. Also, it would be good to have the Inclusive Design students leading community meetings from time-to-time.

I like your idea of organizing all the intro documents, so it is more clear how to get involved.

Personally, I find the Fluid and Floe projects are quite big. A newcomer doesn't necessarily make all the connections. The projects are big enough that a person can get overwhelmed even at the Discovery step :-) Easing the process from Discovery to Setup Tools would be awesome!
I’m not sure if you saw the notes, but this seems to be a theme. It’s something we’d really like to address. We have some concrete first steps listed in the notes, but those probably won’t fully address the issue of “how do all the projects relate”. It’s something that we’re still working through and have had some ideas about.

It's kind of like basic accessibility. First you need access, then once you have some access you can start to figure how to engage and hopefully eventually contribute.
One of our former designers, James Yoon, once described the stages to me as functional -> usable -> desirable. 


On Fri, Mar 18, 2016 at 1:15 PM, Justin Obara <obara.justin at> wrote:
Github has posed a “Creating a new contributor on-ramp” blog post yesterday. The entire post is worth a read, and is likely things we have already discussed in our onboarding meeting and in discussion about our online presence. The thing that struck me the most was the six steps that a user usually takes when progressing into a project. Discover, Setup tools, Learn skills, Identify tasks, Get help, and Feel appreciated. These are all areas for which we have information, but as was mentioned in the meeting, they are not always easy to find. I really like the graphic they have in this post, and feel like we could make an awesome community portal along the lines of this, and etc.  


On March 10, 2016 at 12:51:44 PM, Justin Obara (obara.justin at wrote:

At the upcoming community meeting (March 16) we will have a discussion about how to facilitate onboarding into the community. Please come with examples, anecdotes, and etc of good practices for this that you have seen in other communities. Also think about your own experience joining the community or bringing others in, and reflect on what did and didn’t work.


fluid-work mailing list - fluid-work at
To unsubscribe, change settings or access archives,

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the fluid-work mailing list