OpenMW 0.27.0

[Zini]

I would expect the maintainer of the respective package to serve as a point of contact. Seems logical, since most of our packages are build and maintained by OpenMW team members and these people handle most of the communication with the respective distributions.

[psi29a]

I would expect the maintainer of the respective package to serve as a point of contact. Seems logical, since most of our packages are build and maintained by OpenMW team members and these people handle most of the communication with the respective distributions.

Oddly enough, that is already handled by 'maintainer'... but they want more information as to who or whom owns copyright of the code. So our choices are to list one person or a group.

[Zini]

We do not do copyright assignment. That code belongs to who ever wrote it, which can be tracked by looking into the git logs.

[psi29a]

We do not do copyright assignment. That code belongs to who ever wrote it, which can be tracked by looking into the git logs.

Yes, that is very well known... are you asking me then to list every single person and their email address in the license file? Wouldn't it be simple to say "OpenMW Development Team" and then a url to the readme file that we have with all their information? I'm being pedantic because they are being pedantic.

[Zini]

I am perfectly fine with "OpenMW Development Team and an URL to the readme file, if that is acceptable to Debian.

[psi29a]

I am perfectly fine with "OpenMW Development Team and an URL to the readme file, if that is acceptable to Debian.

Consider it done. Zini, you've been replaced by "OpenMW Development Team"

I'll handle the license cleanup for the 3rd party libs we ship with our code. We just need to clarify which licenses are used within our tarball.

[Zini]

Minor change to the change list: Added bug 910 (was fixed in 0.27.0, but originally not flagged as resolved).

[psi29a]

Can we nuke cmake/FindAudiere.cmake or is this still required for someone?

Since we do ffmpeg/avtools for everything, do we even need mpg123 and libsnd?

[Zini]

They are still options for the sound system AFAIK (haven't used them for a while). We can discuss retiring them, but I would prefer to wait for 0.28.0. Rushing these things never ends well.

[psi29a]

Sure, tasks for 0.28 then... same goes for pushing the license files for the ttf files to where the ttf files live instead of in the main directory.

0.27 will be without opencs right?