Re: [B2-devel] Thoughts on SheepShaver and Basilisk II

[Frank T. <fra...@gm...>]

So as to avoid duplicative effort, can you share what areas you plan to
improve? If you do start working on re-implementing the memory management
layer, I would be willing to help.

On Fri, Jun 15, 2012 at 6:34 PM, Alexander von Gluck
<kal...@un...>wrote:

> On 15.06.2012 17:34, Lew Irwin/Studio Briefing wrote:
> > For us non-techies who are using SheepShaver with the old "fork," what
> > does this mean?
>
> Nothing really.  The GNU license means a fork can take place as long as
> some
> guidelines
> are followed:
>
>  * Copyrights can't be changed (eg, I can't go back and erase the names of
> all the people
>    who made SheepShaver possible)
>  * Trademark laws must be followed. (thus SheepShear vs SheepShaver)
>

And the resulting derivative products are forever locked into the G.P.L..
There are some down-sides to this, but it makes merging back changes from
those derivative products much simpler.


>
> Possible Pros:
>  * SheepShear adds all kinds of neat/crazy/hairbrain new features the
> SheepShaver developers
>    can use upstream if desired.
>  * SheepShear attracts more attention to Macintosh Classic emulation.
>  * If SheepShear dies... the SheepShaver devs have a potential pool of new
> features and changes
>  * If SheepShaver dies... SheepShear lives on.
>
> Possible Cons:
>  * SheepShear splits the community causing two weak projects vs one strong
> one (given the
>    decline in activity of SheepShaver I feel this risk is minimal)
>
>
> I've begin working on SheepShear, and SheepShaver will continue how it's
> founders see fit.
>
> Two code bases "forking" in two directions :)
>
>  -- Alex
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> basilisk-devel mailing list
> bas...@li...
> https://lists.sourceforge.net/lists/listinfo/basilisk-devel
>