| [ee4j-pmc] Proposal: Request for explanations |
Dear Spec Committee and PMC, it would be great to have some explanations for recommendations, so committers and contributors would better and more easily understand the drivers behind each recommendation. For example, the document https://github.com/jakartaee/specification-committee/blob/master/operations.adoc#recommended-specification-project-repository-structure says that it is recommended to have one repo with spec + api plus a second repo with tck. This looks rather arbitraty. There could also be three repos, or just one, or one with api and one with spec + tck. While everybody might assume a good reson behind each recommendation, the document does not explain the actual aniticipated (or measured) benefit of exactly that solution compared to the other solutions. So it would be great if all recommendation documents would have some explanative text telling the exact reason for each recommendation / rule (for example in italics). :-) Thanks -Markus |