In the last couple of months we faced situations where the publiccode.yml:
- is a "placeholder" filled with Lorem Ipsum;
- is under construction (not totally filled);
- has been copied from another repo and the information contained inside are not related to the project;
- is a test repo;
- other possibilities.
As such, I wonder if it could be feasible to add a decentralized mechanism to tell the spiders not to index such a file.
I was thinking at something like a boolean "noindex" key which simply states whether the repo should be indexed or not yet.
What do you think about this?
I think that acting in a centralized way from the spider perspective (e.g., using something like a blacklist) is harder since it requires the intervention of the spider's responsibles who are external from the software publishers group, it does not scale, it is very error prone and it requires a communication channel to be established at least twice.
The main risk is of course that someone could leave the value to "true" and such a software would never be indexed.
What do you think?
In the last couple of months we faced situations where the
publiccode.yml:As such, I wonder if it could be feasible to add a decentralized mechanism to tell the spiders not to index such a file.
I was thinking at something like a boolean "noindex" key which simply states whether the repo should be indexed or not yet.
What do you think about this?
I think that acting in a centralized way from the spider perspective (e.g., using something like a blacklist) is harder since it requires the intervention of the spider's responsibles who are external from the software publishers group, it does not scale, it is very error prone and it requires a communication channel to be established at least twice.
The main risk is of course that someone could leave the value to "true" and such a software would never be indexed.
What do you think?