search

datasciencecampus / coding-in-the-open

A compendium of open-source guidance which aims to share the benefits, risks and a summarised strategy for open-source coding.
https://datasciencecampus.github.io/coding-in-the-open/
MIT License
8 stars 0 forks source link

development labels #56

Open NicciPotts opened 1 year ago

NicciPotts commented 1 year ago

Feedback from survey

What's the difference between "Completed - Active" and "Maintained", and why isn't there an "Archived" option? The DSC package SynthGauge, for instance, is currently "Released" but we are looking to make it clear we will no longer be developing it, and will likely archive the repository.

and

The term "pre-release" is ambiguous. I assume it means prior to releasing as a package, but it could be confused with prior to release of the repo, which doesn't make sense on a publicly released repo. Also, unclear what label a repo where something was tried and finished, so is complete, but didn't meet design intentions.

and

Unfinished - Inactive, Deprecated/Superseded

and

Would it be helpful to also have a label for "deprecated" - ie something which is still released and out there, but which we don't advise people to use any more? Not sure... More generally, it's not clear these labels are intended to be exclusive. Presumably a repo can be all of "Complete - Active", "Released" and "Maintained"?

and

Deprecated (opposite to maintained

and

think I'd make it clear for the released repos whether they are going to be maintained. Basically one set of labels to cover the stage and one set of labels to say whether the code is maintained or not

NicciPotts commented 1 year ago

also linked to #55

r-leyshon commented 12 months ago

@LaurenceJones quick note that Turing Institute Contribution Guidance links to issue labels. Possibly a good idea to include something like that but for development labels in the CONTRIBUTING.MD of the repo template?