community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Ruggeri <>
Subject Re: Open Source class... starting tomorrow
Date Fri, 20 Jan 2017 22:16:59 GMT
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 <>
Sent: January 18, 2017 8:06:48 AM CST
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....
>> 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):
>> 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

To unsubscribe, e-mail:
For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, 7-Bit, 0 bytes)
View raw message