Mailing-List: contact dev-help@corinthia.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@corinthia.incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of svante.schubert@gmail.com
 designates 74.125.82.182 as permitted sender)
From: Svante Schubert <svante.schubert@gmail.com>
Message-ID: <54AE6C24.9070501@gmail.com>
Date: Thu, 08 Jan 2015 12:38:12 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10;
 rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: dev@corinthia.incubator.apache.org
Subject: Re: Coding Standards page
References: <005b01d029de$4819bff0$d84d3fd0$@acm.org>
	<060F1F25-1238-45D5-A38A-54261CEB3071@apache.org>
	<CAK2iWdQ2T9Qwf4PetKBLvv_SEey84J6FHgrUN3Ddg+r8pprXPg@mail.gmail.com>
	<00c801d029f2$1b83a0a0$528ae1e0$@acm.org>
	<010e01d02aba$7715deb0$65419c10$@apache.org>
 <CAK2iWdQJ0za3ib5g9T-CycqPcwEsqYsObkhf0_9SRsAbqKsuAg@mail.gmail.com>
 <015301d02ad3$439e7ab0$cadb7010$@acm.org>
 <A160E301-2C50-48BE-84A7-6E8A0DF3B78F@comcast.net> <54AE69C1.60304@gmail.com>
In-Reply-To: <54AE69C1.60304@gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature";
 boundary="reuL7Dweesa2bJVx6OTlKEepatN6uwqU9"

--reuL7Dweesa2bJVx6OTlKEepatN6uwqU9
Content-Type: multipart/alternative;
 boundary="------------090700010500040803080107"

This is a multi-part message in MIME format.
--------------090700010500040803080107
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Am 08/01/15 um 12:28 schrieb Svante Schubert:
> Am 08/01/15 um 00:51 schrieb Dave Fisher:
>> On Jan 7, 2015, at 3:40 PM, Dennis E. Hamilton wrote:
>>
>>> -- replying below to --
>>> From: jan i [mailto:jani@apache.org]=20
>>> Sent: Wednesday, January 7, 2015 13:51
>>> To: dev@corinthia.incubator.apache.org; orcmid@apache.org
>>> Subject: Re: Coding Standards page
>>>
>>> On Wednesday, January 7, 2015, Dennis E. Hamilton <orcmid@apache.org>=
 wrote:
>>>
>>>> PS: I have the SVN definitions for the ODF documents, and I need to =
update
>>>> them for the Microsoft Office documents.  I assume that having these=

>>>> binaries is all right in collections of test documents, so long as t=
hey are
>>>> not in the part of our repositories that represent released source c=
ode.
>>> It is OK to have binaries for test. Can you please add the right git
>>> attributes to the main test dir.
>>>
>>> <orcmid>
>>>   I don't see a main test dir anywhere.
>>>   If you know of specific file extensions for binary content that we =
have,
>>>   please update the .gitattributes file at the repository root.  I co=
uldn't
>>>   Find anything with a quick scan of the repository.
>>>   (The SVN definitions are different and we don't use our SVN that wa=
y.)
>>> </orcmid>
>>>
>>> [ ... ]
>>>
>> Feel free to make use of the documents at https://svn.apache.org/repos=
/asf/poi/trunk/test-data/
>>
>> Fair warning about copying. In the last year someone complained that a=
 document that belonged to them had been submitted by another person with=
 a bug report. We removed the file with apologies.
>>
>> I would therefore recommend that these test documents get pulled in by=
 reference to POI's repos.
>>
> The centralization of test documents, where some of them (like on
> feature coverage) could to be accessed on demand, downloaded and be
> cached locally, similar as to Maven's .m2 directory mechanism for
> artifact would be indeed a great step forward!
>
> I have a lot of test documents in the ODF Toolkit, the problem is more
> to sort them according to features and to keep the number small, but
> with a good coverage to keep the test duration short and efficient.
>
> Regards,
> Svante
>
Sorry, sent too quickly.

Hopefully sometimes in the future test documents of a file format are
becoming (optional) part of its SDK, even better becoming part of the
standard of the file format itself. Like regression tests would become
part of a standard to provide a measurement for feature coverage of an
application supporting that file format (at least from model
perspective, but not necessary rendering).

This ability would require not only the specification of the model of
the file format, but as well its convertibility (API). As we are
specifying at the moment the changes upon the ODF model
<https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=3Doffice-col=
lab>
being used for change-tracking.

Regards,
Svante


--------------090700010500040803080107
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<html>
  <head>
    <meta content=3D"text/html; charset=3Dwindows-1252"
      http-equiv=3D"Content-Type">
  </head>
  <body bgcolor=3D"#FFFFFF" text=3D"#000000">
    <div class=3D"moz-cite-prefix">Am 08/01/15 um 12:28 schrieb Svante
      Schubert:<br>
    </div>
    <blockquote cite=3D"mid:54AE69C1.60304@gmail.com" type=3D"cite">
      <pre wrap=3D"">Am 08/01/15 um 00:51 schrieb Dave Fisher:
</pre>
      <blockquote type=3D"cite">
        <pre wrap=3D"">On Jan 7, 2015, at 3:40 PM, Dennis E. Hamilton wro=
te:

