Coder Social home page Coder Social logo

universe's Introduction

Universe is a decentralized private key recovery app & protocol.
universe.engineering

Roadmap · Feature request · Explore · Slack

follow on Twitter · Star Repo


Table of contents

Status

Universe Community

Bug report

Found a bug or issue? Please first read the issue & bug guidelines and search for existing and closed issues. If your problem is not addressed yet, please open a bug report.

Feature requests

Feature requests are highly encouraged. We want to hear from you on what you'd like to see and/or how you'd like to utilize or access the Universe node network.

› Request a feature

When submitting a feature request, take a moment to find out whether your idea fits with the scope and aims of the project. Please provide as much detail and context as possible.

Contributing

Please read through our contributing guidelines. Included are directions for opening issues, coding standards, and notes on development.

Roadmap

Universe Labs' mission is to become the largest private key recovery protocol.

› Universe Roadmap

View the Universe Roadmap to learn more about project overview, goals, execution to date, milestones, current tech stack, and more...

Community

Get updates on Universe's development and chat with the project maintainers and community members.

Events

Join one of the upcoming Universe and industry related events.

› Upcoming Universe Events

Maintainers

Guy Lepage

Itamar Reif

Jacob Gadakian

License

By contributing your code, you agree to license your contribution under the MIT License.

universe's People

Contributors

aseoconnor avatar faddat avatar guylepage3 avatar

Stargazers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Watchers

avatar avatar avatar avatar avatar avatar avatar

Forkers

cyperh1337

universe's Issues

Weekly Sprint Call - Jul 29, 2019

Description
Engineering Call - Jul 29, 2019.
Attendees: @faddat @itamarreif @guylepage3

Minutes from call

  • Discussed importance of security at during this phase of the project.
    • Decided to think of things in a time sensitive manor.
    • We can add secure infrastructure if it does not hinder project timing too much.
  • Discussed joining more communities to help us learn based upon years and decades of learnings from others.
  • IMPORTANT: Decided that the beta will be Web focused.
    • No mobile apps at this point.
    • We will build for web first and use wrappers such as Cordova to deploy iOS and Android apps.
  • Guy to contact Daniela Perdomo from goTenna Mesh to set up call with team to request learnings.
  • Guy to contact Google IOT Scott Jensen to set up call with team to request learnings.
  • Discussed how to meet sprint in 1 week as Modestos is on holidays next week.
    • GOAL: To get the feather connected to web app displaying keys. Disconnecting feather removes keys on backend and visually "disables" keys on frontend.
      • Task: Backend connect storage to web client.
      • Task (Frontend): Build Bluetooth client.
      • Task (Frontend): Refactor KeyList.js to connect to universe-server, flush keys upon disconnect.

Roadmap: Stationary Node Hardware

Our goal is 100% open hardware, with no compromises

That said, if we want to ship quickly (and we do) then there will necessarily be compromises.

Here's an article on what another company (System76) is doing to move progressively toward 100% open hardware on their line of computers:

https://opensource.com/article/19/4/system76-hardware

Basically, they're opening one sub-system at a time, and progressively moving towards a fully open platform. Another open hardware company, https://puri.sm is taking roughly the same approach.

When we say open, we mean open CPU, open GPU, open PCB, open software-- the whole stack. Right now, we know that we can do open software, and we can maybe do open PCB (unless there are proprietary blobs there (interconnects), as well, and there very well may be) and we can certainly keep the hardware an "open platform" -- meaning that users will be able to run any software that they choose on it.

