You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/orga/guidelines.rst
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,7 +77,7 @@ recipes.
77
77
Intended Usage
78
78
==============
79
79
80
-
Maintainers' time and CI resources are what enable conda-forge. They are as scarce as they are valuable. conda-forge has enough capacity to support releasing packages, but not developing them.
80
+
Maintainers' time and CI resources are what enable conda-forge. They are just as scarce as valuable. conda-forge has enough capacity to support releasing packages, but not developing them.
81
81
82
82
Publishing a package to conda-forge signals it is suitable for users not involved with development. However, publishing does not always happen error-free. Multiple commits are acceptable when debugging issues with the release process itself.
83
83
@@ -88,10 +88,10 @@ Fortunately, there are options for optimizing the development of a package.
88
88
Renaming Packages
89
89
=================
90
90
91
-
Sometimes packages are misnamed.
92
-
To correct the name of the package, please submit a PR into staged-recipes with the correct name.
93
-
During the review process please make certain to note that the package is a rename and contact a member of conda-forge/core to remove the old feedstock (and potentially package if needed).
94
-
Occasionally the .gitmodules file in the `feedstocks <https://github.com/conda-forge/feedstocks/blob/master/.gitmodules>`__ needs to be updated to remove the old feedstock.
91
+
Sometimes, packages are misnamed.
92
+
To correct the name of the package, please submit a PR into `staged-recipes<https://github.com/conda-forge/staged-recipes>`__ with the correct name.
93
+
During the review process, please make certain to note that the package is renamed and contact a member of conda-forge/core to remove the old feedstock (and potentially package, if needed).
94
+
Occasionally, the .gitmodules file in the `feedstocks <https://github.com/conda-forge/feedstocks/blob/master/.gitmodules>`__ needs to be updated to remove the old feedstock.
95
95
It's not entirely clear what those circumstances are.
96
96
See `conda-forge.github.io#1070 <https://github.com/conda-forge/conda-forge.github.io/issues/1070>`__.
97
97
@@ -100,8 +100,8 @@ See `conda-forge.github.io#1070 <https://github.com/conda-forge/conda-forge.gith
100
100
Fixing Broken Packages
101
101
======================
102
102
103
-
Sometimes you need to remove a package from the conda-forge channel on Anaconda.org. The reasons
104
-
for this are many, but the ones that immediately come to mind are:
103
+
Sometimes, you need to remove a package from the conda-forge channel on Anaconda.org.
104
+
There can be many reasons for this, but the ones that immediately come to mind are:
0 commit comments