[OSCTC-planning] framing our tutorials

[Shauna Gordon-McKeon]

Thanks for the kind words, Mel and Carol -- we do try hard to be open and
to be effective, so it's nice to see that resonating.  :)

Mel, I 100% agree with this:

"Strong support for this, and for the general concept of providing
(optional) "default values" as scaffolding -- recommended projects,
channels, etc. As more experienced FOSSers, we often think "yay,
openendedness is freedom!!!," but to a novice, it looks like jumbled
complexity they don't yet know how to navigate -- and so giving them
concrete pathways can help them learn faster"

I've seen this come up over and over again in open, anarchist or
consensus-based communities.  Freedom can actually be a burden!  Luckily
this is easy for us to provide - we have a number of open source projects
we work with and that we recommend, which we can provide as default values
for the Finding a Project activity.

- Shauna


On Wed, Jul 30, 2014 at 6:37 PM, Carol Willing <
willingc at willingconsulting.com> wrote:

>  Mel makes some excellent points on optional pathways as starting points
> for learning and exploration.
>
> I also think that Shauna and the OpenHatch team do an excellent job of
> modeling what a "healthy" community and learning environment can look like.
> I also think that OpenHatch does a great job of considering the end users'
> needs and differences, listening and responding to feedback, and
> thoughtfully guiding what approach makes sense based on external
> constraints (time, volunteers, attendee background, etc.).
>
> :-)
>
> Carol
>
>
>
>
> On 7/30/14, 1:52 PM, Mallory Lim Chua wrote:
>
>  It might make sense when actually running the activity, to pick
> one or more projects to use as an example.
>
>  Strong support for this, and for the general concept of providing (optional) "default values" as scaffolding -- recommended projects, channels, etc. As more experienced FOSSers, we often think "yay, openendedness is freedom!!!," but to a novice, it looks like jumbled complexity they don't yet know how to navigate -- and so giving them concrete pathways can help them learn faster. It's like the equivalent of pair-programming with a more experienced contributor; by being steered down *a* right path, you learn what "right paths" *can* look like, which makes it easier to construct your own in the future. And of course, people experienced enough to hop off the path and bushwhack on their own can do so. (Edu research basis: http://en.wikipedia.org/wiki/Dreyfus_model_of_skill_acquisition)
>
> The key to avoiding pedagogical hypocrisy (a "closed source" approach to teaching "open source") is to make it clear that these pathways are optional, that they've been semi-arbitrarily constructed by mere mortals as a starting point (as opposed to being Unmodifiable Platonic Ideals Descended from the Heavens), and give (also optional) access to some way for interested people to dig into the processes by which they are made (the curricular equivalent of "view source"). This is sort of like providing... packages -- rpms, debs, etc -- that make default setup really easy for novices, but fine-tuneable for more experienced people.
>
> That having been said, I think OpenHatch is doing an awesome job of applying "The Open Source Way" to the process of developing/teaching pedagogical materials -- pedagogical authenticity is strong with this group. :D
>
> --Mel
> _______________________________________________
> OSCTC-planning mailing listOSCTC-planning at lists.openhatch.orghttp://lists.openhatch.org/mailman/listinfo/osctc-planning
>
>
>
> --
>  *Carol Willing*
> Developer | Willing Consulting
> +1 760 456 9366 | https://willingconsulting.com
>
> _______________________________________________
> OSCTC-planning mailing list
> OSCTC-planning at lists.openhatch.org
> http://lists.openhatch.org/mailman/listinfo/osctc-planning
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openhatch.org/pipermail/osctc-planning/attachments/20140730/69563023/attachment-0001.html>