On 1/21/17 8:57 AM, Phil Steitz wrote:
> On 1/21/17 3:31 AM, Scott Wilson wrote:
>> Hi Daniel,
>>
>> When I taught a first year undergraduate course on FOSS the major syllabus 
>> topics were:
>>
>> - Community
>> - Communications
>> - Governance
>> - Issue Tracking
>> - Sustainability
>> - Version Control
>> - Intellectual Property
>>
>> Each student built a case study on a project they were interested in week by 
>> week published on Wordpress; e.g.
>>
>> https://pete1124.wordpress.com/
>> https://thejibrjabr.wordpress.com/
>>
>> … etc
>>
>> I was planning to put the content for the course on Github, but the Moodle 
>> XML export format doesn’t exactly make it very easy… if its of interest I’d 
>> be happy to share more!
> Personally, I would be very interested in following and maybe
> eventually contributing to this.  The challenges with collaborating
> using Moodle export and/or other ed content specs is an interesting
> problem that it would be great to solve.  Have you ever done this
> before?

A colleague pointed me at this [1].  Using something like this to
manage source content might make open collaborative development of
course content easier.

Phil

[1] https://git-community.cs.odu.edu/zeil/Course_Website_Management


>
> Phil
>>> On 20 Jan 2017, at 22:16, Daniel Ruggeri <drugg...@primary.net> wrote:
>>>
>>> Hi, Phil;
>>>   That makes sense and I will update the syllabus to reflect the proper 
>>> terminology. I will also plan to spend a class each on build tools and 
>>> dependency management as those are both great tooics to include.
>>> --
>>> Daniel Ruggeri
>>>
>>>
>>> -------- Original Message --------
>>> From: Phil Steitz <phil.ste...@gmail.com>
>>> Sent: January 18, 2017 8:06:48 AM CST
>>> To: dev@community.apache.org
>>> Subject: Re: Open Source class... starting tomorrow
>>>
>>> On 1/17/17 10:58 AM, Phil Steitz wrote:
>>>> On 1/16/17 5:14 PM, Daniel Ruggeri wrote:
>>>>> Hi, all;
>>>>>
>>>>> Digging up "ancient" history on this one....
>>>>>
>>>>> https://lists.apache.org/thread.html/28c8decf60ec3c79c97a62c936ec9b816da841eb3fb655144dd219ba@1430955768@%3Cdev.community.apache.org%3E
>>>>>
>>>>>
>>>>> I'm happy to share that tomorrow begins the first day of a class I'm
>>>>> teaching titled "Open Source Software Development" at University of
>>>>> Missouri - St. Louis in the Information Systems department. Since this
>>>>> community shared so many great suggestions to help shape the class, I
>>>>> wanted to drop a big THANK YOU to everyone.
>>>>>
>>>>>
>>>>> I'd also like to share the working syllabus (pardon the empty spots -
>>>>> we're going to figure out what our class project looks like and work on
>>>>> that for most of the second half):
>>>>>
>>>>> https://github.com/DRuggeri/OSSClass/blob/master/syllabus.md
>>>>>
>>>>>
>>>>> As with any decent, open project the material can be shaped by your
>>>>> contributions so don't hesitate to reply here if I missed anything
>>>>> really important to cover. As the course goes on, I'll be posting
>>>>> outlines and resources in the repository above. With luck, this could
>>>>> hopefully become an open curriculum anyone can pick up and teach in any
>>>>> university setting.
>>>> First, many, many thanks for doing this, Daniel!  I really like the
>>>> idea of developing open content for use in courses like this.  I
>>>> will keep watching the repo!
>>>>
>>>> One thing that I don't see there is build tools / systems and
>>>> artifact repositories.  It is no accident that Ant and Maven were
>>>> developed @apache.  Maybe after the scm discussion, you could add
>>>> something on making it easy to build checked out code, which is key
>>>> to making it easy to get involved.  That would segway naturally into
>>>> the evolution of build and dependency management systems.
>>> One more thing that occurred to me after I sent above.  This may
>>> seem like a nit, but I would recommend using the term "Issue
>>> Tracker" rather than "Bug Tracker."  We use these things as part of
>>> the core collaboration machinery and managing bugs is only one thing
>>> that we use them for.
>>>
>>> Phil
>>>> Phil
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>>> For additional commands, e-mail: dev-h...@community.apache.org
>>>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Reply via email to