| 00:48.18 | *** join/#bzflag TimRiker (~TimRiker@bzflag/projectlead/TimRiker) |
| 00:48.18 | *** mode/#bzflag [+o TimRiker] by ChanServ |
| 02:17.36 | *** join/#bzflag khonkhortisan (~Khonkhort@c-24-18-42-215.hsd1.wa.comcast.net) |
| 02:57.30 | *** join/#bzflag bzbugsy (bzbugsy@2600:3c02::f03c:91ff:fe6e:ddc7) |
| 02:57.30 | *** join/#bzflag bzbugsy (bzbugsy@unaffiliated/bzbugsy) |
| 03:09.52 | *** join/#bzflag SpazzyMcGee (~SpazzyMcG@host81-154-21-163.range81-154.btcentralplus.com) |
| 03:10.57 | *** join/#bzflag SpazzyMcGee (~SpazzyMcG@host81-154-21-163.range81-154.btcentralplus.com) |
| 18:21.34 | *** join/#bzflag infobot (ibot@rikers.org) |
| 18:21.34 | *** topic/#bzflag is http://BZFlag.org || https://www.ohloh.net/p/bzflag || http://wiki.BZFlag.org/Getting_Help || Channel Logs: http://ibot.rikers.org/%23bzflag/ || 2.4.2 Current version http://goo.gl/PI9KFD |
| 18:21.34 | *** mode/#bzflag [+v infobot] by ChanServ |
| 19:22.08 | *** join/#bzflag zuii (~akos@BC06BD4B.catv.pool.telekom.hu) |
| 19:25.14 | *** join/#bzflag Bhoren (~quassel@2a01:e35:2eb9:21:e0df:7568:9488:a471) |
| 19:52.00 | *** join/#bzflag contempt (contempt@unaffiliated/contempt) |
| 20:44.04 | *** join/#bzflag Patlabor221 (~JeffM@107-209-61-107.lightspeed.irvnca.sbcglobal.net) |
| 20:44.04 | *** join/#bzflag Patlabor221 (~JeffM@unaffiliated/jeffm2501) |
| 20:44.04 | *** mode/#bzflag [+v Patlabor221] by ChanServ |
| 21:18.25 | Notify | 03BZFlag:68.112.169.101 * 8842 /Installing_on_Linux: /* Installing from tarball */ |
| 21:19.51 | blast007 | wonders if someone doesn't know the definition of a "tarball" ;) |
| 21:20.03 | Patlabor221 | yeah I was just wondering why they'd not use the tarbal |
| 21:20.11 | Patlabor221 | the zip may have the wrong line endings |
| 21:20.18 | blast007 | that was my thought as well |
| 21:20.43 | blast007 | though the unzip program may take care of that.. but still.. the zip is usually the latest archive |
| 21:21.31 | Patlabor221 | it's tar -fvzx right? |
| 21:21.43 | Patlabor221 | or did I set off the bomb? |
| 21:21.48 | blast007 | I usually do the f last, but probably doesn't matter |
| 21:22.02 | blast007 | tar -xzvf bzflag-2.4.2.tar.gz (or similar) |
| 21:22.27 | Notify | 03BZFlag:JeffM2501 * 8843 /Installing_on_Linux: Don't use the zip file on linux, use the tarball |
| 21:22.47 | blast007 | I want the wiki to slowly go away and be replaced with proper documentation on the main site |
| 21:23.00 | Patlabor221 | and I want a million dollars :) |
| 21:23.15 | blast007 | ;) |
| 21:23.15 | Patlabor221 | what would you use to write the documentation in? |
| 21:23.28 | Patlabor221 | MS word files right? |
| 21:23.42 | blast007 | probably CommonMark (formalized Markdown) |
| 21:23.57 | Patlabor221 | and who can edit them and how would edits get published? |
| 21:24.00 | Patlabor221 | push it to a repo? |
| 21:24.06 | blast007 | pull requests |
| 21:24.17 | Patlabor221 | make it so! |
| 21:24.31 | blast007 | I was looking into options |
| 21:24.44 | Patlabor221 | github stores it's wiki as a repo |
| 21:24.48 | Patlabor221 | for each site |
| 21:28.13 | blast007 | At the moment, the two options I'm looking at would be to make the main site be static HTML files that are generated by some static site builder system (like https://sculpin.io/ ) or instead making it a full on Symfony 2 website |
| 21:30.01 | blast007 | I still want to factor in the services rework though.. |
| 21:32.05 | blast007 | is there some good set of formats/software for documenting a system design? somehow Google Docs and Visio just doesn't seem like the best option for documenting software and OS design in detail.. |
| 21:32.27 | blast007 | or at least not if you want more widespread collaboration |
| 21:37.20 | Patlabor221 | Visio is great at making diagrams, I haven't found anything else open source that is as easy |
| 21:37.33 | blast007 | Dia is similar |
| 21:37.40 | Patlabor221 | yeah but not as easy |
| 21:37.45 | Patlabor221 | it's close |
| 21:38.14 | blast007 | I don't own Visio though and I don't play to pay for that, nor do I expect others to ;) |
| 21:38.18 | blast007 | plan* |
| 21:38.21 | Patlabor221 | but comeon, its' all AGILE now, you don't document crap :) |
| 21:38.26 | blast007 | pfft |
| 21:38.47 | Patlabor221 | yeah for an open source project I don't know what you could use to make diagrams that are re-editable |
| 21:38.54 | therealtbe | http://globalnerdy.com/wordpress/wp-content/uploads/2007/11/dilbert-agile_programming.gif |
| 21:39.24 | Patlabor221 | sadly some people treat it like tht |
| 21:40.17 | Patlabor221 | it's mostly become popular as software transitions to web based service |
| 21:40.26 | Patlabor221 | since you don't have to "release" anything |
| 21:40.35 | Patlabor221 | you "deploy" |
| 21:41.22 | Patlabor221 | what editors nativly edit the markdown stuff? |
| 21:42.36 | therealtbe | that markdown stuff seems slightly less painful than latex -> pdf |
| 21:43.34 | therealtbe | but there is one program called Atom that is pretty good since it shows the source on left and preview html on right |
| 21:45.15 | blast007 | markdown is just test |
| 21:45.19 | blast007 | text |
| 21:45.21 | therealtbe | I don't know what the point is tho, because you could just as easily get an HTML editor with preview |
| 21:45.49 | blast007 | and part of the point of markdown/commonmark is that it's human readable even when it's not parsed and converted to another format |
| 21:45.55 | Patlabor221 | you don't want to make docs in HTML therealtbe |
| 21:46.09 | Patlabor221 | blast007, yeah but it'd be nice to see how it'd look in final form |
| 21:46.20 | Patlabor221 | since there is some rendering changes when shown on site. |
| 21:46.41 | Patlabor221 | so start with markdown for docs, and PNG for diagrams and go from there |
| 21:46.53 | Patlabor221 | I don't think people will diagram too much |
| 21:47.08 | Patlabor221 | and you can let people commit the sources for the diagrams if they are needed for later editing |
| 21:47.09 | blast007 | well, it was for the database designs, for instance |
| 21:47.21 | Patlabor221 | UML! |
| 21:48.24 | blast007 | Dia does let you make database diagrams complete with letting you put in column definitions (with data types and all) |
| 21:48.45 | Patlabor221 | then use that as the tool and check in the dia sources |
| 21:49.02 | Patlabor221 | and use a PNG or SVG in the docs |
| 21:49.14 | blast007 | k |
| 21:52.55 | *** join/#bzflag contempt (contempt@unaffiliated/contempt) |
| 21:56.10 | Patlabor221 | it's more important to make the documentaiton then it is to futz of the exact format/tools you use for the data |
| 21:56.19 | Patlabor221 | and if it's open source few can complain |
| 21:56.30 | Patlabor221 | if they do, they can remake it in the tool they want to make edits :) |
| 22:55.00 | *** join/#bzflag zuii (~akos@BC06BD4B.catv.pool.telekom.hu) |
