...

• Opportunity: Joining a brigade is a unique opportunity to work with the core engineering team and participate in work onsite at Menlo Park
• Recognition: The work of brigade members will be showcased widely with the community both online as well as at events, like at ONOS Build
• Experience: Taking part in a brigade is a great opportunity, especially for students, to get experience in network engineering and is a great stepping stone to possibly work at ON.Lab ONF or other member organizations
• Acceleration: Helping a brigade deliver a feature will get work that you care about into an official ONOS release much more quickly than it would without the brigade's efforts.
• Research and Development: A brigade can bring together researchers and engineers from both academia and industry to propose and develop new features and applications in the SDN/NVF domains or to model, measure, and evaluate performance of current implemented services.

...

If you're interested in the work of any of these brigades, please take a look at that brigade's wiki page to learn more about what is happening, what help is needed and how to get in touch with the team.

Expectations

The brigade helps the community scale and take on work items. In using brigades as a work unit, the community is counting on them to execute to their plans successfully. We expect the leader and the brigade members to have the desire, motivation, and skills to make and MEET commitments to the community. Also, as part of the community, it is expected that brigades will engage with the release planning process and the sprint planning process. Specifically, we expect brigades to

• Commit in the release planning meeting to deliverables for a release. The deliverables and requirements can come from many places in the community, or from the brigade itself. The community is counting on the brigade to deliver on its promises for the release.
• The brigade will keep a public location udpated with work items and status so that the brigade's work is visible to the community (a JIRA dashboard, for example).
• The lead, or the lead's delegate, will participate actively in the brigade review meeting held once a month.
• At least one member of the brigade participates in the ONF sprint review meetings to talk about what progress has been made in the brigade over the sprint period. 
• The lead, or the lead's delegate, will participate in the release review meeting to show what the team accomplished for the release.

Roles, Recommendations and Requirements

...

Mentorship is vital in an open source community because so much information and knowledge is often not written down or documented.  Mentors focus on leveling up brigade members so they have the skills to be successful.  For brigades where there are leads or members who do not have easy access to the ON.Lab ONF offices in Menlo Park, mentorship is also crucial since you do not have the ability to easily interact with and ask questions of core team members based there.  Because of that, we encourage all brigades that are not lead by an ON.Lab staff ONF staff member to have a mentor who can support them, answer questions and get them unstuck when they are blocked.  Mentors can be ON.Lab ONF staff members, TST members, module owners or anyone else who has deep knowledge to share about the work the brigade is doing.

...

All brigade leads and mentors are asked to attend a monthly status call – the purpose of the call is to support the effectiveness of brigades by creating a place where leads and mentors can raise any concerns or blockers and where they can learn best practices and tips.  The call is currently scheduled every fourth Wednesday at 10 pacific and you can find the meeting details on the ONOS community calendar.  If you're unable to attend this meeting, please either delegate this to another brigade member or send in a status update before the meeting.  For other meetings, you and your brigade can decide if and when to schedule team meetings.

...

System Test Coverage includes delivery of detailed test plans and shared with the team for reviews.  Critical and Major functional test scenarios are to be targeted for automation.  Automated tests/scripts need to be submitted into the common repository.  By committing test cases to a common repo it helps the community/users to scale the tests in future.  All test cases that are automated need to be run before and after code merges into the mainstream. Once code is committed to the mainstream, automated test scripts need to be integrated to jenkins QA jobs for continuous regression of the features.

ON.Lab ONF test engineer(s) will collaborate with the testers in the brigade and guide them through the test coverage procedures.  Testers on the brigade team can also take advantage of the existing automation framework and tools that ON.Lab uses ONF uses for automated tests.

Refer to System Testing Guide for more details.

...