From 90d9a3966440cb42a51f9a049d3d35112501ae59 Mon Sep 17 00:00:00 2001 From: "Dr. Andrew Annex" Date: Sat, 30 Mar 2024 11:18:16 -0700 Subject: [PATCH 1/6] start draft of incubation status/incubating packages --- Incubation.md | 41 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 41 insertions(+) create mode 100644 Incubation.md diff --git a/Incubation.md b/Incubation.md new file mode 100644 index 0000000..1bdffb6 --- /dev/null +++ b/Incubation.md @@ -0,0 +1,41 @@ +# PlanetaryPy Incubating Packages + +Packages in PlanetaryPy Incubation are packages that wish to eventually join PlanetaryPy as an affiliated package. Entering incubation is not a requirement or prerequisite for any affiliated packages or packages who wish to become affiliated packages. Incubation status is intended to foster the development of packages that may not yet fully meet all of the standards of an affiliated package. + +There are no time-limits to project incubation status or requirement that packages ever submit for review as an affiliated package to PlanetaryPy. However, if an incubating project does succesfully become an affiliated package in PlanetaryPy it will no longer be considered under incubation. + +Incubating PlanetaryPy Packages gain the ability to easily consult with the PlanetaryPy Technical Committee (TC) to advise the project on open source best practices to gradually implement the standards of PlanetaryPy and to join the open source community. Incubating project developers are welcome to join PlanetaryPy meetings prior-to and after submission for consideration for incubation. + +## How submit a Package for Incubation + +If you are a developer of a planetary science package and would like your +package to be in PlanetaryPy Incubation status, simply open a pull request following the process layed out [in proposing a project for incubation]. All that is required is the name of the project, link to the GitHub repository, the software license (if applicable), the code of conduct for the project or deferral to PlanetaryPy's code of conduct (see below), and 1-2 sentences explaining what the package does. No other review critera need to be met. + +Once the submission is successfully merged the project will be listed as being in Incubation on the PlanetaryPy website. + +Incubating projects will retain the status so long as the projects wish, and may withdraw their package from PlanetaryPy at any time. The PlanetaryPy TC will only remove packages from incubation status if: + +1. The package becomes an affiliated package of PlanetaryPy. +2. If the package developers violate the PlanetaryPy Code of Conduct or adopt a Code of Conduct sufficiently divergent from the PlanetaryPy Code of Conduct (see below). +3. Inactivity or inability to establish communication with the incubating project lasting more than two calendar years from the date of induction as an incubating PlanetaryPy project. + +### Community Standards and Governance + +The PlanetaryPy Project believes that good software is an outcome +of a healthy open-source community. The PlanetaryPy project operates +under rules laid out in its [Charter](Charter.md) as well as the +[Code of Conduct](Code-Of-Conduct.md), [Contributing +Guidelines](Contributing.md), and other documents that we'll refer +to as 'governing documents.' If an incubating package does not +explicitly define their own governing documents, it is assumed that +those of the PlanetaryPy Project apply. Incubating packages are +absolutely welcome to explicitly define their own versions of these +documents that govern how they operate, but if these documents or +the behavior of the incubating package's community diverges +significantly from those of the PlanetaryPy Project, or if they diverge after +being accepted as an incubating package, this may be the basis for +being removed from the list of incubating packages. + + + +[incubation-process]: https://planetarypy.org/packages/incubation-process/ \ No newline at end of file From 919428e21ba38e2836dd73f96784b663c7764b38 Mon Sep 17 00:00:00 2001 From: Ross Beyer Date: Sat, 6 Apr 2024 10:47:52 -0700 Subject: [PATCH 2/6] Altered some language and added a "what's in it for them" pitch. --- Incubation.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/Incubation.md b/Incubation.md index 1bdffb6..bf9b73d 100644 --- a/Incubation.md +++ b/Incubation.md @@ -1,10 +1,13 @@ # PlanetaryPy Incubating Packages -Packages in PlanetaryPy Incubation are packages that wish to eventually join PlanetaryPy as an affiliated package. Entering incubation is not a requirement or prerequisite for any affiliated packages or packages who wish to become affiliated packages. Incubation status is intended to foster the development of packages that may not yet fully meet all of the standards of an affiliated package. +Packages in PlanetaryPy Incubation are packages that might eventually join PlanetaryPy as an Affiliated Package. Entering incubation is not a requirement or prerequisite for being an Affiliated Package. Incubation status is intended to foster the development of packages that may not yet fully meet all of the standards of an Affiliated Package. -There are no time-limits to project incubation status or requirement that packages ever submit for review as an affiliated package to PlanetaryPy. However, if an incubating project does succesfully become an affiliated package in PlanetaryPy it will no longer be considered under incubation. +There are no time-limits to project incubation status or requirement that packages ever submit for review as an Affiliated Package to PlanetaryPy. However, if an Incubating Package does succesfully become an Affiliated Package in PlanetaryPy it will no longer be considered under incubation. + +Once listed as an Incubating Package, the developers are expected to attend at least one PlaneatryPy Technical Committee (TC) meeting to discuss their accepted-for-Incubation package. The intent is so that the TC can better understand the package, and provide advice and help to the developers on a wide spectrum of topics like open source best practices, standards, or any other topic that the developers would like help or guidance navigating. Of course, Incubating Package developers are welcome (like anyone else) to join PlanetaryPy TC meetings, even before they might submit a package to be considered. + +Packages in Incubation receive a number of benefits. Just being in this public listing might help users find their functionality more easily, and provides the opportunity for more users and even contributors to get involved with the Incubating Package. Additionally, the TC will be able to direct people to these packages when individuals ask "how they can help" PlanetaryPy. In partnership with the developers, the TC may make the package a part of hack-a-thons or other directed community contribution events or campaigns. Being an Incubating Package is an opportiny, and the TC wants to help those packages succeed. -Incubating PlanetaryPy Packages gain the ability to easily consult with the PlanetaryPy Technical Committee (TC) to advise the project on open source best practices to gradually implement the standards of PlanetaryPy and to join the open source community. Incubating project developers are welcome to join PlanetaryPy meetings prior-to and after submission for consideration for incubation. ## How submit a Package for Incubation @@ -38,4 +41,4 @@ being removed from the list of incubating packages. -[incubation-process]: https://planetarypy.org/packages/incubation-process/ \ No newline at end of file +[incubation-process]: https://planetarypy.org/packages/incubation-process/ From 3cb9be7316d8d528e3c5312b50c7e573983bbeca Mon Sep 17 00:00:00 2001 From: Ross Beyer Date: Sat, 6 Apr 2024 10:49:58 -0700 Subject: [PATCH 3/6] I really should spell-check before I commit these things. --- Incubation.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Incubation.md b/Incubation.md index bf9b73d..6f80291 100644 --- a/Incubation.md +++ b/Incubation.md @@ -2,17 +2,17 @@ Packages in PlanetaryPy Incubation are packages that might eventually join PlanetaryPy as an Affiliated Package. Entering incubation is not a requirement or prerequisite for being an Affiliated Package. Incubation status is intended to foster the development of packages that may not yet fully meet all of the standards of an Affiliated Package. -There are no time-limits to project incubation status or requirement that packages ever submit for review as an Affiliated Package to PlanetaryPy. However, if an Incubating Package does succesfully become an Affiliated Package in PlanetaryPy it will no longer be considered under incubation. +There are no time-limits to project incubation status or requirement that packages ever submit for review as an Affiliated Package to PlanetaryPy. However, if an Incubating Package does successfully become an Affiliated Package in PlanetaryPy it will no longer be considered under incubation. Once listed as an Incubating Package, the developers are expected to attend at least one PlaneatryPy Technical Committee (TC) meeting to discuss their accepted-for-Incubation package. The intent is so that the TC can better understand the package, and provide advice and help to the developers on a wide spectrum of topics like open source best practices, standards, or any other topic that the developers would like help or guidance navigating. Of course, Incubating Package developers are welcome (like anyone else) to join PlanetaryPy TC meetings, even before they might submit a package to be considered. -Packages in Incubation receive a number of benefits. Just being in this public listing might help users find their functionality more easily, and provides the opportunity for more users and even contributors to get involved with the Incubating Package. Additionally, the TC will be able to direct people to these packages when individuals ask "how they can help" PlanetaryPy. In partnership with the developers, the TC may make the package a part of hack-a-thons or other directed community contribution events or campaigns. Being an Incubating Package is an opportiny, and the TC wants to help those packages succeed. +Packages in Incubation receive a number of benefits. Just being in this public listing might help users find their functionality more easily, and provides the opportunity for more users and even contributors to get involved with the Incubating Package. Additionally, the TC will be able to direct people to these packages when individuals ask "how they can help" PlanetaryPy. In partnership with the developers, the TC may make the package a part of hack-a-thons or other directed community contribution events or campaigns. Being an Incubating Package is an opportunity, and the TC wants to help those packages succeed. ## How submit a Package for Incubation If you are a developer of a planetary science package and would like your -package to be in PlanetaryPy Incubation status, simply open a pull request following the process layed out [in proposing a project for incubation]. All that is required is the name of the project, link to the GitHub repository, the software license (if applicable), the code of conduct for the project or deferral to PlanetaryPy's code of conduct (see below), and 1-2 sentences explaining what the package does. No other review critera need to be met. +package to be in PlanetaryPy Incubation status, simply open a pull request following the process laid out [in proposing a project for incubation]. All that is required is the name of the project, link to the GitHub repository, the software license (if applicable), the code of conduct for the project or deferral to PlanetaryPy's code of conduct (see below), and 1-2 sentences explaining what the package does. No other review criteria need to be met. Once the submission is successfully merged the project will be listed as being in Incubation on the PlanetaryPy website. From f1a35adcc65d5436ab45d49dc1d4cc3c4d5a4639 Mon Sep 17 00:00:00 2001 From: "Dr. Andrew Annex" Date: Sat, 6 Apr 2024 12:23:35 -0700 Subject: [PATCH 4/6] adjusting capitalizations and removing double spaces --- Incubation.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/Incubation.md b/Incubation.md index 6f80291..a12a04e 100644 --- a/Incubation.md +++ b/Incubation.md @@ -4,9 +4,9 @@ Packages in PlanetaryPy Incubation are packages that might eventually join Plane There are no time-limits to project incubation status or requirement that packages ever submit for review as an Affiliated Package to PlanetaryPy. However, if an Incubating Package does successfully become an Affiliated Package in PlanetaryPy it will no longer be considered under incubation. -Once listed as an Incubating Package, the developers are expected to attend at least one PlaneatryPy Technical Committee (TC) meeting to discuss their accepted-for-Incubation package. The intent is so that the TC can better understand the package, and provide advice and help to the developers on a wide spectrum of topics like open source best practices, standards, or any other topic that the developers would like help or guidance navigating. Of course, Incubating Package developers are welcome (like anyone else) to join PlanetaryPy TC meetings, even before they might submit a package to be considered. +Once listed as an Incubating Package, the developers are expected to attend at least one PlaneatryPy Technical Committee (TC) meeting to discuss their accepted-for-Incubation package. The intent is so that the TC can better understand the package, and provide advice and help to the developers on a wide spectrum of topics like open source best practices, standards, or any other topic that the developers would like help or guidance navigating. Of course, Incubating Package developers are welcome (like anyone else) to join PlanetaryPy TC meetings, even before they might submit a package to be considered. -Packages in Incubation receive a number of benefits. Just being in this public listing might help users find their functionality more easily, and provides the opportunity for more users and even contributors to get involved with the Incubating Package. Additionally, the TC will be able to direct people to these packages when individuals ask "how they can help" PlanetaryPy. In partnership with the developers, the TC may make the package a part of hack-a-thons or other directed community contribution events or campaigns. Being an Incubating Package is an opportunity, and the TC wants to help those packages succeed. +Packages in Incubation receive a number of benefits. Just being in this public listing might help users find their functionality more easily, and provides the opportunity for more users and even contributors to get involved with the Incubating Package. Additionally, the TC will be able to direct people to these packages when individuals ask "how they can help" PlanetaryPy. In partnership with the developers, the TC may make the package a part of hack-a-thons or other directed community contribution events or campaigns. Being an Incubating Package is an opportunity, and the TC wants to help those packages succeed. ## How submit a Package for Incubation @@ -16,11 +16,11 @@ package to be in PlanetaryPy Incubation status, simply open a pull request follo Once the submission is successfully merged the project will be listed as being in Incubation on the PlanetaryPy website. -Incubating projects will retain the status so long as the projects wish, and may withdraw their package from PlanetaryPy at any time. The PlanetaryPy TC will only remove packages from incubation status if: +Incubating projects will retain the status so long as the projects wish, and may withdraw their package from PlanetaryPy incubation at any time. The PlanetaryPy TC will only remove packages from incubation status if: 1. The package becomes an affiliated package of PlanetaryPy. 2. If the package developers violate the PlanetaryPy Code of Conduct or adopt a Code of Conduct sufficiently divergent from the PlanetaryPy Code of Conduct (see below). -3. Inactivity or inability to establish communication with the incubating project lasting more than two calendar years from the date of induction as an incubating PlanetaryPy project. +3. Inactivity or inability to establish communication with the Incubating Project lasting more than two calendar years from the date of induction as an Incubating PlanetaryPy project. ### Community Standards and Governance @@ -29,15 +29,15 @@ of a healthy open-source community. The PlanetaryPy project operates under rules laid out in its [Charter](Charter.md) as well as the [Code of Conduct](Code-Of-Conduct.md), [Contributing Guidelines](Contributing.md), and other documents that we'll refer -to as 'governing documents.' If an incubating package does not +to as 'governing documents.' If an Incubating Package does not explicitly define their own governing documents, it is assumed that those of the PlanetaryPy Project apply. Incubating packages are absolutely welcome to explicitly define their own versions of these documents that govern how they operate, but if these documents or -the behavior of the incubating package's community diverges +the behavior of the Incubating Package's community diverges significantly from those of the PlanetaryPy Project, or if they diverge after -being accepted as an incubating package, this may be the basis for -being removed from the list of incubating packages. +being accepted as an Incubating Package, this may be the basis for +being removed from the list of Incubating packages. From f8efeb0a2f73d10b7fda95432239fcc1b966a3da Mon Sep 17 00:00:00 2001 From: "Christian J. Tai Udovicic" Date: Tue, 4 Jun 2024 10:38:38 -1000 Subject: [PATCH 5/6] Update Incubation.md Added changes commented above --- Incubation.md | 35 +++++++++-------------------------- 1 file changed, 9 insertions(+), 26 deletions(-) diff --git a/Incubation.md b/Incubation.md index a12a04e..dd5af76 100644 --- a/Incubation.md +++ b/Incubation.md @@ -1,44 +1,27 @@ -# PlanetaryPy Incubating Packages +# PlanetaryPy Incubation Packages Packages in PlanetaryPy Incubation are packages that might eventually join PlanetaryPy as an Affiliated Package. Entering incubation is not a requirement or prerequisite for being an Affiliated Package. Incubation status is intended to foster the development of packages that may not yet fully meet all of the standards of an Affiliated Package. -There are no time-limits to project incubation status or requirement that packages ever submit for review as an Affiliated Package to PlanetaryPy. However, if an Incubating Package does successfully become an Affiliated Package in PlanetaryPy it will no longer be considered under incubation. +There are no time-limits to project incubation status or requirement that packages ever submit for review as an Affiliated Package to PlanetaryPy. However, if a Planetarypy Incubation Package does successfully become a PlanetaryPy Affiliated Package, it will no longer be considered under incubation. -Once listed as an Incubating Package, the developers are expected to attend at least one PlaneatryPy Technical Committee (TC) meeting to discuss their accepted-for-Incubation package. The intent is so that the TC can better understand the package, and provide advice and help to the developers on a wide spectrum of topics like open source best practices, standards, or any other topic that the developers would like help or guidance navigating. Of course, Incubating Package developers are welcome (like anyone else) to join PlanetaryPy TC meetings, even before they might submit a package to be considered. - -Packages in Incubation receive a number of benefits. Just being in this public listing might help users find their functionality more easily, and provides the opportunity for more users and even contributors to get involved with the Incubating Package. Additionally, the TC will be able to direct people to these packages when individuals ask "how they can help" PlanetaryPy. In partnership with the developers, the TC may make the package a part of hack-a-thons or other directed community contribution events or campaigns. Being an Incubating Package is an opportunity, and the TC wants to help those packages succeed. +Once accepted as an Incubation Package, the developers are expected to attend at least one PlaneatryPy Technical Committee (TC) meeting to discuss their Incubation Package. The intent is so that the TC can better understand the package, and provide advice and help to the developers on a wide spectrum of topics like open source best practices, standards, or any other topic that the developers would like help or guidance navigating. Of course, Incubation Package developers are welcome (like anyone else) to join PlanetaryPy TC meetings, even before they might submit a package to be considered. +Incubation Packages receive a number of benefits. Just being in this public listing might help users find their functionality more easily, and provides the opportunity for more users and even contributors to get involved with the Incubation Package. Additionally, the TC will be able to direct people to these packages when individuals ask "how they can help" PlanetaryPy. In partnership with the developers, the TC may make the package a part of hack-a-thons or other directed community contribution events or campaigns. Being an Incubation Package is an opportunity, and the TC wants to help those packages succeed. ## How submit a Package for Incubation -If you are a developer of a planetary science package and would like your -package to be in PlanetaryPy Incubation status, simply open a pull request following the process laid out [in proposing a project for incubation]. All that is required is the name of the project, link to the GitHub repository, the software license (if applicable), the code of conduct for the project or deferral to PlanetaryPy's code of conduct (see below), and 1-2 sentences explaining what the package does. No other review criteria need to be met. +If you are a developer of a planetary science package and would like your package to be in PlanetaryPy Incubation status, simply open a pull request following the process laid out [in proposing a project for incubation]. All that is required is the name of the project, link to the GitHub repository, the software license (if applicable), the code of conduct for the project or deferral to PlanetaryPy's code of conduct (see below), and 1-2 sentences explaining what the package does. No other review criteria need to be met. Once the submission is successfully merged the project will be listed as being in Incubation on the PlanetaryPy website. -Incubating projects will retain the status so long as the projects wish, and may withdraw their package from PlanetaryPy incubation at any time. The PlanetaryPy TC will only remove packages from incubation status if: +Packages will retain the Incubation status so long as the project developers wish, and they may withdraw their package from PlanetaryPy incubation at any time. The PlanetaryPy TC will only remove packages from Incubation status if: -1. The package becomes an affiliated package of PlanetaryPy. +1. The package becomes an Affiliated Package of PlanetaryPy. 2. If the package developers violate the PlanetaryPy Code of Conduct or adopt a Code of Conduct sufficiently divergent from the PlanetaryPy Code of Conduct (see below). -3. Inactivity or inability to establish communication with the Incubating Project lasting more than two calendar years from the date of induction as an Incubating PlanetaryPy project. +3. Inactivity or inability to establish communication with the Incubation Package developers lasting more than two calendar years from the date of acceptance or last contact. ### Community Standards and Governance -The PlanetaryPy Project believes that good software is an outcome -of a healthy open-source community. The PlanetaryPy project operates -under rules laid out in its [Charter](Charter.md) as well as the -[Code of Conduct](Code-Of-Conduct.md), [Contributing -Guidelines](Contributing.md), and other documents that we'll refer -to as 'governing documents.' If an Incubating Package does not -explicitly define their own governing documents, it is assumed that -those of the PlanetaryPy Project apply. Incubating packages are -absolutely welcome to explicitly define their own versions of these -documents that govern how they operate, but if these documents or -the behavior of the Incubating Package's community diverges -significantly from those of the PlanetaryPy Project, or if they diverge after -being accepted as an Incubating Package, this may be the basis for -being removed from the list of Incubating packages. - - +The PlanetaryPy Project believes that good software is an outcome of a healthy open-source community. The PlanetaryPy project operates under rules laid out in its [Charter](Charter.md) as well as the [Code of Conduct](Code-Of-Conduct.md), [Contributing Guidelines](Contributing.md), and other documents that we'll refer to as 'governing documents.' If an Incubation Package does not explicitly define their own governing documents, it is assumed that those of the PlanetaryPy Project apply. Incubation Packages are absolutely welcome to explicitly define their own versions of these documents that govern how they operate, but if these documents or the behavior of the Incubation Package's community diverges significantly from those of the PlanetaryPy Project, or if they diverge after being accepted as an Incubation Package, this may be the basis for being removed from the list of Incubation packages. [incubation-process]: https://planetarypy.org/packages/incubation-process/ From 402ddc63091744c414f8b662d7cf4c5278a6bc1a Mon Sep 17 00:00:00 2001 From: "Dr. Andrew Annex" Date: Tue, 17 Sep 2024 12:40:30 -0700 Subject: [PATCH 6/6] fix typo --- Incubation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Incubation.md b/Incubation.md index dd5af76..b7f143a 100644 --- a/Incubation.md +++ b/Incubation.md @@ -4,7 +4,7 @@ Packages in PlanetaryPy Incubation are packages that might eventually join Plane There are no time-limits to project incubation status or requirement that packages ever submit for review as an Affiliated Package to PlanetaryPy. However, if a Planetarypy Incubation Package does successfully become a PlanetaryPy Affiliated Package, it will no longer be considered under incubation. -Once accepted as an Incubation Package, the developers are expected to attend at least one PlaneatryPy Technical Committee (TC) meeting to discuss their Incubation Package. The intent is so that the TC can better understand the package, and provide advice and help to the developers on a wide spectrum of topics like open source best practices, standards, or any other topic that the developers would like help or guidance navigating. Of course, Incubation Package developers are welcome (like anyone else) to join PlanetaryPy TC meetings, even before they might submit a package to be considered. +Once accepted as an Incubation Package, the developers are expected to attend at least one PlanetaryPy Technical Committee (TC) meeting to discuss their Incubation Package. The intent is so that the TC can better understand the package, and provide advice and help to the developers on a wide spectrum of topics like open source best practices, standards, or any other topic that the developers would like help or guidance navigating. Of course, Incubation Package developers are welcome (like anyone else) to join PlanetaryPy TC meetings, even before they might submit a package to be considered. Incubation Packages receive a number of benefits. Just being in this public listing might help users find their functionality more easily, and provides the opportunity for more users and even contributors to get involved with the Incubation Package. Additionally, the TC will be able to direct people to these packages when individuals ask "how they can help" PlanetaryPy. In partnership with the developers, the TC may make the package a part of hack-a-thons or other directed community contribution events or campaigns. Being an Incubation Package is an opportunity, and the TC wants to help those packages succeed.