Knowledge4Retail

The organizational internal K4R-Trello board can be found at: https://trello.com/b/dqq74dHt/k4r . It contains all main upcoming meetings, tasks etc.
- K4R-Trello board with focus on ERP task: https://trello.com/b/h5uWvlSz/k4r-erp-tasks
- K4R-Trello board with focus on Pilot Application 1 tasks: https://trello.com/b/5Zu6waIE/k4r-pilotanwendung-1-tasks
- K4R-Trello board with focus on Pilot Application 2 tasks: https://trello.com/b/c6XbWgLj/k4r-pilotanwendung-2-tasks
- K4R-Trello board with focus on Pilot Application 3 tasks: https://trello.com/b/N3iJBgrg/k4r-pilotanwendung-3-tasks
- K4R-Trello board with focus on Pilot Application 4 tasks: https://trello.com/b/wgEcqSMz/k4r-pilotanwendung-4-tasks
These boards are maintained by all board members in order to keep the current state progress transparent for all members and to counteracting unexpected bottlenecks.
Please join the k4r chatroom on the conference.uni-bremen.de Jabber server. Feel free to post any code questions there.
A weekly internal meeting takes place: see for details at https://trello.com/c/MdgXmd4U/37-weekly-internal-meeting-tuesdays-1030h

Official K4R core platform repository can be found at: https://gitlab.com/knowledge4retail/k4r-core-api . If you need access please contact Christian Mueller (christian.mueller@uni-bremen.de).

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
For KnowRob Nils created a Cheat sheet for himself that can be found here: https://hackmd.informatik.uni-bremen.de/s/QFx84CJMT#

Local virtual machine featuring a static IP which is publicly accessible can be found at ubuntu@ked.informatik.uni-bremen.de . If you need access, please contact Christian Mueller (christian.mueller@uni-bremen.de) and you will need to send your public ssh-key to Patrick Mania (pmania@cs.uni-bremen.de).
This VM locally runs the K4R-Platform software stack in order to have a test bed until the K4R cloud services are available

clone git@github.com:K4R-IAI/knowrob_k4r.git (checkout branch v0.2)
cd docker
docker-compose up
wait for about 1 minute until the container is healthy (you can check it with docker ps)
type in a browser: localhost:62226
try your own prolog command