dotnet-foundation / dotnet-foundation/projects

Our World & The OASIS API

Open
#116 0 comments 0 reactions 2 assignees View on GitHub

@clairernovotny is already working on this.

Since Nov 3, 2020.

project application
Dominant language
No language data
Stars
157
Forks
37
PR merge metrics
No merged PRs in 30d

Description

1.   General Information

Project Name:

Our World

License:
GNU

Contributor (Company, Organization or individual name(s)):
NextGenSoftware Ltd/NextGen World Ltd/David Ellams/vhurryharry Alexander/jasonliudan Jason Liu

Existing OSS Project? (Yes/No):
Yes
Source Code URL:
https://github.com/NextGenSoftwareUK/Our-World-OASIS-API-HoloNET-HoloUnity-And-.NET-HDK

Project Homepage URL (if different):
http://www.ourworldthegame.com

Project Transfer Signatories:
Full legal name and email address required of the individual(s) with the authority to transfer or contribute the project to the .NET Foundation. Note that if you'd prefer not to include this in the public application, it can be submitted via e-mail to contact@dotnetfoundation.org (referencing this issue number).

David Ellams (david@nextgensoftware.co.uk) - Founder/CTO

2.   Description

Please provide a brief statement about your project in terms that are understandable to the target consumer of the library or project, i.e. an elevator pitch for the project:

Our World is an exciting immersive next generation 3D XR/IR (Infinite Reality) educational game/operating system/ascension
training platform/social network/ecosystem teaching people on how to look after themselves, each other and the planet using
the latest cutting-edge technology. It teaches people the importance of real-life face to face connections with human beings and
encourages them to get out into nature using Augmented Reality similar to Pokémon Go but on a much more evolved scale. This
is our flagship product and is our top priority due to the massive positive impact it will make upon the world...

Our World will be the first AAA MMO game and 2D/3D Social Network to run on HoloChain and the Blockchain. It will also be the first to integrate a social network with a MMO game/platform as well as all of these technologies and devices together. As with the rest of the game, it will be leading the way in what can be done with this NextGen Technology for the benefit and upliftment of humanity.

Our World is an open world real life simulation game. The smartphone geolocation AR version will have similarities to Pokémon
go but with a far more evolved, immersive, and personal feel. It will act as a decentralised distributed crowd sourced
replacement to Google Maps/Earth. Each user will create an avatar that will act as their digital twin just as the 3D world acts as a
digital twin of the real world. Phase 1 is the AR version which we are aiming to have finished by next year with some help. Phase
2 is the 3D VR Console/Desktop version which we are aiming for 2022/2023, again with help from a team.

Please provide a 1 sentence (<140 character) summary of your project to help users when searching the .NET Foundation projects

Our World is an exciting immersive next generation 3D XR/IR (Infinite Reality) educational game/operating system/ascension
training platform/social network/ecosystem teaching people on how to look after themselves, each other and the planet using
the latest cutting-edge technology.

3.   Project Governance

Please complete this section about who will be maintaining the open source project and how it will run.
Project Lead:
(Who is the primary contact point for the community and the .NET Foundation when discussing governance of the project.)

Name: David Ellams
Email: david@nextgensoftware.co.uk
GitHub Profile URL: https://github.com/dellams

Committers:

Which individuals have commit / write access to the repository, what is their GitHub ID and who is their employer (if contributions are on behalf of an employer)

https://github.com/kevinbanas
https://github.com/blacqvve
https://github.com/Cslater1990

They are all independent open source contributors.

Governance Model:

Please describe how new code changes are proposed to the project, how those changes are reviewed and how a decision is made to accept proposed changes. Also describe the process for identifying and appointing new committers.

Pull Requests are made and then David Ellams code reviews and then either feedbacks what needs to be changed or accepts and merges the changes in...

New committers can come from anywhere such as holochain, eosio, telos, Ethereum and many more blockchain communities, Plus from SEEDS, Unity, .NET communities and anywhere else out there, this project connects the whole internet so the target audience is everyone! ;-)

CLA

If already an OSS project, was a Contribution License Agreement in place for contributions accepted? How does the project check who has signed one?

Up to now this has been used, but we are open to any recommendations the .NET Foundation may have in this area.. thank you.

CLA Notification Alias
Provide an email address that will receive CLA related notifications from the .NET Foundation CLA automation

david@nextgensoftware.co.uk

Assignment Model. Under the .NET Foundation assignment model, project ownership and other intellectual property is assigned to the .NET Foundation and the .NET Foundation agrees to grantback a license to the contributor(s).

Contribution Model. Under the .NET Foundation contribution model, a project retains ownership of the project, but grants the .NET Foundation a broad license to the project’s code and other intellectual property. The project also confirms that the project’s submissions to .NET Foundation are its own original work (there are also instructions for any third party materials that might be included).