Tasks

  • Research relative platform openness and completeness-- ex: ARM (and ARM licensees vs one another-- they're not all the same with respect to openness) vs Intel vs AMD vs RISC-V; etc
  • Determine the approximate spec for our first device.
  • Determine just how much of that device's hardware can be open by comparison between vendors
  • Determine the openness-level of drivers for that platform
  • See how binary-blobby (or not) a system image build will be for that platform

Engineering Call - Jul 18, 2019

Description
Engineering Call - Jul 18, 2019.
Attendees: @faddat @itamarreif @guylepage3

Minutes from call

  • Mobile device discovery
    • Not going with the PiNano as it is problematic to get up and running.
    • Going with the Feather and C as the libraries are MUCH more mature as opposed to Rust.
  • Next steps
    • Get a bluetooth server running on the Feather.
    • Get the Feather talking to the web app client.
  • Need to setup a blog
    • First Post: Why the UX is so bad and our mission to solve it.
    • Post a week for 3-4 weeks.
    • Technical post on our solution.

Sprint 11 project management

Description
PM'ing Sprint 11.

Tasks

Any other information you want to share that is relevant to the issue. This might include the lines of code, screenshots, imagery, links, solutions, opinions, feedback, etc.

Fix Slack invitation link as it's no longer working

Describe the bug
Slack share link no longer working. As a result, we need to update the link across...

Replace all instances of old Slack invite link that Slack broke with new invite link.

https://join.slack.com/t/universelabs/shared_invite/enQtNjA2MjM1NjAyNzI0LTUyYWZjM2I5M2VhMTU3YTY3ZGI0YTAwNDQwN2I1Mzc4Yjk3YTg2Y2IxOGMyMDljOTdkM2Y4NTM3ZTAwYzc3NTg
  • GitHub repository README.md files.
  • universe.engineering.
  • Universe Web App.

Remove newsletter email addresses from #social channel

Description
The Mailchimp integration in the (public) #social channel in Slack posted the subscribing email addresses. Although it's fixed now (#33), there are still the old messages containing email addresses in there.

Tasks

  • Remove every message by hand or find a way to remove all messages of the Mailchimp integration at once

Universe Community Update, Issue 3

Description
Universe Community Update, Issue 3 - Bi-Weekly newsletter.

Reference(s)

Tasks

Enhancements
List possible improvements on the newsletter.

Universe Community Update, Issue 2

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

End of Week Sprint Call - Sep 20, 2019

Description
End of Week Sprint Call - Sep 20, 2019.
Attendees: @faddat @itamarreif @guylepage3

Minutes

  • Publicly verifiable secret sharing
  • Want to have it running in the browser
  • Building in the browser
  • Using Typescript for Core

MVP

  • Run it in the browser
  • Using Typescript for Core
  • Build Javascript API
  • Build Web app / Dashboard / Social Proof UI
  • Local storage
  • Core service on top of the file wallet

Possible content for website

  • You care about decentralizing your key management talking about doing decentralized key recovery
  • Prove
  • VALUE from MVP:
    • UX of a good decentralized SSO
    • UX of the dashboard
    • Social proofs easy

Move Sprint 7 issues to Sprint 8 board

Description
Move Sprint 7 issues to Sprint 8 board and add to critical path.

Tasks

  • Define this week's KPI (Key Performance Indicator).
  • Move sprint issues to new current sprint board.
  • Close previous sprint board and open upcoming sprint board.

RfC: Ideas for Venezuela

Request for Comment

Request for Comment from the community about how Universe may assist Venezuelan's with their quest in a regime change and rebuilding their government and economy.

I attended a Galaxy Digital event last night and ran into Santiago Siri, Founder of Democracy Earth. https://twitter.com/santisiri. Santiago used to work out of our offices at Blockstack.

@dant and I attended a “Help Venezuela” workshop at Consensus on Tuesday morning. Someone from Democracy Earth was on one of the 3 panels they had. DE is looking to provide Venezuelans with decentralized voting. They currently use Blockstack ID’s for their identity.

Dan and I were chatting and thinking of ways Universe can assist Venezuelans with ID’s and at the event last night, I asked Santiago how we can help and he said we should get together and brainstorm.

One ambitious long term goal is to provide them with decentralized Blockstack/Universe ID cards. Physical cards.. and digital cards.

I know David Kelts from https://www.idemia.com/ and can reach out to him. David produces 48 states driver’s license ID cards, all of Canada’s and quite a few of Europe’s as well. I’ve had conversations with David at past IIW https://internetidentityworkshop.com/ events about this.

I'd love for everyone to assist.

Consensus session

Tue May 14/ 10:00 AM - 12:00 PM ( 2 Hours )

Not the Petro: Bottom-Up Blockchain Ideas for Venezuela

Room A, Concourse Level

Cryptocurrency has become a lifeline for many Venezuelans seeking respite from the country's dramatic collapse. Hear first-hand from the projects operating on the front lines, and contribute to a broader discussion on how blockchain technology can help rebuild Venezuela's economy and institutions.

Workshop

Speakers

Joe Waltman
Executive Director
GiveCrypto.org
Speaker

Ruben Galindo
CEO
Airtm
Speaker

Eduardo Medina
Lead Developer
Democracy Earth Foundation
Speaker

Mariano Di Pietrantonio
Community Lead Latin America
MakerDAO
Speaker

Jonathan Kohn
CEO and Co-founder
Cripto Conserje
Speaker

Daniel Knobelsdorf
Blockchain Strategist
Kruger Corp
Speaker

Moises Rendon
Associate Director & Associate Fellow
Center for Strategic & International Studies
Moderator

Bailey Reutzel
Multimedia Editor
CoinDesk
Moderator

Yaya Fanusie
Senior Felllow
Foundation for Defense of Democracies
Speaker

Fernando Cutz
Senior Associate
The Cohen Group
Speaker

Elena Sofia Giralt
Meetup Organizer
Blockchain Latinx
Speaker

Alex Gladstein
Chief Strategy Officer
Human Rights Foundation
Speaker

Daniel Sierra
Public Policy Advisor
Venezuelan Embassy
Speaker

Armando Armas
Congressman
Venezuela National Assembly
Speaker

Betilde Muñoz-Pogossian
Director of the Department of Social Inclusion of the Secretariat for Access to Rights and Equity
Organization of American States
Speaker

Josh Swihart
Vice President, Marketing and Business Development
Electric Coin Company
Speaker

Not-the-Petro--Bottom-Up-Blockchain-Ideas-for-Venezuela

Interesting resources regarding DApps

This is a place to collect and discuss interesting resources from the community which address issues tightly or loosely related to dApp development, lifecycle and usage.

Key/identity management

Authentiq

With [the] mobile app, Authentiq ID, you can create a verified ID on your phone and use this to sign in safely with just a touch. No personal data is stored in centrally, it's only exchanged with your consent, and cryptographic keys never leave your phone. (source)

Decentralized peer-to-peer network, Phase 3 roadmap

Description
This is a rough mock of our plans to expand Universe's key recovery service. The recovery service would augment the currently planned Core+API+KeyManager architecture, most likely by adding recovery endpoints to Core.

Network
Using a decentralized peer-to-peer network, keys would be split and distributed among the participants, likely in a threshold-based construction. Retrieval from the network would require the user to provide an authorization token obtained from the KYC process.

Important issues that need to be addressed are arbitrary key storage, figuring out the KYC process, and the degree of decentralization we wish to allow. It would be interesting to allow users to chose their KYC provider out of a set of network-supported providers, allowing for different security models, varying "depths" of KYC, etc.

Experience
The main goal is to achieve the recoverability offered by BIP32-esque constructions that use a mnemonic while providing the user a much more "human-readable" experience. Intuitively, this allows users to recover their cryptographic keys using their tangible, real-world identity, rather than an arcane mathematical process. The identity verification process is already one that consumers are familiar with and are willing to accept at the event that they lose access to their bank or credit card.

Additionally, part of Universe's experience would offer a streamlining of the KYC process meaning that KYC information would already be provided once during the users' onboarding process.

Single Board Computers

Single Board Computers
This is a list of single board computers that it makes sense to try out. Once we've got a hardware platform we feel comfortable with, the next step is to create an image builder so that we can do a build that works like:

board os -> Universe software -> .img file for immediate testing

This way, we can make changes to software and rapidly test them running on our chosen hardware.

Devices

  • Raspberry Pi 3B+
  • Pine Rock64 4GB LTS
  • Pine A64+
  • Pine A64 LTS
  • SiFive HiFive
  • Orange Pi PC
Device Pirce Processor RAM Wifi
Raspberry Pi 3B+ $35 4-core-arm (Brodacom) 1GB Yes
Pine Rock64 $45 4-Core-Arm64 (Rockchip) 4GB No
Pine A64+ $29 4-core-arm64 (allwinner) 2GB No
Pine A64 LTS $32 4-core-arm (allwinner) 2GB Yes
SiFive HiFive $1000 4-core-RISC-V 1GB No
Orange PI PC $15 4-core-armv7h (allwinner) 1GB No

Engineering Call - Jul 24

Engineering Call

Date: Wed, Jul 24, 2019 10am.
Attendees: @itamarreif @faddat @modkaffes @guylepage3

Minutes from Call

Goals

  • Have the web app interacting with a running mobile/feather device in a client-server relationship by the end of Sprint 6.

A few useful resources discussed:

Please comment with any more relevant links and ideas!

Proposal: Update to path to obfuscation and beyond...

Sharing a few ideas Guy and I had yesterday about using the Adafruit Feather to obfuscate passwords from the user. Here's a summary of what we had in mind:

  • sign up with your universe account to the universe app
  • app will sync/pair with feather device
  • when "logging in with universe", the app will request auth from the feather device
  • if the app is installed on a trusted device, feather will authenticate and tell the app where the storage server is (which will then be cached on the trusted device)
  • if the device is not a trusted one, the feather will request confirmation from a trusted device and then confirm back to public device, providing location of storage server too
  • app will then request keys from storage server, using feather to decrypt them

So Guy ordered a few devices for us to start working with and the idea is to incorporate them over the next couple of sprints and create the "bare bones" universe product with the storage on the node, dashboard webapp, and the feather device as a sort of authentication.

Please share your thoughts!

Feedback on the questionnaire

Quick feedback on the questionnaire:

  1. I'd drop the question mark at the end of the single sentence in the middle. Technically it's no question and without it the sentences stands quite bold :)
    Probably also add an "to help you out with this" at the end ("We want to know what is blocking your dApp from growth and mass adoption to help you out with this.").
  2. State more prominently that this is still an open problem (or that we even search the exact problem) and people can contribute to that or even direct us in where it goes.
  3. I'd like to see name and email address optional, as they aren't really required for this. People who don't want to give this out enter some trash there so or so I guess :)
    This change should also include a small note why the email address is needed ("To easily reach out on questions or when looking for more input"). And probably also a small note that this won't go into an email list for newsletter.

