[improve][client] Optimize Third-Party Client Matrix Page
See original GitHub issueThird-Party Client Matrix Page: https://pulsar.apache.org/docs/next/client-libraries
-
Some clients are obsolete, they have not been updated for a long time, should we still show them?
-
What’s the definition of “obsolete client”? For example, a client was last updated before a certain date or something else?
-
Can we show the
last update time
automatically in the third-party client matrix doc as we did in Pulsar README? -
Is it better not to include
pulsar
in the third-party client name to avoid misrepresentation? For example, the third-party Go client,[pulsar-client-go](https://github.com/Comcast/pulsar-client-go)
, looks like the official client, while[pulsar-client-go](https://github.com/apache/pulsar-client-go)
is the official one.
🔹🔹🔹🔹🔹🔹
Any thoughts or anyone would like to implement? Thank you!
🔹🔹🔹🔹🔹🔹
@BewareMyPower thanks for your suggestions!
Issue Analytics
- State:
- Created a year ago
- Comments:9 (7 by maintainers)
Top GitHub Comments
I’m going to replace the “Star” column with a “Badges” column to show badges including stars and last commit. Will investigate a patch by next week.
@Anonymitaet I’m glad to review a patch with its preview. But if you ask me to implement it, perhaps I’ll try to take it later this month. FYI, there’re some predefined “GitHub badges” you can use - search with the keyword.
~What if we create a new issue to track this dedicated topic? I don’t think it’s good we discuss everything about “Optimize Third-Party Client Matrix Page” under this issue without a clear boundary. Open-ended discussions should go to Discussions or mailing lists.~
Well. I see that it’s included in the original proposal. It can be helpful. But we don’t add too much information to overwhelm users’ attention further. (I mean, add one column can be fine, but if we later propose to add more and more columns, it may be bad.)