From 88279b1b28e117db4256a8197e5127dc80c65f36 Mon Sep 17 00:00:00 2001 From: Justin Dorfman Date: Mon, 23 Mar 2026 10:27:05 -0700 Subject: [PATCH] feat: governance and conduct pages, nav/footer, anchors, scroll offset Add Code of Conduct and Governance pages with shareable section anchors. Align site nav and footers with the home page; extend artwork footer links. Style .coc headings and anchor links; use html scroll-padding-top so fragment links clear the sticky header (with a taller offset on narrow viewports). Made-with: Cursor --- artwork.html | 11 +- assets/css/style.css | 56 ++++++++++ code-of-conduct.html | 115 +++++++++++++++++++++ governance.html | 238 +++++++++++++++++++++++++++++++++++++++++++ index.html | 7 +- 5 files changed, 420 insertions(+), 7 deletions(-) create mode 100644 code-of-conduct.html create mode 100644 governance.html diff --git a/artwork.html b/artwork.html index 1d525ea..bf70294 100644 --- a/artwork.html +++ b/artwork.html @@ -18,9 +18,8 @@ @@ -311,8 +310,10 @@

Logotype

© 2026 The SCIP Authors | Apache-2.0 license
Artwork - Discord - GitHub + Code of conduct + Governance + Discord + GitHub
diff --git a/assets/css/style.css b/assets/css/style.css index 558fea8..02868e4 100644 --- a/assets/css/style.css +++ b/assets/css/style.css @@ -3,12 +3,19 @@ --sky: #34c3e5; --paper: #fff3f0; --ink: #060000; + /* Sticky .nav: 12px + 65px logo + 12px padding + small buffer for borders */ + --sticky-nav-offset: 104px; } * { box-sizing: border-box; } +html { + /* Fragment / in-page links scroll so content isn’t hidden under sticky header */ + scroll-padding-top: var(--sticky-nav-offset); +} + body { margin: 0; font-family: "Inter", "Segoe UI", "Helvetica Neue", Arial, sans-serif; @@ -415,7 +422,56 @@ a { border-radius: 4px; } +.coc .coc-heading { + font-size: 20px; + margin: 28px 0 12px; +} + +.coc .coc-heading:first-of-type { + margin-top: 0; +} + +.coc p:last-child { + margin-bottom: 0; +} + +.coc .coc-subheading { + font-size: 18px; + font-weight: 600; + margin: 24px 0 10px; +} + +.coc .coc-heading .coc-anchor, +.coc .coc-subheading .coc-anchor { + color: inherit; + text-decoration: none; +} + +.coc .coc-heading .coc-anchor:hover, +.coc .coc-subheading .coc-anchor:hover, +.coc .coc-heading .coc-anchor:focus-visible, +.coc .coc-subheading .coc-anchor:focus-visible { + text-decoration: underline; +} + +.coc code { + font-family: "SFMono-Regular", Consolas, "Liberation Mono", Menlo, monospace; + font-size: 0.92em; + background: rgba(6, 0, 0, 0.06); + padding: 2px 6px; + border-radius: 4px; +} + +.coc ol.list { + padding-left: 22px; +} + @media (max-width: 720px) { + :root { + /* Stacked logo + nav links sit taller than the single-row header */ + --sticky-nav-offset: 148px; + } + .nav { flex-direction: column; align-items: flex-start; diff --git a/code-of-conduct.html b/code-of-conduct.html new file mode 100644 index 0000000..c9a7e38 --- /dev/null +++ b/code-of-conduct.html @@ -0,0 +1,115 @@ + + + + + + + Code of Conduct - SCIP Code Intelligence Protocol + + + + +
+
+
+ + + +
+ +
+ +
+
+ Community +

SCIP’s Code of Conduct

+

+ How we work together on SCIP: respect, professionalism, and clear expectations. +

+
+
+ +
+
+

+ 1. The Core Principle +

+

+ Be a decent human being. We are all here to build cool things and solve problems. Treat others + with the same respect you expect for yourself. +

+ +

+ 2. Expected Behavior +

+
    +
  • Focus on the work: Critique ideas, not people.
    • +
  • Be welcoming: Help newcomers. We all started somewhere.
    • +
  • + Keep it professional: This is a space for software development, not for + harassment, soapboxing, or personal attacks. +
    • +
+ +

+ 3. What We Won’t Tolerate +

+
    +
  • + Harassment: This includes derogatory comments, threats, or unwanted sexual + attention. +
    • +
  • + Doxing: Sharing someone’s private information without consent is an immediate + ban. +
    • +
  • Trolling: Sustained disruption of threads or baiting others into arguments.
    • +
+ +

+ 4. Enforcement +

+

Let us know if someone acts inappropriately.

+
    +
  • + How to report: + community@sourcegraph.com +
    • +
  • + The Process: We will review the report. We aren't here to be the "thought + police," but we will take action to keep the project productive. +
    • +
  • + Consequences: Actions range from a private warning to a permanent ban from the + organization (Discord and/or GitHub). +
    • +
+ +

+ 5. Final Word +

+

Don’t make it weird. We just want to build a great project together.

+
+
+ + +
+ + diff --git a/governance.html b/governance.html new file mode 100644 index 0000000..8c2c27f --- /dev/null +++ b/governance.html @@ -0,0 +1,238 @@ + + + + + + + Governance - SCIP Code Intelligence Protocol + + + + +
+
+
+ + + +
+ +
+ +
+
+ Governance +

SCIP Project Governance

+

