NDT-DEV email list created

["Jeff W. Boote" <>]

Hi Thomas,

Does that mean you are done? If so, I'm fine with what is here - no need to 
revert. If you have on-going work, then I'd like to talk and coordinate that 
with you. I just wanted to get a good idea of the scope of work you have 
going here.

I'm sorry, I'm just now going through and starting to clean this up from a 
project/release-mgmt perspective and think about adding the next release tag. 
I also should have sent something to the list to say that we were starting 
some comprehensive work.

The work we are starting will restructure most of the code, so functions and 
files will be moving around a lot. This will make merging much more 
complicated and difficult than a normal development cycle which is why it is 
a good idea for me to find out what on-going or pending work people are 
currently doing.

So... Lets just make this a call for all developers to please let me know if 
you have outstanding commits or ongoing work you plan to do in the next 2-3 
months so we can coordinate it.

Thanks!
jeff

On Aug 5, 2011, at 11:21 AM, Thomas Gideon wrote:

> -----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-----