</pre>
        <blockquote type=3D"cite">
          <pre wrap=3D"">-- replying below to --
From: jan i [<a class=3D"moz-txt-link-freetext" href=3D"mailto:jani@apach=
e.org">mailto:jani@apache.org</a>]=20
Sent: Wednesday, January 7, 2015 13:51
To: <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:dev@corinthia.in=
cubator.apache.org">dev@corinthia.incubator.apache.org</a>; <a class=3D"m=
oz-txt-link-abbreviated" href=3D"mailto:orcmid@apache.org">orcmid@apache.=
org</a>
Subject: Re: Coding Standards page

On Wednesday, January 7, 2015, Dennis E. Hamilton <a class=3D"moz-txt-lin=
k-rfc2396E" href=3D"mailto:orcmid@apache.org">&lt;orcmid@apache.org&gt;</=
a> wrote:

</pre>
          <blockquote type=3D"cite">
            <pre wrap=3D"">PS: I have the SVN definitions for the ODF doc=
uments, and I need to update
them for the Microsoft Office documents.  I assume that having these
binaries is all right in collections of test documents, so long as they a=
re
not in the part of our repositories that represent released source code.
</pre>
          </blockquote>
          <pre wrap=3D"">It is OK to have binaries for test. Can you plea=
se add the right git
attributes to the main test dir.

&lt;orcmid&gt;
  I don't see a main test dir anywhere.
  If you know of specific file extensions for binary content that we have=
,
  please update the .gitattributes file at the repository root.  I couldn=
't
  Find anything with a quick scan of the repository.
  (The SVN definitions are different and we don't use our SVN that way.)
&lt;/orcmid&gt;

[ ... ]

</pre>
        </blockquote>
        <pre wrap=3D"">Feel free to make use of the documents at <a class=
=3D"moz-txt-link-freetext" href=3D"https://svn.apache.org/repos/asf/poi/t=
runk/test-data/">https://svn.apache.org/repos/asf/poi/trunk/test-data/</a=
>

Fair warning about copying. In the last year someone complained that a do=
cument that belonged to them had been submitted by another person with a =
bug report. We removed the file with apologies.

I would therefore recommend that these test documents get pulled in by re=
ference to POI's repos.

</pre>
      </blockquote>
      <pre wrap=3D"">The centralization of test documents, where some of =
them (like on
feature coverage) could to be accessed on demand, downloaded and be
cached locally, similar as to Maven's .m2 directory mechanism for
artifact would be indeed a great step forward!

I have a lot of test documents in the ODF Toolkit, the problem is more
to sort them according to features and to keep the number small, but
with a good coverage to keep the test duration short and efficient.

Regards,
Svante

</pre>
    </blockquote>
    Sorry, sent too quickly.<br>
    <br>
    Hopefully sometimes in the future test documents of a file format
    are becoming (optional) part of its SDK, even better becoming part
    of the standard of the file format itself. Like regression tests
    would become part of a standard to provide a measurement for feature
    coverage of an application supporting that file format (at least
    from model perspective, but not necessary rendering). <br>
    <br>
    This ability would require not only the specification of the model
    of the file format, but as well its convertibility (API). As <a
href=3D"https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=3Doff=
ice-collab">we
      are specifying at the moment the changes upon the ODF model</a>
    being used for change-tracking.<br>
    <br>
    Regards,<br>
    Svante<br>
    <br>
  </body>
</html>

--------------090700010500040803080107--

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

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCgAGBQJUrmwlAAoJEDQw8AU3RKko4D8P/RV7lxt09AUP82xJN5iSITjo
VMbv0T9XxE/GaiSlxsZC9kBsL9KgOwMSWaJBG44ZPziuRujX6taTDEKQIyFrytFM
OGzaoX8xK1aA3zbUlogWOwzibDOHA9kJ5EQCSfjV8hzVm+na9c0wryRCd0X46HLh
65+5PHljCOXGOue4ki3AMyAeHmD7kLCQTPB2Q0z3mDZ+/cwNZsg0z09H0075kALy
Qbvs1cHl0ncinfIR3oabqtCwV5dR+2eAmS/HpEYHZlME/8fi+JOEp8aZSo9Iajfm
zYkrUQ23qG5RRohMEhcYzbxrACl8cY4Q8+agnISQG+sTEOXkcEH4YCnUt9RLcdXa
lHU9P1OOCIf+BMOHYsg2kuswLdEuqVnJuaUb2jy08mQMCTXQ9qpLcky3XSNH5/hT
+f06fg9DtBpA0yzdMM5cpVXQyJqs6zOtEUX/Q9s3ypph3u9Wkt7Q9numrGo9sRwX
0N3LlmsDSmyyb8+kEZKKjz9VN8ftYn+/9dyYciw9kr90SaedLlWU7orquUQBDxzE
AQNrYpLcpwAE2I/Ms5LadBGNPrQHPZaz1aORzALKyELuhST6z4Um4nF8J85+GFGk
/6icR1aWqQblnqnCJ7ASaQSjfvWB6FRuhlBsT3Yvccz6odV3RDojHys6ANfxJEyk
3C3pxl2jwLGWvDxljEYu
=u5nJ
-----END PGP SIGNATURE-----

--reuL7Dweesa2bJVx6OTlKEepatN6uwqU9--