As everyone in this list likely know, the two "official" channels used by the YaST Team at SUSE to track changes requested to YaST are:
- https://bugzilla.suse.com (also available as https://bugzilla.opensuse.org) - https://jira.suse.com (also open for openSUSE feature requests) We have well-established mechanisms to process the constant flow of Bugzilla and Jira entries and to track them over time. But since we are getting more and more request via Github issues, we agreed to establish some procedure to try to ensure requests via Github don't get overlooked and forgotten. Today we decided we will create a few labels in all repositories under the YaST organization at Github (we got a script to do perform such batch creation in all repos) and we will use them to know if a given issue needs attention. So this mail is a RFC for the initial set of labels. Please feel free to propose any enhancement, specially to the names of the labels that I just made up. We kind of agreed to start with these four: 1) Label "feedback" To mark issues that are used to discuss future enhancements or relatively general topics. Examples: https://github.com/yast/yast-firstboot/issues/115, https://github.com/yast/yast-installation/issues/903 and all their associated (sub)issues. 2) Label "tracked" To mark bug reports or feature requests that are already processed by someone in the team and have a counterpart in the official Bugzilla, Jira or in the internal Trello board of the YaST Team. That would be the equivalent of moving a bugzilla bug from yast2-maintaners to yast-internal. 3) Label "other-maintainer" To mark issues associated to YaST repositories and/or functionalities that are not maintained by the core YaST Team. Examples: https://github.com/yast/yast-auth-server/issues or https://github.com/yast/yast-crowbar/issues/68 4) Label "needinfo" Similar to the corresponding flag in bugzilla. The main difference is that the YaST Team will need to take full care of the label (eg. removing it if the info was already provided) since not everyone will have the rights to add/remove labels. As said, feel free to propose any change (including names). We plan to mass-create the tags tomorrow. Cheers. -- Ancor González Sosa YaST Team at SUSE Software Solutions
