El lun, 30 oct 2023 a las 14:17, ricardo zanini fernandes (<[email protected]>) escribió: > > Hey folks! > > Last community meeting we had this topic pending regarding the > communication of opening issues. > > I understand that we must use kie-issues now for opening issues and not an > internal JIRA anymore. Great! I like GH issues more. Although, I have a few > Qs and observations > 1) Why use a central repository for opening issues and not opening issues > in the respective repository? This is the convention, and each repo might > have different requirements. Like adding different labels or bots. Having a > central repo for issues seems an anti-pattern.
I guess you mean issues by components like drools, jbpm, sonata, runtimes, cloud... ¿? +1 to that. Do you have a list ? > 2) Can't we have templates when opening issues? How do we communicate to > the community how to open issues? If we go with this central issues repo, > then we need to communicate in each repo that issues can't be opened there. > Or at least disable the issues tab via .asf.yaml file. This passes a weird > message to the community, IMO. The first impression is that we might not > accept issues. A newcomer will have to look for a contrib/readme file to > find where to open. Agreed. > 3) Do we have to migrate internal opening JIRAs to GH Issues? If so, can we > do it as we start working on them instead of a batch migration? N/A in our case as we are working with GH already. > Thank u! > -- > Zanini -- Saludos, Enrique González Martínez :) --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
