IRC log for #brlcad on 20160516

00:17.54 *** join/#brlcad teepee (~teepee@unaffiliated/teepee)
00:56.34 *** join/#brlcad oooedqpkzhfbcewf (~armin@dslb-178-010-188-047.178.010.pools.vodafone-ip.de)
02:52.39 *** join/#brlcad teepee_ (~teepee@unaffiliated/teepee)
05:41.01 *** join/#brlcad ickby (~stefan@x5d844216.dyn.telefonica.de)
06:37.59 *** join/#brlcad ickby_ (~stefan@x5d844216.dyn.telefonica.de)
07:09.54 *** join/#brlcad ickby (~stefan@x5d844216.dyn.telefonica.de)
07:18.42 *** join/#brlcad merzo (~merzo@92.60.189.225)
07:20.55 *** join/#brlcad sniok (~sniok@89.252.29.238)
07:27.38 *** join/#brlcad ickby_ (~stefan@x5d844216.dyn.telefonica.de)
07:30.34 *** join/#brlcad boj_ (~boj@116.7.245.187)
07:37.35 *** join/#brlcad boj (~boj@2001:250:3c00:2074:d949:142a:96b9:2f0e)
07:46.06 *** join/#brlcad ickby_ (~stefan@x5d844216.dyn.telefonica.de)
07:51.57 *** join/#brlcad boj_ (~boj@2001:250:3c00:2074:d949:142a:96b9:2f0e)
07:53.39 *** join/#brlcad ickby (~stefan@x5d844216.dyn.telefonica.de)
07:58.07 *** join/#brlcad ickby_ (~stefan@x5d844216.dyn.telefonica.de)
08:01.26 *** join/#brlcad ickby_ (~stefan@x5d844216.dyn.telefonica.de)
08:56.42 Notify 03BRL-CAD Wiki:Mandeeps708 * 9705 /wiki/Google_Summer_of_Code/2016: changed abstract
11:01.11 *** join/#brlcad amarjeet (~Amarjeet@101.211.171.44)
11:20.46 *** join/#brlcad amarjeet (~Amarjeet@101.211.171.44)
12:20.27 *** join/#brlcad jordi_sayol (~jordi@93.129.21.95.dynamic.jazztel.es)
12:36.31 *** join/#brlcad amarjeet (~Amarjeet@101.211.171.44)
12:51.46 *** join/#brlcad amarjeet (~Amarjeet@101.211.171.44)
13:07.36 *** join/#brlcad ickby (~stefan@x5d844216.dyn.telefonica.de)
13:17.25 *** join/#brlcad yorik (~yorik@177.139.88.136)
13:43.08 *** join/#brlcad kintel (~kintel@unaffiliated/kintel)
13:55.30 *** join/#brlcad ickby (~stefan@x5d844216.dyn.telefonica.de)
13:55.31 *** join/#brlcad Mathnerd314 (~quassel@supertux/Mathnerd314)
14:00.41 Notify 03BRL-CAD:starseeker * 67889 brlcad/trunk/src/tclscripts/man_browser.tcl: Don't try to open a directory.
14:07.42 *** join/#brlcad ickby_ (~stefan@x5d844216.dyn.telefonica.de)
14:15.16 Notify 03BRL-CAD:starseeker * 67890 brlcad/trunk/doc/docbook/system/mann/search.xml: correct exmaples/descriptions for -above and -below.
14:16.33 *** join/#brlcad amarjeet (~Amarjeet@101.211.171.44)
14:33.37 Notify 03BRL-CAD:starseeker * 67891 (brlcad/trunk/AUTHORS brlcad/trunk/CHANGES): list a couple of MGED commands for deprecation - find doesn't work on the MGED command prompt anyway, and the em command can be replaced by search.
14:43.52 Notify 03BRL-CAD:starseeker * 67892 (brlcad/trunk/CHANGES brlcad/trunk/doc/docbook/system/mann/expand.xml): Also call out expand for deprecation - replaced by search. Fix docs while we're at it - using shell globbing, not regex.
14:51.34 *** join/#brlcad ickby (~stefan@x5d844216.dyn.telefonica.de)
14:54.40 Notify 03BRL-CAD:starseeker * 67893 brlcad/trunk/CHANGES: nevermind - find man page appears to be actually for the dbfind command...
15:13.19 Notify 03BRL-CAD:starseeker * 67894 (brlcad/trunk/NEWS brlcad/trunk/src/librt/search.c): If we added an -above option to a flat search, MGED crashed. Initialize the full_paths ptbl to NULL in a flat search so the above function knows not to try to process it.
15:20.31 *** join/#brlcad amarjeet (~Amarjeet@101.211.171.44)
15:57.40 *** join/#brlcad amarjeet (~Amarjeet@49.138.208.141)
16:11.22 *** join/#brlcad kintel (~kintel@unaffiliated/kintel)
16:24.15 *** join/#brlcad merzo (~merzo@user-94-45-58-138-1.skif.com.ua)
16:33.58 *** join/#brlcad LordOfBikes (~armin@dslb-178-010-188-047.178.010.pools.vodafone-ip.de)
16:54.54 *** join/#brlcad amarjeet (~Amarjeet@49.138.208.141)
17:02.05 *** join/#brlcad merzo (~merzo@user-94-45-58-141.skif.com.ua)
17:09.43 *** join/#brlcad amarjeet (~amarjeet@49.138.208.141)
17:11.31 *** join/#brlcad boj (~boj@116.7.245.187)
17:25.02 *** join/#brlcad tandoorichick (3d0c28b1@gateway/web/freenode/ip.61.12.40.177)
17:28.43 Notify 03BRL-CAD Wiki:Amarjeet Singh Kapoor * 9706 /wiki/User:Amarjeet_Singh_Kapoor/GSoC2016/Projec: /* Milestones */
17:33.22 Notify 03BRL-CAD Wiki:Oleksandr dubenko * 9707 /wiki/Google_Summer_of_Code/2016: Added abstract link
17:39.15 *** join/#brlcad sniok (~sniok@89.252.29.238)
17:53.33 *** join/#brlcad amarjeet (~Amarjeet@101.214.253.101)
17:56.01 Notify 03BRL-CAD Wiki:Tandoorichick * 9708 /wiki/Google_Summer_of_Code/2016: /* Automatic Polygonal Mesh Healing */
18:00.36 Notify 03BRL-CAD Wiki:Gaganjyotsingh * 9709 /wiki/Google_Summer_of_Code/2016: /* LibreCAD V3 Bezier and FILE I/O */
18:34.23 *** join/#brlcad kintel (~kintel@unaffiliated/kintel)
18:40.34 Notify 03BRL-CAD:starseeker * 67895 brlcad/trunk/TODO: Make a note that dbfind should be replaced by ls */obj rather than search, due to performance reasons.
18:47.22 Notify 03BRL-CAD:starseeker * 67896 brlcad/trunk/TODO: typo
18:54.09 Notify 03BRL-CAD:starseeker * 67897 brlcad/trunk/CHANGES: I see em was called out earlier
18:56.01 brlcad sniok: if you have at least a half hour availability, it would be good to talk about the website some
18:56.18 sniok Yeah, sure
18:57.20 Notify 03BRL-CAD:starseeker * 67898 brlcad/trunk/CHANGES: deprecate pathlist
18:57.22 brlcad how much time do you have?
18:58.00 sniok About 30-40 minutes
18:58.44 brlcad okay, so we'll keep it snappy :)
18:59.25 brlcad did you make any progress on updating the 3d logo or seeing if one of the gci tasks completed it?
19:01.04 sniok Yes, I'm still developing and tweaking logo
19:01.07 Notify 03BRL-CAD:starseeker * 67899 brlcad/trunk/CHANGES: reorganize to clarify what's being deprecated are mged commands.
19:01.49 sniok I wrote about it on blog over here https://blog.esde.name/logo-tweaks/ and here https://blog.esde.name/more-logos/
19:06.06 brlcad so what I'm seeing... basically you didn't, you half-disregarded it and did something else :)
19:10.14 sniok Yeah, but my main concern is logo that will go in website, and I don't think that rendering and getting image from 3d model is worth it
19:10.49 brlcad logo design is something that is obviously highly subjective
19:12.54 brlcad but also directly pertains to the identity of a project, so we can't just ignore important discussion points like this
19:13.58 brlcad completely understand that there will be design points that you may disagree with and your artistic inputs are an important part of the project
19:14.08 brlcad but there will be disagreements, and how we resolve them will be through discussion
19:15.31 sniok I don't change logo radically, I'm just making tweaks to current version. I understand importance of this question and thats why I'm trying to make it as good as possible
19:16.51 sniok When I'll make my final version we will definitely discuss it
19:16.54 brlcad appreciate you trying to make it as good as possible
19:17.17 brlcad but this is also not something that you'd be expected to get right by yourself
19:17.31 brlcad so you get your "final version" and it has some critical issue, then what? ;)
19:18.04 brlcad you're done, you spent X days working on it, but we can't use it because "requirements" weren't discussed or adhered to
19:18.34 brlcad I'd think that'd either be very frustrating to you, or even disheartening
19:20.20 sniok Ok, I got where are you heading. I should get some input before doing task
19:21.15 brlcad before, during, after .. it's as much about communication as it is the technical work, sometimes more important than the work itself
19:22.57 brlcad for this specific issue of the logo, from my perspective you're essentially building a vector version which is great/needed
19:23.44 brlcad the only issue is a point made in my original response, that having a 3D version is not just nice to have
19:24.15 *** join/#brlcad merzo (~merzo@81-53-132-95.pool.ukrtel.net)
19:24.17 brlcad that doesn't meant that the resultant image has to be rendered, but the silhoette very much should
19:25.44 brlcad it's a reflection of the project, and we're a 3D solid modeling precise engineering system ... it's essential that our logo exist as a precise 3D solid model and that any imagery is derived from that canonical form
19:27.26 brlcad that doesn't mean you have to work on the logo, especially if you don't want to or see why it's worth it -- there's plenty of other work I'm sure we'll easily agree on
19:29.00 brlcad have you tried overlaying your new version over the current rendered version?
19:30.15 sniok Not yet but I will do it
19:31.06 brlcad more importantly, if the last GCI version that supposedly fixed the pin ratio is correct and matches your version, then this could be a good workable version, but that's something that will need to be checked
19:31.53 brlcad however, didn't really intend to talk about the logo ... we have bigger items to discuss :)
19:32.27 brlcad I'm hoping we get on the same page in terms of the marketing aspects of our website design that you are not necessarily privy
19:33.13 sniok What kind of marketing aspects?
19:33.21 brlcad for one, it's highly desirable (for MANY reasons political, social, and technical) that we leverage as much completed GCI work as possible
19:33.52 brlcad so you really should become as intimately familiar with what was done under GCI as possible if you haven't already
19:34.21 brlcad your work is in there too and quality is all over the board, but there are specific elements that need to be incorporated
19:34.58 brlcad maybe not as fun as doing everything yourself, but I cannot stress how essential this will be once coding is under way
19:36.08 sniok yeah that sounds reasonable
19:36.27 brlcad you'll also need to be prepared to work on the web repo, to submit pull requests there for integration and review as we want your work to go live as soon as it's checked and working adequately
19:36.56 brlcad how good is your javascript?
19:37.05 brlcad worked with jquery?
19:37.40 sniok yes, pretty decent
19:37.44 brlcad cool
19:39.20 brlcad you mention docs in your project plan
19:39.34 brlcad have you had a chance to look into the work from last year?
19:41.03 sniok that beta.brlcad.org/w/ site?
19:42.08 brlcad no, the docs project
19:42.30 brlcad the website has three main needs: 1) same theme/style used across main page, wiki, gallery, etc, 2) get documentation online and syncing automatically, and 3) a stronger call to participation
19:42.46 brlcad last year's project was http://brlcad.org/wiki/Google_Summer_of_Code/2015#Synchronize_Wiki_with_Docbook
19:42.52 brlcad that plays right into #2
19:43.33 brlcad that's probably a couple weeks worth of work at a minimum, but mostly styling work, maybe some coding on the search interface
19:45.51 brlcad stylistically, there's a good bit of freedom, but I don't want us to look like our proprietary counterparts at all ...that's a firm requirement... :)
19:47.20 brlcad clean and modern, but doing things (however insignificant) that they are not
19:47.22 brlcad fun, cheeky, inviting
19:47.28 brlcad make sense? :)
19:48.08 sniok yeah
19:50.26 brlcad did you have any questions?
19:52.36 brlcad and please,please, lets continue the discussion later up if you have concerns or don't believe something is worth it because this needs to be an ongoing dialog with mutual understanding
19:53.15 *** join/#brlcad kintel (~kintel@unaffiliated/kintel)
19:53.36 sniok I don't get how docs work
19:54.08 sniok I mean that past year project
19:54.31 sniok Where is web interface to Docbook
19:55.54 sniok Ok, I'll look more into that project and eventually I'll figure out
19:57.12 brlcad last year's project is not online --- there's just code
19:57.24 brlcad that's why it's important to get it online :)
19:57.35 brlcad why its #2 priority-wise
19:58.29 brlcad our docbook sources live in the svn repo, one of our build targets produces the website files
20:00.04 sniok And yes, I'll try to discuss every aspect of project as much as possible
20:22.35 *** join/#brlcad merzo (~merzo@14-6-133-95.pool.ukrtel.net)
20:59.57 *** join/#brlcad ickby_ (~stefan@x5d844216.dyn.telefonica.de)
21:04.21 *** join/#brlcad ickby_ (~stefan@x5d844216.dyn.telefonica.de)
21:04.27 Notify 03BRL-CAD:brlcad * 67900 brlcad/trunk/TODO: boolweave unit tests....
21:34.28 Notify 03BRL-CAD Wiki:122.173.10.26 * 9710 /wiki/Google_Summer_of_Code/2016: /* LibreCAD V3 Bezier and FILE I/O */
21:45.00 Notify 03BRL-CAD Wiki:Tandoorichick * 9711 /wiki/User:Tandoorichick/GSoC2016/Logs: Created page with "The plan is to not make a mesh healing module just for BRL-CAD, but a portable module that can be used by both BRL-CAD and OpenSCAD. Blog will be up in a while."
23:39.00 *** join/#brlcad kintel (~kintel@unaffiliated/kintel)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.