[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Fwd: boundary between main and contrib



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 2021-01-13 at 23:05, apo@debian.org wrote:
> Am Montag, den 11.01.2021, 16:02 +0100 schrieb bret curtis:
> [...]
> > I have the same interest in seeing OpenMW enter into main and away
> > from contrib.  While upstream is busy making their own 'game' that can
be
> > used to demonstrate OpenMW's capabilities, they also provide OpenMW-CS
> > which is a full blown editor that anyone can use to create their own
games
> > for OpenMW. Would the inclusion of the editor warrant the bump to main?
>
> In my opinion, if an editor exists, which is free software and compatible
with
> Debian main, then the engine should be in Debian main too.
>
> OpenMW should be definitely in Debian main, if such an editor exists. In
the
> past we had some controversial discussions about the inclusion of a free
game
> engine and non-free game content. The consensus was: If a free game
engine is
> only useful with non-free game content, then it should be in Debian
contrib.
> Otherwise it should be in Debian main.
>
> Regards,
>
> Markus

That's great to hear. We've been packaging the editor with every release.
https://tracker.debian.org/pkg/openmw
https://packages.debian.org/unstable/openmw-cs

Development has really picked up steam the last year and
modders/content-creators have been using it and giving their feedback as
well.
https://www.youtube.com/watch?v=BX6PTzTNW3Y&feature=youtu.be&ab_channel=unelsson


So how do we go about moving the openmw source package from contrib to
main, just modify the control file and ask some kind soul to upload? Do we
need to include ftpmaster in discussions?

Cheers,
Bret
-----BEGIN PGP SIGNATURE-----
Version: FlowCrypt Email Encryption 7.9.7
Comment: Seamlessly send and receive encrypted email

wsFzBAEBCAAGBQJgAAj+ACEJEMI3e31YTLkwFiEE6+UVEsAp/iYIDx+Wwjd7
fVhMuTBrvg//dhGBaQ4HHm8F+A1GVexWk13vZXalR1jFwGqqKjHuyTxUsF3c
es0UArKgw2I6l2T2JhtVVse/Tq6BXsup1eN3DetLc9LHdkx0rV1pMMCFCU9k
nhsTRULzyfB2MjdCaOZTX5Mxef1YIpNvGKPou9LZ4Z5WkysJXMq3W0WbfMDz
63lu0mItt3ZRhvfHvYqG1HHZTnfAwl3P43BZH6skylTmyLs+TiAJC7EugRmh
CIMqgGIa9lnXp+I1pOi19+ChYqH/esAnxmYB0MUTpiSp5AhkmdJPkz9WSI6l
tv7nuzI8p1bAzv6mhcJml481TTXXWVPRe9oD93DdCFMJCae1urzuKyuKgw7m
UDHJNg0fDI2vVp5pBJQFu6hKSaW0JT0l1r/Kw01oKOBLvxll/I73wYceYmFy
+WLpwkcliF9K2WsL9Wj7Zw9ugTRBy4gl/M73/FaC7n9mt0+QFbFmfOTqeYTp
Yu4coexcEp8MF0c5Ev5fpuTcsrJG9W4o8R1tda++swUJTg/6/AzQBx7YENLJ
Nlg7vBjjfeShC9Cd8FuAhVRoFr+TrdoXNP89heHmz2JkPlFKo3OkXGDGIfCR
JLL3Zjbeoo735ksy5CvL2ZcJp8t+u/tYhHsKjyTs1XXXJIEl5Me1nakpDKF+
+LkBfWCGfOn3A5kHn/KvMR1SXB+FjFfElEo=
=Px1B
-----END PGP SIGNATURE-----

Attachment: 0xC2377B7D584CB930.asc
Description: application/pgp-keys


Reply to: