Skip to content

Add a short clarifying notice to each SPEC - #441

Draft
jarrodmillman wants to merge 1 commit into
scientific-python:mainfrom
jarrodmillman:spec-notice
Draft

jarrodmillman wants to merge 1 commit into
scientific-python:mainfrom
jarrodmillman:spec-notice

Conversation

@jarrodmillman

Copy link
Copy Markdown
Member

This is draft text for a notice I intend to put at the top of every SPEC. The idea is that readers of individual SPECs may not have read the SPEC Purpose and Process. We will also need to be more careful about completing the "Ecosystem Adoption" section. I will open up separate PRs to do that.

See #440.

@jarrodmillman
jarrodmillman marked this pull request as draft October 12, 2026 17:48
@jarrodmillman

Copy link
Copy Markdown
Member Author
2026-10-12T12:01:52,617033483-07:00

@stefanv

stefanv commented Oct 12, 2026

Copy link
Copy Markdown
Member

May be a good idea to link back to the purpose with an encouragement to read that document :)

I left a comment on the wording on the PR that changes purpose.

@bsipocz bsipocz left a comment •

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Having the note sounds to be a good idea to me, thanks Jarrod for the PR!

That being said, will you add this note to each SPEC, so we shall wait with merging until that's done?

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

Successfully merging this pull request may close these issues.

3 participants