Open Source Developers -- do you write up a product comparison that shows how your project measures up against other open source projects in the same category?

• inwee

  1 25 0.0 Shell

  Conveniently send text and commands from file or standard input to WeeChat with this wrapper around WeeChat's FIFO pipe

https://github.com/susam/inwee#without-inwee

• mintotp

  23 1,283 0.0 Python

  Minimal TOTP generator in 20 lines of Python

https://github.com/susam/mintotp#alternative-oath-toolkit

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• uncap

  13 1,024 0.0 C

  Map Caps Lock to Escape or any key to any key

https://github.com/susam/uncap#alternatives

• emacs4cl

  22 361 4.1 Emacs Lisp

  A tiny DIY kit to set up vanilla Emacs for Common Lisp programming

https://github.com/susam/emacs4cl#what-about-portacle

• analysis-pipelines

  2 12 0.0 Python

  Project CRANE (Crisis Racism and Narrative Evaluation) aims to support researchers and anti-racist organisations that wish to use state-of-the-art text analysis algorithms to study how specific events impact online hate speech and racist narratives. CRANE Toolbox is a Python package: once installed, the tools in CRANE are available as functions that users can use in their Python programs or directly through their terminal. CRANE targets users with basic programming but no machine learning skills

  

Do you know some of your users? They might be the ones to ask for help on your project description. Also, for feedback, as a user of open-source projects I don't usually volunteer detailed feedback. If I have a problem or need a new feature I might fill in an issue, but sometimes if there are no guidelines on how to report/request things I feel like my feedback wouldn't be welcome. So maybe add guidelines for that in the FAQ section? Doesn't have to be complex, just an invitation for people to communicate with you through issues, saying you welcome support requests and/or feature requests if you do. Issue templates might be useful too. (An example of mine for inspiration) And if you have specific points you want users to give feedback on, don't hesitate to add a message redirecting to a dedicated issue in your Readme.

• InfluxDB

  www.influxdata.com sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

Suggest a related project