The TORQUE community is vast and diverse; it is comprised of people from all over the world who administer systems ranging from #1 supercomputers to a couple of extra nodes in a physics lab. Community participation also greatly varies. Some report bugs and seek guidance while others contribute significant development work. Others participate in beta programs or perform quality assurance testing on their development systems. Coordinating these efforts happens primarily through three interfaces: the user’s mailing list and the developer’s mailing list, and the github page.
The user’s list is where the majority of questions are directed. Most frequently, you’ll see questions about how to solve a common HPC problem, how to use a feature, how others are solving the same challenge you are facing, etc. All things that are of general interest to users of TORQUE are posted to this list as well, typically including information about deprecating features, upcoming releases, etc. To stay informed, join the user’s list.
The development list stays more focused on design and feature discussions, and typically has a lot less traffic than the user’s list. Typical discussions on the TORQUE developer’s list include deciding how to interface with new hardware, discussing and proposing future projects, and so on. Join the developer’s list.
Finally, our github site. We host the TORQUE code there and try to make full use of the features github offers. Users can submit and discuss bug reports on github, and we often re-direct bug reports on the user’s list to the github site. Users also can submit pull requests for code to be integrated into the main source via github.
We feel like our community is one of our greatest assets. We continually are trying to enhance interactions within the community and offer more tools to continue to make TORQUE usable and understandable. We have been pleased with the results of the recent switch to github and we’re confident that we can continue to improve our coordination.