[Coco] Drivewire and ADOS...

[Aaron Wolfe]

I think I missed something.

Drivewire is absolutely open source.  You are free to take the source and
use it any way you would like within the terms of the GPL.   As far as I am
concerned this can apply to the wiki content as well.

However, this does not grant anyone the right to make changes to the
official project.  As the maintainer, I have the responsibility to prevent
bad changes and the final say on what happens.

Adding documentation for third party software to the DriveWire 4 wiki is a
bad change, and I will not be doing that.

I fully support the effort at cocopedia (for the record, I was the one who
posted the cocopedia link originally :) and hope that it becomes a valuable
resource.  I never meant to imply otherwise and apologize if I did.

On Sep 30, 2013 7:03 PM, "Bill Pierce" <ooogalapasooo at aol.com> wrote:
>
>
> (button pushed) Now I will say something.
> First, I thought Aaron said DriveWire4 was Open Source? So why is HE
responsible for anything? Although he is the only person (that I know of)
working on the code, he said it was open for anyone to work on it.
> He asked for people to help... then didn't want this, didn't want that.
So we are creating a CENTRAL place where all is linked (not stored) to
their original sites with some history (it IS a Wiki) and a few simple
instructions on how to use them.... TOGETHER as they were designed and are
intended to be used.
> If that's wrong and we look at it the way you guys are telling it... The
Rainbow, Hot Coco, The Color Computer Magazine and COUNTLESS others should
never have happened.... because they were a source OTHER THAN THE DEVELOPER
where you could get tutorials, information, addresses and phone numbers.
And the Coco wasn't even open source. If we look at it that way, we
should've ONLY read the Coco manuals and NEVER went somewhere else for
info. We ALL may as well tear down our websites, blogs, downloads,
archives, forums etc. Because it's not the original source.
> Tandy still owns the patents on the Cocos and all rights to it's design
and parts. That makes MOST of us guilty of copyright infringement from day
one. And you're worried that someone's posted instructions may become
outdated? Have you been to the countless abandoned Coco sites that are now
some of the only sources for info? I've seen some that haven't been touched
since 1999, 2001, 2003 etc. Real up to date info. And this is our source
for info? That's sad.
>
> Now you're telling me it's wrong to do a tutorial on a OPEN SOURCE
project whose documentation seems to confuse some people? Or the website
may get hacked, or the hardware may change, or the code may change?
>
> I'm sorry, that's a big pile of BS straight from it's source!
> Correction, I'm not sorry, it's the way I feel.
>
> It's a sad day when info can't be collected and shared and this is a sad
conversation... so I'm out of it again.
>
> Bill Pierce
> My Music from the Tandy/Radio Shack Color Computer 2 & 3
> https://sites.google.com/site/dabarnstudio/
> Co-Webmaster of The TRS-80 Color Computer Archive
> http://www.colorcomputerarchive.com/
> Co-Contributor, Co-Editor for CocoPedia
> http://www.cocopedia.com/wiki/index.php/Main_Page
> E-Mail: ooogalapasooo at aol.com
>
>
>
>
> -----Original Message-----
> From: Aaron Wolfe <aawolfe at gmail.com>
> To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
> Sent: Mon, Sep 30, 2013 6:24 pm
> Subject: Re: [Coco] Drivewire and ADOS...
>
>
> On Sep 30, 2013 3:47 PM, "Gene Heskett" <gheskett at wdtv.com> wrote:
> >
> > On Monday 30 September 2013 15:33:28 Al Hartman did opine:
> >
> > > -----Original Message-----
> > > From: Aaron Wolfe
> > >
> > > > I believe the most helpful approach will be to provide documentation
> > > > that explains the role and scope of the DriveWire software clearly,
> > > > so that users will understand the demarcation.  This way hopefully
> > > > their first place common sense will take them to the correct project
> > > > for support.
> > >
> > > It would be less work, more useful, and more effective to have it on
the
> > > Drivewire site in a client troubleshooting section.
> >
> > While I can see your point here, I'm afraid I'll have to plead the
mugwump
> > syndrome.
> >
> > Why?  Because then, in the new bee's eye's, Aaron then becomes
responsible
> > for something not of his making, and which he has no power to correct.
 I
> > would object to that were I in Aaron's shoes.
> >
> > I for one am very pleased that Aaron has blessed us with this software.
> > But this scrimmage line pileup I see here, with Aaron on the bottom,
flat
> > needs to stop, its unfair at best.
> >
>
> Thanks Gene :-)
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco