Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

requirements for nobloat.org listed projects #1

Open
10 tasks
cinemast opened this issue May 31, 2020 · 1 comment
Open
10 tasks

requirements for nobloat.org listed projects #1

cinemast opened this issue May 31, 2020 · 1 comment

Comments

@cinemast
Copy link
Member

cinemast commented May 31, 2020

For components

  • the project has no dependencies
  • if the project has (dev, runtime, or external) dependencies they are explicitly listed, well justified (e.g. in the README) and the size is cont. monitored.
  • the resulting artifact sizes are measured
  • the user is not forced to adopt a certain architecture / framework in order to use the component
    • E.g React forces the reactive paradigm on the user of components
  • downstream developers can easily grab just the parts they need (copy/paste, modular independent components)
    • avoid common/core components which are required by all other components
  • the scope of the component is clearly defined (goals + non-goals) in the README
  • coverage analysis for the typical use-cases of the component should result in > 90% usage

For applications

  • the resulting artifact sizes are measured
  • the resulting arrtifacts have been optimized (e.g. stripped of debug-symbols, etc.)
  • should be able to run in a standalone-mode without requireing the user to install additional runtimes/frameworks.
@cinemast
Copy link
Member Author

Idea for an automated tool: https://github.com/nobloat/ruler

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant