**** BEGIN LOGGING AT Thu Aug 20 02:59:59 2015
Aug 20 03:43:05 <neem0> nerdboy: available/awake?
Aug 20 03:45:55 <nerdboy> no/yes/maybe
Aug 20 03:49:34 <neem0>  /I don't know/Can you repeat the question/
Aug 20 03:49:49 * neem0 rolls Malcolm in the Middle intro music
Aug 20 03:49:53 <neem0> :)
Aug 20 03:50:21 <neem0> anyway, actual question
Aug 20 03:50:34 <neem0> nerdboy: any good link how I should pack the python code to be installable?
Aug 20 03:50:57 <neem0> I could go and copy alexander's code from PyBBIO, but that's overkill for the simple structure I have going on right now
Aug 20 03:51:16 <neem0> also, I've set the code up as a python package, setting up the examples now
Aug 20 03:51:28 * neem0 still need to push that package code, hmmm
Aug 20 03:54:12 <neem0> nerdboy: currently reading this -> https://packaging.python.org/en/latest/distributing.html
Aug 20 03:54:19 <neem0> any better places to look at?
Aug 20 03:56:16 <nerdboy> either setuptools or distutils
Aug 20 03:56:38 <nerdboy> i think setuptools is the current Python Way
Aug 20 03:57:48 <nerdboy> Setup.py, install to /usr/lib64/python3.4/site-packages/ and lay an egg
Aug 20 03:58:22 <nerdboy> pythonN.N/site-packages...
Aug 20 03:59:33 <neem0> alrighty
Aug 20 03:59:35 * nerdboy does downstream packaging
Aug 20 03:59:44 <neem0> reading on it now, should have it done in a bit
Aug 20 04:07:42 <neem0> also, on the current note of uploading half done code
Aug 20 04:08:06 <neem0> nerdboy: take a look at the packaging for the Python code -> https://github.com/nvisnjic/BeagleSat/tree/master/python
Aug 20 04:09:03 * neem0 isn't happy with the half done code pushing part, but it's for the betterment of the code, they say :/
Aug 20 04:09:27 <nerdboy> oh, stuff a sock in it...
Aug 20 04:09:53 <neem0> :D
Aug 20 04:09:53 <nerdboy> peer/code review is your future, get used to it
Aug 20 04:10:08 * neem0 *stuff*
Aug 20 04:10:58 * neem0 but.. *mumbles something unintelligable*
Aug 20 04:11:02 <neem0> ;)
Aug 20 04:13:47 <neem0> anyway, nerdboy does the packing look good? need to change naming/placement/something?
Aug 20 04:13:59 <neem0> granted all of that can be done at some point later, but still
Aug 20 04:19:21 <nerdboy> looks okay, might work better algorithms/{correction,filters,other} maybe
Aug 20 04:20:05 <nerdboy> did you have something in mind for how the current layout should "grow"?
Aug 20 04:20:56 <neem0> yup
Aug 20 04:21:25 <neem0> so for the input, as long as we're on python, I guess I'll just add libs to PyBBIO, which includes one or two more sensors
Aug 20 04:21:30 <neem0> for the processing/correction
Aug 20 04:22:03 <neem0> the functions I'll need eventually is invariant & variant Correction of data
Aug 20 04:22:28 <neem0> and the compute of corr. factors  for invariant & variant alg
Aug 20 04:23:13 <neem0> invariant is technically done with this setup we have now, only minor improvement later is possible with the rotation stuff, but that is usually handled onboard a sensor chip (it can be handled in software as well)
Aug 20 04:23:54 <neem0> variant is waaay more complicated, and I'll be patching it up with a basic setup I hope very soon (next week maybe?)
Aug 20 04:24:02 <neem0> so variant will maybe need more files and such
Aug 20 04:24:47 <neem0> also, invariant correction is small, so it is in correction.py
Aug 20 04:25:21 <neem0> I put fitting in algorithms in a separate file (could have done it in one), since it's mostly code I changed to suit me, but still need to respect the original author and the licence
Aug 20 04:25:37 <neem0> /fitting/invariant fitting/ ^
Aug 20 04:26:03 <neem0> apart from the correction, I guess we'll be expanding the submodules for beaglesat with stuff like imaging,comms,telemetry, etc etc, at a point later in time
Aug 20 04:27:13 <neem0> nerdboy: ^ that's pretty much the idea, although the sensor stuff is in Python, stuff after should be in C and wrapped for use in python
Aug 20 04:27:17 <neem0> right?
Aug 20 04:35:05 <nerdboy> sounds good
Aug 20 04:35:44 <nerdboy> except, "like sands through the hourglass, so go the days of GSoC"...
Aug 20 04:35:45 <neem0> alrighty
Aug 20 04:35:54 <neem0> yeah
Aug 20 04:35:56 <nerdboy> you have very little time
Aug 20 04:36:06 * neem0 needs to buy a bigger hourglass
Aug 20 04:36:31 * neem0 and then drill a hole in the top to put more sand in (and on the bottom)
Aug 20 04:36:38 <neem0> yeah, aware of that
Aug 20 04:36:57 <neem0> well before tomorrow I'll have all the things on the checklist, or so I hope
Aug 20 04:37:18 <neem0> the Python code for the package/API/install/examples for the invariant correction
Aug 20 04:37:48 <neem0> documentation as well (wiki I guess for now, although I might be able to squeeze in a doxygen :) )
Aug 20 04:38:14 <neem0> after that I'll go fix the invariant part and we can go pushing stuff back to C from there
Aug 20 04:38:43 <neem0> once the deadline flies by
Aug 20 04:39:03 <neem0> nerdboy: that schedule makes sense?
Aug 20 04:41:36 <nerdboy> if it takes care of your list, you should be good
Aug 20 04:46:00 <neem0> will do
Aug 20 04:46:12 <neem0> anyway, back to the trenches
Aug 20 15:05:53 <neemo> gm
Aug 20 15:13:53 <alexanderhiam> neemo: the packaging is looking good
Aug 20 15:15:11 <alexanderhiam> the BeagleSat.correction.algorithms does seem a bit overcomplicated perhaps
Aug 20 15:16:25 <alexanderhiam> fyi the Python way to do stubs (unimplemented functions/methods) is to use the 'pass' statement
Aug 20 15:16:32 <alexanderhiam> that way the code will still run
Aug 20 15:16:40 <alexanderhiam> https://docs.python.org/2/tutorial/controlflow.html#pass-statements
Aug 20 15:18:12 <alexanderhiam> I think it only makes sense for the algorithms to be in their own modules in their own subpackage if they can be used in multiple places
Aug 20 15:19:10 <alexanderhiam> i.e. if the BeagleSat.correction.algorithms.invariantFitting module can be passed to multiple correction routines/objects then it would make sense to have it on its own
Aug 20 15:19:59 <alexanderhiam> but if only the invariantCorrection routine can use it, it might make more sense to just have an invariantCorrection class that includes the algorithm
Aug 20 15:20:15 <neemo> true, was thinking of that
Aug 20 15:20:40 <neemo> the only places I think it will be used is for the single/array processing which is in invariantCorrection
Aug 20 15:21:06 <neemo> and I'll add convenience functions for pulling data from a file/processing/putting it back to a different file
Aug 20 15:21:21 <neemo> which I guess would be the most used mode for the data storing / later processing
Aug 20 15:21:23 <alexanderhiam> ok, then perhaps you could have a BeagleSat.correction package with different modules for each algo
Aug 20 15:21:46 <alexanderhiam> so you'd have a BeagleSat/correction/invariantCorrection.py
Aug 20 15:21:59 <neemo> makes sense to me
Aug 20 15:22:12 <neemo> but the correction.py would be on the same leve las the actual algorithms
Aug 20 15:22:22 <alexanderhiam> and BeagleSat/correction/variantCorrection.py
Aug 20 15:22:36 <neemo> I could I guess remove correction.py and make an __init__.py that loads all of them into beaglesat? if that's what you mean?
Aug 20 15:22:38 <alexanderhiam> well that way you wouldn't need a correction.py
Aug 20 15:22:41 <alexanderhiam> right
Aug 20 15:22:42 <neemo> yeah
Aug 20 15:22:52 <neemo> so __init__.py that imports all of them?
Aug 20 15:23:55 <alexanderhiam> and you can take advantage of Python's duck-typing and have a class for each correction algo with the same methods so they can be used interchangeably
Aug 20 15:24:37 <alexanderhiam> in which case you could have the __init__.py import the classes so you don't need to go that extra level to import them into user code
Aug 20 15:24:54 * nerdboy distracted by a cratered build server...
Aug 20 15:26:18 <neemo> hmmmm alright, I'll look into that
Aug 20 15:26:29 <neemo> alexanderhiam: a link perhaps? So I can oggle a working example
Aug 20 15:26:35 <alexanderhiam> which part?
Aug 20 15:26:50 <neemo> erm
Aug 20 15:27:07 <alexanderhiam> you mean that whole structure I'm describing?
Aug 20 15:27:10 <neemo> actually I just read that it's classes, so just make def algorithmnameclass
Aug 20 15:27:27 <neemo> and import from __init__.py
Aug 20 15:27:33 <neemo> so nvm about the link
Aug 20 15:27:38 <alexanderhiam> class InvariantFitting
Aug 20 15:27:40 <neemo> yeah
Aug 20 15:27:43 <neemo> got it
Aug 20 15:27:52 <alexanderhiam> and do you know what I mean about duck typing?
Aug 20 15:28:07 <alexanderhiam> not sure how international that term is
Aug 20 15:28:12 <neemo> also I had some issues when installing for python3 with the setup.py I have now
Aug 20 15:28:15 <neemo> it installs
Aug 20 15:28:23 <neemo> but I cant do from beaglesat import BeagleSat
Aug 20 15:28:35 <alexanderhiam> oh, PyBBIO doesn't work with python3, so that wouldn't work out too well
Aug 20 15:28:40 <neemo> know anything about that? (the code should be 2.x/3.x compatible for what I'm seeing)
Aug 20 15:28:49 <neemo> yeah that I understood
Aug 20 15:28:58 <alexanderhiam> just stick with 2.7
Aug 20 15:29:00 <neemo> but even my beaglesat package refuses to import :?
Aug 20 15:29:03 <neemo> alright
Aug 20 15:29:06 <neemo> 3.x later, maybe
Aug 20 15:29:14 <alexanderhiam> I've yet to touche python 3
Aug 20 15:29:22 <alexanderhiam> or touch it even
Aug 20 15:29:43 <neemo> touche :)
Aug 20 15:29:47 <neemo> ok
Aug 20 15:29:52 <neemo> also an interesting erm, import problem
Aug 20 15:30:08 <neemo> I've made the previous example to work with the code I've put into the package
Aug 20 15:30:11 <neemo> works good
Aug 20 15:30:14 <neemo> but
Aug 20 15:30:34 <neemo> I have to do a : from bbio import * in the example code
Aug 20 15:30:55 <neemo> Laika.registerSensor( "MPU_1", "MPU9250", bbio.SPI0)
Aug 20 15:30:59 <neemo> wihtout the bbio. part
Aug 20 15:31:12 <alexanderhiam> odd... let me pull the latest and give it a try...
Aug 20 15:31:15 <neemo> Laika.registerSensor( "MPU_1", "MPU9250", SPI0) <- this, asks for an undefined SPI0 if I use it
Aug 20 15:31:18 <neemo> mkey
Aug 20 15:31:41 <alexanderhiam> oh yeah, you'll need to use bbio.SPI0 if you just import bbio
Aug 20 15:32:07 <neemo> can I make it so that I don't need to import bbio at all and use SPI0 as a definition from bbio
Aug 20 15:32:16 <neemo> since i do a from bbio import * in my main beaglesat.py
Aug 20 15:32:22 <alexanderhiam> no
Aug 20 15:32:27 <neemo> so ideally, the examples would like to import only beaglesat
Aug 20 15:32:30 <alexanderhiam> and you shouldn't import * in the package
Aug 20 15:32:33 <neemo> hmmm
Aug 20 15:32:34 <alexanderhiam> from anything
Aug 20 15:32:54 <neemo> true that, it's temporary though
Aug 20 15:33:32 <alexanderhiam> you can either do 'from bbio import X, Y, Z' to import individual things, or 'import bbio' and use bbio.X
Aug 20 15:33:42 <alexanderhiam> that's just the way it goes in Python
Aug 20 15:33:49 <neemo> if i import bbio in beaglesat.py
Aug 20 15:34:04 <neemo> beaglesatExample.py which imports beaglesat
Aug 20 15:34:09 <neemo> is still unaware of SPI0
Aug 20 15:34:25 <neemo> right? :/ (or I messsed something up and have to play with my imports)
Aug 20 15:34:25 <alexanderhiam> for the most part you never want to do a 'from X import *' inside a package/module for namespace clutter reasons
Aug 20 15:34:39 <neemo> trying to avoid that yeah
Aug 20 15:34:46 <alexanderhiam> that will put everything from the bbio namespace into the beaglesat namespace
Aug 20 15:34:50 <neemo> I'll be importing in beaglesat only the sensors I want to support
Aug 20 15:34:55 <alexanderhiam> so you'd have beaglesat.SPI0
Aug 20 15:35:01 <neemo> ok
Aug 20 15:35:09 <neemo> will look into it and patch it up in a bit
Aug 20 15:35:20 <neemo> anyway the example code works, will add the visualizer as well in a bit
Aug 20 15:35:31 <alexanderhiam> cool
Aug 20 15:35:34 <neemo> and I'll be moving the correction algorithms to classes for import
Aug 20 15:35:45 <neemo> so should have everything working in a few hours
Aug 20 15:35:56 <alexanderhiam> awesome
Aug 20 15:36:00 <neemo> file input output in a bit more as well
Aug 20 15:36:13 <neemo> and then, erm... probably get a powernap and off to the github wiki
Aug 20 15:36:22 <alexanderhiam> so you're back home now, right? What time zone?
Aug 20 15:36:40 <neemo> yup
Aug 20 15:36:42 <neemo> +0200
Aug 20 15:36:55 <neemo> 5 o clock pm now
Aug 20 15:37:20 <neemo> though I'm not a guy to hold a regular sleeping schedule, so ping me when you like
Aug 20 15:37:40 <neemo> anyway the code should be working by tonight and be testable and such, and I'll use the night to document things
Aug 20 15:37:41 <alexanderhiam> ah, that's a bit easier of a difference
Aug 20 15:37:46 <neemo> yup
Aug 20 15:38:12 <neemo> +8 or less  to you? (not sure which US zone, so many time zones)
Aug 20 15:38:32 <neemo> anyway, buy nightime your time (8am my place) the docs should be done
Aug 20 15:38:55 <alexanderhiam> 11:38AM here
Aug 20 15:38:56 <neemo> which leaves tomorrow the last couple of hours to fix anything I missed and correct stuff which isn't good
Aug 20 15:38:57 <alexanderhiam> EST
Aug 20 15:39:01 <neemo> EST
Aug 20 15:39:11 <alexanderhiam> sometimes -4, sometimes -5
Aug 20 15:39:19 <neemo> nerdboy: is PST right? cali?
Aug 20 15:39:21 <alexanderhiam> EST/EDT
Aug 20 15:39:51 <neemo> gotcha, so so +6 towards me
Aug 20 15:39:58 <neemo> alright
Aug 20 15:40:23 <neemo> well I'm gonna do this last stretch, but nerdboy alexanderhiam anything you want me to fix ping me asap so I can get to it and be done with it by tomorrow night ;)
Aug 20 15:40:47 <neemo> alexanderhiam nerdboy: current state looking good? apart from the corrections we mentioned above
Aug 20 15:41:06 <alexanderhiam> yeah, it's getting there
Aug 20 15:41:30 <alexanderhiam> just keep pushing so we can let you know right away if something should be changed
Aug 20 15:58:40 <neemo> deal
Aug 20 15:58:44 <neemo> off to more coding then
Aug 20 16:10:05 <Abhishek_> shubhangi: ping
Aug 20 18:44:13 <ebadawy> jkridner: ping
Aug 20 18:44:19 <jkridner> hi
Aug 20 18:44:35 <ebadawy> sorry for not being there is time :(
Aug 20 18:44:51 <ebadawy> have some time now?
Aug 20 18:50:33 <ebadawy> jkridner: incase you missed it, moto-timo have made a quick prototype to what he was talking about ,, http://moto-timo.github.io/bone101/Support/bone101
Aug 20 18:50:40 <ebadawy> what do you think?
Aug 20 18:51:18 <jkridner> the rules look a bit bulky and non-obvious to me.
Aug 20 18:51:29 <jkridner> not all of the divisions have these.
Aug 20 18:51:50 <ebadawy> ok, have made a another tweak to it ,, http://ehab93.github.io/bone101/Support/bone101/
Aug 20 18:53:10 <jkridner> https://jqueryui.com/accordion/ is more obvious, for example.
Aug 20 18:53:43 <ebadawy> but this is better for small content
Aug 20 18:54:13 <ebadawy> I remember you asked for images for each section as people don't tend to read too much, right?
Aug 20 18:56:22 <jkridner> Other large documentation pages don't necessarily close: http://getbootstrap.com/javascript/
Aug 20 18:56:42 <jkridner> other people complained there was too much information and important information was getting missed.
Aug 20 18:58:14 <ebadawy> jkridner: so you are suggesting to get the long page? :)
Aug 20 18:59:08 <jkridner> I just don't see these collapsing views as improvements as they stand now... I think the fact that there is information that is being missed isn't being made more clear by them.
Aug 20 18:59:32 <jkridner> I want elements that will encourage people to read all parts of this page that they didn't previously.
Aug 20 18:59:50 * jkridner wonders by the edits if you've actually read it and find it meaningful.
Aug 20 19:00:57 <ebadawy> ^ most of it, yes.
Aug 20 19:01:44 * jkridner keeps reading pages like http://www.dtelepathy.com/blog/inspiration/14-beautiful-content-heavy-websites-for-inspiration for more ideas
Aug 20 19:01:59 <jkridner> ebadawy: then you find this "More..." element useful?
Aug 20 19:02:03 <jkridner> and intuitive?
Aug 20 19:02:19 <jkridner> is this information you'd go back and reference or simply read once?
Aug 20 19:02:40 <jkridner> is there a right approach to delivering it for the right usages?
Aug 20 19:03:25 <ebadawy> for me, as end user I think so, I can only go to the section I want to read an expand it for more information
Aug 20 19:03:49 <ebadawy> I am just not a big fan of long pages :)
Aug 20 19:04:44 <ebadawy> that is why I was asking to make it in a separated tabs, but you need the content to be one page
Aug 20 19:04:56 <jkridner> ebadawy: then make it *work* like a bunch of different pages, but I'd like to avoid breaking links to things like http://beagleboard.org/support/bone101/#headers
Aug 20 19:06:09 <ebadawy> it should be working there also http://ehab93.github.io/bone101/Support/bone101/#headers
Aug 20 19:06:15 <jkridner> A simple set of "<< Previous    Next >>" links in a very obvious place would be fine with me, as long as we can jump to the individual pages.
Aug 20 19:06:49 <jkridner> ebadawy: in the past, I did the whole thing as a slideshow... but having the navigation links to jump forward became critical for the information.
Aug 20 19:07:09 <jkridner> automatically displaying information upon issuing a scroll would be good in addition to the buttons.
Aug 20 19:07:39 <jkridner> there is need to walk people through this information because they might not be familiar with it.
Aug 20 19:08:23 <ebadawy> ^exactly, I think this is the problem with the long page
Aug 20 19:08:53 * ebadawy trying to imagine how "<< Previous    Next >>" should look like.
Aug 20 19:09:07 <jkridner> heck, I wouldn't mind putting all the information in bonecards, but getting to the information should be as easy as scrolling and each page should be able to be reached with anchor links, including the existing anchros.
Aug 20 19:09:11 <jkridner> er, anchors.
Aug 20 19:10:04 <ebadawy> how can I get these list of anchors, are they the just the heading lines?
Aug 20 19:11:31 <jkridner> no, you need to look at the source.
Aug 20 19:12:10 <ebadawy> h tags with ids?
Aug 20 19:13:22 <jkridner> yeah, anything with an id.
Aug 20 19:15:01 <ebadawy> okay, so just to make sure I'm getting you right. what I should do is to make sure all anchors work with this current page http://ehab93.github.io/bone101/Support/bone101/
Aug 20 19:15:36 <jkridner> I don't like the current graphics for expanding. I think they are hard to see.
Aug 20 19:16:02 <ebadawy> even with the animated arrows?
Aug 20 19:16:10 <jkridner> If I were to do it myself right now, I think I would try to figure out how to put all the information in Bonecards and navigate with scrolling to make sure everything fits on the screen at the same time.
Aug 20 19:16:20 <jkridner> er, not at the same time...
Aug 20 19:16:41 <jkridner> I mean while viewing any particular part.
Aug 20 19:17:52 <ebadawy> yeah, got you
Aug 20 19:18:14 <ebadawy> but there will be ALOT of bonecards!
Aug 20 19:18:50 <jkridner> yeah.
Aug 20 19:19:13 <jkridner> would make it simpler to do it in a presentation-style, like I used to do.
Aug 20 19:19:28 <jkridner> bone101 used to be a slideshow... let me see if I can find a link to the old one.
Aug 20 19:19:42 <ebadawy> please
Aug 20 19:19:55 <jkridner> I'd probably adjust the index to work something more like http://getbootstrap.com/javascript/#buttons
Aug 20 19:20:30 <ebadawy> yeah, that what I was goint to do
Aug 20 19:20:35 <jkridner> http://beagleboard.org/static/presentations/boston2011/beagleboard101/#(1)
Aug 20 19:21:17 <jkridner> ^^^ is how I used to introduce people to BeagleBoard-xM
Aug 20 19:21:27 <jkridner> I had something similar for BeagleBone at one point.
Aug 20 19:22:26 <jkridner> doing a slide presentation like that and http://beagleboard.org/static/presentations/boston2011/beaconbasicio/#(1) should be very easy if the information was broken into bonecards.
Aug 20 19:22:56 <jkridner> if there is a good index, then jumping around in the presentation shouldn't be so aweful.
Aug 20 19:24:27 <ebadawy> I'm imagining what you asking for is to be presented more like what is in demos but without microcards, am I gettinig you right?
Aug 20 19:24:30 <ebadawy> http://ehab93.github.io/bone101/Support/BoneScript/demo_blinkled/
Aug 20 19:25:29 <ebadawy> with a reasonable linking and jumping to right contents sure
Aug 20 19:25:33 <jkridner> why without? why not go ahead and use them?
Aug 20 19:25:58 <jkridner> the scrolling on the demos isn't very good right now
Aug 20 19:26:23 <ebadawy> is it? why?
Aug 20 19:27:40 <jkridner> you have to scroll down just to see the index of cards.
Aug 20 19:27:52 <jkridner> going left-and-right isn't obvious.
Aug 20 19:28:03 <jkridner> scrolling left-and-right doesn't work.
Aug 20 19:28:30 <jkridner> scrolling up and down or using up and down arrow won't bring you to the next card.
Aug 20 19:29:07 <ebadawy> ^^^^ can put microcards on the top, but I think it should be there as it is now
Aug 20 19:29:36 <jkridner> the good thing is this discussion is filling me with some crazy fun ideas. :)
Aug 20 19:30:04 <ebadawy> cool :)
Aug 20 19:30:30 <ebadawy> why scrolling left-and-right doesn't work?
Aug 20 19:31:00 <ebadawy> haven't attached any action to up and down scrolling
Aug 20 19:34:17 <jkridner> ebadawy: what do you think about navigation and appearance of http://beagleboard.org/static/presentations/boston2011/beagleboard101/#(1) ?
Aug 20 19:34:22 <jkridner> ebadawy: not sure. arrows work, but using the scroll function on the mouse doesn't.
Aug 20 19:37:07 <ebadawy> ^^ it is good, some times up/down arrows works with me which I think they shouldn't, indexing is a good way of navigation also
Aug 20 19:37:41 <ebadawy> some contents comes over the beagle
Aug 20 19:39:06 <ebadawy> ^^^ if you mean using a scroll on bonecards, no it is not functioning
Aug 20 19:39:16 <jkridner> so, do you like the idea of breaking down the content into bonecards (fixes the size for amount of content on a page, like a slide does) and displaying it a bit like the presentation viewer, but including an accordian index like the getbootstrap page?
Aug 20 19:39:58 <jkridner> I know you are supposed to be pencils down, so I see this could fall outside the scope of GSoC, but I'd like to avoid having you do more stuff that I'd want to throw away.
Aug 20 19:41:20 <ebadawy> sure I have no problem to continue contributing, but if you are asking if "I" like it, well I don't think so :)
Aug 20 19:41:29 * jkridner wonders if force-reloading a page (perhaps preserving some local edits somehow) would enable the "stop" function.
Aug 20 19:41:41 <ebadawy> don't like to only see some bonecards in the homepage :)
Aug 20 19:42:00 <jkridner> ebadawy: yeah, I'm asking about your taste/beliefs to best convey information.
Aug 20 19:43:03 <jkridner> hoping you can understand what care-abouts I have: 1) making the individual pages easy to look good and predictable (like bonecards and presentations) without information overload
Aug 20 19:43:03 <ebadawy> I can do it, but I won't be as much happy as seeing the content separated as it is now
Aug 20 19:43:09 <jkridner> 2) making content easy to fork
Aug 20 19:43:44 <ebadawy> ^you are talking about demos?
Aug 20 19:43:46 <jkridner> 3) making navigation simple without breaking links coming from other sites, ie. http://beagleboard.org/support/bone101/#headers-spi
Aug 20 19:44:01 <jkridner> 4) making discovery of content easy and obvious.
Aug 20 19:44:07 <jkridner> ebadawy: I'm talking about all of bone101.
Aug 20 19:44:13 <jkridner> bone101 is your intro to all things BeagleBone
Aug 20 19:44:28 <jkridner> including a community generated library of demos.
Aug 20 19:44:51 <ebadawy> yeah, but the forking point how it should be! you mean a gist fork?
Aug 20 19:45:00 <jkridner> but, no reason all of the bone101 content shouldn't leverage what tools we create for this if done right.
Aug 20 19:45:36 <jkridner> gist and/or git/github.... gist is just super-handy for those new to github. just makes sense that they are forking some smaller element.
Aug 20 19:46:54 <ebadawy> good points I think, thanks for that
Aug 20 19:47:55 * jkridner has to run away again. :(
Aug 20 19:48:28 <ebadawy> okay, just a quick question before you leave
Aug 20 19:48:30 <jkridner> I'll be back on for just a few minutes in about 15-20 minutes from now... and then I'll be gone until late evening.
Aug 20 19:49:05 <ebadawy> as a one day left, what updates do you expect to see
Aug 20 19:49:24 <ebadawy> as we can discuss anything later
Aug 20 19:51:29 <jkridner> I think the template title issue is something significant to discover, but might not be reasonable to ask in this timeframe.
Aug 20 19:52:48 <ebadawy> sorry, I don't get it, do you mean the anchor links?
Aug 20 19:54:12 <jkridner> no, the page titles, per my comments on the merge.
Aug 20 19:54:21 <jkridner> did you already address https://github.com/jadonk/bone101/issues/28 ?
Aug 20 19:55:06 <ebadawy> ^^oh, sorry get it
Aug 20 19:55:08 <jkridner> seems everything else critical is covered, but I'll want you to make sure you do a good write-up (README.md) regarding the functionality of forking/etc.
Aug 20 19:55:24 <ebadawy> ^ will do
Aug 20 19:55:29 <jkridner> ugh... missed my window. :'-(
Aug 20 19:55:50 <ebadawy> for issue #28 haven't chekced it before, but I think it is solved
Aug 20 20:35:20 <ds2> hmmmmm
**** ENDING LOGGING AT Fri Aug 21 02:59:58 2015