**** BEGIN LOGGING AT Fri Aug 21 02:59:58 2015 Aug 21 11:03:01 jkridner : https://github.com/shubhi1407/PRU-framework/wiki ... give it a read if you get time Aug 21 12:38:22 shubhangi: thanks. very nice documentation. I'll provide some feedback based on my reading... Aug 21 12:39:24 AMP -> I know this is Asynchronous MultiProcessing, but I'd generally avoid abbreviations like this in documentation to avoid the risk other people might not know. Aug 21 12:39:40 at least to avoid the possibility of it being vague. Aug 21 12:41:25 the bulleted list for categories makes the categories a bit ambiguous, since there is only a single bullet followed by an ordered list. Aug 21 12:41:35 also the word "couple" to me is always 2. Aug 21 12:44:32 jkridner: thanks for the feedback. I'll make the necessary corrections Aug 21 13:18:17 gm Aug 21 13:18:47 nerdboy: Cali up and running? :) Aug 21 15:19:52 _av500_: ping again. Aug 21 16:14:21 neem0: got a mtg... Aug 21 16:17:41 nerdboy: nps, just ping back when you're done Aug 21 16:17:57 got a couple of questions about the license and other details Aug 21 16:18:11 Wikiing atm and final touches for the visualizer Aug 21 16:31:30 which open source license is up to you Aug 21 16:31:42 i tend to use GPL Aug 21 16:33:45 GPLv@ Aug 21 16:33:47 v2 Aug 21 16:33:52 is what I was aiming for Aug 21 16:34:03 if you made changes to other GPL'd code then it would cover those bits if you distribute changed stuff Aug 21 16:34:04 gonna push a LICENSE.md to the root Aug 21 16:34:05 makes sense? Aug 21 16:34:15 sounds fine to me Aug 21 16:34:29 well, the code for the solver was based on a GPLv3 code Aug 21 16:34:43 so GPLv2 should cover that as well, no? Aug 21 16:44:24 "based on" how? Aug 21 16:45:14 GPL3 is probably better for that... Aug 21 16:47:46 based on, as in gave me inspiration how to do the matlab stuff in python Aug 21 16:47:58 linalg specifically Aug 21 16:48:42 I've left the licence and copyright name/links in the file Aug 21 16:48:48 and its GPL3 Aug 21 16:51:32 neem0: if you're redistributing GPLv3 code I think you have to use GPLv3 for the whole project Aug 21 16:52:12 makes sense Aug 21 16:52:35 alexanderhiam: significant differences between GPLv3 and v2? if you can give me the rundown Aug 21 16:52:38 ? Aug 21 16:53:05 * neem0 goes googling as well Aug 21 16:53:38 3 is more Stallman-ish mostly Aug 21 16:54:06 but you're not redistributing other gpl3 code, so... Aug 21 16:54:22 * nerdboy off to a mtg... Aug 21 16:54:59 wait, are you redistributing gpl3 code? i.e. do you have someone elses gpl3 code in your repo? Aug 21 16:57:43 alexanderhiam: edited and a part (50%) of the original code, but yes and it's on GPLv3 Aug 21 16:58:01 I could'ev arrived to the same thing by myself. but didn't make sense to reinvent the wheel Aug 21 16:58:22 ok, then I'm fairly certain that per GPLv3 the whole project has to be GPLv3 Aug 21 16:58:23 alexanderhiam: So I presume that means I'm using GPLv3 Aug 21 16:58:26 ok Aug 21 16:58:29 is that a problem? Aug 21 16:58:37 which makes the choice easy ;) Aug 21 16:58:46 no problem at all Aug 21 16:58:49 since, well, I don't know much about the license :) Aug 21 16:58:51 alright Aug 21 16:58:54 so GPLv3 it is Aug 21 16:59:08 * neem0 not to self, edit python package info to v3+ instead of v2+ Aug 21 16:59:11 anyway Aug 21 16:59:24 alexanderhiam nerdboy: Care to take a look at the code? any last change whishs Aug 21 16:59:25 http://www.gnu.org/licenses/quick-guide-gplv3.en.html Aug 21 16:59:27 whishes Aug 21 16:59:31 thanks alexanderhiam Aug 21 17:00:02 also, I'm going to push the visualizer, which works nicely (if you have X on your BBB) Aug 21 17:01:04 alexanderhiam: you mentioned referenceData for testing in the email. I'm going to pack some real data I have now, but it ain't that good (mostly since I don't have a nice mag. clean area to test) Aug 21 17:01:29 it works though, but better data will be in later Aug 21 17:01:49 do you want me to pack some simulated data for the test (as reference) ? Aug 21 17:01:59 alexanderhiam: nerdboy ^ Aug 21 17:02:03 that would be good Aug 21 17:02:14 so simulated is ok? Aug 21 17:02:42 for the raw data, or the test data to base the correction on? Aug 21 17:02:42 I mean, not simulated, just more stable Aug 21 17:04:37 alexanderhiam: also about the licence -> https://gist.github.com/jnrbsn/708961 Aug 21 17:04:52 clone this into my github root folder under LICENSE.md ? Aug 21 17:04:57 that enough ? Aug 21 17:05:35 pull it from gnu.org Aug 21 17:06:11 http://www.gnu.org/licenses/gpl-3.0.en.html Aug 21 17:06:12 best to have it in a plaintext LICENSE.txt Aug 21 17:06:26 http://www.gnu.org/licenses/gpl-3.0.txt Aug 21 17:06:27 in the root Aug 21 17:07:24 http://www.gnu.org/licenses/gpl-howto.html Aug 21 17:07:25 that last link ^ Aug 21 17:07:34 read carefully and follow exactly Aug 21 17:08:55 on it Aug 21 17:09:07 anyway all the examples are up in the repo Aug 21 17:09:19 cool Aug 21 17:09:25 got a couple of basic and one that shows the whole data pipeline Aug 21 17:09:26 how's the documentation coming? Aug 21 17:09:34 getdata/store/load/process etc Aug 21 17:09:38 working on it Aug 21 17:09:46 want to patch up the visualizer first Aug 21 17:09:59 after that copy the licence and document Aug 21 17:10:05 that should round up the list, right? Aug 21 17:16:35 neem0: be sure to comment on and close those github issues as you go Aug 21 17:18:28 alright Aug 21 17:18:47 I mean, I'm asking for feedback to close them, aka permission Aug 21 17:18:59 since I think most of them are solved or will be in the next 30 mins (looks at licence) Aug 21 17:19:28 your repo your issues ;) Aug 21 17:22:17 haha Aug 21 17:22:19 I like that Aug 21 17:22:26 well, of to license Aug 21 17:22:29 and close them issues Aug 21 18:30:21 alexanderhiam: https://github.com/nvisnjic/BeagleSat/blob/master/LICENCE.txt & https://github.com/nvisnjic/BeagleSat/blob/master/python/beaglesat/beaglesat.py (in the header) Aug 21 18:30:29 that good enough for licensing? Aug 21 18:32:15 just about. You need the copyright and license note in every code file (I usually leave it out of the __init__.py files) Aug 21 18:33:28 it's also best to mention at the top level (e.g. in the README) any redistributed code Aug 21 18:33:41 with it's copyright and what license it's under Aug 21 18:36:08 ls Aug 21 18:36:12 ls Aug 21 18:36:15 yeeah Aug 21 18:36:38 * neemo you're hitting the wrong window with your requests :/ Aug 21 18:36:39 xD Aug 21 18:36:49 alright, will be copying and pasting then Aug 21 18:37:03 the Readme file will be fixed in a sec Aug 21 21:17:00 jkridner: Just realized what X forwarding can do with BeagleLogic, although I bet if I'd get a decent framerate out of it. **** ENDING LOGGING AT Sat Aug 22 02:59:58 2015