2010/9/30 Chris Watkins <chriswater...@appropedia.org>

>
>
> 2010/9/29 Karsten Wade <kw...@redhat.com>
>
>
>> I guess what I'm looking for is for us to not have to maintain this
>> content.  The less original content that we write, the less we have to
>> maintain.  There are a lot of places where this textbook can draw from
>> other sources - take the Subversion chapter as an example.
>>
>
> This is wise.
>
> Is there an active open source wiki, or Linux wiki, that can be used for
> this? This would be the ideal - give others in the broader OSS community the
> opportunity to easily contribute, and make it findable as part of a broad
> and visible body of knowledge.
>
> Getting off topic a bit, but... The problem is that there doesn't seem to
> be an active wiki in this field, unfortunately. Still, maybe do a search for
> the best of what's out there, that uses a suitable license, and at least
> that's a big step in the direction of openness, and better than maintaining
> it internally.
>
> I just checked http://wiki.linuxquestions.org/wiki - there's are more spam
> edits than genuine ones. linux.wikia.com has large ads and little
> activity, but at least the spam is removed quickly. If anyone wants to set
> up or resuscitate an open source Linux or general tech wiki, I'd be happy to
> happy to lend some support.
>

Consider https://secure.wikimedia.org/wikipedia/en/wiki/Main_Page. It's
active and well maintained.


>
> Where sufficient content doesn't exist, let's write it and offer ouri
>> version as a canonica reference.  In the case of programming security
>>
>> and FOSS, I hope we can find existing works and not have to (re)invent
>> this wheel.
>>
>> Then the work for those chapters/sections is more in gluing and
>> editing, and reworking for style.
>>
>

{...}
>>
>

Chris Watkins
_______________________________________________
tos mailing list
tos@teachingopensource.org
http://teachingopensource.org/mailman/listinfo/tos

Reply via email to