> > For Cordova tooling I expect no one outside of the developers to > really know what happens where - but if I see it correctly we almost > don't have any tooling JIRA issues as well, right? > There's plenty tooling related JIRA issues. And rightly so.
IMHO, joining all tooling packages in a mono-repo might be beneficial for this and other problems. But that is something for another day. That is indeed a problem that Github hasn't solved yet (afaik). One > can of course create individual issues, then mention the parent issue > there to create an automatic link between the issues. > > > (Can we > > productively use whatever tools GitHub provides here, or will we have to > > get permission from INFRA for every little thing we do?) > > Which tools do you refer to? External Kanban tool or something similar? > In general we are just Members of the Github repos and don't have any > power to change settings etc - Admin is only Apache, which means > INFRA. > I was thinking of "Projects". I saw them on the team level. Don't really know what they do though. But basically I was speaking hypothetically. Hoping someone with experience of that kind of GitHub usage would chime in.