4.   Repository Layout

The .NET Foundation host guidance for new projects and details on recommended structure here:
https://github.com/dotnet/home/tree/master/guidance

Note that the open source repository should be the master where changes are made by the core development team using the same PR process that is used for non-committer contributions.

Please define below any changes you would want to make to your repositories as part of the process of joining the .NET Foundation

5. Eligibility Criteria

Please complete the following for your project

  • The project is built on the .NET platform and/or creates value within the .NET ecosystem.
  • [ X] Yes
  • No
  • The project produces source code for distribution to the public at no charge.
  • [ X] Yes
  • No
  • The project's code is easily discoverable and publicly accessible (preferably on GitHub).
  • [ X] Yes
  • No
  • The project contains a build script that can produce deployable artifacts that are identical to the official deployable artifacts, with the exception of code signing (Exception may be granted for strong name keys, though strongly encouraged to be committed. Exception relies on OSS signing being in the build script for public builds).
  • Yes
  • [ X] No
  • When applicable, project must use reproducible build settings in its toolchain.
  • Yes
  • [X ] No
  • Yes
  • [X ] No
  • The project uses either embedded PDBs or publish symbol packages to NuGet (if applicable).
  • [ X] Yes
  • No
  • The project code signs their artifacts as appropriate.
  • Yes
  • No
  • The project organization has 2FA enabled. Requiring 2FA must be done as part of onboarding if not already enabled.
  • Yes
  • No
  • Libraries that are mandatory dependencies of the project are offered under a standard, permissive open source license which has been approved by the .NET Foundation (exceptions include a dependency that is required by the target platform where no alternative open source dependency is available such as the .NET Framework or a hardware specific library).
  • [ X] Yes
  • No
  • Committers are bound by a Contributor License Agreement (CLA) and/or are willing to embrace the .NET Foundation's CLA when the project becomes a Member.
  • [X ] Yes
  • No
  • The copyright ownership of everything that the project produces is clearly defined and documented.
  • [ X] Yes
  • No
  • The project has a public issue tracker where the status of any defect can be easily obtained.
  • [X ] Yes
  • No
  • The project has a published Security Policy.
  • Yes
  • [X ] No
  • The project has a home page which provides high level information about its status and purpose.
  • [ X] Yes
  • No
  • The project has a public communication channel where community members can engage with maintainers.
  • Yes
  • No
  • The project has a publicly available location where members can review and contribute to documentation.
  • [X ] Yes
  • No

6.   PR Plan

Please summarize the public relations plan for the announcement when joining the foundation (and releasing as open source if appropriate). What is the main story we wish to promote, through what channels, what issues should we be aware of?  For significant news events then please also work with your .NET Foundation contact to ensure a full PR plan is developed.

The news will be made on our blog at http://www.ourworldthegame.com/blog as well as shared across all our networks (facebook, twitter, linkedin, Telegream & Discord)/

7.   Infrastructure Requirements

Please describe any infrastructure requirements for the project. For example, how will build servers be operated? Any web hosting or service hosting requirements? Do we need to set up SSL certificates or provide Authenticode Code Signing arrangement for releases?

Currently the OASIS API is deployed on a private server on WinServ:

http://oasisplatform,world/swagger.

Soon it will also be deployed on Azure, Holochain and ThreeFold P2P networks and more to follow...

8.   Additional Notes

Please provide any additional information required or use this area for notes during the onboarding process. If this open source project has similarities with any other projects in this space then please detail them and why this project is different. If there are any potential issues that you feel the project might need help with early on then also state them here and discuss with your .NET Foundation Contact.

Since our time is very tightly pressured because we are still looking for funding so we only have limited time to work on this, we have not been able to tick all of your eligible boxes above, we hope you may be able to either waiver these or help us with them? Because after all, this project is for a VERY GOOD cause so we hope you can find it in your hearts to do all you can to fast-track this project and to also help support it anyway you can... we are hoping by joining the .NET Foundation that it will get the exposure it needs to attract both funding and devs to help speed it up... its been a lot for just one guy (David Ellams), mainly working on it since 2013! Thank you :). 👍

In case you have not noticed, the world could really do with a project like this right now! :) This would also give VERY GOOD PR to you and Microsoft... :) Thank you.

We are about to launch a Kickstarter campaign and would love to have this on-boarded before then so we can count on the support of the .NET Foundation, Microsoft & the .NET community for this campaign, thank you. HELP US HELP YOU! ;-)

WELCOME TO THE FUTURE.

TOGETEHR WE CAN CREATE A BETTER WORLD.

In Love, Light & Hope,
The Our World Tribe

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.