valerio

Hi @MonikaEve, thank you for your interest in GrimoireLab, and indeed you are more than welcome to contribute to it. If you want to get a glimpse of GrimoireLab, you...

Sure @MonikaEve , @sduenas and myself will be happy to set up a call, just ping us when you are ready :)

Thank you for letting us know, enjoy!

1. Issue/pr comments are in the raw indexes but are not propagated to the dashboards. However, as you can see [here](https://github.com/chaoss/grimoirelab-elk/blob/master/grimoire_elk/enriched/github.py#L272), comments info is used to derive some metrics such...

> @valeriocos When is this release to be expected? It's already out (currently we are in 0.2.42) > Are those 2 scripts supposed to be ran only when upgrading to...

It would be easier to define a process, where issues are first opened to the grimoirelab repository. The maintainers review them and add labels based on the component(s) involved. Issues...

> @valeriocos the problem that I see with that workflow is that requires a lot of interaction and it's prone to errors. You might either forget to open a new...

the contributor should receive a notification about the issue that has been transfered: https://help.github.com/en/github/managing-your-work-on-github/transferring-an-issue-to-another-repository > People or teams who are mentioned in the issue will receive a notification letting them...

@GeorgLink @sduenas , this is the reason why I suggested at https://github.com/chaoss/grimoirelab/issues/284#issuecomment-582367772 to open the issues in the grimoirelab repository (this one), and then the maintainers take care of creating...

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., https://github.com/chaoss/grimoirelab/issues/233). For users interested in single tools...