All of lore.kernel.org
 help / color / mirror / Atom feed
From: Devyn Collier Johnson <devyncjohnson@gmail.com>
To: Bart Oldeman <bartoldeman@gmail.com>
Cc: linux-msdos@vger.kernel.org
Subject: Re: DOSEMU Version 2 has been Released (DevynCJohnson@Gmail.com)
Date: Wed, 10 Jul 2013 06:16:00 -0400	[thread overview]
Message-ID: <51DD3460.4060202@Gmail.com> (raw)
In-Reply-To: <CABHtM7X7kFn1igPciY1t3xp9D3CESq59Q=6U3mnLZ6t8DfbQyQ@mail.gmail.com>

I will delete the project.

On 07/09/2013 10:13 PM, Bart Oldeman wrote:
> Hi,
>
> I feel I should clear up the confusion a bit, as official DOSEMU maintainer.
>
> Yes, it is true that life has changed quite a bit for me since 2007
> and I am now chasing two small children after work which does not
> leave as much energy or time to work on DOSEMU. There has however been
> some activity, after 1.4.0 in SVN, the 1.4.0.1 patch release in 2008,
> and quite a bit of development in git since Stas returned last year.
> The distributions now release based on git that we tried to keep in a
> stable state (the devel branch in git is allowed to change more).
>
> So, if somebody skilled with more time than me puts in all the effort
> to release a new version of DOSEMU I should welcome that.
>
> However, this is not the case here:
> 1. "dosemu-reborn" is practically the same as dosemu 1.4.0 but with
> licensing changes, some formatting changes and adds "#DOSEMU was
> reborn by Devyn Collier Johnson" at various places. A "2.0" should be
> instead (IMHO) based on git, be heavily tested, and come with a proper
> list of user-visible changes (and not a deleted NEWS file).
> 2. The license was changed from GPLv2-only to GPLv3-only. Sorry, you
> cannot do that in a fork. While I personally have no problem with
> GPLv3, you would have to ask all copyright holders to make such a
> change, or replace all code by those copyright holders (the dosemu
> files that say "GPLv2 or later" are the exceptions). (Quite similarly
> you cannot fork the Linux kernel under GPLv3 either).
>
> So while I have no problems with people forking, in the way it is done
> here I stronly object, and will only confuse people. But I will gladly
> pass maintainership to somebody who can release a "DOSEMU 2.0" that
> truly deserves that title.
>
> Regards,
> Bart Oldeman
>
>
>
>
>
>
> On 9 July 2013 09:11, Devyn Collier Johnson <devyncjohnson@gmail.com> wrote:
>> Aloha DOSEMU Users!
>>
>> I want to info everyone that DOSEMU has been released and is no longer
>> abandonware. Feel free to contribute to the new DOSEMU team and help DOSEMU
>> compete with DOSbox.
>>
>> https://launchpad.net/dosemu-reborn
>>
>> Mahalo,
>>
>> Devyn Collier Johnson
>> DevynCJohnson@Gmail.com
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  parent reply	other threads:[~2013-07-10 10:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-09 13:11 DOSEMU Version 2 has been Released (DevynCJohnson@Gmail.com) Devyn Collier Johnson
2013-07-09 13:42 ` Mateusz Viste
2013-07-09 20:25   ` Stas Sergeev
2013-07-09 16:30 ` Frantisek Hanzlik
2013-07-09 20:14 ` Stas Sergeev
2013-07-10  2:13 ` Bart Oldeman
2013-07-10  6:50   ` Stas Sergeev
2013-07-10 10:16   ` Devyn Collier Johnson [this message]
2013-07-10 10:30     ` Stas Sergeev
2013-07-10 11:52       ` DOSEMU Version 2 has been Released Ivan Baldo
2013-07-11 13:44         ` Resurrect DOSEMU Devyn Collier Johnson
2013-07-11 13:56           ` Paul Crawford
2013-07-11 14:31             ` Frederic Herman
2013-07-11 13:58           ` Mateusz Viste
2013-07-15 10:50             ` Stas Sergeev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51DD3460.4060202@Gmail.com \
    --to=devyncjohnson@gmail.com \
    --cc=bartoldeman@gmail.com \
    --cc=linux-msdos@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.