Skip to content

Commit f84c227

Browse files
texodustexodus
authored
Merge pull request #3087 from perspective-dev/fix-ci-32
OpenJS onboarding pt.2
2 parents dc85be7 + b2f61d5 commit f84c227

12 files changed

+485
-27
lines changed

‎.github/PULL_REQUEST_TEMPLATE.md‎

Lines changed: 23 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,23 @@
1-
### Pull Request Checklist
2-
3-
- [ ] Description which clearly states what problems the PR solves.
4-
- [ ] Description contains a link to the Github Issue, and any relevent
5-
Discussions, this PR applies to.
6-
- [ ] Include new tests that fail without this PR but passes with it.
7-
- [ ] Include any relevent Documentation changes related to this change.
8-
- [ ] Verify all commits have been _signed_ in accordance with the DCO policy.
9-
- [ ] Reviewed PR commit history to remove unnecessary changes.
10-
- [ ] Make sure your PR passes _build_, _test_ and _lint_ steps _completely_.
1+
<!--
2+
3+
Please make sure you've read the
4+
[`CONTRIBUTING.md`](https://github.com/perspective-dev/perspective/blob/master/CONTRIBUTING.md)
5+
and followed the instructions precisely before opening a Pull Request. Pull
6+
Requests from new contributors which do not may be closed without comment.
7+
8+
## Final Pull Request Checklist
9+
10+
As a reminder from [`CONTRIBUTING.md`](https://github.com/perspective-dev/perspective/blob/master/CONTRIBUTING.md). Please do not _literally_ inlude this list in your PR!
11+
12+
- Includes a thorough Description which clearly states what problems the PR
13+
solves.
14+
- Description contains a link to the Github Issue, and any relevent Discussions,
15+
this PR applies to.
16+
- Include new tests that fail without this PR but passes with it.
17+
- Include any relevent Documentation changes related to this change.
18+
- Verify all commits have been _signed_ in accordance with the DCO policy.
19+
- Disclosed AI tooling assistance.
20+
- Reviewed PR commit history to remove unnecessary changes.
21+
- Make sure your PR passes _build_, _test_ and _lint_ steps _completely_.
22+
23+
-->

‎.github/workflows/build.yaml‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -955,9 +955,9 @@ jobs:
955955
with:
956956
name: perspective-python-dist-aarch64-macos-14-3.9
957957

958-
- uses: actions/download-artifact@v4
959-
with:
960-
name: perspective-python-dist-x86_64-macos-14-3.9
958+
# - uses: actions/download-artifact@v4
959+
# with:
960+
# name: perspective-python-dist-x86_64-macos-14-3.9
961961

962962
- uses: actions/download-artifact@v4
963963
with:

‎CONTRIBUTING.md‎

Lines changed: 59 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -37,8 +37,6 @@ guidelines:
3737
- Make sure your PR passes _build_, _test_ and _lint_ steps _completely_ before
3838
opening a PR. Make _sure_ you've run these locally, even if you think your
3939
change will not impact this step!
40-
- Don't open a PR for auto-generated, AI-assisted or otherwise inauthentic
41-
contributions.
4240
- Sign commits (e.g. with `-s`) in accordance with the DCO policy detailed
4341
below, _before_ opening a PR.
4442
- Please make sure PRs include the following _not optional_ components:
@@ -56,6 +54,10 @@ guidelines:
5654

5755
## DCO
5856

57+
> [!IMPORTANT]
58+
>
59+
> Signed commits are required for all PRs.
60+
5961
The Perspective project requires contributors to affirm their contributions via
6062
a [Developer Certificate of Origin](https://developercertificate.org), which
6163
certifies that developers are authorized to make their contribution, either on
@@ -71,3 +73,58 @@ automatically scan and flag any pull requests that lack a valid sign-off.
7173
If you have any general questions about contributing to Perspective, please feel
7274
free to open a discussion on
7375
[github](https://github.com/perspective-dev/perspective/discussions)
76+
77+
## AI Assistance Notice
78+
79+
This section was forked from
80+
[`ghostty`](https://github.com/ghostty-org/ghostty),
81+
[MIT License](https://github.com/ghostty-org/ghostty/blob/main/LICENSE)
82+
([File](https://github.com/ghostty-org/ghostty/pull/8289/files))
83+
([PR](https://github.com/ghostty-org/ghostty/pull/8289)). Thanks @mitchellh!
84+
85+
> [!IMPORTANT]
86+
>
87+
> If you are using **any kind of AI assistance** to contribute to Perspective,
88+
> it must be disclosed in the pull request.
89+
90+
If you are using any kind of AI assistance while contributing to Perspective,
91+
**this must be disclosed in the pull request**, along with the extent to which
92+
AI assistance was used (e.g. docs only vs. code generation). If PR responses are
93+
being generated by an AI, disclose that as well. As a small exception, trivial
94+
tab-completion doesn't need to be disclosed, so long as it is limited to single
95+
keywords or short phrases.
96+
97+
An example disclosure:
98+
99+
> This PR was written primarily by Claude Code.
100+
101+
Or a more detailed disclosure:
102+
103+
> I consulted ChatGPT to understand the codebase but the solution was fully
104+
> authored manually by myself.
105+
106+
Failure to disclose this is first and foremost rude to the human operators on
107+
the other end of the pull request, but it also makes it difficult to determine
108+
how much scrutiny to apply to the contribution.
109+
110+
In a perfect world, AI assistance would produce equal or higher quality work
111+
than any human. That isn't the world we live in today, and in most cases it's
112+
generating slop. I say this despite being a fan of and using them successfully
113+
myself (with heavy supervision)!
114+
115+
Please be respectful to maintainers and disclose AI assistance.
116+
117+
## Final Pull Request Checklist
118+
119+
Before opening a Pull Request, be sure:
120+
121+
- Includes a thorough Description which clearly states what problems the PR
122+
solves.
123+
- Description contains a link to the Github Issue, and any relevent Discussions,
124+
this PR applies to.
125+
- Include new tests that fail without this PR but passes with it.
126+
- Include any relevent Documentation changes related to this change.
127+
- Verify all commits have been _signed_ in accordance with the DCO policy.
128+
- Disclosed AI tooling assistance.
129+
- Reviewed PR commit history to remove unnecessary changes.
130+
- Make sure your PR passes _build_, _test_ and _lint_ steps _completely_.

‎GOVERNANCE.md‎

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
# `perspective` Project Governance
2+
3+
## Maintainers
4+
5+
- [@texodus](https://github.com/texodus)
6+
- [@timkpaine](https://github.com/timkpaine)
7+
8+
Maintainers are responsible for issue/PR triage, feature additions, maintenance,
9+
bugfixes, security fixes, releases, promoting existing contributors to
10+
maintainers, managing repo and CI configuration, etc.
11+
12+
## Contributors
13+
14+
Anyone who contributes code or content or time, via issues or pull requests or
15+
otherwise. Contributors do not have any additional permissions on the project.

‎PROJECT_CHARTER.md‎

Lines changed: 72 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,72 @@
1+
# `perspective` Charter
2+
3+
`perspective` is a data visualization and analytics component, especially
4+
well-suited for large and/or streaming datasets.
5+
6+
## Section 0: Guiding Principles
7+
8+
The `perspective` project is part of the [OpenJS Foundation][openjs foundation],
9+
which operates transparently, openly, collaboratively, and ethically. Project
10+
proposals, timelines, and status must not merely be open, but also easily
11+
visible to outsiders.
12+
13+
## Section 1: Scope
14+
15+
`perspective` is a data visualization component, any features related to data
16+
visualization on any platform are potentially in scope.
17+
18+
## Section 2: Relationship with OpenJS Foundation CPC.
19+
20+
Technical leadership for the projects within the [OpenJS
21+
Foundation][openjs foundation] is delegated to the projects through their
22+
project charters by the
23+
[OpenJS Foundation Cross-Project Council](https://openjsf.org/about/governance/)
24+
(CPC). In the case of the `perspective` project, it is delegated to the
25+
[`perspective` Maintainers](GOVERNANCE.md#maintainers) (the “Maintainers”). The
26+
OpenJS Foundation's business leadership is the Board of Directors (the “Board”).
27+
28+
This `perspective` Charter reflects a carefully constructed balanced role for
29+
the Maintainers and the CPC in the governance of the OpenJS Foundation. The
30+
charter amendment process is for the Maintainers to propose changes using simple
31+
majority of the full Maintainers, the proposed changes being subject to review
32+
and approval by the CPC. The CPC may additionally make amendments to the project
33+
charter at any time, though the CPC will not interfere with day-to-day
34+
discussions, votes or meetings of the Maintainers.
35+
36+
### 2.1 Other Formal Project Relationships
37+
38+
Section Intentionally Left Blank
39+
40+
## Section 3: `perspective`'s Maintainers Governing Body
41+
42+
`perspective` is governed by its [maintainers](GOVERNANCE.md#maintainers).
43+
44+
## Section 4: Roles & Responsibilities
45+
46+
The roles and responsibilities of `perspective`'s Maintainers are described in
47+
[GOVERNANCE.md](./GOVERNANCE.md).
48+
49+
### Section 4.1 Project Operations & Management
50+
51+
Section Intentionally Left Blank
52+
53+
### Section 4.2: Decision-making, Voting, and/or Elections
54+
55+
Section Intentionally Left Blank
56+
57+
### Section 4.3: Other Project Roles
58+
59+
Section Intentionally Left Blank
60+
61+
## Section 5: Definitions
62+
63+
- _Contributors_: contribute code or other artifacts, but do not have the right
64+
to commit to the codebase. Contributors work with the project’s maintainers to
65+
have code committed to the code base. A Contributor may be promoted to a
66+
Maintainer by the Maintainers. Contributors should rarely be encumbered by the
67+
Maintainers and never by the CPC or OpenJS Foundation Board.
68+
69+
- _Maintainers_: Contributors with any kind of decision-making authority in the
70+
project.
71+
72+
[openjs foundation]: https://openjsf.org

‎README.md‎

Lines changed: 35 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -88,4 +88,38 @@ applications.
8888
<td><a href="https://www.youtube.com/watch?v=0ut-ynvBpGI"><img width="240" src="https://img.youtube.com/vi/0ut-ynvBpGI/0.jpg" /></a></td>
8989
<td></td>
9090
</tr>
91-
</tbody></table>
91+
</tbody></table><br/><br/>
92+
93+
---
94+
95+
<br/>
96+
<picture>
97+
<source media="(prefers-color-scheme: dark)" srcset="https://github.com/openjs-foundation/artwork/raw/master/openjs_foundation/openjs_foundation-logo-horizontal-white.svg?raw=true">
98+
<img width="200" src="https://github.com/openjs-foundation/artwork/raw/master/openjs_foundation/openjs_foundation-logo-horizontal-black.svg?raw=true">
99+
</picture>
100+
<br/>
101+
<br/>
102+
<br/>
103+
104+
The Perspective project is a member of the
105+
[The OpenJS Foundation](https://openjsf.org/).
106+
107+
Copyright [OpenJS Foundation](https://openjsf.org) and Perspective contributors.
108+
All rights reserved. The [OpenJS Foundation](https://openjsf.org) has registered
109+
trademarks and uses trademarks. For a list of trademarks of the
110+
[OpenJS Foundation](https://openjsf.org), please see our
111+
[Trademark Policy](https://trademark-policy.openjsf.org/) and
112+
[Trademark List](https://trademark-list.openjsf.org/). Trademarks and logos not
113+
indicated on the
114+
[list of OpenJS Foundation trademarks](https://trademark-list.openjsf.org) are
115+
trademarks™ or registered® trademarks of their respective holders. Use of them
116+
does not imply any affiliation with or endorsement by them.
117+
118+
[The OpenJS Foundation](https://openjsf.org/) |
119+
[Terms of Use](https://terms-of-use.openjsf.org/) |
120+
[Privacy Policy](https://privacy-policy.openjsf.org/) |
121+
[Bylaws](https://bylaws.openjsf.org/) |
122+
[Code of Conduct](https://code-of-conduct.openjsf.org) |
123+
[Trademark Policy](https://trademark-policy.openjsf.org/) |
124+
[Trademark List](https://trademark-list.openjsf.org/) |
125+
[Cookie Policy](https://www.linuxfoundation.org/cookies/)

‎SECURITY.md‎

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
# Security Policy
2+
3+
## Supported Versions
4+
5+
Security updates are applied only to the latest release.
6+
7+
## Reporting a Vulnerability
8+
9+
To report a security issue, please use the GitHub Security Advisory
10+
["Report a Vulnerability"](https://github.com/perspective-dev/perspective/security/advisories/new)
11+
tab.
12+
13+
Report security bugs in third-party modules to the person or team maintaining
14+
the module. You can also report a vulnerability through the
15+
[npm contact form](https://www.npmjs.com/support) by selecting "I'm reporting a
16+
security vulnerability".
17+
18+
## Escalation
19+
20+
If you do not receive an acknowledgement of your report within 6 business days,
21+
or if you cannot find a private security contact for the project, you may
22+
escalate to the OpenJS Foundation CNA at `security@lists.openjsf.org`.
23+
24+
If the project acknowledges your report but does not provide any further
25+
response or engagement within 14 days, escalation is also appropriate.

0 commit comments

Comments
 (0)