Re: [Atcollab-general] AT 2.0

[Boaz N. <boa...@es...>]

Thank you, Eugene.  Thanks for your help also.

My position at ESRF will be ending next week, so I will have less direct connection with the AT development
going on at ESRF.  I will be starting a new position at the company RadiaSoft (http://radiasoft.net/ <http://radiasoft.net/>) in Boulder, Colorado, in October.
I expect that I can continue work on AT in some form with RadiaSoft, but I don’t expect to be able to be the main coordinator
for the AT collaboration.  I hope that others can step up to fill this role.  I think that GitHub will give us some new tools for
helping to manage the development.  We already have 7 developers signed up under the atcollab org. on Github:
https://github.com/atcollab <https://github.com/atcollab>

I think one of the issues we need to resolve is who is responsible for which parts of the code, documentation, etc.
In GitHub, the way it works is that people make changes to a part of the code in their local git repository.  They then issue
a “pull request”.  Someone needs to decide whether or not to accept this pull request, which then merges the changes into the main repository.
So far, everyone we’ve added to the atcollab organization is listed as “owner” meaning they fave full rights for editing and accepting pull requests.
I think we should continue to go ahead with this sense of mutual trust, but also figure out who is responsible for what.  We don’t want to put people
in the position of having to accept code that they don’t understand.  Having a robust set of testing routines would definitely help this situation.

Looking forward to seeing the continuing development of AT, past 2.0!

Best wishes,
Boaz

> On Aug 26, 2017, at 3:19 AM, Eugene Tan <Eug...@sy...> wrote:
> 
> Big thanks for your dedication Boaz and the rest of the contributors for getting it here! I certainly feel there is some momentum starting to build here. The operators here are excited to see the python developments. 
> 
> Keep up all the good work everyone. 
> 
> 
> 
> Eugene
> 
> Senior Physicist 
> Accelerator physics and operations group 
> Australian Synchrotron
> 
> On 26 Aug. 2017, at 12:39 am, Boaz Nash <boa...@es... <mailto:boa...@es...>> wrote:
> 
>> Dear all,
>> 
>> Following with the timeline we’ve discussed, I went ahead and tagged the code in 
>> the at2devel SVN branch on SourceForge from today.  This is AT 2.0.  A zip file may be downloaded here:
>> https://sourceforge.net/projects/atcollab/files/latest/download <https://sourceforge.net/projects/atcollab/files/latest/download>
>> 
>> Please download this when you have a chance and give it a try.  The demo files in atmat/atdemos should
>> work.  The integrators are compiled with atmexall as usual.
>> 
>> I didn’t yet add an overall license file to the repository.  Licensing the software should be agreed upon by the contributors.
>> The suggestion by Will Rogers was to use the Apache Licence 2.0.  If people have comments or other suggestions, let us know here
>> on the mailing list, otherwise we will go ahead with this license.
>> 
>> For continuing development, we will be migrating over to GitHub in the near future.  As of now, the at2devel branch on SourceForge is no longer
>> operational.  Please don’t make any new commits to this repository.  If we need to issue some bug fixes in the near future, we can
>> create branches for this purpose to merge back into the trunk.
>> 
>> Thanks to all who contributed to this release!!
>> 
>> Best regards,
>> Boaz
>> 
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org <http://slashdot.org/>! http://sdm.link/slashdot <http://sdm.link/slashdot>_______________________________________________
>> Atcollab-general mailing list
>> Atc...@li... <mailto:Atc...@li...>
>> https://lists.sourceforge.net/lists/listinfo/atcollab-general <https://lists.sourceforge.net/lists/listinfo/atcollab-general>