Edit page FlossContributionFAIL

[wiki.git] / FlossContributionFAIL

diff --git a/FlossContributionFAIL b/FlossContributionFAIL
index 9a2d15143bba7ea00aef96098a756d35240a0d29..4f7385c73e442976c4ec9af65e4f5b8230a2cd47 100644 (file)
--- a/FlossContributionFAIL
+++ b/FlossContributionFAIL
@@ -1,17 +1,17 @@
 == How to tell if contributing to a FLOSS project is doomed to FAIL ==
 
 === Contributor License Agreements ===
- - Your project requires a CLA: 10 points of FAIL
- - The CLA donates code to a for-profit who competes with potential contributors: +50 points of FAIL
- - The CLA doesn't give full rights on the contribution back to the contributor: +100 points of FAIL
+ * Your project requires a CLA: 10 points of FAIL
+ * The CLA donates code to a for-profit [+20 points of FAIL]
+ * The CLA donates code to an entity whch competes with other potential contributors: +50 points of FAIL
+ * The CLA doesn't give full rights on the contribution back to the contributor: +100 points of FAIL
 
-=== Review process ===
- - Code review process is not documented [+10 points of FAIL]
- - Current review process differ from documentation [+5 points of FAIL]
- - Simple patches require the agreement of multiple maintainers [+20 points of FAIL]
- - Review process requires filing a ticket in a bug tracker for each patch [+20 points of FAIL]
- - Patches must be reviewed in a bug tracker [+50 points of FAIL]
- - Patches must be thrown at a review system or mailing-list, without naming a specific reviewer [+100 points of FAIL]
- - Large portions of your code base have no designated maintainer [+50 points of FAIL]
- - A clear maintainer exists, but is inactive, unresponsive or unwilling to review patches [+100 points of FAIL]
- - 
\ No newline at end of file
+=== Code review process ===
+ * Review process is not discoverable nor documented [+10 points of FAIL]
+ * Current review process differ from documentation [+5 points of FAIL]
+ * Simple patches require the agreement of multiple maintainers [+20 points of FAIL]
+ * Review process requires filing a ticket in a bug tracker for each patch [+20 points of FAIL]
+ * Patches must be reviewed in a bug tracker [+50 points of FAIL]
+ * Patches must be thrown at a review system or mailing-list, without naming a specific reviewer [+100 points of FAIL]
+ * Large portions of your code base have no designated maintainer [+50 points of FAIL]
+ * A clear maintainer exists, but is inactive, unresponsive or unwilling to review patches [+100 points of FAIL]