You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, as Openconent we have different projects published in developers italia, one of which has a flat line as vitality index. It's quite strange because is our most active repository: 5 people working on it daily (15 total authors), many releases each weeks.
Is there something wrong with our repositories or is that flatline normal?
I checked the logs of the crawler using the API of developers italia, but they don't give information about the vitality parameters used the produce the index.
The text was updated successfully, but these errors were encountered:
Tried to experiment locally but the calculation was correct, turns out the crawler cache in the deployment's volume was stale, probably someway triggered by the rename.
Hi, as Openconent we have different projects published in developers italia, one of which has a flat line as vitality index. It's quite strange because is our most active repository: 5 people working on it daily (15 total authors), many releases each weeks.
The project is:
https://developers.italia.it/it/software/opencontent-stanza-del-cittadino-core-410a6e
The flat line:
A basic stat from gitlab:
If I check another project with just 1 active developer, I see an higher vitality index:
https://developers.italia.it/it/software/opencontent-opensegnalazioni-bd5f42
Vitality:
The same stat from gitlab:
Is there something wrong with our repositories or is that flatline normal?
I checked the logs of the crawler using the API of developers italia, but they don't give information about the vitality parameters used the produce the index.
The text was updated successfully, but these errors were encountered: