From: Sean P. <sea...@ma...> - 2012-11-07 00:37:09
|
I setup a section on our wiki to document the transition to github. That can be found here: http://stlab.adobe.com/wiki/index.php/Github_migration Not a lot there at the moment - but should be enough to get people started. Sean On Tue, Nov 6, 2012 at 3:15 PM, Sean Parent <sea...@ma...> wrote: > I've started what is planned to be a long migration of ASL to github. The > ASL perforce database is now locked. > > You can find the current ASL mainline sources at: > > github/stlab/legacy > > The reason why they are in the legacy repo is that I plan to move the > libraries to a structure conforming with the boost modular libraries > (github/boost-lib). > > I will be starting with some of the libraries I've been using in a product > I've been working on at Adobe (currently these are forked from ASL, so I'm > doing this as part of upstreaming that work). > > Beside moving to github and module based libraries, I'm also working on: > > Updating ASL to C++11, removing unnecessary dependencies from boost (where > C++11 libraries suffice) and removing overlap with newer boost libraries. > > Simplifying ASL by removing the ABI stable support for those libraries > that use it, and taking a more pragmatic approach to the libraries (many > were done as experiments where the complexity is unwarranted given the > results). > > As modules are split out and cleaned up I plan to propose them for > inclusion in boost as appropriate. > > I'd also like to consolidate as much of the remaining > ASL infrastructure (we currently have mailing lists and issue tracking on > source forge, website and wiki hosted by Adobe, and now source code moving > to github). Suggestions and recommendations welcome. > > I'm hoping that moving to github will make it easier to collaborate with > others on ASL. If you would like to help, let me know. If you have > suggestions, let me know. > > Thanks, > Sean > |