These are chat archives for machinekit/machinekit

18th
Dec 2015
Michael Haberler
@mhaberler
Dec 18 2015 15:47
I'm considering a "project" tag for the issue tracker
the idea is to parcel out themes which fit a limited time budget and are important building blocks for the project
example: get PRU support going for BB X15
automate the build of czmq/zeromq/libsodium/libwebsockets with the same scheme we have in place for machinekit
what do you think?
Bas de Bruijn
@luminize
Dec 18 2015 15:49
good idea, maybe collect issues in the same tag? tag starting with "project-" for example? or gather sub issues under a "parent" issue?
Michael Haberler
@mhaberler
Dec 18 2015 15:50
well those would be filed as issues and tagged 'project' - you can easily refer to related issues in the text with the sharp<issuenumber> link
I was thinking of standalone issues, wouldnt know what a parent issue should mean - but we could certain link from the website under 'Contributing'
Bas de Bruijn
@luminize
Dec 18 2015 15:53
parent issue is like gathering all issues that need to be done for solving something. More like a task/subtask way of seeing things. but that purely personal and i think github is not the tool to work with subtasks. Having a parent task, with a list of subtasks gets a nice overview though
GP Orcullo
@kinsamanka
Dec 18 2015 22:29
I'm changing the travis settings for PR #838 now. Any incoming PRs will fail the travis-ci tests before #838 is merged
Michael Haberler
@mhaberler
Dec 18 2015 22:30
so should I hit merge #838 or not
simple commands to a simple man please
GP Orcullo
@kinsamanka
Dec 18 2015 22:52
Yes please