cfc65a13f6
This commit includes updates that affects the build, testing, and
deployment of Tile38.
- The root level build.sh has been broken up into multiple scripts
and placed in the "scripts" directory.
- The vendor directory has been updated to follow the Go modules
rules, thus `make` should work on isolated environments. Also
some vendored packages may have been updated to a later
version, if needed.
- The Makefile has been updated to allow for making single
binaries such as `make tile38-server`. There is some scaffolding
during the build process, so from now on all binaries should be
made using make. For example, to run a development version of
the tile38-cli binary, do this:
make tile38-cli && ./tile38-cli
not this:
go run cmd/tile38-cli/main.go
- Travis.CI docker push script has been updated to address a
change to Docker's JSON repo meta output, which in turn fixes
a bug where new Tile38 versions were not being properly pushed
to Docker
57 lines
2.2 KiB
Markdown
57 lines
2.2 KiB
Markdown
Contributing to Paho
|
|
====================
|
|
|
|
Thanks for your interest in this project.
|
|
|
|
Project description:
|
|
--------------------
|
|
|
|
The Paho project has been created to provide scalable open-source implementations of open and standard messaging protocols aimed at new, existing, and emerging applications for Machine-to-Machine (M2M) and Internet of Things (IoT).
|
|
Paho reflects the inherent physical and cost constraints of device connectivity. Its objectives include effective levels of decoupling between devices and applications, designed to keep markets open and encourage the rapid growth of scalable Web and Enterprise middleware and applications. Paho is being kicked off with MQTT publish/subscribe client implementations for use on embedded platforms, along with corresponding server support as determined by the community.
|
|
|
|
- https://projects.eclipse.org/projects/technology.paho
|
|
|
|
Developer resources:
|
|
--------------------
|
|
|
|
Information regarding source code management, builds, coding standards, and more.
|
|
|
|
- https://projects.eclipse.org/projects/technology.paho/developer
|
|
|
|
Contributor License Agreement:
|
|
------------------------------
|
|
|
|
Before your contribution can be accepted by the project, you need to create and electronically sign the Eclipse Foundation Contributor License Agreement (CLA).
|
|
|
|
- http://www.eclipse.org/legal/CLA.php
|
|
|
|
Contributing Code:
|
|
------------------
|
|
|
|
The Go client is developed in Github, see their documentation on the process of forking and pull requests; https://help.github.com/categories/collaborating-on-projects-using-pull-requests/
|
|
|
|
Git commit messages should follow the style described here;
|
|
|
|
http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
|
|
|
|
Contact:
|
|
--------
|
|
|
|
Contact the project developers via the project's "dev" list.
|
|
|
|
- https://dev.eclipse.org/mailman/listinfo/paho-dev
|
|
|
|
Search for bugs:
|
|
----------------
|
|
|
|
This project uses Github issues to track ongoing development and issues.
|
|
|
|
- https://github.com/eclipse/paho.mqtt.golang/issues
|
|
|
|
Create a new bug:
|
|
-----------------
|
|
|
|
Be sure to search for existing bugs before you create another one. Remember that contributions are always welcome!
|
|
|
|
- https://github.com/eclipse/paho.mqtt.golang/issues
|