| 00:32.42 | *** join/#asterisk-dev leedm777 (~textual@2604:2d80:8404:828e:a9a0:d1f7:ea6e:d76b) |
| 00:32.42 | *** mode/#asterisk-dev [+o leedm777] by ChanServ |
| 01:01.07 | *** join/#asterisk-dev leedm777 (~textual@2604:2d80:8404:828e:b1fd:3fd0:8b7b:b0a3) |
| 01:01.07 | *** mode/#asterisk-dev [+o leedm777] by ChanServ |
| 01:36.59 | *** join/#asterisk-dev leedm777 (~textual@2604:2d80:8404:828e:edd3:ce4e:57ca:377d) |
| 01:36.59 | *** mode/#asterisk-dev [+o leedm777] by ChanServ |
| 01:53.04 | *** join/#asterisk-dev shuishui (~chirpin-2@114.221.20.224) |
| 02:23.01 | *** join/#asterisk-dev leedm777 (~textual@2604:2d80:8404:828e:cdc6:78b0:4150:66e0) |
| 02:23.01 | *** mode/#asterisk-dev [+o leedm777] by ChanServ |
| 02:25.47 | *** join/#asterisk-dev shuishui (~chirpin-2@114.221.20.224) |
| 02:36.39 | *** join/#asterisk-dev sh_smith (~sh_smith@cpe-76-174-26-91.socal.res.rr.com) |
| 02:54.37 | *** join/#asterisk-dev shuishui (~chirpin-2@114.221.20.224) |
| 03:00.12 | *** join/#asterisk-dev elguero (~miguel323@74-95-21-41-Connecticut.hfc.comcastbusiness.net) |
| 03:19.10 | *** join/#asterisk-dev infobot (~infobot@rikers.org) |
| 03:19.10 | *** topic/#asterisk-dev is Asterisk Development Discussion -=- http://www.asterisk.org/developers -=- Tier 2 and 3.14159265 support is in #asterisk -=- Check out our blog! blogs.asterisk.org -=- Follow on Twitter at @AsteriskDev |
| 05:55.35 | *** join/#asterisk-dev shuishui (~chirpin-2@114.221.20.224) |
| 06:12.57 | *** join/#asterisk-dev shuishui (~chirpin-2@114.221.20.224) |
| 07:15.03 | *** join/#asterisk-dev jkroon (~jkroon@uls-154-73-35-201.wall.uls.co.za) |
| 08:00.36 | *** join/#asterisk-dev CELYA_ (~Thunderbi@2a01:e0a:d:1111:1dd7:b42:3b85:c2f5) |
| 08:03.55 | *** join/#asterisk-dev tzafrir (~tzafrir@local.xorcom.com) |
| 08:03.55 | *** mode/#asterisk-dev [+o tzafrir] by ChanServ |
| 08:04.20 | *** join/#asterisk-dev tsearle (~tsearle@37.19.10.33) |
| 08:04.20 | *** mode/#asterisk-dev [+o tsearle] by ChanServ |
| 08:19.02 | *** join/#asterisk-dev pchero_work (~pchero@109.70.54.56) |
| 08:49.21 | *** join/#asterisk-dev hehol (~hehol@gatekeeper.loca.net) |
| 10:30.04 | *** join/#asterisk-dev tsearle_ (~tsearle@37.19.10.33) |
| 10:30.05 | *** mode/#asterisk-dev [+o tsearle_] by ChanServ |
| 10:41.35 | *** join/#asterisk-dev tsearle__ (~tsearle@37.19.10.33) |
| 10:41.36 | *** mode/#asterisk-dev [+o tsearle__] by ChanServ |
| 11:05.31 | *** join/#asterisk-dev shuishui (~chirpin-2@114.221.20.224) |
| 12:07.42 | tsearle | is there a way to increase the debug level via logger.conf? I want to get debug messages from modules loading (when started by systemd) |
| 13:00.59 | *** join/#asterisk-dev hehol (~hehol@gatekeeper.loca.net) |
| 13:04.54 | *** join/#asterisk-dev leedm777 (~textual@2604:2d80:8404:828e:3994:773c:393c:7988) |
| 13:04.54 | *** mode/#asterisk-dev [+o leedm777] by ChanServ |
| 14:03.33 | *** join/#asterisk-dev leedm777 (textual@nat/digium/x-fsfguijmkukvyjct) |
| 14:03.33 | *** mode/#asterisk-dev [+o leedm777] by ChanServ |
| 14:21.50 | *** join/#asterisk-dev snuff-work (~snuff-wor@210.9.148.102) |
| 14:21.50 | *** mode/#asterisk-dev [+o snuff-work] by ChanServ |
| 14:38.47 | *** join/#asterisk-dev cresl1n (Adium@asterisk/libpri-and-libss7-expert/Cresl1n) |
| 14:38.47 | *** mode/#asterisk-dev [+o cresl1n] by ChanServ |
| 15:01.38 | *** join/#asterisk-dev kharwell (kharwell@nat/digium/x-nshbhbzqyddgfezb) |
| 15:01.38 | *** mode/#asterisk-dev [+o kharwell] by ChanServ |
| 15:35.58 | *** join/#asterisk-dev bford (d8cff501@gateway/web/freenode/ip.216.207.245.1) |
| 15:35.58 | *** mode/#asterisk-dev [+o bford] by ChanServ |
| 16:21.32 | *** join/#asterisk-dev coreyfarrell (~coreyfarr@24-177-86-98.dhcp.nwtn.ct.charter.com) |
| 16:21.32 | *** mode/#asterisk-dev [+o coreyfarrell] by ChanServ |
| 16:51.45 | *** join/#asterisk-dev snuff-work (~snuff-wor@210.9.148.102) |
| 16:51.45 | *** mode/#asterisk-dev [+o snuff-work] by ChanServ |
| 16:54.08 | coreyfarrell | file: just saw your corrected 'function' spelling on the +1 review.. do you want me to fix the commit msg or no? |
| 16:54.21 | file | I'm not that bothered, others might be |
| 16:57.23 | coreyfarrell | hmm gerrit let me fix the commit msgs from the web and didn't force me to rebase the whole series. |
| 16:59.31 | coreyfarrell | when I made the readme changes I decided to experiment with reformatting as mardkdown. see https://github.com/coreyfarrell/asterisk/tree/readme-md-testing#readme compared to https://github.com/asterisk/asterisk#readme |
| 17:02.32 | coreyfarrell | I know few are here so I'll probably have to ask again next week, any opinion on including README.md? the file is changed less than once a year so having it duplicate would not be a real burden. cresl1n? |
| 17:04.28 | cresl1n | What's the question exactly? |
| 17:05.01 | cresl1n | Should we add a README.md? |
| 17:05.21 | coreyfarrell | that's the question.. |
| 17:05.32 | cresl1n | I don't have a big problem with having a README.md in there |
| 17:06.50 | cresl1n | What does everybody else think? |
| 17:07.07 | coreyfarrell | unsure, this is the first I've brought it up :) |
| 17:08.33 | file | I don't have an opinion either way. :P |
| 17:11.33 | coreyfarrell | cresl1n: speaking of README, any ideas what to do with https://issues.asterisk.org/jira/browse/ASTERISK-27430 ? |
| 17:12.19 | coreyfarrell | the README refers to very important security documents that don't exist :( |
| 17:13.06 | kharwell | coreyfarrell: how readable is the README.md in text only view? I'd be for just converting it over (not having two files) if still easily readable |
| 17:13.38 | kharwell | nvm just clicked the raw file. Looks decent enough to me |
| 17:13.45 | coreyfarrell | :) was just going to give you a link |
| 17:14.41 | coreyfarrell | kharwell: speaking of which I also experimented with an awk script that converted CHANGES -> CHANGES.md. |
| 17:17.00 | coreyfarrell | kharwell: the raw/plain text MD is still readable, but the awk script going in the other direction would be more "perfect". For example when converting from txt to MD some of the headerings are the wrong level (from older versions of asterisk). |
| 17:17.02 | kharwell | Just my opinion, but I'd be good with converting them and just having the *.md files |
| 17:17.51 | gtjoseph | while you're at it, anything you could do to make cherry-picking easier on that file would also be cool. |
| 17:18.03 | *** join/#asterisk-dev leedm777 (textual@nat/digium/x-mlsrgyprncxbbcqo) |
| 17:18.03 | *** mode/#asterisk-dev [+o leedm777] by ChanServ |
| 17:18.12 | file | oh god |
| 17:18.17 | file | goes to see if something exists |
| 17:19.33 | coreyfarrell | gtjoseph: what do you mean for the CHANGES file? the '.md' file has the exact same line-feeds as the plain text so switching would have no effect on cherry-picks (assuming we either convert or don't on all branches) |
| 17:20.25 | gtjoseph | i'm just thinking of the section headers always seeming to be inside the 3 line context area and preventing merges |
| 17:21.05 | gtjoseph | at least that's always what I seem to hity |
| 17:23.08 | gtjoseph | anyway, i'm on vacation so don't listen to me. :) |
| 17:24.11 | coreyfarrell | gtjoseph: in the CHANGES.md I added extra line-feeds after the heading 'Functionality changes from Asterisk 15.1.0 to Asterisk 15.2.0'. github seemed to ignore the extra line-feeds. |
| 17:25.05 | coreyfarrell | https://github.com/coreyfarrell/asterisk/blob/readme-md-testing/CHANGES.md vs https://raw.githubusercontent.com/coreyfarrell/asterisk/readme-md-testing/CHANGES.md. so in theory using MD would allow us to put more space before/after headings, potentially make it easier to deal with merges? |
| 17:25.12 | gtjoseph | no biggie. i was just making extra work. :) |
| 17:25.20 | *** join/#asterisk-dev snuff-work (~snuff-wor@210.9.148.102) |
| 17:25.20 | *** mode/#asterisk-dev [+o snuff-work] by ChanServ |
| 17:27.33 | coreyfarrell | gtjoseph: it'd be an easy change, CHANGES.md is generated by an awk script which already adds the '---' (<hr>) before each version header. it could easily inject extra line-feeds (though I think how the RAW md looks should be considered). |
| 17:28.05 | gtjoseph | OK, cool then! |
| 17:28.10 | coreyfarrell | in some cases I think extra line-feeds would make the raw markdown easier to read. |
| 17:30.48 | coreyfarrell | oh does anyone have an Asterisk logo that we can add to the repo to use at the very top of the README.md? |
| 17:36.41 | *** join/#asterisk-dev snuff-work (~snuff-wor@210.9.148.102) |
| 17:36.42 | *** mode/#asterisk-dev [+o snuff-work] by ChanServ |
| 17:47.27 | *** join/#asterisk-dev snuff-work (~snuff-wor@210.9.148.102) |
| 17:47.27 | *** mode/#asterisk-dev [+o snuff-work] by ChanServ |
| 18:00.10 | *** join/#asterisk-dev CELYA_ (~Thunderbi@2a01cb0583d31d00f1751575d81cec9c.ipv6.abo.wanadoo.fr) |
| 18:03.58 | *** join/#asterisk-dev snuff-work (~snuff-wor@210.9.148.102) |
| 18:03.58 | *** mode/#asterisk-dev [+o snuff-work] by ChanServ |
| 18:07.55 | *** join/#asterisk-dev jkroon (~jkroon@165.16.204.166) |
| 18:50.19 | *** join/#asterisk-dev snuff-work (~snuff-wor@210.9.148.102) |
| 18:50.19 | *** mode/#asterisk-dev [+o snuff-work] by ChanServ |
| 19:07.50 | *** join/#asterisk-dev oej (~oej@h-205-12.A165.corp.bahnhof.se) |
| 19:07.50 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 19:46.26 | *** join/#asterisk-dev tzafrir (~tzafrir@62-90-199-170.barak.net.il) |
| 19:46.27 | *** mode/#asterisk-dev [+o tzafrir] by ChanServ |
| 20:48.43 | coreyfarrell | it's too bad gerrit didn't have a display of queued/active jobs from jenkins |
| 20:49.05 | coreyfarrell | and sorry for jamming things up |
| 20:51.19 | file | coreyfarrell: it's on Jenkins |
| 20:51.44 | file | there's 58 things in the queue, and then the running jobs |
| 21:03.18 | tm1000 | confirming that the BUNDLE is not part of Asterisk 14 or 13? http://blogs.asterisk.org/2017/09/06/upcoming-webrtc-improvements-asterisk-15/ |
| 21:03.47 | file | it's not |
| 21:05.48 | tm1000 | booooooooooooo |
| 21:39.44 | *** join/#asterisk-dev snuff-work (~snuff-wor@210.9.148.102) |
| 21:39.44 | *** mode/#asterisk-dev [+o snuff-work] by ChanServ |
| 22:04.30 | cresl1n | tm1000: Do I hear a 15 in your future? |
| 22:04.39 | tm1000 | lol |
| 22:04.43 | tm1000 | we are already using 15 |
| 22:04.48 | cresl1n | YES! |
| 22:04.55 | tm1000 | its just a hard sell for clients |
| 22:05.10 | coreyfarrell | kharwell: FYI the console-completion series is going to be rebased onto master once ast_completion_vector gets merged. |
| 22:05.15 | cresl1n | New features, functionality |
| 22:05.24 | tm1000 | and for some reason react-native-webrtc has a lock on the bundle policy |
| 22:05.26 | cresl1n | hopefully the features are compelling enough |
| 22:05.28 | tm1000 | so we have to have it |
| 22:05.33 | cresl1n | ah |
| 22:07.54 | kharwell | coreyfarrell: ack. were you planning on cherry-picking at that time as well? |
| 22:08.59 | coreyfarrell | possibly. how much of it have you reviewed? I was going to do some reworking on the cli_completion patch unless you've already reviewed it. |
| 22:09.01 | tm1000 | cresl1n: is the general mindset at Digium Asterisk 13 and 14 are old and busted and 15 is the new hotness? |
| 22:09.12 | tm1000 | (not a critique!) |
| 22:10.06 | coreyfarrell | kharwell: or I could leave it as is and just do additional commit if you've already reviewed cli_completion. up to you. |
| 22:10.12 | kharwell | coreyfarrell: I was just starting to look when I saw your message. So since it sounds like you want to fix it up some more and rebase I'll hold off for now |
| 22:10.14 | tm1000 | I mean in regards to bundle I was shocked to see that only in 15, the video mixing makes sense to only be in 15. |
| 22:10.40 | file | bundle was needed for multiple streams, and is tightly coupled to the redone stream support in PJSIP |
| 22:10.48 | kharwell | coreyfarrell: nah it's fine. Go ahead and add them to cli_completion |
| 22:11.10 | tm1000 | file: gotcha |
| 22:13.51 | *** join/#asterisk-dev leedm777 (~textual@2604:2d80:8404:828e:6d61:e3b1:1eb7:e508) |
| 22:13.51 | *** mode/#asterisk-dev [+o leedm777] by ChanServ |