I am happy to share that we have started to move our development of MetaCG from an internal Gitlab to its public Github repository. Hooray \o/
The workflow can now follow the regular Github workflow, where you
- Fork the repository.
- Work on a feature. Preferrably in a feature branch off of devel.
- Open a PR against the devel branch.
- Go through normal code review and CI before merging the PR.
MetaCG started as a project during my PhD and has since seen a few contributors from the Institute of Scientific Computing. The development was done in a private Gitlab instance as this was suggested for research projects at the time and gave us the possibility to add, e.g., CI resources from the Compute Center without worrying about malicious actors. It was also nice to address the existing paranoia that someone could steal ideas or write a paper about something before you can.
However, since then, the MetaCG project has evolved quite a bit and is now less of a research project and more of “just some useful infrastructure”. This means that many of the things that are developed inside the MetaCG project can be developed easily in the open. Moreover, we have made good progress in getting (almost?) all parts ready to be built in a relatively standard container and run tests there. So, we just increased the coverage of our Github actions to provide some initial safety net. This will increase over time to make contributions easier and get back to the coverage that the project had with the internal CI resources.
With that being said, if you are curious about MetaCG, check out my old post about it and the idea behind it. Of course, feel free to check out the source, use it in your projects, and consider adding fixes and features. We are currently quite busy in adding more things to it and have started to improve the helper tools that ship with MetaCG.
No responses yet