2 ms·
Its probably a good idea to standardize things for everyones benefit and thats where the protocol key word kicks in. Tangentially on a personal note I find it
by sandeepkd 2mo ago
Its probably a good idea to standardize things for everyones benefit and thats where the protocol key word kicks in.
Tangentially on a personal note I find it offensive to use the word protocol when proposing a solution in the beginning at this early stage. My reservations extend all the way to MCP as well, glueing things together to make it work for your own use case isn't a worthy candidate to be a protocol. There is no mention of any committee members other than Recruitics which makes it hard to capture all the use cases, concerns, long term vision from different parties.
- fraywing 2mo agoHey there, totally understand your sentiment. We have seven other companies involved that are listed on the website and have provided feedback for general use-cases -- given adoption curves are super hard, early traction we have around OJCP is encouraging to me. A lot more to do, but any help or ideas are greatly appreciated. I'm chatting with other OSS organizations to help make sure this lands in no specific organizational control.
- sandeepkd 2mo agoI value the effort to standardize things and make them consistent, benefits everyone. I do appreciate you for taking lead here. However more than objection my worry is about the "PROTOCOL" key word being diluted. Imagine if everyone runs with it to solve their motivated use cases. Btw I am not sure if the other companies involved are listed on the publicly listed pages or internal one, would be good idea to check it again. All I checked was https://github.com/ojcp-org/ojcp/blob/main/GOVERNANCE.md https://github.com/ojcp-org/ojcp/blob/main/GOVERNANCE.md https://github.com/ojcp-org/ojcp/discussions https://github.com/ojcp-org/ojcp/discussions
- fraywing 2mo ago[dead]