License Clarification
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
Can the owners please clarify their interpretation of the AGPL?
Considering using the pm2 runtime to manage a nodejs app (pm2 installed on the server as a totally separate package and not included in the package.json of the nodejs app). Not using the analytics api. Only process manager.
Would the nodejs app managed by pm2 have to be open source?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names the pm2 runtime, a Node.js application, and the AGPL, but mentions no source file, test, or entry point. Start by reviewing the repository's licensing information and existing project documentation; done would require a maintainer-approved clarification of whether this deployment arrangement affects the application's licensing obligations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100