Thanks Mel; I will try and provide answers to the issues raised in the next
couple of days.
Regards,
Michael.
On Mon, Nov 8, 2010 at 12:45 AM, Mel Chua <m...@redhat.com> wrote:
> Hi, Michael - I wanted to respond on your grant request so we can move
> forward with getting you equipment this month. My main concern is one of
> scope - this is taking on a *lot*, and I'd like to try focusing on one area
> of focus at a time and documenting results from it this term, and then if
> that goes well perhaps looking into the other areas next term.
>
> You've divided your request into (1) recording equipment, (2) User
> Equipment (3) Communication/Network, and (4) Android SDKs - so here's what
> I'd say.
>
> I'll get you (1) recording equipment, and you choose one of (2), (3), or
> (4) and let me (and the TOS list) know the following:
>
> 1. The final bill of materials for the research area you've chosen, given
> the feedback that others on this list have given on the hardware you were
> thinking of "I want 3 of the Beagleboards version foobar that Chris
> mentioned, but 2 of the older ones so we can experiment with different ARM
> architectures..."
>
> 2. A course website, course description that includes an explanation of
> how/when the equipment will be used, and enrollment number (if you don't
> have the exact number of students, estimate how many you'll have and then
> update it when you have the final count). Basically, how many students will
> this grant "touch," and in what way - and where will the work of those
> students be viewable so we can see what they've made with the grant
> equipment afterwards?
>
> 3. A list of specific ways (and dates/times, if applicable) people from the
> FOSS community can see and/or interact with the students in the class, since
> fostering interaction with the FOSS community (rather than simply "working
> with FOSS tools") is a primary purpose behind these grants. I'm thinking
> about items like "Final design reviews happen on <this date> and people with
> <this sort of expertise> can give <this sort of feedback> at <this location>
> if you sign up ahead of time <this way>."
>
> 4. A list of deliverables from you/your class to the TOS community - so far
> you've specified deliverables students will create for *you* for their
> classwork, but what I care about more is the things that will be reusable by
> the other *professors* in the TOS community. Where will course materials be
> posted, what parts of them will be reusable by other institutions? ("We will
> create 3 labs that teach the following topics A, B, and C using materials
> from <this list>, and they will be hosted at <this location>, and we will
> email the TOS community when they are available; the estimated completion
> date is <date>.")
>
> Does this make sense? (Folks on the list - does this sound reasonable?) I
> don't want to make you feel blocked by unnecessary bureaucracy, but I do
> want to make sure we have a clear idea of what's going to be happening with
> this grant, and when and how it'll be visible and usable to whom.
>
> --Mel
>
> PS: Matt's http://teachingopensource.org/index.php/User:Jadudm/PTV makes a
> good example to look at. :)
>
_______________________________________________
tos mailing list
tos@teachingopensource.org
http://teachingopensource.org/mailman/listinfo/tos
