Is it normal practice in Github for a valid issue to be closed if the Dev can't work on it at the moment?

This page summarizes the projects mentioned and recommended in the original post on /r/opensource

InfluxDB - 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.
www.influxdata.com
featured
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com
featured
  • Back In Time

    Back In Time - An easy-to-use backup tool for GNU Linux using rsync in the back

  • In my own project we do it more transparent. We close if there is a good reason for it. We don't close just because no one is working on something. If there are no resources to work in it now but it seems important we keep it open until it is fixed. We do use milestones and priority labels to give the users an idea about our plans.

  • InfluxDB

    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.

    InfluxDB logo
NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts

  • Opportunity for beginners: Some code cleaning in "Back In Time"

    1 project | /r/opensource | 7 Dec 2023
  • Free software project "Back In Time" requests for translation

    1 project | /r/China | 13 Oct 2023
  • [English -> Portuguese EU / Brazil] Text about attracting translators to a FOSS project

    1 project | /r/translator | 1 Sep 2023
  • Free Software project "Back In Time" requests for translators

    1 project | /r/GREEK | 3 Jul 2023
  • Free Software project "Back In Time" requests for translators

    2 projects | /r/localization | 1 Jul 2023