+ How SCIP stays stable and open: roles, the SEP process, and Core Steering Committee oversight. +

+
+
+ +
+
+

+ Overview +

+

+ The SCIP Code Intelligence Protocol (SCIP) is an open source project designed to provide a + standard format for indexing source code. +

+

+ To ensure the protocol remains stable, performant, and universally applicable, this project + operates under a Sponsor-Led Governance Model. This means that while we + encourage and rely on community contributions, the strategic direction and core protocol schema + are guided by a Core Steering Committee. This model is designed to foster a rich ecosystem of + language-specific indexers while maintaining a highly stable core. +

+ +

+ Roles and Responsibilities +

+ +

+ 1. Contributors +

+

+ Contributors are the lifeblood of SCIP. Anyone can be a Contributor by submitting pull requests, + opening issues, improving documentation, or participating in discussions. +

+
    +
  • + Responsibilities: Follow the + Code of Conduct and ensure PRs pass all + CI checks. +
    • +
+ +

+ 2. Domain Maintainers +

+

+ Because SCIP relies on a diverse ecosystem of language-specific indexers (e.g., + scip-typescript, scip-java), we delegate authority over specific domains + to Domain Maintainers. +

+
    +
  • + Authority: Domain Maintainers have merge rights (CODEOWNERS) over + their specific language indexers or tooling directories. They manage the day-to-day roadmap, + issue triage, and PR reviews for their domain. +
    • +
  • + Nomination: Contributors who demonstrate sustained, high-quality contributions + to a specific domain can be nominated by an existing Maintainer and approved by the Core + Steering Committee. +
    • +
+ +

+ 3. Core Steering Committee (CSC) +

+

+ The Core Steering Committee is the governing body of the SCIP project. It is responsible for + the overall architectural vision, core schema definitions, and final dispute resolution. +

+
    +
  • + Authority: The CSC has final approval over all core protocol changes, + cross-cutting architectural decisions, and the SCIP Enhancement Proposal (SEP) process. The CSC + has the authority to veto technical decisions that do not align with the project's long-term + stability. +
    • +
  • + Composition: The CSC is bootstrapped, and as the project matures, seats may be + offered to external Domain Maintainers who have demonstrated exceptional leadership and + cross-domain expertise. +
    • +
+ +

+ The SCIP Enhancement Proposal (SEP) Process +

+

+ To ensure predictability and avoid wasted engineering effort, all major architectural changes, + protocol schema modifications, or significant new features must go through + the SEP process. +

+
    +
  1. + Draft: A Contributor or Maintainer submits an issue outlining the proposed + design, motivation, and tradeoffs (using the SEP template). +
    2. +
  2. + Discuss: The community and Maintainers debate the merits and technical details + of the proposal asynchronously. +
    3. +
  3. + Resolve: The Core Steering Committee reviews the proposal and the community + feedback. The CSC will explicitly mark the SEP as Accepted, + Deferred, or Rejected. +
    4. +
  4. + Implement: Only after an SEP is accepted should significant engineering time be + spent on the implementation pull request. +
    5. +
+ +

+ Decision Making +

+

+ For day-to-day operations within specific domains, Domain Maintainers operate on a "lazy + consensus" model—if no maintainer objects to a PR within a reasonable timeframe, it is merged. +

+

+ For project-wide decisions, schema changes, and governance updates, the Core Steering Committee + seeks consensus. If consensus cannot be reached, decisions are made by a simple majority vote + among CSC members. +

+ +

+ Intellectual Property +

+

+ We do not require a Contributor License Agreement (CLA). When contributing to the project, you + affirm that you have the right to submit the code under the project's open source license. +

+ +

+ CSC Membership Lifecycle +

+

We follow these rules to keep the Core Steering Committee (CSC) active and focused.

+ +

+ 1. Adding Members +

+

+ We may add new members as the project grows. We typically choose people doing impactful work in + the Core Steering Committee. +

+
    +
  • + Nomination: Any current CSC member can nominate a candidate. +
    • +
  • + Election: We need a two-thirds vote to approve a new member. +
    • +
  • + Sourcegraph Role: Since Sourcegraph financially sponsors SCIP, they can appoint + internal members at any time. +
    • +
+ +

+ 2. Leaving the Committee +

+

+ If you no longer have time to contribute, you should step down. You will become an Emeritus + member. This means you can't vote, but we will still recognize your work in the repository. We + might ask for your advice on complex issues in the future. +

+ +

+ 3. Inactivity +

+

+ The CSC needs to respond quickly to avoid blocking others. If you ignore votes or reviews for six + months, we will automatically move you to Emeritus status. +

+ +

+ 4. Removal +

+

+ We may remove a member to protect the project. This requires a unanimous vote from all other + active members. We only do this for severe Code of Conduct violations or actions that hurt the + protocol's stability. +

+
+
+ + +
+ + diff --git a/index.html b/index.html index 0457039..50e4362 100644 --- a/index.html +++ b/index.html @@ -19,7 +19,6 @@ @@ -41,7 +40,7 @@

-
At a glance
+
Key features
  • Standardized index format
  • Language-agnostic schema for indexers
    • @@ -106,6 +105,8 @@

    Contribute to SCIP

    Questions, suggestions, code, and docs contributions are welcome. The development docs outline project structure and common workflows. Find us on GitHub. + Please read the Code of Conduct and + Governance pages before you contribute.

    @@ -117,6 +118,8 @@

    Contribute to SCIP

    © 2026 The SCIP Authors | Apache-2.0 license
    Artwork + Code of conduct + Governance Discord GitHub