Skip to content

Milestones

List view

  • No due date
    0/5 issues closed
  • We should have at this point a functional version of Behavior Graphs integrated in Hubs, this meaning: - The code should be merger in the Hubs main branch - All the current supported Blender Hubs components should have their counterpart nodes to update their properties and listen to their events. - Functionality should work on Desktop, Mobile and VR - Components should have networking support.

    Overdue by 1 year(s)
    Due by November 1, 2023
    0/3 issues closed
  • No due date
    24/26 issues closed
  • Current Work in progress based on past discovery and exploration

    Overdue by 4 year(s)
    Due by March 31, 2021
    1/2 issues closed
  • How do we work? Organize and document our tools and practices

    Overdue by 4 year(s)
    Due by June 30, 2021
  • As a prominent pioneers in the field, Hubs & Mozilla have a responsibility to contribute to the organizations that shape the future of the XR/AR/VR world Identify standards bodies that (will) influence the VR/AR industries in ways that are pertinent to Mozilla's mission by Q2 Work with firefox as browser based standards Estimate the cost of participation (in time, money, skills, code, legal etc) to stay "minimally active" in each of those bodies that we care about by Q2 Appoint or find volunteers who want to represent Mozilla in these groups and support them by Q3

    Overdue by 3 year(s)
    Due by January 1, 2022
  • As a team, we comb through the entire application and find suggestions for the dev team to consider adding to the current body of work. Prioritize suggestions by size and urgency. Filter suggestions that may be involved in larger initiatives. Team evaluation of app Affinity map pain points/suggested solutions Address all outstanding issues in Hubs Backlog Evaluate priority of suggestions Propose suggestions to product team

    Overdue by 4 year(s)
    Due by June 30, 2021
    1/22 issues closed
  • Mozilla Hubs branding Structured organized Figma file; easy to use for anyone who need branding material Set vision and feel of brand of Hubs Established guidelines on usage of branding artwork All current channels unified including but not limited to Twitter Twitch Youtube Vimeo Discord Implemented in a design proposal for a rebrand of Hubs.Mozilla.com (HMC) version 2.0

    Overdue by 4 year(s)
    Due by June 30, 2021
  • Turn current Hubs UI into a standard Design System Set vision and mission of system Set guidelines of use Building out the file utilizing best practices in Figma Standardize component labelling and layout Agreed upon workflow for managing version history Extend the library with new components Document & Share outside of the Mozilla community Hubs design system

    Overdue by 3 year(s)
    Due by December 31, 2021
  • As we grow the Hubs eco-system, we need to research and explore alternative ways that Hubs can produce income as well as highlight any additional value propositions Review previous exploration by conducted by Product co-development agreements partnerships revenue sharing others... Explore new opportunities Document all arrears of exploration Propose at least one(1) alternative business model option

    Overdue by 3 year(s)
    Due by December 31, 2021
  • 3d artists creators ecosystem, what tools do they need

    No due date
  • Establish a presence within all major communication channels (Discord, Twitch, Twitter, etc.) and track channels, members and activities Actively engage with the community, as measured by min twelve(12) “Feedback Posts” newsletters and min twelve (12) live meetups with the community

    Overdue by 3 year(s)
    Due by December 31, 2021
    0/1 issues closed
  • To produce a testable prototype demonstrating a number of proposed new features and experience enhancements within a cohesive Hubs system. The prototype need only be to a standard suitable for testing, placing emphasis on a cohesive system over polished individual parts. This is to be delivered by the end June 2021.

    Overdue by 4 year(s)
    Due by June 30, 2021
    1/9 issues closed
  • Leverage design expertise to make the product more accessible "Create an “Accessible Hubs” community on Discord by Q1; identify members and define use of channel Audit Hubs design system for accessibility by H1 Exploration into Accessible Hubs VR; conceptualizing new solutions; emphasis on headset by EOY · Generative workshop to gather pain points & potential concepts · Hackathon for theoretical solution implementation" Proposal for short term & long term implementation plan by EOY

    Overdue by 3 year(s)
    Due by December 31, 2021
    0/2 issues closed