Packages Feed for Oboo Smart Clock

greenbreakfast 5f4d944f69 upping card manager and cards package version numbers - prep for new release 1 year ago
card-manager 5f4d944f69 upping card manager and cards package version numbers - prep for new release 1 year ago
clock-mcu a5b3a379ad Merge pull request #7 from ouellettetech/neopixelupdate 1 year ago
oboo-clock-base 634b101c64 open sourcing oboo software packages repo 1 year ago
oboo-clock-cards 5f4d944f69 upping card manager and cards package version numbers - prep for new release 1 year ago
oboo-repo-keys 634b101c64 open sourcing oboo software packages repo 1 year ago
schematic 634b101c64 open sourcing oboo software packages repo 1 year ago
wifi-warp-core-oboo 634b101c64 open sourcing oboo software packages repo 1 year ago
CHANGELOG.md 634b101c64 open sourcing oboo software packages repo 1 year ago
LICENSE 634b101c64 open sourcing oboo software packages repo 1 year ago
README.md 28dde6f287 updated readme with info on collaborating 1 year ago

README.md

Oboo-Packages

OpenWRT Packages Feed for Oboo Smart Clock.

This repository holds the source code and OpenWRT makefiles for all custom Oboo Smart Clock software packages.

Where are the Packages Published?

The compiled packages can be found here: http://repo.getoboo.com/oboo-clock/packages/

How Can I Test my Changes?

The packages from this repo are build by the Oboo-Source build system. Follow the instructions from that repo to create an initial build.

Then:

  1. Make your code changes in Oboo-Source/feeds/oboo/ and recompile the affected packages
  2. Take the new ipk file from bin/packages/mipsel_24kc/oboo/ and install on your Oboo Smart Clock
  3. Test out your new changes

How Can I Contribute?

If you have a code change that you would like to share with everyone, please create a Pull Request and provide the following:

  • Use a clear and descriptive title for the PR to identify the code change.
  • Provide a step-by-step description of the enhancement in as many details as possible.
  • Describe the current behavior and explain which behavior you expect to see instead with your change and why.
  • Increment the PKG_VERSION or PKG_RELEASE for the affected package for changed to be properly propagated to other users
  • Pull Requests must be atomic, that is, focus on a single improvement

How is Code Released?

Once the PR is accepted in this repo, create a PR with a dummy change in the Oboo-Source repo to trigger the CD system.

It will build the packages and release them to: http://repo.getoboo.com/oboo-clock/packages/latest/