Skip to content

Latest commit

 

History

History
89 lines (63 loc) · 4.79 KB

CONTRIBUTING.md

File metadata and controls

89 lines (63 loc) · 4.79 KB
Raw

Interested in contributing? As an open source project, we'd appreciate any help and contributions! On top of the Networked-Aframe framework itself, you can also contribute to this related component:

Join the Community on Slack

  1. Invite yourself to the A-Frame Slack channel.
  2. Join the A-Frame slack
  3. Join the #networked-aframe channel

Get Help or Ask a Question

If you're not sure how to do something with Networked-Aframe, please post a question (and any code you've tried so far) to Github Issues.

File an Issue

  1. Search the issue tracker for similar issues.
  2. Specify the version of Networked-Aframe in which the bug occurred.
  3. Specify information about your browser and system (e.g., "Firefox Nightly on OS X")
  4. Describe the problem in detail (i.e., what happened and what you expected would happen).
  5. If possible, provide a small test case with Glitch, a link to your application, and/or a screenshot. You can fork/remix this Glitch project.

Contribute Code to Networked-Aframe

Here's how to submit a pull request (PR):

  1. Have a GitHub account with SSH keys set up.
  2. Fork the repository on GitHub.
  3. Clone your fork of the repository locally (i.e., git clone [email protected]:yourusername/networked-aframe).
  4. Run npm install to get dependencies and npm run dev to serve the test examples. Follow this tutorial on how to get started
  5. Create a branch to work in (i.e., git checkout -b mybranch).
  6. Make changes to your fork of the repository, commit them, and push them (i.e., git add -A . && git commit -m 'My Changes (fixes #1234)' && git push origin mybranch).
  7. If necessary, write unit tests and run with npm run test.
  8. Make sure your code follows codestyle of the rest of the project.
  9. If your commit changes the external API of Networked-Aframe update the documentation
  10. Submit a pull request to the master branch. If you head to the Networked-Aframe repository after running git push from earlier, you should see a pop up to submit a pull request.
  11. Address review comments if any.

As per usual with open source, you would agree to license your contributions under the MIT License.

Share your Work

  1. Create something awesome with networked-aframe
  2. Publish your work to Github (and GitHub pages) so everyone can learn from your work.
  3. Share it on Slack on the #projects channel.
  4. Let A-Frame know about it so they can feature it on their blog: A Week of A-Frame. For this just tweet your project with a small video to @aframevr
  5. For bonus points, write and publish a case study to explain how you built it.

Help Your Fellow A-Framers

On Slack

  1. Invite yourself to the A-Frame Slack channel.
  2. Join the #networked-aframe channel
  3. Help answer questions that people might have and welcome new people.

On GitHub

  1. Help respond to newly-filed GitHub issues

Curate and Make Efforts Known

Every week, the A-Frame team rounds up all the cool stuff happening with A-Frame on their blog. If you tweeted about it and added a comment on Slack, there is a good chance for it to be included in the next blog post.

Also feel free to message us on #networked-aframe channel on Slack.

Spread the Word

If you want to hold an event and talk about WebVR, A-Frame and/or Networked-Aframe, check out the presentation kit.

Thanks so much for contributing and helping grow WebXR!