- Nick Yeates Open Source Strategist http://community.redhat.com +1 301-219-6149
> On Apr 6, 2015, at 5:39 PM, Karsten Wade <[email protected]> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > >> On 04/06/2015 12:51 PM, Nick Yeates wrote: >> Jim, Karsten, >> >> We have been working on a new version of this content with a >> slightly different approach. See building blocks of it here: >> https://github.com/nyeates/os-curriculum >> >> Make sure to read the README. This is more about teaching >> professors how to teach or include open source. We will curate >> links and metadata instead of actual content. It will house example >> lessons, projects and rubrics, which is what we have seen teachers >> need. > > Right, the POSSE textbook was an in-time response of a not-quite > different angle of intention, but providing the material we weren't > seeing available under an open content license at that time. > >> Jim, two things: 1) Do you want to take part in our small >> expert-feedback panel (7 prof’s for now) - directional feedback for >> now, not specific 2) Where would you ideally like to go from here: >> a) to give us the content updates that you do have (added to >> Karsten's existing content out on Fedora space) b) wait and see >> where the new curriculum takes us >> >> I would suggest a little bit of all the above. > > - From your description above it sounds as if the Practical OSS > Exploration textbook is one of the resources that you would curate a > link toward? Yes, I believe you are correct. I need to swallow more of your content first, but I believe you are correct. We are still trying to figure out how this all fits together, and that advice is sound. > Do we know what usage statistics are like for that book? Is it worth > taking some updates for it and using it as a reference to pull ideas > from for educators reading the Teaching Open Source Curriculum? No idea on usage. I think it is worth keeping separate and referencing as a primary source. > >> Karsten: Where is your source located? anywhere public or sharable? > The wiki is really the upstream source, we used DocBook XML as an > interim format. That said, I can't yet find the DocBook XML source but > it should be somewhere, I'm not recalling where. I'll have to ask > around for clues! We are using asciidoc for now. It's loads better than xml and tags for something so content heavy. > >> Also, am I right to assume that yours will go out of update, once >> this new one is live, or that it already has? > > That's not clear to me, if the book is being used it sounds as if it > might be one of your referenced works rather than supplanting it? > Maybe you can explain a little further about e.g. sample lessons? > > I'd also appreciate seeing what changes Jim has in mind, they may turn > the material into something more useful. You have solidified to me that it is likely to stay separate and continue to exist and to be referenced. > > Anyway, I'll track down the XML and get it up on GitHub at least. > > - - Karsten > - -- > Karsten 'quaid' Wade .^\ CentOS Doer of Stuff > http://TheOpenSourceWay.org \ http://community.redhat.com > @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.22 (GNU/Linux) > > iEYEARECAAYFAlUi/SUACgkQ2ZIOBq0ODEHbIgCdF/sKdqaz3u7CJdLFrvYYefTl > OgcAn1QEkXXUM/Ua83YVdBch3DiniJiF > =ediX > -----END PGP SIGNATURE----- _______________________________________________ tos mailing list [email protected] http://lists.teachingopensource.org/mailman/listinfo/tos
