Code of Conduct
Idea Description
The Django Commons team is looking to add an asynchronous chat platform to the organization and exploring integrating with the Django Discord server.
Which existing platforms would this idea affect?
Rationale
Django Commons is a subcommunity of the Django community. It's meant to be community owned third-party packages and is seeking to adopt sustainable practices. This in large part means getting more people involved. Given that the third-party ecosystem is a major strength of Django as a whole, a stronger integration could help improve the community as a whole.
Problem
Django Commons is going through changing the admins and currently has a team of 8. We've primarily relied on in-person meetings to communicate, but that's no longer an option with meetings of that size. Email isn't a preferred option at this time, which leaves a chat platform.
Would you like to be involved in this idea?
Other Contributors
For now this would be the Django Commons admin team, which is 8 people:
- bckohan
- cunla
- Daksh777
- ryancheley
- Stormheg
- TildaDares
- tim-schilling
- williln
Other Details
We're currently settling on Discord as the best of the free options. We're unsure if we'll roll our own or set up our own server. We feel it'd be easier to transition from a few channels in the Django discord to our own server rather than the reverse.
What is the feasibility of the following options:
- Single private channel for Django Commons admins
- A private channel and a public channel
- A private channel, public channel, a private video channel and a public video channel
That third option would be used for us hosting partially public meetings on the Discord to help people get involved in the community work.
Code of Conduct
Idea Description
The Django Commons team is looking to add an asynchronous chat platform to the organization and exploring integrating with the Django Discord server.
Which existing platforms would this idea affect?
Rationale
Django Commons is a subcommunity of the Django community. It's meant to be community owned third-party packages and is seeking to adopt sustainable practices. This in large part means getting more people involved. Given that the third-party ecosystem is a major strength of Django as a whole, a stronger integration could help improve the community as a whole.
Problem
Django Commons is going through changing the admins and currently has a team of 8. We've primarily relied on in-person meetings to communicate, but that's no longer an option with meetings of that size. Email isn't a preferred option at this time, which leaves a chat platform.
Would you like to be involved in this idea?
Other Contributors
For now this would be the Django Commons admin team, which is 8 people:
Other Details
We're currently settling on Discord as the best of the free options. We're unsure if we'll roll our own or set up our own server. We feel it'd be easier to transition from a few channels in the Django discord to our own server rather than the reverse.
What is the feasibility of the following options:
That third option would be used for us hosting partially public meetings on the Discord to help people get involved in the community work.