LTS Test Drive Program

What is the LTS Test Drive program?

The LTS Test Drive program is a program where we invite you to find bugs in the latest release on the 2.x line. You will receive $500 for each accepted high severity issue and $250 for low severity issues.

If you are interested, please sign up with the form on the right. If you are interested to learn more, scroll down to gain more information about the LTS Test Drive Program.

All bug reports need to be submitted by December 2nd at the latest to recieve compensation.

LTS Test Drive Program Guidelines

Thanks for expressing interest in the Device OS LTS test Drive Program, we are excited that you've chosen to help us find reliability issues for our forthcoming LTS release. To help get the most of your time, we are asking that participants comply with a few important guidelines related to submission of bugs.

What are Long Term Support (LTS) releases?

Long Term Support (LTS) releases for Device OS are independent branches of Device OS that are feature-frozen in time. They do not receive updates with new features, API changes, or improvements that change the function or standard behavior of the device.

LTS releases are subject to a higher degree of testing and scrutiny than standard Device OS releases on our master branch. In order to drive more adoption of release candidates, we are establishing a test drive program, with a goal to have enhanced user testing.

We hope you sign up for the LTS test drive program because we deeply value your expertise.

Bug Report Guidelines

  1. A bug report must be submitted via a typeform response (which we will send to you once you sign up), and that report must include the following: Summary of problem in terms of how observed behavior goes against expectations. Link to relevant documentation that sets expectations if possible. If documentation does not exist, please state your expectations clearly.
  2. Clear steps to reproduce the problem must be described that can be re-executed against a Particle Dev Kit. Additionally, the following are required:
  • device type: For example, "Boron LTE"
  • device id: For example, "2c0032000a47363339343638"
  • RF signal strength: For cellular devices, be sure to refresh the device vitals reported by the Particle Console device details page (i.e. a page like https://console.particle.io/devices/<device-id>). Additionally, please click "Download History" to retrieve a CSV of other detailed information about the device's operating environment that may help to reproduce your bug report. Ideally your cellular signal is 42% or higher; bug reports less than this are less likely to receive compensation due to inability to reproduce a poor RF environment. The bug submission form will contain a "Cellular Signal" field and a "Vitals CSV" where you can provide these important technical details as part of your bug report.

Image from iOS (2)

  1. A minimal application firmware should be provided that, when used in concert with the reproduction steps, will allow a QA engineer to observe the same bug characteristics you reported. Your firmware should not require special hardware peripherals. Instead firmware should emulate, mock out, or simplify interactions with the peripheral to demonstrate the bug.

Compensation Guidelines

Bug reports that can be reproduced internally at Particle using your bug report and are deemed a bug (rather than a feature request) will result in a cash reward. The amount will be determined by whether the issue is labeled as high severity or low severity. The labeling of severity against reported bugs occurs via a weekly Production Triage process with stakeholders from Customer Success, Product, and Engineering. You will receive $500 for each accepted high severity issue and $250 for low severity issues.

You will hear back within 3 weeks of submission whether your bug was accepted or not. For those that accepted, you will receive follow-up instructions on how to go about receiving payment.

High Severity Bug Bounties

To get you started, here are some areas of the platform where we'd love your help finding bugs. These are more likely to be compensated.

  • Over the Air Firmware Updates (OTA): Especially updates that upgrade from one recent device-os version to another such as 1.5.4 to 2.0 rc2 or 2.0 rc1 to 2.0 rc2.
  • Cloud connectivity: Situations where the signal strength and quality is high, but the device still struggles to stay connected to the Particle Cloud.
  • Cellular connectivity: Situations where the cellular modem is not behaving as expected in the given RF environment. Focus on interactions with the modem over mobile operator conditions/specifics/towers. Local mobile operator issues should NOT be filed as bugs and instead be filed as tech support requests.
  • Device OS crashes: Situations where Device OS crashes or is unavailable for routine operations in an unexpected way.
  • Bricked devices: A permanent failure mode where Device OS crashes and will not boot up again even after power cycling the device.
  • API calls causing race conditions: Situations with multi-threaded mode on where interactions with Device OS system APIs cause the system to lockup or behave in erratic, unexpected ways.

Low Severity Bug Bounties

Conversely, here are a few areas where we are less interested in bug reports. These are less likely to receive bug report compensation.

  • Application specific issues: Please avoid reporting bugs where significant application complexity is obfuscating whether this is a bug in your application or a bug in Device OS. For example, suppose your application makes some advanced modifications in the typical network setup and you think you have found a bug in Device OS. In this situation, when supplying a minimal firmware with your bug report, exclude the code that modifies the network setup.
  • Bugs occurring in poor RF signal/quality environments: It is known that the platform behaves less reliable in poor RF environments. Thus, we're restricting the scope of bug report compensation to our classification of fair connectivity or better. For LTE, when RSRP is -112 dBm or greater and when RSRQ is -13 dBm or greater. We may still consider them if the bug boundaries are close or the nature of the bug isn't impacted by RF conditions.
  • Wi-Fi devices: While we are interested in bug reports for Wi-Fi devices, we are much more interested in bug reports for cellular devices. Local cellular mobile operator issues should be filed as support requests rather than LTS bug reports. If they turn out to be modem/firmware related and a bug comes from it, please reference the ticket number so we can associate them. Cloud side bugs in Console, Build, or other tools: This program is focussed on Device OS LTS release, though we appreciate bug reports for other aspects of the platform, they are unlikely to be financially compensated.

Particle Individual Contributor License Agreement

Based on the Google Individual Contributor License Agreement, v1.1

The content of this page is licensed under the Creative Commons Attribution 3.0 License.

In order to clarify the intellectual property license granted with Contributions from any person or entity, Particle Industries, Inc. ("Particle") must have a Contributor License Agreement ("CLA") on file that has been signed by each Contributor, indicating agreement to the license terms below. This license is for your protection as a Contributor as well as the protection of Particle; it does not change your rights to use your own Contributions for any other purpose. Please complete the following information about you and the Contributions and sign electronically by filling out the form below.

You accept and agree to the following terms and conditions for Your present and future Contributions submitted to Particle. Except for the license granted herein to Particle and recipients of software distributed by Particle, You reserve all right, title, and interest in and to Your Contributions.

Definitions "You" (or "Your") shall mean the copyright owner or legal entity authorized by the copyright owner that is making this Agreement with Particle. For legal entities, the entity making a Contribution and all other entities that control, are controlled by, or are under common control with that entity are considered to be a single Contributor. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.

"Contribution" shall mean any original work of authorship, including any modifications or additions to an existing work, that is intentionally submitted by You to Particle for inclusion in, or documentation of, any of the products owned or managed by Particle (the "Work"). For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to Particle or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, Particle for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by You as "Not a Contribution."

Grant of Copyright License. Subject to the terms and conditions of this Agreement, You hereby grant to Particle and to recipients of software distributed by Particle a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Your Contributions and such derivative works.

Grant of Patent License. Subject to the terms and conditions of this Agreement, You hereby grant to Particle and to recipients of software distributed by Particle a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by You that are necessarily infringed by Your Contribution(s) alone or by combination of Your Contribution(s) with the Work to which such Contribution(s) was submitted. If any entity institutes patent litigation against You or any other entity (including a cross-claim or counterclaim in a lawsuit) alleging that your Contribution, or the Work to which you have contributed, constitutes direct or contributory patent infringement, then any patent licenses granted to that entity under this Agreement for that Contribution or Work shall terminate as of the date such litigation is filed.

You represent that you are legally entitled to grant the above license. If your employer(s) has rights to intellectual property that you create that includes your Contributions, you represent that you have received permission to make Contributions on behalf of that employer, that your employer has waived such rights for your Contributions to Particle, or that your employer has executed a separate Corporate CLA with Particle.

You represent that each of Your Contributions is Your original creation (see section 7 for submissions on behalf of others). You represent that Your Contribution submissions include complete details of any third-party license or other restriction (including, but not limited to, related patents and trademarks) of which you are personally aware and which are associated with any part of Your Contributions.

You are not expected to provide support for Your Contributions, except to the extent You desire to provide support. You may provide support for free, for a fee, or not at all. Unless required by applicable law or agreed to in writing, You provide Your Contributions on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON- INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE.

Should You wish to submit work that is not Your original creation, You may submit it to Particle separately from any Contribution, identifying the complete details of its source and of any license or other restriction (including, but not limited to, related patents, trademarks, and license agreements) of which you are personally aware, and conspicuously marking the work as "Submitted on behalf of a third-party: "named here".

You agree to notify Particle of any facts or circumstances of which you become aware that would make these representations inaccurate in any respect.