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

question(licensing): coordinate Cloud scope and contributor communication

Aperta
  • Qualcosa non va?
#2,201 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
20/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
go
Ambito
developer-experience

Direzione di ricerca

Start with the root LICENSE, GitHub contribution terms, and the cited cloudserver, cloudstore, dashboard, auth, Dockerfile, and cloud-image workflow references. The issue says the bounded audit did not establish complete provenance or a specific additional-consent gap. A maintainer decision would need to settle rights-holder authority, Cloud scope, licensor, license variant, and version cutoff before any proposal; no code change is requested.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

status:needs-review type:question
Existing Issue Search
  • I searched existing issues and will add evidence to a canonical tracker when applicable.
Question

What scope, provenance evidence, and contributor communication process should be settled before considering a change to the Engram Cloud server license?

Informational coordination only. This is not a request for legal acceptance or contributor signatures. It does not authorize implementation, a license change, a CLA rollout, a PR, or individual contributor outreach.

Why does this need issue tracking?

A bounded public audit identified durable policy and technical decisions that should not be conflated with a blanket request for contributor consent. A tracked question gives maintainers one place to distinguish documented permissions, actual gaps, and decisions that still need rights-holder or legal review.

Current licenses and contribution rules remain in force. This issue is not implementation approval.

Affected Area

Project workflow or policy

Release Context

Not release-specific. Public main snapshot: a6f66c2ea21f6ec2fcec4b4d6d54c576bb069897 (2026-10-28 21:06:49 UTC).

Additional Context
Direction under discussion, not a licensing decision
  • Keep Engram core and the Cloud client under MIT and preserve existing grants and notices.
  • Consider FSL 1.1 only for a precisely defined Cloud-server scope. The future MIT/Apache-2.0 variant, licensor and effective version cutoff remain undecided.
  • Welcome internal adoption by companies of any size and compatible third-party professional services. Paid consulting is not automatically a competing use.
Existing permission evidence
  • The root MIT license expressly permits modification, distribution, sublicensing and sale subject to notice preservation. Existing MIT grants cannot be withdrawn by publishing this issue.
  • Pico CSS 2.1.0 has MIT notices; the identified htmx 2.0.4 upstream license is 0BSD. Pico license, htmx license. Exact upstream asset-byte equivalence and shipped-notice coverage were not fully audited.
  • GitHub contribution terms describe a default inbound repository-license grant, not proof of actual ownership, employer authority or the absence of a separate agreement.
  • No specific additional-consent gap was established by this bounded audit. That is not legal clearance, and it does not establish that every contributor must sign again or that no additional permission could be needed.
Audit scope and limitations
Decisions still open
  1. Establish imported-code provenance, actual rights-holder authority and any applicable separate agreements.
  2. Define a prospective file/shared-package/binary-distribution scope, including third-party notices, before proposing effective license edits.
  3. Identify the licensor, exact FSL future-license variant and version cutoff; separately review any alternative commercial-licensing grant.
  4. Distinguish transparency notices from specific permission requests that are actually necessary. Silence or a reaction is not new consent.

Please keep this as an informational maintainer question. No blanket acceptance collection, individual collaborator mentions, CLA setup, PR or code/license change is requested here.

Lingua principale
Go
Stelle
7.1k
Fork
729
Merge medio
9h 5m
PR unite (30g)
301

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

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 Gentleman-Programming/engram

Tutte le issue di Gentleman-Programming/engram

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.