Re: RFC: Dealing with MSDN errors.

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--===============2658221641331523205==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="sieuksFuNL07D4nvsUBvo9mLDVrvGcdlV"

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--sieuksFuNL07D4nvsUBvo9mLDVrvGcdlV
Content-Type: multipart/mixed; boundary="O2j0H1kMjct0tJBaHaGR35l6utuEJNM9P";
	protected-headers="v1"
From: Cesar Strauss <[email protected]>
To: [email protected]
Message-ID: <0f5548f9-ad45-2afd-e505-a6bbac889091-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [MinGW-dvlpr] RFC: Dealing with MSDN errors.
References: <58C519DA.1080003-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
In-Reply-To: <58C519DA.1080003-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>

--O2j0H1kMjct0tJBaHaGR35l6utuEJNM9P
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 03-12-2017 06:50, Keith Marshall wrote:
> How should we best deal with reports of probable erroneous MSDN content=

> such as: https://sourceforge.net/p/mingw/bugs/2248/ ?
>=20
> Here, the poster provides an acceptable test case, which demonstrates
> that the MSDN information is most likely incorrect, but can refer us
> only to known sources of plagiarised Microsoft header file content, to
> support his proposed correction.  Obviously, we cannot examine those
> plagiarised sources, but should we just take his word for it, and
> correct our headers, as he suggests?
>=20
> Opinions?

It would have been best if the reporter had found the correct prototype
by trial and error. We cannot do that now, since we already know the answ=
er.

You could argue that the correct prototype is now found in "publicly
available documentation". Which, in this case, is the text of the bug
report itself. We already consider Internet references like blog posts
as "publicly available documentation", if I am not mistaken. You could
add this on top of your patch:

  "MSDN is wrong. The correct type for parameter X is Y according to
https://sf.net/..."

On the other hand, for such a small change, it could also pass as "fair
use" instance, even if the source itself is copyrighted.

Maybe make the "documentation or references" requirement more explicit
on the bug reporting page. We do link to
http://www.mingw.org/reporting_bugs, but it is a bit buried in there.
Maybe write a dedicated page, like the one on
https://wiki.winehq.org/Clean_Room_Guidelines

Regards,

Cesar


--O2j0H1kMjct0tJBaHaGR35l6utuEJNM9P--

--sieuksFuNL07D4nvsUBvo9mLDVrvGcdlV
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHIEARECADIWIQQCb1/P7ch/bupd10ne0AVHqalkTAUCWMVMdRQcY2VzdHJhdXNz
QGdtYWlsLmNvbQAKCRDe0AVHqalkTBhoAKC+lzncU4Vj3kMdxqOLLnGZ0LVtuQCg
nnyKh8f0Iu3YZhZphR8xJABZf2I=
=zZGY
-----END PGP SIGNATURE-----

--sieuksFuNL07D4nvsUBvo9mLDVrvGcdlV--


--===============2658221641331523205==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

------------------------------------------------------------------------------
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford
--===============2658221641331523205==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
MinGW-dvlpr mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr

--===============2658221641331523205==--