Transfer to rasg-affiliates

[piyanatk]

Should we transfer this repository to rasg-affiliates now, if that is allowed? Becoming rasg-affiliates is one of the long-term goals of this repository, and it makes more sense now that we do not only have collaborators from within UKZN.

@steven-murray Do you know if there is any requirement?

[steven-murray]

There are definite requirements: things like having CI setup, having installation instructions, linting, a basic test suite (I think there's some coverage level that they will require, but I can't remember it, and I can't find the document that outlines it). I will contact the group to find the requirements.

At this stage, I'd aim for basic CI setup and coverage tracking, and then contact the group for further info.

[steven-murray]

Do you know how to setup CI @piyanatk ?

[steven-murray]

The list of requirements is on the README here: https://github.com/RadioAstronomySoftwareGroup/RadioAstronomySoftwareGroup.github.io/tree/add_content.

Quote:

RASG-Affiliated Repos, in general, should have:

• Continuous integration (CI) set up to run tests & report coverage with badges on the README.
• A method for installing the repo using pip install . (even if the package is not on PyPI).
• A descriptive README.
• Code documentation, including but not limited to docstrings (we prefer the numpy docstring style, as described here).
• Meet pep8 code format standards (flake8 or pycodestyle can be used to enforce this).
• Permissive open source license (e.g., BSD or MIT, NOT a copyleft license such as the GPL). For some reading on the concerns around copyleft licenses see this, this and this.
• Signoff from the RASG managers. We will consider all of the above requirements and a plan for long-term support as criteria for support.

[piyanatk]

Do you know how to setup CI @piyanatk ?

I have been reading about about it, but no I do not at the moment.

[steven-murray]

To be doing what the cool kids do right now, you should probably go for Github Actions