Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Universe Community Update, Issue 2 #10

Closed
9 tasks done
guylepage3 opened this issue Mar 19, 2019 · 2 comments
Closed
9 tasks done

Universe Community Update, Issue 2 #10

guylepage3 opened this issue Mar 19, 2019 · 2 comments
Assignees
Labels
growth Growth and/or marketing related item(s) and issue(s)

Comments

@guylepage3
Copy link
Contributor

guylepage3 commented Mar 19, 2019

Description
Universe Community Update, Issue 2 - Bi-Weekly newsletter

#9 Issue 1 - Mar 5, 2019

Tasks

  • Header imagery
    • Highlight for imagery - Meta Docs
    • Imagery
  • Overview
  • Current focus
  • Update
    • Highlight for imagery - Universe.engineering
    • Imagery

Enhancements
List possible improvements on the newsletter.

  • Add what's ahead section
@guylepage3 guylepage3 self-assigned this Mar 23, 2019
@guylepage3 guylepage3 added the growth Growth and/or marketing related item(s) and issue(s) label Mar 23, 2019
@guylepage3
Copy link
Contributor Author

guylepage3 commented Apr 2, 2019

Universe

universe-newsletter-issue-002-header@2x

Universe Community Update, Issue 2

Tue, Apr 2, 2019

Welcome to the 2nd Universe Community Update.

Let's make this newsletter better!

Please let me know if there's anything you'd like me to add or remove from the newsletter. Contact Core Team. Feedback is welcome. Thank you.

Current focus

We are moving back to an 80% focus on funding for Universe and 20% on product and growing the team.

Update

The last few weeks have been filled with Meta product releases, key management scaffolding, funding and administrative work and inbound hiring.

We unintentionally, pulled back from funding and focused on product as well as managing quite a bit of inbound admin and HR.

On the key management side of things, we made some progress with architecture. And the open source community made some contributions to refactoring universe.engineering on the back end in anticipation for the v1 beta build.

With the public release of Meta v1.5 and documentation, we have been receiving great feedback from developers and have been making patch updates to both the software and documentation. If you have any issues or feature requests, please let us know.

There has been a spike in folks looking to work on the project. If you are wanting to work as a Core Team member at Universe Labs, the best thing you can do is join the Slack and/or start contributing to the project. All forms of contributions are welcome.

Execution over the past few weeks

  • Refactored universe.engineering in prep for v1 beta key management software.
  • Started on a new architecture for universe.engineering.
  • Released Meta v1.5 with Documentation.
  • Customer feedback and patch updates to Meta and Meta documentation.
  • Research and development on the Universe Node hardware device.
  • We've officially secured some pre-seed funds through a couple of investors (Announcement coming soon).
  • Started working on a new Docs site for Meta, meta-ui.com.
  • Started working on new open source product, UX Flow Sketch Library.
  • Update to Meta UI Sketch Library.
  • Started working on Cosmos, Blockstack, Universal Login, MetaMask integrations.

universe engineering-v1 7 4

Screenshot of universe.engineering v1.7.4 (GitHub).

What's Ahead?

In the coming weeks, we are looking to make some headway with universe.engineering key management software and finalize project funding. We will also be updating the Roadmap and announcing attendance at a couple of events.

@guylepage3
Copy link
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
growth Growth and/or marketing related item(s) and issue(s)
Projects
None yet
Development

No branches or pull requests

1 participant