NDT-DEV email list created

[Aaron Brown <>]

Hey Will,

Are you using the password from https://code.google.com/hosting/settings ?

Cheers,

Aaron

On Feb 10, 2014, at 3:30 PM, Will Hawkins <> wrote:

Aaron,

I'm sorry to be so needy, but I'm having trouble with creating a "branch" :

svn copy https://ndt.googlecode.com/svn/trunk/
https://ndt.googlecode.com/svn/branches/Issue111/ -m "Creating branch to
resolve Issue 111." --username

I get the following error (after entering my username/password 3x):
svn: MKACTIVITY of '/svn/!svn/act/9b8e8065-af8c-405a-9779-718d6b42a31b':
authorization failed: Could not authenticate to server: rejected Basic
challenge (https://ndt.googlecode.com)

Does this seem like something I should be seeing?

Thanks again for your patience!
Will


On 02/10/2014 01:33 PM, Aaron Brown wrote:

Hey Will,

You should be able to commit to the repo

Cheers,
Aaron

On Feb 10, 2014, at 1:00 PM, Will Hawkins <> wrote:

I do! It's

Does that work?

Thanks!

On 02/10/2014 12:38 PM, Aaron Brown wrote:

Hey Will,

Sorry for the delay, do you have an account that you can login to google with?

Cheers,
Aaron

On Feb 10, 2014, at 12:22 PM, Will Hawkins <> wrote:

Hey Aaron!

I'm sorry to reply to myself, but I was wondering if you have to give me
explicit permission to the svn repository?

Will

On 02/07/2014 04:31 PM, Aaron Brown wrote:

Hey Will,

On Feb 7, 2014, at 2:44 AM, Will Hawkins <> wrote:

Hello everyone!

My name is Will Hawkins and I am on the MeasurementLab team here at the Open Technology Institute. First of all, I want to say thank you for the work you've done and continue to do on NDT. It is obviously a big part of the platform :-)

I've been working with MLab at OTI for almost 2 years now, but I've recently started digging in to the NDT server code. I found a few places where I think that I can help and I was wondering the best way to contribute. Is it best to submit patches? If so, should those go to this list or should they go to the issue tracker on code.google.com? Just let me know the best way to contribute, and I will send a few patches along!

Welcome, and thanks for digging and working on the code :) The easiest way is to create a branch, and make changes. We can review them and once ack’d, you can merge them into trunk.

Again, thank you so much for working so hard on this code. I hope that I'll have the chance to contribute meaningfully and help you all out!

Glad to have you contributing :)

Cheers,
Aaron