Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Document IP Policy

Aperta
#31 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@achrinza ci sta già lavorando.

Dal 11/5/2022.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

P3

Formally document the IP Policy of the LoopBack Project, which may include:

  • Supported licenses
  • Copyright notices
  • Exceptions granted by the board

The IP Policy must be within the constraints of https://github.com/openjs-foundation/cross-project-council/blob/845960f44870e731c1208497c154952a87468b8d/governance/IP_POLICY_GUIDANCE.md.

Git Repository licenses to check

We'll need to check the licenses of our Git Repositories to ensure they're compliant with the list from the OpenJS Foundation IP Policy Guidance document.

For those with incompatible licenses:

  • If there's no DCO sign-offs, we can change the license immdiately
  • If there's DCO sign-offs...
    • If it's a StrongLoop/IBM maintainer or a maintainer that has signed the CLA, we can the change the license(?)
    • If it's an active maintainer, get their permissions to change the license.
    • If it's own outside contributor, we may need to get their permission to change the license(?)
    • Otherwise, we may need to get an exception from the OpenJS Foundation.

A tick represents a compatible license and not outstanding issues,

  • cicd - MIT License
  • explorer.loopback.io - MIT License
  • loopback-connector - MIT License
  • loopback-connector-cassandra - MIT LIcense
  • loopback-connector-cloudant - Artistic License 2.0
    • DCO sign-offs:
      • @/dhmlau (IBM)
  • loopback-connector-couchdb2 - Apache License, Version 2.0
  • loopback-connector-dashdb - Artistic License 2.0
    • DCO sign-offs:
      • @/dhmlau (IBM)
  • loopback-connector-db2 - Artistic License 2.0
    • DCO sign-offs:
      • @/dhmlau (IBM)
      • @/pktippa (Outside contributor)
  • loopback-connector-elastic-search - MIT License
  • loopback-connector-grpc - MIT License
  • loopback-connector-kv-extreme-scale - MIT License
  • loopback-connector-kv-redis - MIT License
  • loopback-connector-mongodb - MIT License
  • loopback-connector-mssql - MIT License
  • loopback-connector-mysql - MIT License
  • loopback-connector-openapi - MIT License
  • loopback-connector-oracle - MIT License
  • loopback-connector-postgresql - Artistic License 2.0
    • DCO sign-offs:
      • @/dhmlau (IBM)
      • @/akshatdubeysf (Sourcefuse)
  • loopback-connector-redis - MIT License
  • loopback-connector-rest - MIT License
  • loopback-connector-soap - MIT License
  • loopback-connector-sqlite3 - Artistic License 2.0
    • DCO sign-offs:
      • @/achrinza (TSC Member)
      • @/dhmlau (IBM)
  • loopback-datasource-juggler - MIT License
  • loopback-ibmdb - Artistic License 2.0
    • DCO sign-offs:
      • @/dhmlau (IBM)
  • loopback-next - MIT License
  • loopback.io - MIT License
  • loopback4-example-kafka - MIT License
  • loopback4-example-shopping - MIT License
  • loopback4-extension-grpc - MIT License
  • project-contacts - No License
  • security - MIT License
    • Check if we dual-license our security advisories under CC-0 for compatibility with other advisory databases (e.g. GitHub Advisory Database)
  • strong-error-handler - MIT License
  • strong-soap - MIT License

see also: https://github.com/loopbackio/loopback-connector-sqlite3/issues/10

Lingua principale
Nessun dato sulla lingua
Stelle
0
Fork
0
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di loopbackio/loopback-governance

Tutte le issue di loopbackio/loopback-governance

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.