Remove projects used for test or exercise

[BrandonMrBot]

@kauedesousa description:

Trials with these keywords c("chocolate","egg","exercise","excercice","excerise" "example","playground","excesise","exrcsie","exersice","test", 'choco') should be removed or not exposed through the API. Also we need to find a way to identify real trials from the test / exercise trials in the platform.

@marieALaporte comments:

• It's crucial to have more than just keywords to identify whether a project is a dummy or not. While I support the idea of having a dedicated server for this purpose, I am open to other solutions.
• Dummy projects should be automatically deleted from the server after a certain period of time. Given that they incur costs, such as storage, it's essential to manage them efficiently.
• ALL API endpoints should not expose data from these projects except if @kauedesousa is teaching how to use the API during his course.

[BrandonMrBot]

Point 1:

I agree, I understand that we are doing this exercise in order to make it faster to identify those existing test projects and help Kaue as soon as possible.

It is possible that some projects do not have those keywords and are test as well, that is why in ClimMob we are designing an interface that forces users to provide that information (If the project is Real/Training) and also if the project is already finished.

Another action we can perform is, in the creation of the project the users must indicate if the project is Real/Training. What do you think?

Point 2:

I agree, we will create the necessary procedures for this, initially we will only delete the repositories created on disk that are the ones that consume more storage, later we will consider deleting the information from the database, but it seems to us that it would also be important to have statistics if we want to know how many people trained as project managers we have in ClimMob and things like that.

Point 3

Perfect, I'll check this

[MarManrow]

@marieALaporte , we will store the curation you provided, but we will also use this feature to ask users for their own categorizations. This is because, after we removed (or hid) some projects based on your and @kauedesousa's suggestions, some users requested reactivating specific projects. With this implementation, we could conduct a double cross-validation.

Let me know if you'd like further adjustments!