NOTE: Article in Progress
Large number of open-source projects
overwhelmed with all names
project details distributed over multiple places
more and more features expected from current gen application
other side, less but better (less features, but done perfectly)? e.g., terminal commands? then using piping
many projects doing the same thing in different ways, certain subtle features
comparison: parameters for comparison?
possible parameters: documentation, learning curve, response time, ease of integration with other tools, licence, active development?
parameters: API for various programming languages, REST API, graphical user interface, command line options, distributed, centralized/decentralized, asynchronous/synchronous API operations, targeted platforms? domain specific parameters? flexibility? supported algorithms?
svg diagrams: overview / overall picture
multi-user? multi-profile per user like firefox? collaborative?
svg diagrams: storage
interactive
threads? asynchronous/synchronous operations?
resources linked to external sources (like wikipedia, RDF)
evolution of requirements like the resources involved and associated interfaces
project recommended for a purpose?
distributed (computing/storage) by default? single or multiple machines
available interfaces (visual, commandline)
resource access (shareable URLs)? search/filter?
configurable backend especially for storage?
References
- Chełkowski, Tadeusz, et al. "Inequalities in Open Source Software Development: Analysis of Contributor’s Commits in Apache Software Foundation Projects." PLOS ONE, edited by Christophe Antoniewski, vol. 11, no. 4, Apr. 2016, p. e0152976. DOI.org (Crossref), doi:10.1371/journal.pone.0152976.
- Open Source
- Project
