Georg J.P. Link

Hi Marco, How do you plan to deal with members who are in multiple teams? We’ve discussed this feature in the past and I don’t know whether or how much...

> Another option would be to have only one repository of code but I don't really like this idea because we usually try to produce tools that don't require the...

> The issues can be opened in the grimoirelab repository, tagged and then moved to the specific repository (github provides a features to transfer issues) by maintainers. I guess I...

Okay, so the author of an issue gets notified. When they come back to our issue tracker, do we expect them to remember that an issue had been moved? What...

Hi @valeriocos, I went back to read your original suggestion. Is the reason you want to keep different issue trackers so that you can easily see which issues relate to...

@valeriocos : > From an end-user perspective (someone that wants just to use grimoirelab) it makes sense to open an issue in the grimoirelab repo (e.g., #233). For users interested...

I agree that we seem to have discussed all relevant points and additional discussion would be fruitless. This is my last comment unless someone asks me a direct question. I...

For the tags, we can maybe use the name of the repository that it an issue belongs to: * `component:chaoss/grimoirelab-elk` * `component:chaoss/grimoirelab-sigils` * ...

> we won't be able to drill down to get specific numbers in terms of issues for each one of the sub-projects or components Does GrimoireLab support issue labels that...

> because CHAOSS started using GitHub (I don't know the reasons) There was no deliberation. We needed a platform that worked better than a wiki.