django-tailwind-cli

[ryancheley]

Hi @django-commons/django-tailwind-cli! I wanted to take a moment and check in with you about how the transition to Django Commons has been.

• Have you run into any friction having your project in Django Commons, if so, can you describe them?
• Is there anything we can do to help your team or repo out?
• Do you have any questions or concerns for us?

If you'd like to chat with us privately, our email is django-commons-admin@googlegroups.com. Thanks!

[oliverandrich]

Hey @ryancheley! Thanks for reaching out. The transition has been wonderful and went smoothly. So far I have only two topics on my task list for the project that related to django-commons.

• Find out how to link to the official code of conduct without having to copy it and still get the prominent link on the landing page of the project.
• Find a co-maintainer.

[cunla]

Re: link to code of conduct

You can have in your COC a link to the COC in the membership repo - check out playground-coc as an example

[oliverandrich]

Thanks. This is a good advice and I just updated the CoC of the project accordingly.

[ryancheley]

@oliverandrich I’m so glad to hear that it’s going well! For the two points you’ve raised:

• Find out how to link to the official code of conduct without having to copy it and still get the prominent link on the landing page of the project.

The django-typer package has a GitHub Workflow that does this. The admins are also looking at ways to make this process easier not just for the CoC but other files as well. See this issue

• Find a co-maintainer.

The Admins are also talking about how to surface these types of things more easily within the organization. We don’t have any answers (yet), but it’s one of the things we’re hoping to be able to offer guidance on in the future.

[oliverandrich]

Just learned from your ticket, that there is a SECURITY.md file too. Can I just add it to my repository, or do I have to prepare the project for it?

[ryancheley]

As far as I know you can just add it to your repo, but I’ve only seen it on the django-typer project and not implemented it myself. There is a pretty good write up here of the steps needed. Hope that helps!

[tim-schilling]

Hi @django-commons/django-tailwind-cli, we're circling back around 💫 We want to ask Ryan's original questions to see if there's any update. We're also looking into how can we improve the new contributor experience with the overall goal of helping find regular contributor and more maintainers for projects.

• Meet and greets
• Project introduction videos

If any of that sounds interesting to you, feel free to engage on the discussions or here.

[williln]

Hi @django-commons/django-tailwind-cli -- this is our semi-annual checkin. If there is anything Django Commons can do to help you or your project, please let us know! Otherwise, happy coding ⭐

[oliverandrich]

Hi Lacey, from my side, everything is fine and works like expected. Thanks for reaching out and the support. Best regards, Oliver

…

Am 12.09.2025 um 20:00 schrieb Lacey Henschel ***@***.***>: Hi @django-commons/django-tailwind-cli <https://github.com/orgs/django-commons/teams/django-tailwind-cli> -- this is our semi-annual checkin. If there is anything Django Commons can do to help you or your project, please let us know! Otherwise, happy coding ⭐ — Reply to this email directly, view it on GitHub <#124 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAAF5UFZYIY4NAOLDMAV6L3SMC3NAVCNFSM6AAAAACGLWJZ6GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMZYG4YDGMI>. You are receiving this because you were mentioned.

[tim-schilling]

Hi @django-commons/django-tailwind-cli this is just our semi-annual checkin. Let us know if there is anything Django Commons can do to help, or if there is anything else on your mind! Otherwise, happy coding 🥳

As an additional reminder, though not at all a suggestion/requirement. It may be worth looking through who has regularly contributed to your project to see if you'd like to elevate them to be a committer or a maintainer. I mention it because it's easy to forget to review the repositories community and helping people grow. Similarly, if you or anyone else wants to step back, that's fine too! If we can help coordinate, please let us know.

[tim-schilling]

Whoops, forgot some things. There are two other things:

1. Can the @django-commons/django-tailwind-cli-admins please share your emails with us? You can email us at django-commons-admin@googlegroups.com to avoid publishing publicly here.
2. We are working on a new policy around project abandonment. As a community organization, we need to have clear guidelines on when the community should pass the project onto someone else or signaling that the project is in a period of low activity. We'll share this new policy with you when we have it ready for comment. This will include a timeline for adoption. If you have questions, please let us know!