-
-
Notifications
You must be signed in to change notification settings - Fork 1k
Include an exploratory packages section to the ecosystem page. #2184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Include an exploratory packages section to the ecosystem page. #2184
Conversation
These may change more frequently. It will contain GSoC or other DEP created third-party packages.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🚢
This needs to be reviewed by the other SC members before merging for content / wording. |
@@ -93,6 +93,15 @@ <h2>Packages - use community solutions</h2> | |||
|
|||
<p>We will refresh this list at least yearly to keep up to date.</p> | |||
|
|||
<hr /> | |||
<h3>Exploratory packages needing feedback</h3> | |||
<p>These packages are being explored by the Django Software Foundation for their viability and can use your feedback.</p> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<p>These packages are being explored by the Django Software Foundation for their viability and can use your feedback.</p> | |
<p>The Django Software Foundation is exploring the viability of these packages and can use your feedback.</p> |
Also, I wonder if "The Steering Council" or "The Django maintainers" would be a better group here than "The DSF"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I blame being in Jeff's office hours for my inability to write properly. You're 100% right, this is a SC thing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<p>These packages are being explored by the Django Software Foundation for their viability and can use your feedback.</p> | |
<p>The Steering Council is exploring the viability of these packages and would benefit from your feedback.</p> |
<h3>Exploratory packages needing feedback</h3> | ||
<p>These packages are being explored by the Django Software Foundation for their viability and can use your feedback.</p> | ||
<ul> | ||
<li><a href="https://github.com/RealOrangeOne/django-tasks">Django Tasks</a> — A lightweight task queue for Django applications, suitable for simple background task processing.</li> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This leaves out one of the big things I think we're looking for feedback about for Django Tasks: how good is the API as a common interface for task queues supporting multiple backends?
These may change more frequently. It will contain GSoC or other DEP created third-party packages.
Rendered version with the
<hr />