django/dsf-working-groups

Working group mechanism for the DSF

Django

Django is a high-level Python web framework that encourages rapid development and clean, pragmatic design. Thanks for checking it out.

All documentation is in the "docs" directory and online at https://docs.djangoproject.com/en/stable/. If you're just getting started, here's how we recommend you read the docs:

• First, read docs/intro/install.txt for instructions on installing Django.
• Next, work through the tutorials in order (docs/intro/tutorial01.txt, docs/intro/tutorial02.txt, etc.).
• If you want to set up an actual deployment server, read docs/howto/deployment/index.txt for instructions.
• You'll probably want to read through the topical guides (in docs/topics) next; from there you can jump to the HOWTOs (in docs/howto) for specific problems, and check out the reference (docs/ref) for gory details.
• See docs/README for instructions on building an HTML version of the docs.

Docs are updated rigorously. If you find any problems in the docs, or think they should be clarified in any way, please take 30 seconds to fill out a ticket here: https://code.djangoproject.com/newticket

To get more help:

• Join the #django channel on irc.libera.chat. Lots of helpful people hang out there. Webchat is available.
• Join the django-users mailing list, or read the archives, at https://groups.google.com/group/django-users.
• Join the Django Discord community.
• Join the community on the Django Forum.

To contribute to Django:

• Check out https://docs.djangoproject.com/en/dev/internals/contributing/ for information about getting involved.

To run Django's test suite:

• Follow the instructions in the "Unit tests" section of docs/internals/contributing/writing-code/unit-tests.txt, published online at https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/unit-tests/#running-the-unit-tests

Supporting the Development of Django

Django's development depends on your contributions.

If you depend on Django, remember to support the Django Software Foundation: https://www.djangoproject.com/fundraising/

dsf-working-groups's Issues

Idea: Internal tooling WG

The framing of this idea is the typical role that an IT admin would play in a company, who would allow the use/denial of certain services/tools.

This WG would probably be one that would be around for a short while if it gets started and then close until needed again.

Currently from a just Communications perspective, the community uses the following tools:

• Trac
• Forum
• GitHub
• Discord
• Slack
• Mailing lists
• IRC

There would be other categories to consider as well.

While they all have their specific differences and unique nuances, there might be an opportunity for streamlining the tools we use so more people are gathered on a single platform and where appropriate align what is available on each tool (eg forum categories to Discord categories)

The WG would make proposals for wider community acceptance as well as help to either action the required changes or nudge those with privileges to do so.

If there is any budget is spent on these tools, the WG could consider any savings that might be made by consolidating any tooling.

Finally, the WG could look to research the full potential of each tool we use as a community through automations or bots etc.

Form Fundraising WG

The Fundaising WG has been formally approved by the Board but right now it's just a placeholder. Broadly speaking we know we want to form a much larger group to work on fundraising strategy, but beyond that things are pretty open.

I'm opening this issue to track two things:

• interest: if folks are interested in serving on this WG, please express interest here
• Progress on getting the group up and running

Right now (Jan 10 2024), we're essentially waiting on someone(s) to pick up and flesh out what the group does, who will be on it, etc. (See what @sarahboyce did with the Social Media WG as a template for what needs to happen.)

I'd intended on taking lead here, but likely won't get around to it for ... a few months, if not longer. So if someone else is motivated to get things moving, that'd be great, dive in! I'd be very happy to guide/mentor someone if you're interested and have time but aren't sure where to start.

Process Suggestion: Discord for Working Groups to meet

We recently had a suggestion that the Django Discord server could be a potential meeting place for Working groups if they desired.

Briefly Discord has fine-grain permissions/roles to ensure only members have access to the required channels (text and/or video/voice)

I would like to suggest that it be an option for asynchronous communication for a Working Group and perhaps the default for synchronous meetings. This would require a change under "Proposing a working group" to include discord.

I would be happy to raise a PR to suggest the change

Idea: social media / comms WG

One of the next groups we want to form is a social media / communications WG. Let's use this space to start talking about the scope, membership, etc etc.

Open DjangoCon EU Support Group membership to aspiring organisers.

I know it's draft, so suggesting a tweak.

DjangoCon EU Support Group membership currently states:

Membership is open to former organizers of DjangoCon EUs.

That makes sense.

BUUUT... there are lots of people at each DjangoCon EU that have a Ooo, maybe I could do this near me moment. They should be able to join (maybe as an associate member or something) so that they can get a taste, have access to resources on How to do it…, and so on.

It might take a year or two for that moment to grow into an actual drive to do it, but we want to capture and nurture that moment (where at the moment it kind of just evaporates...)

Idea: Website working group

@marksweb suggests:

I think it would also make sense to have a working group for djangoproject.com given the significance of the website for the project & the community.

Currently there's people helping out, and it's fairly easy to find someone if you need something. However if these groups are being created, a more formal approach for the website seems sensible. And I'd be interested in being part of this.

There's also a website redesign on the horizon I believe, so that would also suit a group in it's own right I'd suggest.

The board has talked about this and generally speaking it's probably something we wanna do at some point. I think the next step would be to start to draft a charter (as covered in the README) and form membership.

If folks want to dive in feel free, or if you're just interested in helping out you could use this issue to register interest.