Open source uDALES

[dmey]

We should discuss if and when the project is going to be open-sourced and what needs to be done before then.

[bss116]

As briefly discussed: we will need to consider how to deal with branches -- some are supposed to be open source (e.g. python processing development branch) and some should be private (e.g. code development on modelling trees).

[dmey]

It is common to have the main repo public and for users/contributors to have their own (private) fork under their own account -- If that is the case we just need to document this and delete any of the branches we don't want to have public at uDALES/u-dales

[dmey]

@bss116 does this need to be discuss at the next meeting/chat? In a way this relates to how users/developers are supposed to work with this repo (i.e. #44).

[bss116]

@dmey we can discuss this when we feel the code is ready to be released (not sure this will be already the next meeting 😉), i.e. after milestone 0.1.0 (or maybe 0.2.0).

[bss116]

Note: We need to put tests for macos and debug back in before open sourcing the code (undo #111).