#linuxcnc-devel Logs

Apr 10 2017

06:17 AM njh: Hi archivist - what was the reason for reverting the 'Simple_LinuxCNC_G-Code_Generators' page on the old wiki? I presume it was related to the email I got from Sammel Lothar?
08:29 AM jepler: njh: according to IchGucksLive, there are generators that are on the old version of that page that are not in the github.
08:30 AM jepler: njh: there was some discussion here http://tom-itx.no-ip.biz:81/~tom-itx/irc/logs/%23linuxcnc-devel/2017-04-06.html starting around "01:53 PM" and then again http://tom-itx.no-ip.biz:81/~tom-itx/irc/logs/%23linuxcnc-devel/2017-04-09.html
08:30 AM njh: jepler: I went to quite a lot of effort to migrate everything across, but it looks like a missed his aerofoil one - but very happy to fix my mistake.
08:32 AM njh: received a very confusing and slightly hostile email from him - hopefully it is just a misunderstanding
08:32 AM njh: jepler: thanks
08:33 AM jepler: njh: I can imagine being angry that someone has apparently deleted my contribution to an open source project, and the language problem doesn't help. Thank you for being willing to work on this!
08:33 AM jepler: njh: it's a drag to work with other human beings sometime
08:33 AM jepler: ...aaannnnddd that's my cue to actually go in to $DAY_JOB instead of sitting around the internet commenting on github issues
08:33 AM njh: heh, thankfully very rewarding other times!
08:52 AM jepler: njh: thank you
09:55 AM archivist: njh yes his aerofoill stuff and other links had all been lost
09:56 AM njh: archivist: can you qualify 'and other links had all been lost' ?
09:56 AM njh: I am aware of the aerofoil section and will try and sort that out tonight
09:56 AM archivist: info about 21. gcmc - G-Code Meta Compiler
09:57 AM archivist: I did not look too deeply
09:57 AM njh: "GCMC - G-Code Meta Compiler" is there - in fact I wrote more to make it clear what it was
09:58 AM archivist: where I did not look at your page as that is not where people will expect or look for it
09:59 AM njh: I certainly don't want to make things worse
09:59 AM njh: but did got to quite a bit of effort to make things better
10:00 AM njh: if the git GitHub repo doesn't fulfil its need - then it would be good to get some feedback on how it is lacking
10:00 AM archivist: I was just dealing with the local IRC and thinking about what is where and why
10:01 AM njh: But the reason for undertaking the work at all, was to make it easier to download all the tools and provide some version control for the various versions of them
10:01 AM archivist: so code moving yes, links er...why
10:02 AM njh: So that there is one place that you can go to, to scan down the list of available software and find what you are looking for
10:03 AM archivist: actually that is now one more place,
10:03 AM njh: one more place?
10:04 AM archivist: wiki, the main site, and every other thing that was not on that page
10:04 AM njh: I was also under the impression that there was a goal to move things off the Wiki - several people have referred to it as the Old Wiki - so I am not sure about that
10:05 AM njh: so you are suggesting having a "G-code generators" wiki page that lists all the various generators, that points people to Github for the Python tools?
10:05 AM archivist: so now it is look at wiki bounce to github bounce to http://www.vagrearg.org/content/gcmc
10:08 AM njh: there is also this page that lists G-Code generators:
10:08 AM njh: http://wiki.linuxcnc.org/cgi-bin/wiki.pl?Cam
10:09 AM njh: I certainly don't want to get into a Wiki editing war. I was just trying to make things better - and in my opinion it was a bit of a mess
10:10 AM njh: Those links that the bottom of the page, are valuable but they are not related to the title of the page 'Simple LinuxCNC G-Code Generators Written in Python'
10:26 AM archivist: a couple of things to think about, all the incoming links to the original page, the original creators of the content, and there is no way for me to fix the problem for both person A and person B at the same time
10:31 AM njh: I tried finding incoming links to the original page using Google - there are surprisingly few and I updated the ones I could - I think more of an issue is that people remember the page as a good list of tools
10:32 AM njh: I am going to try and get the aerofoil stuff added to GitHub tonight for IchGucksLive - he has emailed me an updated version
10:32 AM njh: I just want to make sure there isn't anything else people think I have missed - I am aware it is other people's work, not mine and want to make sure it is improved and not worse/lost
10:33 AM njh: I did drop the link to hugomatic.ca - it seems to be down and has been for a long time - anyone know what happened to it? - it was very useful
10:34 AM archivist: can the content be found on the web archive?
10:34 AM njh: Maybe but I think all the calculations were done server-side - so would only get a static snapshot if it is there
10:36 AM archivist: I have a few online calculators on my pages
10:36 AM njh: Ah! Win: https://github.com/hugomatic/cncOnline
10:39 AM archivist: mine have no python :) eg http://www.archivist.info/gear/designcrossedhelical.php
11:12 AM seb_kuzminsky: i think njh made things better by moving the code from the wiki to github, but i can understand that not everyone will agree
11:12 AM seb_kuzminsky: i think github is better than the wiki for those programs because it makes collaborative development easier
11:13 AM seb_kuzminsky: but i'm used to having git in my workflow, and i know that not everyone is comfortable with it
11:14 AM seb_kuzminsky: one github feature that we don't use for linuxcnc is "releases", maybe that could be useful here?
11:14 AM seb_kuzminsky: https://help.github.com/articles/creating-releases/
11:15 AM seb_kuzminsky: it lets you denote specific commits as "releases", and github makes them available as tarballs and zip files and other things
11:15 AM jepler: If an original author of something prefers the workflow of putting it on wiki.linuxcnc.org vs putting it in github (e.g., because they don't care to have a github account or accept the github TOS) then I think it is a preference we ought to respect. But in this case I'm not sure if IGL is resistant to using github at all, or just the accidental ommission of that one generator from github..
11:16 AM seb_kuzminsky: here's an example: https://github.com/SebKuzminsky/pycam/releases
11:16 AM seb_kuzminsky: jepler: you're right, it's the maintainer's choice how and where they maintain their software
11:30 AM JT-Shop: I would prefer all my software to remain on the wiki if for no other reason to preserve any links to the software
11:36 AM njh: I have seen people reference to 'Old Wiki' - is there a place to replace it at some point? - it does seem quite outdated
11:37 AM seb_kuzminsky: njh: there's no plan to replace it that i know of
11:38 AM njh: ah, ok
11:38 AM seb_kuzminsky: i think the wiki is a sort of crazy wild west place where anything goes, and i think stuff we're serious about maintaining the quality of should live in git (either the linuxcnc.git repo or a related one, like the one you made)
11:38 AM seb_kuzminsky: but i'm just some guy
11:39 AM njh: seb_kuzminsky: I am sure you are special really
11:40 AM njh: that is something that hasn't been clear with LinuxCNC - is there any official leadership - or just people who do stuff?
11:40 AM JT-Shop: I agree with seb if it is a part of LinuxCNC and is distributed with LinuxCNC it's place is git
11:41 AM njh: how do you decide when releases are ready?
11:42 AM seb_kuzminsky: njh: mostly it's just people doing stuff
11:42 AM seb_kuzminsky: some of us do things that are vital to the project, like cradek running our git server, and jepler running our forum server
11:43 AM seb_kuzminsky: i'm the release manager for 2.7, so it's me that decides when to make releases there
11:46 AM njh: Ah, cool
11:48 AM seb_kuzminsky: which reminds me, i should make 2.7.9 soon... i think i said that a month ago
12:41 PM jepler: which reminds me, need to do software updates on the forum
12:45 PM jepler: OK a quick bounce and we'll be on the latest kernel there too
01:03 PM seb_kuzminsky: hit diggity
01:03 PM seb_kuzminsky: *hot
01:10 PM KGB-linuxcnc: 03Sebastian Kuzminsky 052.7 7183394 06linuxcnc 10docs/man/man1/halui.1 docs: flesh out max-velocity pins in halui manpage * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=7183394
01:26 PM KGB-linuxcnc: 03Sebastian Kuzminsky 052.7-ilowpass-fix 3588a2b 06linuxcnc 10(6 files in 2 dirs) tests: reorg ilowpass test so i can add a low-gain test next to it * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=3588a2b
01:26 PM KGB-linuxcnc: 03Sebastian Kuzminsky 052.7-ilowpass-fix d7813e8 06linuxcnc 03tests/ilowpass/low-gain/README 03tests/ilowpass/low-gain/expected 03tests/ilowpass/low-gain/test.hal tests: add a test of ilowpass with low gain * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=d7813e8
01:26 PM KGB-linuxcnc: 03Sebastian Kuzminsky 052.7-ilowpass-fix 05d6396 06linuxcnc 10src/hal/components/ilowpass.comp ilowpass: round the output instead of truncating * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=05d6396
01:55 PM KGB-linuxcnc: 03Sebastian Kuzminsky 052.7 a1f1aa4 06linuxcnc 10docs/man/man1/halui.1 docs: add units info to halui max-velocity pins in manpage * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=a1f1aa4
05:27 PM linuxcnc-build: build #2560 of 1402.rip-wheezy-rtpreempt-i386 is complete: Failure [4failed runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1402.rip-wheezy-rtpreempt-i386/builds/2560 blamelist: Sebastian Kuzminsky <seb@highlab.com>
06:04 PM seb_kuzminsky: cradek: thanks for taking care of that PR
06:05 PM seb_kuzminsky: fyi, if you merge it instead of cherry-picking, the commit will have the same SHA and github will see that SHA show up in the target branch, and close the PR automatically
06:18 PM cradek: if it's the one I think I remember, I modified it
06:18 PM cradek: but anyway, welcome
06:18 PM cradek: I don't have a good handle on all of github's mystery-meat stuff
06:18 PM cradek: thanks for fixing ilowpass!
06:29 PM linuxcnc-build: build #4901 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4901 blamelist: Sebastian Kuzminsky <seb@highlab.com>
11:29 PM seb_kuzminsky: cradek: does that fix look right to you? i'm changing the behavior, as noted in the PR message, and i'm not sure how dangerous it it
11:30 PM seb_kuzminsky: seems safe to me, hence the PR, but maybe i'm not thinking of something