Add More Data

The data you can add to your instance can be basically classified in two buckets:

• data repositories: source code repositories, trackers, mailing lists, chat rooms, etc.
• affiliations: contributor data (name, email, usernames), organizations (names and domains) and the relationship between contributors and organizations (enrollments).

How to Add More Data

In case you want to add more repositories to your Bitergia Analytics instance, we recommend creating a support ticket with your request. Bitergia has in its mid-term plan to create a user interface to add those repositories. In the meantime, there is a way to take control of this by modifying a JSON file with the list of repositories for each project.

Organizing Data

Some customers organize their repositories in groups. This is especially useful when you have many.

By Project - standard

An open source project may have more than one repository, so it usually makes sense to look at them together as a whole. This is the standard way of organizing repositories.

The project-repository assignment is custom to your dashboard and we need you to provide it to us. Once assigned, the data of each repository gets a project field with the assigned value that can then be used to filter.

Classifying Projects - advanced

Some open source communities have several open source projects that fall into different groupings. For example,

• per maturity level of the project governance: Sandbox, Incubating, Graduated.
• per technology: IoT, AI, Web, Network, Multimedia, Critical, ...
• per vertical market segment: Aerospatial, Medical, E-commerce, Automotive, ...

We can create custom fields per project to create other independent classifications to support these classifications. You can let us know how you want to group your projects, including the reasons for wanting the groups, and we can discuss the best solution for your use case.

Classifying Repositories - advanced

It can be useful to create custom groupings of repositories that span multiple projects. For example, in a community of multiple projects, each project could have a repository dedicated to receiving improvement requests. Analyzing the activity across all projects can give insights into who is making improvement requests not just in one project but across the community.

We create these custom groupings of repositories by assigning custom labels. This allows for finer granularity but is also very burdensome to maintain as projects evolve and repositories get added and removed.

Affiliation Data

The information about how to extend data from contributors or/and organizations is available in the affiliations section.