First of all how many are undocumented ? Do we have any statistics ? Personally I don't thinks it's a huge issue because most people use catalog as an easy install and not to discover new packages. I have not even bothered to read the ones that are documented. Frankly I don't mind because I always document and if I need a package I will just document it. On Sat, 11 Jun 2016 at 12:44, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:
2016-06-11 10:17 GMT+02:00 Esteban Lorenzano <estebanlm@gmail.com>:
On 11 Jun 2016, at 09:17, stepharo <stepharo@free.fr> wrote:
Esteban
The current catalog is an inbox. We should define the rules for the real ones and validate the entries.
Entries that are not described should not be put in the real catalog.
yes, but validation rules is something for the future. What do we do with the ones that now are in the inbox but do not fulfils the minimum requirements? This requires a fix now, and the possible fix is hide them⦠and report the non documented projects to this list, so people who maintain them can document it.
so, ideal: have a monkey process to run validations for newly added packages (btw, Pavel, I think the same âcatalog-updaterâ script can be extended for this.
OK!
possible right now: not showing the ones who are bad documented and then report periodically which ones should be documented.
Esteban
Stef
Le 10/6/16 à 14:52, Esteban Lorenzano a écrit :
Hi,
I was doing a pass on the catalog⦠I think is very negative that
non-documented projects appear there⦠because most people does not know what does projects are about and newcomers will find weird a project install tool with lots of projects without any description.
So I was thinking on put an option âshow allâ and hide those projects by default⦠but now I think those projects SHOULD NOT BE VISIBLE AT ALL, as a way of:
- offer better experience to non-power users, and - encourage people to actually document their projects⦠is very annoying to have so much of them without any documentation.
What do you think?
cheers, Esteban