Researching Cosmos

Description
As a result of deciding to go with Cosmos for our recovery app, @faddat will need to research some unknown unknowns.

Tasks

  • Find out how fees work.
  • Find out how to acquire Atoms as we are in New York state and it's difficult to purchase them due to the bit license.

Setup simple command line & git reference for beginners

Description
Setup simple command line & git reference for beginners. Such as designers, marketers, etc.

Documentation tasks

  • Terms & Terminology
  • Bash or Terminal Shell Commands
  • Developer Tools and Developer Environment Setup
  • Workflow
  • How to commit code changes
  • Terminal Shell Environment Setup

Sprint 11 – Critical Path

Description
The following is a critical path list of all tasks needed to execute to meet the goals for the release of the Universe Key Recovery App Alpha.

Goals
Get a full alpha where users can enter their back-up passphrase in order to "split" apart their back-up passphrase, and manually share 3 "parts" with 3 trustees. The user should also be able to combine the 3 "parts" in order to view the back-up passphrase.

  • The app should utilize Shamir's Secret Sharing.

References

Other Critical Paths

Tasks

Weekly Scrum Call - Jul 8

Description
Weekly Scrum Call
Jul 8, 2019
Attendees: @dantrevino @modkaffes @faddat @itamarreif @guylepage3

Minutes

  • Modestos completed auth front end wire up. 🎉😎🎉😎🎉😎
  • Guy and Dan to review PR's from Modestos.
  • Itamar to create issue containing C resources for Jacob.
  • Itamar to create issue on talking to professor about best language to use.
  • Itamar to create issues for next steps.
  • Guy to order all Pi's.
  • Jacob and Itamar to organize repos.
  • Guy to continue on with investor meetings.
  • Talking to Lukas Etter about Swiss entity.

