software:k4r
This is an old revision of the document!
Table of Contents
Knowledge4Retail
Organisational
- Please join the kvr chatroom on the conference.uni-bremen.de Jabber server. Feel free to post any code questions there.
Github
- 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. You can assign your PR to any 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
Workspace Setup Tips
- 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
software/k4r.1598264656.txt.gz · Last modified: 2020/08/24 10:24 by stelter