rmannibucau commented on PR #577:
URL: https://github.com/apache/kafka-site/pull/577#issuecomment-1884622256

   @mimaison well I wouldn't say red flags but I fully understand the surprise 
on kafka side if it was never discussed on/offline first - we had the same 
debate on TomEE side years ago.
   But it is not uncommon at apache to have such a page, even with a single 
company or even with no company and request for companies:
   
   * https://hop.apache.org/community/commercial/ (0)
   * https://struts.apache.org/commercial-support.html (1)
   * https://directory.apache.org/commercial-support.html (1)
   * https://superset.apache.org/community (direct link to the company behind - 
this one is more surprising for me since instead of encouraging the 
"registration" of vendors it hides it somehow but guess it is a small 
clumsiness)
   * https://tomee.apache.org/commercial-support.html (2)
   * https://plc4x.apache.org/users/commercial-support.html (2)
   * https://camel.apache.org/community/support/
   * https://openmeetings.apache.org/commercial-support.html
   * https://guacamole.apache.org/support/
   * 
https://cwiki.apache.org/confluence/display/HADOOP2/Distributions+and+Commercial+Support
   * https://activemq.apache.org/support
   * https://netbeans.apache.org/front/main/help/commercial-support/
   * https://royale.apache.org/royale-commercial-support/
   * (way more but guess you got the idea)
   
   To give an example of the "rationale behind" please have a look to 
https://github.com/apache/superset/issues/8852 issue.
   
   An important point to take into consideration is that several products - and 
I think Kafka is exactly there - wouldn't live without external support (it is 
true for most broker or server) so it is guaranteeing its community and helping 
its user base to do this kind of page - and trust me, ~5 years ago I didn't 
understand that as well as today so I say it very humbly.
   
   So overall, due to kafka adoption it can only be good to get such a page 
IMHO but I agree that if you feel it is not straight forward and it must be 
discussed more deeply cause Kafka wants to write its own content, a thread 
sounds the way to move it forward and a core commiter should then probably take 
the leadership on that "doc" track and this pr marked as pending while this 
work is done.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@kafka.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to