Join the Community

The VOLTTRON team aims to work with users and contributors to continuously improve the platform with features requested by the community as well as architectural features that improve robustness, security, and scalability. Contributing back to the project, which is encouraged but not required, enhances its capabilities for the whole community. To learn more, check out Contributing and Documentation.

Slack Channel

volttron-community.slack.com is where the VOLTTRON™ community at large can ask questions and meet with others using VOLTTRON™ Signup via https://volttron-community.signup.team/

Mailing List

Join the mailing list by emailing volttron@pnnl.gov.

Stack Overflow

The VOLTTRON community supports questions being asked and answered through stack overflow. The questions tagged with the volttron tag can be found at http://stackoverflow.com/questions/tagged/volttron.

Office Hours

PNNL hosts office hours every other week on Fridays at 11 AM (PST). These meetings are designed to be very informal where VOLTTRON developers can answer specific questions about the inner workings of VOLTTRON. These meetings are also available for topical discussions of different aspects of the VOLTTRON platform. Currently the office hours are available through a Lync meeting.

• Join Lync Meeting
• Dial in Number: 1-866-528-1882
• Conference Number: 886916

Meetings are recorded and can be reviewed here.

Contributing Back

• Contributing to VOLTTRON
  • Getting Started
    • Forking the main VOLTTRON repository
    • Cloning ‘YOUR’ VOLTTRON forked repository
    • Adding and Committing files
    • Pushing to the remote repository
    • Getting modifications to the main VOLTTRON repository
    • What happens next?
  • Next Steps
    • Merging changes from the main VOLTTRON repository
  • Other commands to know
    • Viewing what the remotes are in our local repository
    • Stashing changed files so that you can do a merge/pull from a remote
    • Applying the last stashed files to the current repository
    • Finding help about any git command
    • Creating a branch from the branch and checking it out
    • Checking out a branch (if not local already will look to the remote to checkout)
    • Removing a local branch (cannot be current branch)
    • Determine the current and show all local branches
  • Hooking into other services
• Contributing Documentation
  • Building the Documentation