Added as proposed: "awaiting-feedback" - @Lukasz feel free to add rules accordingly.
Reduced the number of labels from 63 to 29 labels. Added descriptions to most of them and re-added to most of the issues at best effort. Cheers, Lukas Am Fr., 5. Juli 2024 um 11:19 Uhr schrieb Łukasz Dywicki < l...@code-house.org>: > One suggestion - the 'pending-close' label might stay. Some issues we > have are stale/awaiting testing, we need some labels for that. Ideally > we could employ stale bot who would automatically close issues labelled > with 'pending-close' or 'awaiting-feedback' if no action is made by > reporter within a month or so. > > Its great that we have reporters, but not so great if they do not show > nor provide additional information within months from reporting issue > and receiving answer. > > Cheers, > Łukasz > > On 5.07.2024 08:48, Lukas Ott wrote: > > We currently have 63 labels: > > > https://docs.github.com/en/issues/using-labels-and-milestones-to-track-work/managing-labels > > > > instead of keeping plc4X which is internally understood I would keep the > > language label and the name of the protocol. > > > > What do you think? > > > > My suggestion would be the following: > > ADS -> keep > > API -> keep > > beginner -> keep > > BLOCKER-> keep > > bug-> keep > > build-> keep > > c-> keep > > CANopen-> keep > > code-Generation-> keep > > core -> delete > > CRITICAL -> keep > > dependencies-> keep > > docker-> keep > > documentation-> keep > > documentation-update -> delete > > driver-ads -> delete > > driver-modbus-> delete > > driver-opc-ua-> delete > > driver-profinet-> delete > > driver-s7-> delete > > duplicate -> keep > > easy-fix-> delete > > enhancement-> delete > > Ethernet/IP -> keep > > examples-> delete > > Fatek -> keep > > feature -> keep > > feature-request -> delete > > github_actions -> keep > > go -> keep > > good first issue -> keep > > help wanted -> keep > > improvement -> delete > > integration-camel -> keep > > integration-kafka-connect -> keep > > integration-nifi -> keep > > invalid-> delete > > java -> keep > > low-hanging-fruit -> delete > > MAJOR -> keep > > MINOR -> keep > > Modbus -> keep > > new feature -> delete > > newbie -> delete > > OPC-UA -> keep > > pending-close -> delete > > plc4c -> delete > > plc4j -> delete > > Profinet -> keep > > python -> keep > > Question -> delete > > scraper -> delete > > Task -> delete > > test-> delete > > testing-> delete > > TRIVIAL-> delete > > util-pool-> delete > > wish-> delete > > wontfix-> delete > > > > > > Regards > > Lukas > > > > Am Fr., 5. Juli 2024 um 08:24 Uhr schrieb Christofer Dutz < > > christofer.d...@c-ware.de>: > > > >> I also noticed that as each issue lists up all the names, it's hard to > >> search for "Modbus" for example. > >> > >> Chris > >> > >> Gesendet von Outlook für Android<https://aka.ms/AAb9ysg> > >> ________________________________ > >> From: Łukasz Dywicki <l...@code-house.org> > >> Sent: Friday, July 5, 2024 12:53:13 AM > >> To: dev@plc4x.apache.org <dev@plc4x.apache.org> > >> Subject: Labels, labels everywhere > >> > >> I've noticed that we have plenty of labels in github, which do overlap. > >> > >> For example: > >> Java, plc4j > >> OPC-UA, driver-opc-ua > >> ADS, driver-ads > >> > >> There are many more which probably come from JIRA import. > >> Can we clarify which we intend to use and re-assign elements/reduce > >> their number? > >> > >> Best, > >> Łukasz > >> > > >
