Please join the kvr chatroom on the conference.uni-bremen.de Jabber server. Feel free to post any code questions there.

If you find packages and software you want to edit for the purpose of this project, please fork it into the k4r-organisation https://github.com/K4R-IAI. If you don't have access there yet, ask Michael N. for access.

Please keep the master branch of common repositories in a working state. You can create your own development or bugfix branch. Once you are done with development, open a pull request (PR) to get your contribution merged into master.

Some repositories are maintained by multiple people. Please assign your PR to at least one of the maintainers, preferably to a person who you know also uses the part of the code you changed. To find the maintainer, look at the previous commits in the repo or the closed PRs and see who merged them.

Write down all dependencies to other git repos in a .rosinstall

Write down debian package dependencies in the package.xml

If you have dependencies to packages which you don't work on yourself, you might want to consider to put them into a different workspace and layer your development workspace on top. This will save you a lot of building time, since the bigger your workspace is, the longer a catkin build process lasts. A tutorial on how to setup workspace layers can be found here: http://wiki.ros.org/catkin/Tutorials/workspace_overlaying

Official K4R core platform repository can be found at: https://gitlab.com/knowledge4retail/K4R

Local virtual machine featuring a static IP which is publicly accessible can be found at https://gitlab.com/knowledge4retail/K4R . If you need access, you will need to send your public ssh-key to Patrick.