Skip to main content

Community Charter

The Allium community helps bring people together to share their expertise, best practices and processes, tools and technology, and more. Our design systems are focused on collecting working user interface components and emerging patterns so that they can be shared across TELUS digital experiences. By bringing the community together, we can collaborate earlier, include different perspectives, ensure accessibility and usability, and enable a more efficient developer experience. As the Allium Design Systems codify our tools and ways of working, our community helps shape that culture.

  1. Benefits of an empowered community
  2. Roles and responsibilities
  3. Practices

Benefits of an empowered community​

  • Unlock community creativity and domain knowledge expertise; team members know best what their product and application need
  • Enable each other through robust and supportive facilitation
  • Provide knowledge, training opportunities, and self-serve materials so everyone knows what good looks like
  • Focus on reusable and accessible components; align on minimal acceptance criteria and provide processes to audit and improve
  • Empower the community leaders to review and approve each other; avoid bottlenecks by relying on a few

Roles and responsibilities​

All users of the Allium Design Systems UI libraries, component libraries, and documentation are members of the community.

  1. All members of the community
  2. Digital Platform Ambassadors

All members of the community​

  • All are welcome as members of the community, from users to contributors
  • Feedback are wanted and welcome in order to make robust experiences
  • Report bugs, recommend improvements to documentation and components
  • Request or contribute new components
  • Create components with standards and best practices
    • Apply the TELUS brand, design principles, code standards, and accessibility considerations
    • Review art direction and accessibility
  • Communicate early and often
    • Check for existing or similar requests
    • Multiple touchpoints (Github, Slack channels, meetings, office hours)
  • Collaborate openly
    • Get feedback early and avoid re-work
    • Share the workload
    • Different roles can provide perspective and context

Digital Platform Ambassadors​

  • Representatives from sales and services teams, practice and product teams
    • Design and dev leads of respective sales and service teams
    • Art direction and UX from Design CoE (reach out during their respective touch points)
    • Allium team
    • Trusted contributors/committers (promoted from community)
      • Low barrier of participation (front-end developers with a minimum year experience)
      • Have experience and knowledge of global/foundational systems thinking
  • Active participation
    • Strongly encourage attendance to report back to your team
    • If unable to attend, make sure a representative from your team is available
    • Showcase your team’s product-specific components and patterns
      • Meeting certain criteria so contribution is ready for development
      • Reviewing practice
      • Be reminded of progress of contribution
    • Facilitate community meetings
  • Account for community work
    • Plan your roadmaps and schedules accordingly to accommodate contribution work
    • Encourage team members to volunteer design and development time, attendance is key
    • Review designs
    • Review Figma components
    • Review code
  • Shared ownership of the Allium community libraries
    • Recommend publishing to the community libraries to avoid dependency on private libraries
    • Review issues and contributions to the Allium community library
    • Align and assign work effort
    • Approve contributions

Practices​

  1. Allium weekly meeting
  2. Activities and support touch points

Allium weekly meeting​

  • Every Wednesdays at 12 p.m. PST / 3 p.m. EST
  • Reach out the Allium team or your support person for the calendar invite
  • Join #dpa-community Slack channel for news, updates, reminders, and discussions

Activities and support touch points​