Write blurb for Will Seggos' blog post

Universe is an open, blockchain agnostic UX solutions community working removing blockers that are impeding growth and mass adoption of dApps.

We have been talking to dApp developers, crypto platform founders, VC's and as many individuals in the crypto community to discover what the main blockers are today.

The largest issue facing developers seems to be either on-boarding or re-engaging users. Some platforms have a long, on-boarding experience while others on-board users quickly but then lose users after they need to relink or sign back in to their account.

These issues are derived from key management.

The Universe community is focused on solving the key management issue by providing a one time setup and key management app that allows users to sign up and stay connected easily. The first stage in attacking this problem is to build the key management app followed by offering an always on, open source node device to give users ownership of their keys.

We're looking for engineers, designers, dApp developers to join the community and work together on solving these major issues with blockchain technology adoption.

Sprint 6 – Critical Path

Description
The following is a critical path list of all tasks needed to execute to meet the goals for the release of the Full Alpha Demo with Feather Device.

For Sprint 6 we have the goal to get a full alpha demo with the feather working. The following tasks are required to do so.

References

Tasks

If time

Move Sprint 10 issues to Sprint 11 board

Description
Move Sprint 10 issues to Sprint 11 board and add to critical path.

Tasks

  • Set up new Sprint kanban board.
  • Define this week's KPI (Key Performance Indicator).
  • Move sprint issues to new current sprint board.
  • Close previous sprint board.

