Development Lifecycle

A typical contribution to this repo follows this path:

fork the repo
make a new branch for your work (based on any branch that suits your needs)
make a pull request into the dev branch
- when merged this will trigger CI jobs
merged PRs in the dev branch will be mirrored in the release-candidate branch automatically
maintainers will merge release-candidate into master when a new release is created
- this maintains the master branch even with the latest release, and the dev branch as the cutting-edge

What to Contribute

Goals of this Arduino core, listed in order of priority, are:

Coverage of the Arduino built-in functions demonstrated by Sketch compatibility.
Creation of a well-structured and easy to extend Arduino core.
Prioritizing usage of mbed functionality
Efficient use of existing AmbiqSuite HAL code.
Backward-compatible improvements to the standard Arduino libraries.

Great things to contribute:

bug fixes
libaries to support Apollo3 peripherals

Where to Contribute

In keeping with the goal of creating a well-structured, easy to understand, and easy to extend Arduino core it is importatnt to carefully consider where new code should be located.

There are two main places where you might add code:

The core Arduino_Apollo3\cores\arduino
Variants Arduino_Apollo3\variants

Code that goes in the core should be applicable to any Apollo3-based board as opposed to code that is specific to a particular variant.

How to Contribute

First, get an idea of whether or not your efforts will be worthwhile - you don't want to write a lot of code just to be told that the work doesn't fit the goals of the repo. There are two good places to discuss possible additions:

GitHub Issues: Follow the guidelines for submitting an issue (Issue Template), then discussion of viability and best approach can ensue.
SparkFun Apollo3 Arduino Core Development Forum:

Consider where your contribution will fit best:

Arduino-mbed bridge: for code that applies to any Arduino board based on mbed functionality
SparkFun Ambiq Apollo3 mbed fork: for adding support for the Apollo3 microcontroller within mbed
Arduino Apollo3 (this repo): for support of Arduino functionality that is not covered in mbed

When you start to write code keep in mind the presentation of these changes. We accept changes using Github pull requests, as the most seamless way for both ourselves and contributors. When making commits for a change please use descriptive commit summaries. For considerable changes we expect a detailed yet formal and concise description of the change in the commit message. If you make 2 or more considerable changes, they should go in separate commits. The same applies to unrelated changes - for example, don't put formatting changes and actual code changes in one commit. Follow the Code Conventions

In your first accepted Pull Request it is up to you to add your name to the Acknowledgements file. Please do this in its own individual commit. If you are contributing for a second, third, or nth time there is no need to add any more to the acknowledgements file - your contributions are recorded by your commit messages.

When you submit a pull request, please make sure that it's understood why you propose this change: what problem it addresses, how it improves the work and at the same time does not degrade it with respect to the priorities in the What to Contribute section. Good, detailed commit messages are an easy way to achieve this, and yet sometimes it's better to put informal points, colloquial arguments and big examples in comments to a pull request instead, to keep commit messages concise and focused.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!