[Chaoss-software] [Meeting item] Collaboration of projects within the Software TC

Daniel Izquierdo dizquierdo at bitergia.com
Thu Oct 19 07:21:28 UTC 2017


Hi Jesús,

Thanks for this set of emails. Some comments in line.

On 18/10/17 00:49, Jesus M. Gonzalez-Barahona wrote:
> As I commented in the thread proposing our kick-off meeting as the
> CHAOSS TC, I'm going to start email threads with the proposed topics.
> Let's see if this works. If it doesn't work, I'll announce a time slot
> for a synchronous meeting next week.
>
> This is the first item that I proposed to discuss:
>
> * Item:
>
> According to our charter [1], we should "produce integrated, open
> source software for analyzing software development". So, we should
> discuss how to start working in this direction.
>
> [1] https://chaoss.community/about/governance/
>
> * Discussion:
>
> We have now three projects in the CHAOSS Software TC: Prospector,
> GrimoireLab, cregit. During the conversations that lead to the launch
> of CHAOSS, we decided that, at least for a start, the idea was to have
> GrimoireLab a the "glue" for all the projects, so that they would
> interoperate, at least to some extent, via GrimoireLab.
>
> In this regard, Prospector is already integrated, since it was ported
> to use GrimoireLab/Perceval for data retrieval when it was updated to
> newer versions of its dependencies.
>
> WRT cregit, I've talked to Daniel German about using a new Perceval
> backend to extract the information it produces, and then showing it
> GrimoireLab dashboards. In fact, I have a Perceval backend wrote that,
> improved, could do the trick. But i need to find some time to update
> and improve it.
>
> Then, I would like to find ways of including other projects, which
> could cover areas not already covered. Since GrimoireLab produces
> comprehensive databases with a lot of data from the original
> repositories, this should be easy. Any idea in this respect is welcome.

I'd say that we should produce some kind of on boarding guidelines. This 
typically helps people to understand where to start from several points 
of view.

For instance,

* What do I need to do if I want to integrate a non-supported data source?

  + First, this developer needs to check if that data source is not 
currently supported

  + Then, the developer should start in some place: a new Perceval 
backend? directly creating a new ElasticSearch index?

  + How should I define a new ElasticSearch index? are there guidelines? 
recommendations?

>
> There is also an specific case that maybe we could consider, which is
> ghData [2]. Since it is being actively used by the Metrics TC, it would
> be specially interesting to find ways of integrating it with
> GrimoireLab. Sean and me talked briefly about this in LA, and maybe we
> can try to follow the discussion.
>
> [2] https://github.com/OSSHealth/ghdata

This would be a great example of how to integrate things and may help to 
start that on boarding guideline.

Regards,
Daniel.

>
> As I understand it, currently ghData gets data from GHTorrent and
> GitHub. Maybe one step to walk would be to explore to which extent we
> could have a Perceval backend to query git, GitHub or other data
> sources not currently supported. Or interfacing directly to the
> GrimoireELK database. (for a brief explanation of the role of Perceval
> and GrimoireELK in GrimoireLab, please have a look at [3] [4] [5]).
>
> [3] https://grimoirelab.gitbooks.io/training/grimoirelab/intro.html
> [4] https://grimoirelab.gitbooks.io/training/grimoirelab/intro/components.html
> [5] https://grimoirelab.gitbooks.io/training/grimoirelab/intro/scenarios.html
>
> Any comments on any of this?
>
> Saludos,
>
> 	Jesus.
>

-- 
Daniel Izquierdo Cortazar, PhD
Chief Data Officer
---------
"Software Analytics for your peace of mind"
www.bitergia.com
@bitergia



More information about the Chaoss-software mailing list