Austin S. Hemmelgarn

> The installer failed to write files when the Netdata service is already running. Users has to stop the service for installer to work. > > So, the installer should...

Quick update on this from my end: - Most of item 4 was resolved by #18230. - Item 3 and the rest of item 4 will be mostly fixed indirectly...

Item 6 will be resolved by #18251.

@thiagoftsm > @Ferroin I am still having some local issues with https://github.com/netdata/netdata/pull/18010 that fixed 3 and 4, let me know how I can help you for we finish this. I’m...

> > area/collectors: Functionally replaced by existing collectors/* labels for specific collectors. > > It is not. Few examples of how I use it: > > * an issue with...

> It is very desirable to not delete it, the suggested approach (_the presence of collectors/* and no other associated area tag_) doesn't work for me: > > * as...

> @Ferroin how will this effect existing issues? Would we need some sort of script to relabel them based on new mapping etc? or is that somehow something that can...

> @Ferroin are you going to address [this](https://app.codacy.com/gh/netdata/netdata/pullRequest?prid=11305941) codacy warning. Codacy still hasn’t learned about PEP 634 structural pattern matching yet, so it’s still throwing false positives like this.

> > Labels that should be project views instead: Customer Success, config. manager, distributed auth, Use Cases, and all of the *-team labels (which should not only be project views,...

> In general, I like all the suggestions here, though I'm not quite sure about moving label management to a file. The Github UI to add and manage labels will...