Open mentalisttraceur opened 1 year ago
Note: lots of technical projects have something like this. A couple examples:
I centered SRFI as the main example because of a key similarity: Scheme's RFIs are optional standardized extensions which keep the core spec minimal, and Conventional Commit's RFI would do the same.
The current spec seems to suggest just hosting extension specs in our own repos. Here's why I think a conventional-commits/requests-for-implementation
repo is a worthwhile addition over that:
Specifications hosted in the community org are much more likely to keep existing.
Specifications hosted in the community org are much easier to find (both discovering ones you don't know about which might be useful, and ones that you know about but don't know the location of).
I could not ask for a better illustration of these two points than the example extension mentioned in the FAQ, @jameswomack/conventional-commit-spec
, which either no longer exists, never existed, or exists somewhere that I was unable to find.
CCRFI-1
, that's clearly a "CCRFI". You learn once what a CCRFI is, and then you always recognize/know exactly what it what it is. What's the reference to an extension/proposal in someone's repo? jameswomack/conventional-commit-spec
could be almost anything, and needs context to even suspect that it's probably a repo on one of the code hosting websites. Even an explicit URL, without context, is just a URL. Meanwhile, the string CCRFI-42
could show up anywhere, with no context or even in a misleading context, and you could have a great chance of immediately identifying it as a reference to a CCRFI.I'm not sure I see value in this. Can you elaborate more on a use case you have that would benefit from this?
@damianopetrungaro probably not until I have recharged from how much effort I've put into very thoroughly covering the value more abstractly.
Hopefully someone else has more reserves of unpaid time/patience/desire/knack for concrete examples, or your mind will start to generate/notice examples now that you have the idea.
The Conventional Commits community would benefit a lot from mimicking Scheme's "Request for Implementation" (SFRI) process to coordinate common (or nontrivial-to-design-well) extensions.
This would allow us to
So I propose:
requests-for-implementation
repo under theconventional-commits
org.