Creating the group

If you want to gather people together to work on a task, you should log in and create a group!

Fill in the name you want to give your group and then give some info to explain the aims of the group and how you are collaborating. You definitely want to include in the description:

  1. The URL that describes the list of issues you are working on. For example, the link to Drupal 9 core issues in the Batch API, would be…
  2. Link to Slack / DrupalChat, etc. chat channel if you use one.

Fill in the group image if at possible to make your group easy to recognize in the listing.

Involving people with the skills you need

Fill in the tag content section to help people find you group based upon their interests and skills. The "We need" tag list is especially useful for attracting people with specific skills to your group.

Often, the skills an initiative needs changes as the initiative progresses. To begin with, you might need developers and designers but maybe as it grows you want to add a project manager, maybe some accessibility knowledge, or a documentation writer.

That's why we have made it possible to add "we need" tags to your group as you go, or even post a News Topic in your group, to which you should also apply the same "We need" tags. Then when people are searching for something to get involved with, they can search by their own special skills and find that your group is crying out for them!

Remember to remove tags if you no longer need those skills!

If you need more "We need" tags adding, please raise it via a message in the Contributions Room Management group.

Best practices for group events

Group events are designed to be used for two kinds of things:

  1. Group workshop or Online group meeting type of event. Specific group activities like review sessions or introduction activities that people can be involved in. If you are doing these as DrupalCon BoFs, then that would require a DrupalCon ticket too. You can also use a Jitsi or Zoom or Google Hangouts, etc. for these an involve people that are not DrupalCon ticket holders. The accessibility group has some good examples: a Claro theme review and office hours.
  2. Group's core working hours. Times when leaders or specific people from the team would be available. The Help Topics group has a good example for core group hours.