Universe architecture v1

Description
We need to design a software architecture that is scalable, secure, modular, and as open as possible. The architecture also needs to provide an exceptional UX for users and be as decentralized as possible.

Elements

  1. Core
    A Go service that runs locally, orchestrating between the different parts of the system. It will handle incoming requests from the UI or API, routing them to what is now the Bluetooth (feather/notary) device or the storage node. Similarly it will pass information returned from the Bluetooth device back to the UI or API.
  2. User interface (e.g. web app, CLI)
    The user interface will communicate with the Core service using a locally exposed REST API (for now, this will, most likely, be changed). Actions initiated by the user will be passed to the Core service for handling.
    This will be a modular part for which Universe will build a web application implementation, but a CLI or a different web app could be built just the same, each offering a different experience, or different levels of control over security parameters.
  3. API
    For integration into other apps, an API providing functionality such as signing transactions, logging in, etc., will be exposed in a similar fashion from the Core service.
  4. Key Manager (e.g. Bluetooth device, Ledger, Apple's enclave)
    This is the only part that accesses the plain keys. It will be isolated from the rest of the system for security, and will return the signed transactions, validated tokens, etc.
    The intention is for this part to also be modular, allowing for the integration of any device that securely stores the keys. For example, a Ledger driver or an implementation using Apple's Secure Enclave could both be built.
  5. Vault storage & recovery
    This is the software that will run on Universe's home nodes. These nodes will contain a local backup of a user's vault ciphertext. However, this could be replaced by other implementations in a similar manner. For example, one could use their personal home backup system (e.g. Apple Time Machine).

v1 Universe software architecture hand sketch

2019-08-09-universe-software-architecture

from @itamarreif

Update Slack invitation link with new link to form

Describe the bug
Update Slack invitation link with new link to form as Slack links can become deprecated.

Replace all instances of old Slack invite link with new invite link to form.

https://universelabs-slackin.herokuapp.com/
  • universe.engineering.
  • GitHub repository README.md files.
  • Once URL resolves, create a new issue to update again in Sprint 10. Done #49.

References

Versioning and releases

Description
We should choose a process for versioning and releases that allows us to easily deploy while being responsible with our software releases.

Versioning Reference(s)

Release Reference(s)

Deliverables

  • Guy to update README.md files to pull from Git Tags.
  • Team needs to push releases where necessary. alpha, beta, etc. releases where applicable.

Build out README.md and repository

Structure

  • Header
  • Status
  • Quick start
  • Report bug – (Links to new CONTRIBUTING.md#bug-reports)
  • Feature requests (short version)
  • Feature requests
  • Contributing – (Links to new CONTRIBUTING.md)
    • Using the issue tracker – (On new CONTRIBUTING.md)
    • Bug reports – (On new CONTRIBUTING.md)
    • Pull requests – (On new CONTRIBUTING.md)
    • Feature requests – (Links to README.md#feature-requests)
    • Code guidelines – (On new CONTRIBUTING.md)
    • Versioning – (On new CONTRIBUTING.md)
  • Roadmap – (Links to new universelabs/universe/#ROADMAP)
  • Community
  • Events – (Links to new universelabs/universe/#EVENTS)
  • Repository maintainers
  • License section
    • Create LICENSE
  • Add Open source icon
  • Create Bug report template
  • Create Feature request template
  • Create Custom issue template

Move Sprint 8 issues to Sprint 9 board

Description
Move Sprint 8 issues to Sprint 9 board and add to critical path.

Tasks

  • Set up new Sprint kanban board.
  • Define this week's KPI (Key Performance Indicator).
  • Move sprint issues to new current sprint board.
  • Close previous sprint board.

Roadmap: Specs discussion

Based upon the feedback for the community, dapp developers, and platform founders, Phase 1 focus is key management software. Phase 2 we will be moving over to hardware device for key management. Universe targets onboarding dApp users with one setup for all major platforms.

  • For v1, we will focus on managing users' “less secure” private keys and most importantly sign up on the top 5-10 services all at one time
    • Less secure would mean, social app identity
    • More secure (something we’ll do later) - identity key management for serious apps that manage your health data, government id, etc.
  • We want 1 single place to go for our MetaMask, Blockstack, DID, Solid, U-port, Civic, etc. identities and phrases, keys, or whatever else people are calling crypto passwords backups.
  • We want a password because passwords work.
  • We will need to pay attention to how each platform signs up its users, then sign them up on each platform and then encrypt and store their backup phrases.
  • Universe is a fail-safe place for users to go when they forget their back up phrases.
  • Despite we want to use a shared decentralized identity standard like the one developed at Decentralized Identity Foundation, we want to figure out an alternative way if things are moving slowly with the standard.

Weekly Scrum Call - July 22, 2019

Description
Weekly Scrum Call
Jul 22, 2019
Attendees: @modkaffes @faddat @itamarreif @guylepage3

Minutes

  • Guy updated team on seed round funding.
  • Discussed the current state of the deck.
  • Blog: We want to self-host our blog
    • @modkaffes to research Gatsby to see if it has good SEO support. If it does not, then we will have to go with Ghost.
    • Guy has roughly 20 posts ready to go.
    • First post should be on "Why what we're doing is so important."
  • We will be extending our current sprint by one week.
  • @guylepage3 to clean up sprint kanban board.
  • @guylepage3 to present team with new Roadmap.
  • Discussion around website update. Not to be updated.
  • Next sprint
  • Jake to go through readmes and create a readme issue. To use @guylepage3's readme template.
  • @guylepage3 to post one-paragraph project explainer from investor intro e-mails in an issue in the same spot as our deck issue.

Here comes a great week!

Look into Mailchimp Slack app preferences

Description
Look into Mailchimp Slack app preferences.

@dantrevino mentioned the following in Slack.

Dan 11:38 PM
@guy i'm not sure putting peoples email in public #social channel via mailchimp is a good idea. Is there an opt-in for doing that?

As a result we should look into finding a solution that does not expose subscriber's email address.

Map Slack invite URL slack.universe.engineering to Slackin URL

Description
I’ve set us up with a new “Slack” invitation page with reCAPTCHA so that we can onboard users easier as well as not have to worry about the Slack invite links disappearing.

https://universelabs-slackin.herokuapp.com

As a result we now need to point https://universelabs-slackin.herokuapp.com to https://slack.universe.engineering.

Tasks

References

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.