Antoine Brunet

Ok I'll setup the PRBEM/IRBEM-extras repository. I think it's okay to have a simple repository with everything in the extras folder without messing with submodules. Plus this way we can easily preserve the SVN history the same way it was done for IRBEM. I agree with you concerning the github pages, I'll open an issue about this on the IRBEM github.

Paul, thanks for pointing this to me. As far as I can tell the extras folder contains separate projects that are not integrated (for now) in IRBEM. If some or all of these projects are still relevant, I see the following options : - Creating a separete github repo for each of the extras projects. These could be under the PRBEM github organization, with a dedicated development team (or the IRBEM-dev github team). - Creating a IRBEM-extras github repo with all the extras. This could be the simplest...

Hello to all IRBEM contributors, I have tried to send this message to the dev mailing list, but it looks like it's not reaching you. As discussed in the lastest PRBEM meeting, there seems to be a strong consensus towards migrating IRBEM to the Github platform. I am currently setting up a Github Organisation to manage the PRBEM activities on Github, the first of which will be a IRBEM development team and repository. As IRBEM contributors, you probably should be part of this team on the github platform...