[TOS] any interest in activities to introduce FOSS projects?

Joel Sherrill joel.sherrill at gmail.com
Sat Apr 27 20:22:17 UTC 2019

On Sat, Apr 27, 2019, 11:32 AM Clif Kussmaul <clifkussmaul at gmail.com> wrote:

> Hi everyone,
> A year or so ago, I went to a library open house where students and
> faculty demoed FOSS tools like Audacity, FreeMind, Inkscape, GIMP, &
> WordPress. However, no one I talked to had participated in their project’s
> community. This seems like a missed opportunity, especially for someone who
> uses one project heavily (e.g. a musician who uses MuseScore, a designer
> who uses InkScape).
> Thus, I’d like to develop some activities to help non-technical people
> learn more about a specific FOSS project, and how to access it’s online
> resources and interact with the community. I plan to start with Audacity &
> MuseScore. Please let me know if you have other project suggestions, or
> would like to work together on such activities. My hope is that after the
> first few we can create a template to make it easier to do more.

I'm the project lead for RTEMS.org which is a free real-time operating
system. Our users are primarily technical but we do end up with experienced
developers a d students who have no embedded cross development experience.

With that background, every open source project needs documentation to
market the project to find these potential users, on-ramp them from
different backgrounds and skills levels, and introduce them to the project

There also needs to be comparable documentation for on-ramping contributors
like developers, patch submitters, documentation fixes, etc.

Some of the projects you mention have been Google Summer of Code
participants so should have some new developer focused content.

Personally I like patterns. If you are looking across a set of projects
like it sounds, define roles and what should be in place. Including a
suggestion on organisation of it all and artifact names. This could develop
into a standard model and that would help new users and open source
organisations since they would have a roadmap.

Remember every document should have a well-defined audience and scope.

Some of the documents may be related to the business cases associated with
using the software. A standard I work with has a business and technical
side to ensure there business barriers to adoption are addressed.

That's just random thoughts.


> Clif
> ---
> Clif Kussmaul  clif at kussmaul.org  http://kussmaul.org  +1-484-893-0255
> EDT=GMT-5  (he/him)
> _______________________________________________
> tos mailing list
> tos at teachingopensource.org
> http://lists.teachingopensource.org/mailman/listinfo/tos
> TOS website: http://teachingopensource.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.teachingopensource.org/pipermail/tos/attachments/20190427/395a80ad/attachment.html>

More information about the tos mailing list