Code for other tools such as SmartDashboard, Shuffleboard, RobotBuilder, OutlineViewer, and more are contained in their own repositories inside the organization. The code for all of the robot libraries (including CameraServer/cscore, NetworkTables/ntcore, and WPIUtil) is contained in the “ allwpilib” repository. Yes, the three headings in a row is on purpose! The answer to all of these questions is GitHub! The WPILib developers have code for all of the WPILib libraries and tools contained in a single GitHub Organization. Where is the Code? How Do I Report Bugs? How Do I Contribute? During the FRC build and competition seasons, changes are limited to bug fixes we believe are impacting teams and unlikely to break existing functional code. GitHub: GitHub Issues and PRs are used to communicate regarding specific issues or changesĮach year we brainstorm and collect ideas for improvements in the period shortly after Championship, implement over the summer, test in the fall, and prep to ship by Kickoff.Note: This Slack is also connected to a WPILib Gitter that community members can use to talk with the WPILib team. WPILib Developer Slack: A Slack Workspace set up to allow WPILib Core Developers to communicate with each other and with other members of the CS Team.Control System Team calls: Throughout the year members of the FRC Control System team (FIRST, NI, CTRE, WPI) have weekly calls to track status on Control System development.The WPILib development team uses a few different tools/methods for communication and coordination: A full list of contributors can be found on the Contributors tab of the Github repos for each project: Īdditional development support is also provided by Cross The Road Electronics (CTRE) and NI as members of the Control System team. You can see a video depicting a graphical history of WPILib development from 2012 to 2018 here. Volunteer: Jaci Brunning, Thad House, Peter Johnson, Joe Ross, Dustin Spicuzza, Tyler Veness WPI (alumni): Jonathan Leitschuh, Patrick Plenefisch, Fred Silberberg WPI (current): Ryan Benasutti, Sam Carlberg, Arjun Gandhi, Evan Gilgenbach, Ryan Lapoint, Brad Miller, Austin Shalit, Griffin Tabor The current list of Core Developers (alphabetical): These folks are a combination of current and former WPI students and FRC community members who were asked to become Core Developers based on consistent or significant contributions to the libraries. As WPILib has migrated closer to an Open Source model, we have assembled a larger group of “Core Developers” who handle most of the development of the library and tools. “Modern” (cRIO and later) WPILib development was originally done by Brad and a small number of WPI students with additional support on the initial release from DEKA, BAE Systems, NI (especially Joe Hershberger), and a few other volunteers. Since then WPILib has continued to grow and evolve as the primary library used by C++ and Java teams in FRC. A year later, Java support was added as a result of work done by WPI students working on a senior project (MQP). When National Instruments (NI) was working on the cRIO control system for the 2009 FRC season, WPILib was identified as a good supplement to provide support for teams programming in C++ and became an official part of the system. The intent was to abstract away some of the lower level details of the hardware (interrupt routines, voltage measurements and conversions, communications details, etc.) and allow students to focus on solving higher level problems. WPILib was originated in 2005 by WPI professor Brad Miller as a way to simplify program development for the IFI robot control system being used in FRC at the time. Before anyone TL DRs or falls asleep, there may be a special opportunity tucked away at the end of this blog post (no, it’s not a game hint!). Great questions, Brian! As the FIRST Staff member responsible for managing the FRC Control System team, Frank asked me to share a little bit about the WPILib team. Perhaps it would be nice to have a Frank blog post about the WPILib team, the history, who they are, how they work, how to report bugs or feature requests, etc.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |