-
Notifications
You must be signed in to change notification settings - Fork 2
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
Migrating: cats-actors #146
Comments
@valencik not sure what the process is, should I open a PR to include the project or is something that the steering group does? |
Someone needs to open the PR to add the project to the website, but folks are a little busy at the moment, so it's taking a little while. If you wanted to open a projects.yml PR, that would be great. |
The blog post actually doesn't often happen for individual libraries. That guideline predates the current wave of libs coming in as affiliates -- it's been a long time since we did one (like, possibly years), and realistically individual posts are probably more appropriate for Organization libraries than Affiliate ones. (We should think about formalizing the policy there, which hasn't been reviewed in quite a while.) That said, I should think about drafting a summary one for the libraries that have joined as affiliates in recent months, and do a quick Mastodon post. |
Thank you for clarifying!
…On Thu, Jun 27, 2024 at 2:52 PM Justin du Coeur, AKA Mark Waks < ***@***.***> wrote:
The blog post actually *doesn't* often happen for individual libraries.
That guideline predates the current wave of libs coming in as affiliates --
it's been a long time since we did one (like, possibly years), and
realistically individual posts are probably more appropriate for
Organization libraries than Affiliate ones. (We should think about
formalizing the policy there, which hasn't been reviewed in quite a while.)
That said, I should think about drafting a summary one for the libraries
that have joined as affiliates in recent months, and do a quick Mastodon
post.
—
Reply to this email directly, view it on GitHub
<#146 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AANKHJX2ASEMZG6USCKCYR3ZJQDKRAVCNFSM6AAAAABJU3B3SWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJUGU4TSMJRGY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Migration Checklist
Project Submission Issue: #144
For All Projects:
Announcements
These steps are optional but encouraged.
The text was updated successfully, but these errors were encountered: