Determine standard process for onboarding projects (working groups, etc)

Circling back here as creating the structure (essentially what this issue is about) for the community to organize and sustain is a primary goal of this group (and the fundraising campaign we're in the process of launching).

As mentioned in previous comments (and several Slack discussions), I think updating and restructuring the Drupal Contribution Areas → to function more like WordPress Teams could be a solution.

The Global Community Team (which functions as the 'umbrella' group for the entire community) provides some good inspiration.

• Team Pledges

- the driver of this is the Five for the Future program that encourages organizations to contribute five percent of their resources in the form of full and part-time community contributors. The result is hundreds of contributors able to spend thousands of hours per week focusing on community.

• Team Members

- each team has multiple part/full time members assuming well-defined community roles

• Meetings

- regularly scheduled Slack meetings with a well-defined format and roles (see this section of the WordPress community handbook)

• Working groups

- working groups and initiatives are treated more like separate projects rather than something 'owned' by a team; so I think this already translates considering Drupal Contribution area pages reference related initiatives and working groups.

• Projects

- each team defines its own goals and priorities; as a result there are several well-defined, active projects (see the Community team's project page for a good example)

• Posts

- every team creates content frequently; this is because teams are able to contribute more time

Considering we'll have the ability to enable and credit financial contributions (via extending the Funding module and crediting system), our contributions to improving/extending the contributor guide → create a more robust structure for a much larger, active and organized community than what we have now.

We should have the capacity to do both once a few organizations and individuates can help us make it happen!
https://opencollective.com/drupal-contribution/projects/community-enable...

Referencing #3357732: Policy: Accept funds on behalf of particular working groups and initiatives → before closing as duplicate (or requesting) as that issue does not introduce or attempt to resolve anything not already addressed here.

Accept funds on behalf of particular working groups and initiatives

This is not a policy since Drupal Contribution (the non-profit organization → ) does not have capacity to do anything beyond providing tools and resources to projects (see the Open Collective definition) and groups we support (see [#3280977}).

While earmarking funds downstream to projects could happen in the future - we first need to compensate the people committing time (as a contractor or future employee) required to operate and sustain (see {#325492]).

The main positive outcome of the issue and Slack discussion from earlier today was an entry point for documentation (a primary goal/outcome of this and it's parent issue from the start)[#3325045}

• Update and improve the Contributor Guide →
• Update and restructure the Contribution Areas landing page → ; consider consolidating with the Community landing page →
• Update and structure each contribution area so the landing pages are consistent and welcoming to contributors; standardize and include elements like team members (including an aggregate of contributor time), meetings, working groups, projects posts, sponsors, etc.
• Improve and extend contributor task, role, and skill pages →

Piggybacking on some related discussions about Drupal platforms/tools and Open Collective (as an open source funding platform + fiscal sponsor service), I mentioned the following in #event-organizers (Drupal Slack):

Word on the street is there may soon be a EOWG project on the Drupal Contribution collective (the process is still evolving but EOWG team/board members are involved in #drupal-contribution-group).

• Projects are a lightweight way for collectives to manage budgets for initiatives independent of their parent collectives. Use a project if:
• You would like to collect funds for a specific initiative or idea
• You would like to allocate part of your collective's budget to a specific initiative
• You would like to track the spending on a specific initiative separate from the rest of your collective

Projects have many of the same features as Collectives. Projects have their own balances, contributions, and expenses. Projects can describe contribution tiers, set goals, and provide updates.

If/when that happens, EOWG will be able to use these platforms and funding tools to sustain w/o needing to apply/create your own collective (which still might be a good option down the line).

I thought it was important to copy/paste the Open Collective docs on projects to clarify the independence and responsibility a project like EOWG would have.

Per my last comment, we now have a starting point for defining and documenting a process and policies. In the meantime we can direct questions and evaluations here.

Transferring this responsibility over to the Sustainability Team.

Closed as not needed until parent issue #3377002: Create top-level Drupal collective (Open Collective) → is approved.