Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

To address the challenges outlined in "Enhancing the Core Contributor Experience," I propose the following solutions to benefit both newcomers and the broader Core Contributor community:

Centralized Documentation:

  • Perform a thorough audit of existing documentation and consolidate it into a well-organized central repository. This will address the current challenge of overwhelming and dispersed information.

Enhanced Content Order and Quality:

  • Improve clarity, engagement, and informativeness of the content. Ensure accessibility for both technical and non-technical users. Implement a search, structured table of contents, cross-referenced links, and a logical content arrangement to facilitate easy navigation. Address issues of scattered information that complicate access for new Core Contributors.

Identify Content Requirements:

  • Define the New Handbook Structure

    • Based on survey feedback and existing Core Contributor information, outline the sections of the Handbook that can be developed progressively.

    • Key Information to Include based on the Survey Feedback:

      • Define abbreviations and terms (e.g. CC, OEX, TOC, OEP, ADR).

      • Clearly articulate the Core Contributor’s purpose, vision, and mission.

      • Outline actionable steps for involvement, including role-specific links.

      • Structure content based on roles, similar to GitLab’s role-based handbook model.

      • Define responsibilities for various Core Contributor roles.

      • Provide guidelines for assessing commitments to ensure accountability.

      • Offer guidelines for effective use of communication tools as proposed by Ali Hugo.

      • Include the contact details of a specific representative for role-specific guidance.

      • Detail the sprint process and outline expectations for each Core Contributor, including check-ins if necessary.

      • List all active working groups with links to their collaborative spaces.

      • Decide which information to include directly in the handbook and which to reference through links (e.g., Product Review Process, Product Proposals).

Easy Submission of Changes:

  • Host the handbook in a GitHub repository to facilitate easy submission of changes through formal pull requests. This will allow others to review and approve changes before they are implemented in the Wiki, or similar.

Add Handbook Link to Core Contributor Onboarding Course:

  • Ensure the handbook is linked in the Core Contributor onboarding course for easy access and reference.

Impact

To measure the effectiveness of the handbook, we could use the following metrics:

  1. Usage Statistics: Use built-in analytics to monitor the number of views and interactions with the handbook. Confirm if current tools already capture this data.

  2. Newcomer Feedback: Send a brief, automated survey to new Core Contributors shortly after onboarding to gather quick feedback on clarity and usefulness.

  3. Information Clarity: Monitor the number of support requests Axim receives related Core Contributor responsibilities. Confirm if current tools already capture this data.

...