admin: Update pull request and issue templates (AcademySoftwareFounda…

…tion#3946) The most important fix is to remove links to the old CLAs and update references to the mail list to the new one. Also spruced up some language while I was there, hopefully to coax out improved PRs and Issues. Signed-off-by: Larry Gritz <[email protected]>
lgritz · Aug 20, 2023 · c7f8169 · c7f8169
1 parent e3f6665
commit c7f8169
Show file tree

Hide file tree

Showing 3 changed files with 15 additions and 10 deletions.
diff --git a/.github/ISSUE_TEMPLATE/build_problem.md b/.github/ISSUE_TEMPLATE/build_problem.md
@@ -7,10 +7,10 @@ assignees: ''
 
 ---
 
-**PLEASE DO NOT REPORT BUILD TROUBLES AS ISSUES**
+**PLEASE DO NOT REPORT BUILD TROUBLES AS GITHUB "ISSUES" UNLESS YOU ARE RALLY SURE IT'S A BUG**
 
 The best way to get help with your build problems is to ask a question on the
-[oiio-dev developer mail list](http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org).
+[oiio-dev developer mail list](https://lists.aswf.io/g/oiio-dev).
 
 When you email about this, please attach one or both of the following:
 1. The full verbose build log, which you can create like this:

diff --git a/.github/ISSUE_TEMPLATE/question.md b/.github/ISSUE_TEMPLATE/question.md
@@ -19,7 +19,7 @@ But if you are just asking a question:
 * I can't build OpenImageIO
 
 For anything of this nature, the best way to get help using OpenImageIO is
-to ask a question on the [oiio-dev developer mail list](http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org).
+to ask a question on the [oiio-dev developer mail list](https://lists.aswf.io/g/oiio-dev).
 
 The [documentation](https://openimageio.readthedocs.org)
 is pretty comprehensive, so please check there first; you may find the answer

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,3 +1,8 @@
+<!-- This is just a guideline and set of reminders about what constitutes -->
+<!-- a good PR. Feel free to delete all this matter and replace it with   -->
+<!-- your own detailed message about the PR, assuming you hit all the     -->
+<!-- important points made below.                                         -->
+
 
 ## Description
 
@@ -15,13 +20,13 @@
 <!-- Put an 'x' in the boxes as you complete the checklist items -->
 
 - [ ] I have read the [contribution guidelines](https://github.com/OpenImageIO/oiio/blob/master/CONTRIBUTING.md).
-- [ ] If this is more extensive than a small change to existing code, I
-  have previously submitted a Contributor License Agreement
-  ([individual](https://github.com/OpenImageIO/oiio/blob/master/src/doc/CLA-INDIVIDUAL), and if there is any way my
-  employers might think my programming belongs to them, then also
-  [corporate](https://github.com/OpenImageIO/oiio/blob/master/src/doc/CLA-CORPORATE)).
 - [ ] I have updated the documentation, if applicable.
 - [ ] I have ensured that the change is tested somewhere in the testsuite
   (adding new test cases if necessary).
-- [ ] My code follows the prevailing code style of this project.
-
+- [ ] If I added or modified a C++ API call, I have also amended the
+  corresponding Python bindings (and if altering ImageBufAlgo functions, also
+  exposed the new functionality as oiiotool options).
+- [ ] My code follows the prevailing code style of this project. If I haven't
+  already run clang-format before submitting, I definitely will look at the CI
+  test that runs clang-format and fix anything that it highlights as being
+  nonconforming.