Hi Dan,
I disagree with this approach. We have a centralized source repository for a reason, if it is not up to the level you need we can discuss updating it / modifying it as necessary, since AMBER and AMBERTools are single 'products'. If I want to make small tweaks here and there to cpptraj I will make them in the 'official' AMBER git tree. If you want to keep a mirror on github fine but it will be your responsibility to migrate any changes made to the central repository to your github repository. You will also need to deal with any conflicts that might arise due to the official tree being out of date with your github tree.
This might seem like a good idea to you but keep in mind that it could rapidly degenerate into tens or even hundreds of github trees here and there for everyones pet component of AMBER Tools. There is no way I am going to be searching around to piece together all the little pieces, have multiple trees on my machine for each project etc.
In my opinion this is a BAD idea and it just dilutes the brand that is AMBER and makes it more difficult for us to all work as a team on a single product.
My $0.03.
All the best
Ross
> On Dec 4, 2015, at 10:03, Daniel Roe <daniel.r.roe.gmail.com> wrote:
>
> Hi All,
>
> I'd like to request that all future development of cpptraj be done via
> GitHub (https://github.com/Amber-MD/cpptraj). I've been doing all of
> my development there for a few months and I really like the
> development model. I have been periodically merging the changes on
> GitHub back into the main Amber repository. There are several
> advantages over developing in the main Amber repository:
>
> 1) It is a safer development model in that there is automated error
> checking. You do development on your own "fork" of the main GitHub
> repository, and then generate a "pull request" when you want to have
> your changes merged in. Before you can do this, the test cases are
> automatically run by Travis-CI (https://travis-ci.org). While this
> won't eliminate mistakes, it should reduce them.
>
> 2) The "Issues" feature of GitHub makes it easy to track
> cpptraj-related problems or feature requests. The GitHub web interface
> also has a lot of other nice tools for tracking development and
> collaborating.
>
> 3) It provides a mechanism to provide advanced users with the latest
> features, so now only critical bugs need to be addressed by AmberTools
> updates. Essentially the AmberTools version of cpptraj is the stable
> release, and the GitHub version is beta.
>
> If you have any questions, comments, or concerns, let me know. Thanks!
>
> -Dan
>
> --
> -------------------------
> Daniel R. Roe, PhD
> Department of Medicinal Chemistry
> University of Utah
> 30 South 2000 East, Room 307
> Salt Lake City, UT 84112-5820
> http://home.chpc.utah.edu/~cheatham/
> (801) 587-9652
> (801) 585-6208 (Fax)
>
> _______________________________________________
> AMBER-Developers mailing list
> AMBER-Developers.ambermd.org
> http://lists.ambermd.org/mailman/listinfo/amber-developers
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Sun Dec 06 2015 - 21:30:03 PST
