Comments on: Curriculum is Not the (Whole) Problem

By: Aaron

Aaron — Sat, 29 Aug 2009 17:44:19 +0000

@Zoe – Well, I can tell you there’s an investment of time (~20-30hrs/week each person) since July into this, and we’re shooting to kick off development (next week, even) of the backend (baqon) services to expose and a prototype application for people to play with.

The name “BAQON” came out last November (the LETSI event in Pensacola). Since this effort is going to be open and the learning applications for what we want to enable are so obvious (at least, so far, to us), the nod to the community is VERY intentional.

And srsly: everything’s better with baqon.

I tell you all of this, but that won’t get you to believe it. This has itched at me for a while, but the problem I describe above just revealed itself in July. And the more people we’re talking to about it, the more affirming it is. I’ve kept hoping someone would talk me down, and instead people keep giving more to embolden the idea.

November should see a limited demo; probably lean, not so fat

By: Zoe Rose

Zoe Rose — Sat, 29 Aug 2009 17:20:04 +0000

…I will believe in this if you can convince me that it isn’t an elaborate scheme to use the acronym ‘baqon’.

By: Twitter Trackbacks for Curriculum is Not the (Whole) Problem | Aaron Silvers [aaronsilvers.com] on Topsy.com

Sat, 29 Aug 2009 15:44:33 +0000

[...] Curriculum is Not the (Whole) Problem | Aaron Silvers http://www.aaronsilvers.com/2009/08/curriculum-is-not-the-whole-problem – view page – cached Harold's thesis, is how to manage knowledge but when you get down to it there are deeper dives… that's where we find bigger, fundamental challenges. — From the page [...]

By: Aaron

Aaron — Sat, 29 Aug 2009 14:25:33 +0000

Oh, and it’s not a requirement to eat bacon during our meetings, but it is an undocumented feature of the API

By: Aaron

Aaron — Sat, 29 Aug 2009 14:23:54 +0000

@Brian – High level: our thinking is that BAQON.org will be where everyone will be able to access the source code, organize to expand or improve it, support each other, etc. You know as well as I do that an open source effort requires a lot of help, so any weigh-in you can provide around user experience and interaction is key, dude. Key. In all honesty, if designers and developers (heck, USERS) can wrap their heads around what I’m talking about, think about the applications that could be enabled by the capabilities we’re working to make available — that’s what’s going to drive the requirements for expansion beyond what our small group can imagine. We’re going to need a way for people to get a taste of what they’ll be able to do, capture what else people need, and build to those needs.

The team is small (for now) to stay focused and organized enough to get something out there and documented. We expect to have something to demonstrate by the end of the year (we’re shooting for November and December milestones right now) — the site to start building as we can get to it (hopefully October –we could use some help with that pretty soon — :^).

By: Brian Dusablon

Brian Dusablon — Sat, 29 Aug 2009 13:40:54 +0000

Sweet. Looking forward to it. As you well know I’m busy as hell, but I would love to help out on this project, specifically around the user interface and interaction.

Is it a requirement to eat bacon during all the online collaborative meetings? I hope so.