Admission criteria? - Githubissues

lewtds / awesome-viet-foss

A curated list of FOSS projects originated by Vietnamese

Creative Commons Attribution Share Alike 4.0 International

24 stars 2 forks source link

Admission criteria? #1

Open lewtds opened 9 years ago

lewtds commented 9 years ago

Certainly we can't accept every single one out there. There must be a line somewhere. But what criteria should we rely on to decide which project gets in? For now, to be accepted, I think the projects should:

Have a FOSS license
Be useful in some way
Be original work (not a fork with little added value, but we may consider forks with heavy improvements)
Be known to the public (e.g. having more than maybe 10 stars on GitHub)
(more to be added)

cmpitg commented 9 years ago

Be actively developed?
Be a good piece of work (having coding convention with consistent style, having documentation, issue tracker, ...)?

However, I think those criteria should serve as a thin foundation to decide whether a project is worth honouring. A good project doesn't necessarily have to have all the criteria.

lewtds commented 9 years ago

These are exactly the two items I deliberately left out when writing this issue.

I'm edging toward requiring the projects to be actively maintained, so that people may not accidentally contribute to an inactive project only to see their contribution ignored. But if we do, a lot of good ones will be barred from entry, while they may still be a good learning opportunity for new developers. Another option is to still list them, but mark as unmaintained explicitly.

Your second point is also very valid, but IMHO, it's hard and considered rude to judge other people's work. Maybe I'm just being overly polite here, though. :-?

+1 last point.

cmpitg commented 9 years ago

Your first point leads to some questions: Does it matter whether or not a project is actively maintained? If it does, does it matter to display it explicitly in the project list?

IMHO, I'd answer no and no, for

the maintenance status of a project doesn't reflect its quality;
on the other hand, the "unmaintained" status is discouraging; speaking for myself, I often cross out an apparently-unmaintained project unless its title/purpose is really seducing, or when I have no other choice; besides,
sometimes, it's the idea that counts a lot

Regarding judging people's work, we would want to neither compare people nor their projects. The purpose is to honour good ones. And isn't "awesome" already subjective by its own mean? ;-).

cmpitg commented 9 years ago

@lewtds Any other thoughts on this matter? Shall we summarize and put this discussion somewhere in the README file?

cmpitg commented 9 years ago

@lewtds Heads up :-).

cmpitg commented 8 years ago

@lewtds Heads up man. Do you have time to maintain the repo?