NDT-DEV email list created

[Thomas Gideon <>]

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

On 08/05/2011 01:12 PM, Jeff W. Boote wrote:
> 
> Can I ask who this is? (Your email address is not very informative
> in this sense.)

Sorry, it is Thomas from OIT/NAF.

> I'm curious what changes you are committing to trunk? What is the 
> scope here? Typically changes should be discussed with the
> developers before being committed to trunk. I would expect you to
> commit them to a branch and then suggest them for inclusion in the
> next release. We are actively modifying the code for a planned
> release right now, and do not want things changing in trunk causing
> undue time merging.

The changes are to add an identifying string that each client can set so
that collected data can be divvied out by which client ran the test, if
desired.

Apologies, I should have pinged you to coordinate these changes. They
seemed so small, very similar to the client browser changes that I
didn't think about the impact on other active development.

I can back out my changes, branch from r394, and re-commit my changes to
that branch.

> I would appreciate it if you would create a branch for whatever your 
> ongoing work is, and communicate with the rest of the developers 
> before merging things into trunk.

Again, I didn't think the changes were intrusive and there is no tag for
a release later than 3.6.1. That release doesn't include the client
browser meta data changes from which I was basing the client application
metatdata changes. Ideally we'd like to stage an incremental updated
that adds the client identifier ASAP if at all possible so that Tizian
Refice at Google can adjust her data parsing and we can get the client
identifier into the data stream sooner rather than later.

- -- 
Thomas Gideon
Sr. Staff Technologist, Open Technology Initiative
New America Foundation
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEAREIAAYFAk48JowACgkQ65xMDm9EZnNuugCgj8Clbga9sc/jZXwxZifArHDt
AHgAniUpZTFbzlU3K/Hs2USzBGfczEIo
=6itg
-----END PGP SIGNATURE-----