From david.burleigh at gmx.com Wed May 4 13:31:06 2016 From: david.burleigh at gmx.com (David Burleigh) Date: Wed, 4 May 2016 09:31:06 -0400 Subject: [General] qtox for Ubuntu Message-ID: <20160504093106.39bded8b@DZ> I followed the instructions for adding the repository for Ubuntu, but still qtox is not installable via apt-get. So I downloaded the 64-bit package for Linux from github and made a launcher for it, and it runs fine, but I'd rather depend on the repository. What's happening with that? From email at oranges.net.nz Wed May 4 20:51:09 2016 From: email at oranges.net.nz (oranges) Date: Thu, 5 May 2016 08:51:09 +1200 Subject: [General] qtox for Ubuntu In-Reply-To: <20160504093106.39bded8b@DZ> References: <20160504093106.39bded8b@DZ> Message-ID: <572A60BD.8010207@oranges.net.nz> What version of ubuntu were you trying to install it for? From david.burleigh at gmx.com Wed May 4 20:56:30 2016 From: david.burleigh at gmx.com (David Burleigh) Date: Wed, 4 May 2016 16:56:30 -0400 Subject: [General] qtox for Ubuntu In-Reply-To: <572A60BD.8010207@oranges.net.nz> References: <20160504093106.39bded8b@DZ> <572A60BD.8010207@oranges.net.nz> Message-ID: <20160504165630.7ff018be@DZ> Ubuntu (Mate Edition) Version 16.04 (64-bit) On Thu, 5 May 2016 08:51:09 +1200 oranges wrote: > What version of ubuntu were you trying to install it for? > _______________________________________________ > General mailing list > General at lists.tox.chat > https://lists.tox.chat/listinfo/general From Chris.Clemson at btinternet.com Wed May 4 21:00:21 2016 From: Chris.Clemson at btinternet.com (Chris Clemson) Date: Wed, 4 May 2016 22:00:21 +0100 Subject: [General] qtox for Ubuntu In-Reply-To: <20160504093106.39bded8b@DZ> References: <20160504093106.39bded8b@DZ> Message-ID: <572A62E5.8060001@btinternet.com> Hi David, It's working fine on my 32bit 15.10 ubuntu installation. Do you have Synaptic package manager installed? That will show all correctly configured repositories under Settings->Repositories, and will also show errors if the repository doesn't work correctly. Chris > I followed the instructions for adding the repository for Ubuntu, but > still qtox is not installable via apt-get. So I downloaded the 64-bit > package for Linux from github and made a launcher for it, and it runs > fine, but I'd rather depend on the repository. What's happening with > that? > _______________________________________________ > General mailing list > General at lists.tox.chat > https://lists.tox.chat/listinfo/general From zetok at openmailbox.org Wed May 4 21:14:34 2016 From: zetok at openmailbox.org (Zetok Zalbavar) Date: Wed, 4 May 2016 22:14:34 +0100 Subject: [General] qTox development & organization Message-ID: <572A663A.5000504@openmailbox.org> Hi folks. As you might be aware if you're in #qtox channel on freenode, qTox is getting organized ? committee has been made. Committee members are active maintainers. There are 3 tasks that committee will handle: ###################################################################### 1. Propose voting during meetings on proposals that need decision and core team members disagree on. 2. Ensure that actions are taken if someone from the committee is MIA. 3. Ensure that qTox gets regular releases. ###################################################################### In case of task 2), action is to remove committee member if they're absent on every meetings for 2 months without any notice. ###################################################################### Meetings are to happen every Saturday at 18:00 UTC?00:00 in #qtox channel @ freenode. Cat pics included. Feel free to bring your own though :) Logs from meetings & likely short summaries will be sent to mailing list. Hopefully Tox will make a ML for qTox, but there are no high hopes for that. That basically sums up sort of "meeting" that happened 2016-05-04 on #qtox @ freenode. More organizational stuff in the future. And log of most important part of the meeting. ######################################################################## [17:31:37] So we're kinda back to the steering commitee thing then? I'll always be reachable by mail, but not always in 1day, so you'll need more people [17:32:08] org or not, if you want that, something needs to be set up [17:32:30] yes, and we shouldn't load everybody with 100% work, because that's how people burn out [17:32:53] tux3: use case: business evaluates qTox ? whether they'll use it depends on stable it is, how active development & community is, and how likely project is to still be worked on in 5 years [17:33:09] tux3: with you being always gone, you can throw that out of the window [17:33:16] Good job. [17:33:37] Tox is still officially alpha/beta, my official disclaimer is please don't use it if your life/business depends on it! [17:33:49] that needs to change too [17:33:56] true [17:34:09] I think we can consider 1.4.x beta [17:34:12] Well there's 400 issues just waiting for me to fix them :) [17:34:18] * Andrew7 (~ziltro at vems.default.ziltro.uk0.bigv.io) has joined [17:34:34] they are not waiting for you alone :) [17:34:42] sudden6: um, more likely 1.5, when initramfs' video PR gets merged [17:35:05] how about you guys build your world dominating empire after tox actually works... like with things that matter. multi-device and offline messaging. then you can argue allll day long while people can actually make use of the thing [17:35:14] tux3: so, what is your proposal to fix things? [17:35:38] zero-ghost, gimme an ETA for tox actually working that isn't "maybe someday" :) [17:35:39] zero-ghost: where is working implementation? [17:35:48] exactly... [17:35:50] Hi, can I be part of world domination? [17:36:02] zetok, let's start with the commitee thing since we were talking about that [17:36:08] Andrew7: our army is always recruiting :3 [17:36:16] Andrew7: join, you'll see the world ;) [17:36:32] Do I get guns and car stickers? [17:36:38] Andrew7: grab yourself a pitchfork and attack NSA [17:36:54] Andrew7, you get your name on a lot of really cool government lists :) [17:37:22] tux3: yep, starting with the commitee thing would probably good [17:37:31] tux3: multi-device and offline messages can be solved already by just building on whats out there instead of reinventing the wheel and putting people off for the next 2 years [17:37:51] Awh NSA means travelling to america though. [17:37:56] zero-ghost: I haven't seen anything that would confirm what you're saying [17:38:00] zeronet, ipfs, maidsafe... the only smart thing any of the tox clients can do is build onto them [17:38:06] openbazaar using ipfs for offline stores [17:38:12] it doesnt get any more obvious than that [17:38:56] Anyway, before taking over the world... I've had a problem with qTox which is otherwise brilliant... [17:39:00] you reinvent your own network taking another 2..3..4 years and tox is gone in a puff of smoke [17:39:03] i dont wanna see that [17:39:13] zero-ghost, that's a fine idea, but someone needs to actually do the work eventually. So far it's not hapenning, so instead of witing forever for this t be finished, we move forward [17:39:23] When I turn off or unplug my monitor, qTox crashes. Even at the select profile screen. [17:39:45] Andrew7: OS? [17:39:49] Andrew7, oh we had an issue like that with multi-monitors before I think [17:39:58] It may be a problem with Qt [17:40:06] it is [17:40:16] Ubuntu 16.04 (also happened on 14.04) [17:40:28] Now a backtrace with debug symbols would be neat [17:40:38] It's a DisplayPort monitor, so I assume qTox is seeing that there are 0 monitors attached and perhaps doing maths on 0? [17:40:40] Andrew7: https://github.com/tux3/qTox/issues/3065 [17:41:06] Ooh someone else noticed it! [17:41:12] Maybe I should add to that... [17:41:23] please post a backtrace [17:41:42] I havent' tried it with HDMI, but I know that with DisplayPort the computer/OS/whatever gets to know when the monitor is removed. [17:41:53] I tried compiling a debug version. i did not succeed. [17:42:07] So all I have at the moment it: Segmentation fault (core dumped) [17:42:21] Welp: https://bugreports.qt.io/browse/QTBUG-42985 https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1450137 https://bugs.kde.org/show_bug.cgi?id=340267 [17:42:27] It's a known upstream bug apparently [17:42:38] personnaly, i see a project is very good when it split in different sub-project to keep the main KISS [17:42:55] where the qtox contrib on tox or qt ? :) [17:43:03] part of my metrics. [17:43:13] interestingly I don't have this problem [17:43:33] I plug unplug screens nearly daily, qTox did never crash [17:43:51] sudden6: Do you have DisplayPort? I've found that turning off the monitor on its power button doesn't cause the problem, but turning off at the mains or unplugging the cable causes it. [17:43:59] as an example, blender never share outside his tree the great gl interface code they made, nether the renderer or the game engine. [17:44:38] and qtox is rewriting a markdown thing etc... [17:44:38] This bug seems to be fixed in the next version of Qt, we'll try to update when possible. [17:44:48] Ok, that's good! [17:45:05] Andrew7: I use VGA atm, but I don't remeber it happening on DisplayPort either [17:45:27] maybe openSUSE did some patching to qt? [17:45:52] https://a.uguu.se/kswbpr.png [17:46:00] so, there's that. [17:46:15] which other symbol can be used? [17:46:28] | [17:46:32] uhm [17:47:04] HTML Tables? :D [17:48:10] Or yeah, | is good [17:49:51] tux3: I still haven't heard the answer for what you'd propose [17:50:08] We were discussing the comitee thing and we got sidetracked [17:50:20] so much for discussing it. [17:50:27] sudden6 you talked about people being reachable quickly? [17:50:36] yes [17:50:55] So should we have some sort of mailing list or bulleting board? [17:51:03] there is ML [17:51:13] and that doesn't fix the problem [17:51:16] I'd prefer someone on irc [17:51:23] it's irrelevant to the problem [17:51:33] fastest communication on earth [17:51:42] what ML btw? [17:51:46] except for tox ;) [17:51:49] mailing list [17:52:06] yeah where can I find that ML you talked about?^^ [17:52:13] README.md [17:52:15] on top [17:52:48] oh general tox ML [17:52:50] * zetok calls it the art of hiding in plain sight ^.^ [17:53:07] sudden6: there would have been a qTox one, if Tox didn't suck [17:53:16] :) [17:53:56] but yeah, Tox people had something against that idea [17:53:56] And so we would use that ML for what? [17:54:00] exactly [17:54:03] personally I don't like MLs, but I could be motivated to use one [17:54:05] "reasons" [17:54:36] Damn that explains everything, "reasons" :) [17:54:36] MLs are good for announcements [17:54:57] MLs are not very discoverables tho [17:55:11] Unless you're already invested in a project, it's not the first thing I check out [17:55:37] So I wouldn't bury public announcements in there. That's what a website is for! :) [17:55:39] ok, then MLs are out [17:55:53] good [17:56:24] tux3: so? [17:57:00] zetok, feel free to propose some ideas. Org or not if you want people to be reachable, we need something then [17:57:07] IRC is something I suppose [17:57:15] I propose IRC [17:57:16] ok, then MLs are out +1 [17:57:20] But we can't really force people to be on IRC 8 hours a day [17:57:32] why not use github issue ? [17:57:36] Timezones and all that [17:57:48] tux3: the only one who has to be online 24/7 is you [17:58:09] we can't provide coke :( [17:58:14] Awesome, I just need to find 24 extra hours to free in my schedule :/ [17:58:28] tux3: ok, then org it is :) [17:59:13] Org won't magically make people available. [17:59:28] no, it will show that there are other people than you who can be contacted [17:59:36] But there aren't, apparently! [17:59:43] yes, since there's no org [17:59:59] And the org will not fix that if there's nothing behind it [18:00:07] well zetok and me have pretty high uptime ;) [18:00:08] That's why we're trying to organise something here [18:00:12] True [18:00:27] >tux3> And the org will not fix that if there's nothing behind it [18:00:33] actually, it will fix it [18:00:54] What we could do is schedule regular meetups to discuss things. I'm not available 24/7 but I can be there for that [18:01:06] ok [18:01:13] If you want to discuss things or make a commitee thing, that could be a solution [18:01:26] regular meetings +1 [18:01:45] then send out log of the chat per mail? [18:01:52] Why not [18:02:14] doesn't sound bad [18:02:46] Impyy, nurupo: can Tox provide ML(s) for qTox? [18:03:11] one will probably be sufficient [18:03:47] (for now) [18:03:57] ok [18:04:28] how often should the meetups occur? [18:04:38] time? [18:04:47] 2 people with write access are in america, others are in europe [18:05:02] TheSpirit & dubslow, both ~inactive [18:05:19] although TheSpirid said that he possibly could help in a few months [18:05:25] TheSpirit* [18:06:18] 6 pm sounds fine? [18:06:22] Every week or every other week sounds fair [18:06:24] (UTC) [18:06:25] 6pm GMT? [18:06:36] Depends on what day [18:06:46] weekend ? [18:07:02] friday or saturday could work for me [18:07:11] weekend 6pm is ok for me [18:07:18] I'd propose Saturday, since then we'd get also cat pics [18:07:25] heh, lgtm [18:07:33] good [18:07:49] every week or every second week? [18:08:13] * abbat has quit (Remote host closed the connection) [18:08:14] every week? [18:08:29] Might as well start every week, and if we have nothing to say we'll scale back [18:08:33] + limit on length of meeting for max 2h, preferably 1 [18:08:42] yeah [18:08:43] +1 [18:09:12] and soon on new groupchat ;) [18:09:15] put this in README.md? [18:09:41] * genesis loves running jokes , sorry [18:10:11] sudden6: wouldn't MAINTAINING.md be better? [18:10:47] zetok: README.md would make it more visible to possible new devs [18:11:11] * zetok wonders about that [18:11:31] wouldn't someone really interested in qTox read MAINTAINING.md "just in case" ? [18:11:39] at least I would probably be motivated by a regular meeting where I could get the newest news [18:11:50] also, if someone would be interested in contributing, they probably should read CONTRIBUTING.md [18:11:56] err [18:12:06] * sudden6 is a news junky [18:12:23] * tux3 can relate [18:12:27] * zetok too [18:13:02] I conclude people interested in qTox are news junkies too^^ [18:13:16] it's in the name [18:13:18] but what I was thinking, is making meetings to be primarily about managing qTox & stuff, and when there's time/interest left, other stuff too [18:13:45] but we're cute. [18:13:52] :) [18:14:06] true, people derailing organisational discussions could be a problem [18:14:06] tux3: ? told you that it's the right name ;D [18:14:22] lol [18:14:40] I still have a file with horrible name ideas in it :) [18:14:50] :D [18:15:07] * zetok doesn't remember other names, even the old one by now [18:15:51] tux3: When qTox turns 10 years old you have to release this list ;) [18:16:25] Hehe some are still on the repo from where it was a tiny thing! [18:16:30] https://github.com/tux3/qTox/blob/84d6c1063e88cd33e8d5978d2dfb91fc278d4de5/main.cpp [18:17:18] urgh [18:17:19] lol [18:17:30] One day I'll rewrite git history just to make this disappear :) [18:17:35] now Ricin actually exists as a tox client xD [18:17:50] Cyanide too [18:18:07] (or is it ded by now?) [18:18:13] tux3: you predicted the future :D [18:18:22] err [18:18:38] Well most of those were not mine :) [18:18:41] also you got qTox repo on a lot of lists^^ [18:18:44] IIRC it was SkyzohKey who proposed Ricin [18:19:24] oooh, I thought he only recently discovered Tox [18:19:34] nope [18:19:44] nicks change, people not so much [18:20:03] * sudden6 is going to stalk everybody on gh from now on [18:20:34] i've to fix my contrib and add toxsuite one day ^^ [18:21:00] uhm, the discussion derailed again, put meeting times in README.md now? [18:21:02] but the community takes people so much for dumbass when they don't speak well english [18:21:58] sudden6: I'm not really happy with putting that in README.md [18:22:21] ok, why? [18:22:29] Either sounds fine to me. But README is already so full of crap no one reads it beyond the pretty picture and download link anyways... [18:22:48] I mean I hadn't even seen the mailing list until now :) [18:23:20] yeah [18:23:21] i.e. meetings are supposed to get job done, and putting that in README.md would point everyone (including trolls) to precise point in time-space continuum where they can disturb things the most [18:23:24] That said, either is fine. [18:24:00] zetok, I know Tox has a long tradition of hating transparancy and running everything in sikrit hidden channels, but I don't think it would be a problem [18:24:18] If people want to chip in, that's fine. If there are trolls, they'll get banned [18:24:37] tux3: thing is, I don't want to make situation that requires banning [18:24:59] if massive trolling action would happen, we could mute the channel temporarily [18:25:08] or something like that [18:25:29] moving it slightly out of sight of by-passing trolls (by having it in MAINTAINING.md) IMO would help with that, while still providing info for people that would be actually interested [18:25:43] sudden6: yeah, but that would be bad [18:25:54] Hm. You're assuming bad faith by default :/ [18:26:02] yes, but I don't expect massive trolling [18:26:09] Hiding things because some people may be troll is not great [18:26:12] um, I just assume that people will be people [18:26:16] Meh [18:26:23] it's not hidden [18:26:30] it's in the place it's supposed to be located [18:26:48] meeting of maintainers ? MAINTAINING.md [18:27:00] sudden6 : you can mute an user too [18:27:04] Either way is fine by me, but I don't think trolling will be an issue [18:27:26] genesis: yes, but you'll have a hard time if it's more than a few [18:28:05] what if we test if trolling is an issue on the first few meetings? [18:28:12] Sure, let's do that [18:28:57] * zetok disagrees [18:30:19] Ugh, so let's go with MAINTAINING.md then I suppose [18:30:34] ... [18:30:37] um, I just wanted to note that and move on [18:30:47] so, lets move on [18:30:48] --------------- [18:30:55] Well make up your mind >< [18:31:10] I disagreed. [18:31:27] since you two want it in readme, it will be in readme [18:31:34] next point [18:31:35] ok [18:31:45] i think organisation need a votation tool, does github provide such as you know ? [18:31:55] genesis: no [18:32:14] Github has the +1/-1 thingy on posts, but if we're a handful we can just reach consensus [18:32:22] thanks, always a missing thing, german hacker try to do some stuff about that, but it's a mess. [18:32:45] (liquid democraty) [18:32:48] vote by discussion is probably the best way [18:32:51] tux3: +/- is not really functional, since you can't remove it [18:32:59] also, I too prefer vote by discussion [18:33:03] I agree [18:33:08] ( http://www.public-software-group.org/liquid_feedback ) [18:33:25] those new github emotioncons are of limited use for these sort of things [18:33:32] (IMHO) [18:33:49] Point: committee [18:33:50] AIUI it was just a solution to the +1/-1 issue spam [18:34:03] So what is that comitee going to do exactly? [18:34:09] sudden6: ? ? [18:34:13] they should have used the reddit style [18:34:53] 1. collect proposals from new/outside devs [18:35:28] 2. ensure actions are taken if someone from the comitee is MIA [18:35:55] Doesn't 1) intersects with github issue proposals in a way? Or different kind of proposals? [18:36:01] 2 souds good to me [18:36:07] tux3: ~different ones [18:36:10] 3. Ensure that qTox gets regular releases [18:36:26] About 3), there's the problem of signing keys. [18:37:20] Currently any collaborators can make a new release by just pushing to the stable branch with a tag, but I have the signing keys [18:37:26] Do we want to do something about that? [18:37:44] yes, but about that later [18:38:15] 2) means bigger changes, like change of comitee, or final decissions big ui changes [18:38:23] 1. perhaps s/devs// ? [18:39:02] oh sorry, I meant 1) with the above [18:39:34] For big UI changes I like to get as many people's opinions on GitHub as possible so far [18:40:00] yes, but someone has to make the final decission [18:40:14] I'm happy to let other people decide on this (because I have no tastes =] ), but I think it's important to have open discussion before taking a decision [18:40:32] I don't want the get as much feedback as possible thing to change either :) [18:40:46] Awesome :) [18:40:47] I have no taste either... [18:41:18] :D [18:41:21] * zetok has one [18:41:31] but then again, it does include green Hacker font [18:41:34] so, there's that. [18:41:37] So I don't know if our meetings will be as visible as github issues, that's why UI discussions on GitHub sound better to me [18:41:50] yeah [18:41:55] Plus people can post mockups and have a friendly, permanent interface there. [18:42:34] sudden6, by changes of committee you mean like adding/removing collaborators? [18:42:44] to point 1) also more code level decissions like dependency changes, or which style to use with signal and slot macros [18:42:50] Right [18:43:47] >1. collect proposals from new/outside devs [18:44:25] so, rather than than, I'd propose `1. propose voting during meetings on particular proposals that need decision` [18:44:37] or maybe not [18:45:08] perhaps vote only if there's bigger disagreement between people [18:45:18] Yea, that sounds better [18:45:20] tux3: I think for adding removing collaborators there should be special rules [18:45:26] sec, lemme see how Rust does it, they have something good for that in place [18:45:37] zetok: yes, I think thats better [18:45:42] zetok is secretely trying to turn tox into rust :) [18:45:53] Can't blame you [18:45:56] he alreadid did :P [18:46:08] yeah^^ [18:46:30] he prefers awful syntax as qt magnificience. [18:46:35] * Chiitoo wants github emoticons to burn in hellfire. Or heavenfire, depending. [18:47:26] sudden6, what kind of rules? [18:48:52] something like a majority of the comitee has to agree on that [18:49:43] https://www.rust-lang.org/community.html#the-rust-team ? I haven't been able to find a good explanation, but basically if there's disagreement between people in team, team gathers to vote in a meeting about the issue [18:50:38] so, something like that [18:50:51] sounds good [18:51:09] we also should define MIA [18:51:27] I propose to be the living definition of MIA :) [18:51:39] * tux3 has quit (Quit: Leaving) [18:51:58] * tux3 (~tux3 at unaffiliated/tux3) has joined [18:51:58] * ChanServ gives channel operator status to tux3 [18:52:10] lol [18:52:18] good example^^ [18:52:19] Just kidding. [18:52:45] We're going to end up with a full blown constitution and social contract like Debian! [18:53:03] They have a nice democrary if you want to draw inspiration from something [18:53:04] `1. propose voting during meetings on particular proposals that need decision and core team members disagree on` ? refined [18:53:05] I meant a case like "I'm gone for 2 months, don't kick me from the team" [18:53:28] sudden6: yeah that would be nice to have [18:53:37] I'm good at running a dictatorship...? [18:54:39] s/particular// ? [18:54:59] Bikeshedding [18:55:04] ok, anything wrong with refined `1)` ? [18:55:09] Sounds good to me [18:55:17] lgtm [18:55:53] So just to be clear, the members of the commitee are the collaborators, yes? [18:56:27] not quite [18:56:30] Well. [18:56:47] It's hard to justify having people in one group and not the other. [18:57:25] they're in `Committee` group in an org [18:58:18] tux3: thing is, "Collaborators" isn't flexible or extensible enough [18:58:45] i.e. when there are people working on website, they're collaborators.. [18:58:49] I think we should start with a commitee size of ~5 people, based how active everybody is there could be more [18:59:12] If you want 5 peoples, name names, because we have 6 collaborators [18:59:18] Plus yours truly [18:59:31] where can I find the list of collaborators?^^ [18:59:46] Well, the github API only I think... [18:59:50] you should just know it ^.^ [18:59:59] works for me? [19:00:00] something like /repos/tux3/qTox/collaborators iirc [19:00:18] For me, I see it in the settings [19:00:24] But I think it's public [19:00:26] https://github.com/tux3/qTox/pull/3113 ? handy list, without me [19:01:07] * zetok wonders if dubslow will be ever back :( [19:01:26] From what I understood, probably not :/ [19:01:35] oh :( [19:01:40] :( [19:01:51] Well I haven't talked to him in a long time actually, but yeah [19:01:56] that'd make 6 people on committee [19:02:18] * zetok wonders about TheSpirit [19:02:31] So at this point I think it would make sense to demote dubslow until he comes back.. [19:02:32] would make a good starting point, also we have to see if the others are actually interested [19:04:03] Do you want to send emails to tell people about the committee? [19:04:14] so the list would be tux3 zetok agilob antis81 TheSpiritXIII sudden6 [19:04:39] yes, also please let us exchange emails [19:05:42] Exchange mail addresses you mean? [19:06:10] yes, I only have yours and zetoks [19:09:16] So what about 2) ensure actions are taken if someone from the comitee is MIA ? [19:09:28] What kind of actions? [19:09:56] something like don't count him for the voter base [19:10:23] if MIA without notice probably remove from comitee after some time [19:10:38] Okay [19:10:50] ok [19:11:21] missing every meeting for 2/3 months without any notice? or too strict? [19:11:38] barrdetwix at gmail.com , zetok at openmailbox.org , info at agilob.net , sudden6 at gmx.at ? GPG suport works ; nilsfenner at web.de , thespiritxiii at gmail.com ? people to CC [19:11:50] (in case of $stuff) [19:13:25] missing every meeting for 2 months without notice seems ok for me [19:13:30] lgtm [19:16:29] ok, I think that we got the basics down, and 3 points are agreed on? [19:16:50] Sounds about right yes [19:16:50] yep :) [19:16:58] ok -- Kind regards, Zetok Zalbavar ---- My Tox ID: 29AE62F95C56063D833024B1CB5C2140DC4AEB94A80FF4596CACC460D7BAA062E0A92C3424A0 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From zetok at openmailbox.org Wed May 4 21:16:57 2016 From: zetok at openmailbox.org (Zetok Zalbavar) Date: Wed, 4 May 2016 22:16:57 +0100 Subject: [General] qtox for Ubuntu In-Reply-To: <20160504093106.39bded8b@DZ> References: <20160504093106.39bded8b@DZ> Message-ID: <572A66C9.3010505@openmailbox.org> On 04.05.2016 14:31, David Burleigh wrote: > I followed the instructions for adding the repository for Ubuntu, but > still qtox is not installable via apt-get. So I downloaded the 64-bit > package for Linux from github and made a launcher for it, and it runs > fine, but I'd rather depend on the repository. What's happening with > that? Just use the right repo: https://github.com/tux3/qTox/blob/master/INSTALL.md#community-builds It works. -- Kind regards, Zetok Zalbavar ---- My Tox ID: 29AE62F95C56063D833024B1CB5C2140DC4AEB94A80FF4596CACC460D7BAA062E0A92C3424A0 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From Chris.Clemson at btinternet.com Wed May 4 21:21:57 2016 From: Chris.Clemson at btinternet.com (Chris Clemson) Date: Wed, 4 May 2016 22:21:57 +0100 Subject: [General] qtox for Ubuntu In-Reply-To: <20160504171312.6c26a889@DZ> References: <20160504093106.39bded8b@DZ> <572A62A0.5060207@btinternet.com> <20160504171312.6c26a889@DZ> Message-ID: <572A67F5.9000608@btinternet.com> Hmm, If you look at https://pkg.tox.chat/debian/dists/nightly/xenial/binary-amd64/ The Packages file is 0 bytes, which is not a good sign. If you look at a similar directory for wiley: https://pkg.tox.chat/debian/dists/nightly/wily/binary-i386/ Packages is 11k, which makes more sense. I've looked in a few other release directories, and it seems that not all of the releases have valid Packages files :( Could this be the issue? > Hi Chris. Yes, I do have Synaptic installed, and under Repositories it > shows "https://pkg.tox.chat/debian nightly xenial" but doesn't find > qtox. > > On Wed, 4 May 2016 21:59:12 +0100 > Chris Clemson wrote: > >> Hi David, >> It's working fine on my 32bit 15.10 ubuntu installation. >> Do you have Synaptic package manager installed? >> That will show all correctly configured repositories under >> Settings->Repositories, and will also show errors if the repository >> doesn't work correctly. >> >> Chris >> >> [...] >> From david.burleigh at gmx.com Wed May 4 21:43:14 2016 From: david.burleigh at gmx.com (David Burleigh) Date: Wed, 4 May 2016 17:43:14 -0400 Subject: [General] qtox for Ubuntu In-Reply-To: <572A67F5.9000608@btinternet.com> References: <20160504093106.39bded8b@DZ> <572A62A0.5060207@btinternet.com> <20160504171312.6c26a889@DZ> <572A67F5.9000608@btinternet.com> Message-ID: <20160504174314.3fed0dc5@DZ> Bingo! I guess I'll just have to wait... On Wed, 4 May 2016 22:21:57 +0100 Chris Clemson wrote: > Hmm, > > If you look at > https://pkg.tox.chat/debian/dists/nightly/xenial/binary-amd64/ > > The Packages file is 0 bytes, which is not a good sign. > If you look at a similar directory for wiley: > https://pkg.tox.chat/debian/dists/nightly/wily/binary-i386/ > > Packages is 11k, which makes more sense. > I've looked in a few other release directories, and it seems that not > all of the releases have valid Packages files :( > Could this be the issue? > > > [...] > [...] > > _______________________________________________ > General mailing list > General at lists.tox.chat > https://lists.tox.chat/listinfo/general From david.burleigh at gmx.com Wed May 4 21:44:28 2016 From: david.burleigh at gmx.com (David Burleigh) Date: Wed, 4 May 2016 17:44:28 -0400 Subject: [General] qtox for Ubuntu In-Reply-To: <572A66C9.3010505@openmailbox.org> References: <20160504093106.39bded8b@DZ> <572A66C9.3010505@openmailbox.org> Message-ID: <20160504174428.23c958bf@DZ> I don't know what you mean. I don't see a repository there for Ubuntu/Debian. On Wed, 4 May 2016 22:16:57 +0100 Zetok Zalbavar wrote: > On 04.05.2016 14:31, David Burleigh wrote: > [...] > > Just use the right repo: > https://github.com/tux3/qTox/blob/master/INSTALL.md#community-builds > > It works. > From email at oranges.net.nz Wed May 4 21:51:43 2016 From: email at oranges.net.nz (oranges) Date: Thu, 5 May 2016 09:51:43 +1200 Subject: [General] qtox for Ubuntu In-Reply-To: <20160504165630.7ff018be@DZ> References: <20160504093106.39bded8b@DZ> <572A60BD.8010207@oranges.net.nz> <20160504165630.7ff018be@DZ> Message-ID: <572A6EEF.7080508@oranges.net.nz> There's no 16.04 package for any tox client yet, you should bump the issue on the qtox or utox trackers for them to do so. On 05/05/16 08:56, David Burleigh wrote: > Ubuntu (Mate Edition) Version 16.04 (64-bit) > > On Thu, 5 May 2016 08:51:09 +1200 > oranges wrote: > >> What version of ubuntu were you trying to install it for? >> _______________________________________________ >> General mailing list >> General at lists.tox.chat >> https://lists.tox.chat/listinfo/general > _______________________________________________ > General mailing list > General at lists.tox.chat > https://lists.tox.chat/listinfo/general > From email at oranges.net.nz Wed May 4 22:01:08 2016 From: email at oranges.net.nz (oranges) Date: Thu, 5 May 2016 10:01:08 +1200 Subject: [General] qtox for Ubuntu In-Reply-To: <572A67F5.9000608@btinternet.com> References: <20160504093106.39bded8b@DZ> <572A62A0.5060207@btinternet.com> <20160504171312.6c26a889@DZ> <572A67F5.9000608@btinternet.com> Message-ID: <572A7124.7020401@oranges.net.nz> The files are not valid in the sense that there are no packages for that particular stream, so they're zero bytes. it's the result of defining a lot of the release/os combos ahead of time even when there are no packages for them and how that interacts with the reprepro tool that generates the repo layout. From antonbatenev at yandex.ru Wed May 4 23:03:31 2016 From: antonbatenev at yandex.ru (Anton Batenev) Date: Thu, 5 May 2016 02:03:31 +0300 Subject: [General] qtox for Ubuntu In-Reply-To: <20160504174428.23c958bf@DZ> References: <20160504093106.39bded8b@DZ> <572A66C9.3010505@openmailbox.org> <20160504174428.23c958bf@DZ> Message-ID: <20160505020331.47494c12@rene.tower> On Wed, 4 May 2016 17:44:28 -0400 David Burleigh wrote: = Community builds = There are community builds for wide range of distrubutions: For xUbuntu 16.04 run the following: sudo sh -c "echo 'deb http://download.opensuse.org/repositories/home:/antonbatenev:/tox/xUbuntu_16.04/ /' >> /etc/apt/sources.list.d/qtox.list" sudo apt-get update sudo apt-get install qtox To add the key, run: wget http://download.opensuse.org/repositories/home:antonbatenev:tox/xUbuntu_16.04/Release.key sudo apt-key add - < Release.key > I don't know what you mean. I don't see a repository there for > Ubuntu/Debian. > > On Wed, 4 May 2016 22:16:57 +0100 > Zetok Zalbavar wrote: > > > On 04.05.2016 14:31, David Burleigh wrote: > > [...] > > > > Just use the right repo: > > https://github.com/tux3/qTox/blob/master/INSTALL.md#community-builds > > > > It works. -- Anton Batenev -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From zetok at openmailbox.org Sat May 7 20:59:35 2016 From: zetok at openmailbox.org (Zetok Zalbavar) Date: Sat, 7 May 2016 21:59:35 +0100 Subject: [General] qTox Meeting: The Second Message-ID: <572E5737.7010901@openmailbox.org> qTox meeting 2016-05-07, #qtox @ freenode Maintainers present: * TheSpiritXIII (a.k.a. DaSpirit) * tux3 (late to the party) * zetok Maintainers absent with notification of absence: * sudden6 (had to leave just before the party) Maintainers absent without notification of absence: * agilob (1st absence without notification) * antis81 (1st absence without notification) Short summary: ? there were cat pics to get the party started ? zetok got access to weblate, now translations from it will be properly managed (often updates to & from weblate, etc) ? translations from weblate were pulled in, and as much as possible was used (yes, qTox just got a few new languages) ? qTox repo now has guards on `master` & `stable` branches, which will prevent accidental force-pushes to them (just in case) ? OBS at some point will be used for Linux repositories packages for the distros that don't package qTox yet Don't miss the cat pics on the next meeting ;) Log from the meeting (log time UTC+1): ######################################################################## [19:24:37] * DaSpirit has quit (Read error: Connection reset by peer) [19:53:15] * tux3 (~tux3 at unaffiliated/tux3) has joined [19:53:15] * ChanServ gives channel operator status to tux3 [19:57:23] * DaSpirit (~DaSpirit at unaffiliated/daspirit) has joined [20:09:08] hm [20:09:14] tux3: o/ [20:09:30] hai [20:11:18] hi tux3, how have you been? [20:12:03] vindelschtuffen, good, thanks. And you? [20:13:30] [07:42:28] I think if you chose to go with OBS we should simply redirect people [20:13:30] [07:42:35] no reason to mirror infrastructure that is already there [20:13:30] [07:42:51] if I had a choice I would do that [20:13:30] [07:42:56] just let me know what you do choose [20:13:46] tux3: anyway; translations? [20:14:20] zetok, well you started something with weblate yesterday? [20:14:35] yes and no [20:15:56] tux3: is it possible to add me to weblate management? [20:16:39] tux3: also, I've ~wasted 3 days waiting for you; if I had the access translations would have been merged by now, and weblate would have been properly handled [20:16:46] access to qTox repo, that is [20:17:06] tux3: here you have a great example of why not having qTox under an org is shitty [20:18:09] zetok, so, how does one add someone to weblate management? [20:18:30] no idea ? if not doable, too bad [20:18:53] Hm, I found an ACL, try connecting to hosted.weblate.org w/ your github account [20:18:59] it's already there [20:19:16] https://hosted.weblate.org/user/zetok/ [20:19:35] Ok, you should be owner of all of "Tox" on weblate now [20:19:57] * Bill_MI has quit (Quit: Bye...) [20:20:09] ok, I see [20:20:52] ok [20:21:11] tux3: it's set to pull changes for gh repo on commit to repo, right? [20:21:57] zetok, I think so [20:22:03] .. [20:22:19] you know, all repo hooks are visible in settings [20:22:30] if there's no weblate one, then it's not set [20:22:39] Oh! Oh [20:22:41] * Bill_MI (~Bill at d14-69-45-181.try.wideopenwest.com) has joined [20:23:13] * zetok calls it "a waste of time" [20:24:14] tux3: in any case; I'm going to merge PR with changes from weblate that I could get ? after that weblate will need to be reset to match current master [20:24:24] Hrm, the weblate doc is confusin [20:24:37] They have a billion different hook endpoints [20:24:56] oh, tux3 is here [20:25:01] nurupo, hi [20:25:02] was just writing email to you [20:25:13] will copy-paste it in here instead then [20:25:29] ye of little faith [20:27:54] tux3: also, while you're at changing settings, change guards on qTox repo [20:27:57] zetok, okay I got the stars to align, the weblate hook should be setup correctly [20:28:00] Guards? [20:28:07] yep [20:28:14] Protected branches? [20:28:23] yep [20:29:17] Fair enough, for stable and master [20:29:29] + travis [20:29:44] >Hi there, So, zetok has asked us to make a mailing list dedicated solely to qTox at lists.tox.chat (https://lists.tox.chat). [20:29:44] >I have asked him about the scope of the ml, because it sounds like qTox ml would overlap with the Support ml and Development ml. As a user having issues with qTox and seeing Support and qTox mls, it would be very confusing which one to use, so the qTox ml should have some distinctive scope, such that it could be named qTox- ml. All I could get out of zetok was that the qTox ml should be for general discussion, which isn't very specific [20:29:44] (https://gist.github.com/nurupo/bf2cf7fe51885115b9b6b7d9a36478a7). I mean, it could work, we have to discuss it, but there is some obvious overlap with other mls. So, I was just wonderting if you happen to have any input on that. [20:29:47] zetok, But what if travis fails? [20:29:48] tux3: here ^ [20:30:41] nurupo: "a general ML for qTox that users of other clients may consider a spam" [20:30:48] tux3: that's your problem to watch out for [20:31:23] nurupo, As I understood it the qtox ML wasn't mainly for providing support, so users should still go to the Support ML. The qTox ML could be renamed qTox-dev to avoid confusion I suppose [20:31:27] tux3: generally, no commits should go on master if they at least don't build [20:31:58] zetok, yeah but I remember travis failing for stupid reasons several times and it would suck to freeze the repo because of that [20:31:59] tux3: and if there's a problem with travis itself, then it's up to repo maintainer to fix the settings/travis [20:32:16] zetok, I never signed up for maintaining travis :/ [20:32:43] tux3: no, but you could turn off the setting until travis gets fixed [20:32:55] https://github.com/zetok/tox ? I do that with it, it works [20:33:06] I had to turn travis check 0 times [20:33:13] same goes for the repo with Tox spec [20:33:24] Or, maintainers could just not merge PRs where travis fails. Unless it's a travis problem [20:33:28] requires travis, 0 times that it actually had to be turned off [20:33:45] tux3: yeah, and instead maintainers themselves push broken stuff [20:34:18] tux3: either case, it's just a check for something that should pass tests anyway [20:34:44] Yeah but we don't need a hard software block to follow a policy :/ [20:34:45] If maintainers can't be trusted to check that stuff even compiles, then travis won't save us [20:35:11] policy is a bullshit ? hard block does it right [20:35:24] You can't replace people with checkboxes [20:35:40] no, I can add checkboxes to help people not push broken stuff on master [20:36:10] Travis helps people not push broken stuff, if people ignore travis either 1) they have a good reason 2) they made a mistake and need talking to [20:36:50] checkbox is simpler & less time consuming than talking to ? it outright points out "you're doing it wrong!" [20:37:09] travis builds succeeded is a very poor metric though. ideally you should have a test suite written out, with many test cases, that automatically test if a PR broke anything. like toxme friend additon test, message sending test, file transfer test, etc. non-ideally it could be done manually, but it's a lot more time consuming and harder to verify that -- someone other than the person making PR would need to do that (a tester) as the PR person could just [20:37:09] be lazy and lie about it [20:38:09] * Bill_MI has quit (Quit: Bye...) [20:38:29] https://travis-ci.org/zetok/tox/jobs/128527981#L844 :) [20:39:00] those are unit tests [20:39:11] what i'm talking about are integration tests [20:39:20] and automated ui tests [20:39:29] those are harder to make [20:39:52] tux3: btw, you didn't reply to the OBS email [20:40:00] hum [20:40:08] nurupo, sorry, I've been a bit overwhelmed with mails lately.. [20:40:27] nurupo: actually, I think that I have at least 1 integration test [20:40:54] and for UI code I have tests too [20:41:04] tux3: didn't know anyone else other than me and GitHub writes to you :) [20:41:09] (UI ? string formatting) [20:41:16] nurupo, I wish :) [20:41:17] tux3, I'm well, thank you [20:41:20] zetok: UI -- visual [20:41:38] text is visual [20:41:45] and it's certainly an interface [20:41:49] nurupo, we're trying to officialize the OBS community builds, because our current packages have problems [20:41:58] tux3: also, we are getting A LOT of complains about qTox not being in Ubuntu 16.04 package repository [20:42:17] nurupo, .. the official Ubuntu repos or the tox.chat repos? [20:42:32] tox.chat [20:42:40] obviously [20:42:52] Obviously, but I though we did support Xenial, lemme check [20:43:01] tux3: some people are complaining every other day, asking why qTox developers don't provide packages and if it cares about the users (or it's just dying out) [20:43:15] hm [20:43:20] nurupo, hence why we're happy to move to the OBS builds [20:43:22] the pkg repo has 0 packages [20:43:42] Oh yeah, we stopped at wily [20:44:17] nurupo: then tell people that packages are provided, and it's just tox.chat providing broken stuff [20:44:29] problem fixed. [20:44:49] So. I don't know if it's worth it to create the whole bunch of xenial builds or just redirect people to OBS at this point.. [20:44:53] > nurupo, we're trying to officialize the OBS community builds, because our current packages have problems <-- i'm curious, what problems? [20:45:16] nurupo, they are pretty much unmaintened since I don't have time for them, and they don't work well for some people [20:45:22] nurupo: tux3 is the problem [20:45:24] As well as not existing at all for Ubuntu Xenial [20:45:29] > nurupo: then tell people that packages are provided, and it's just tox.chat providing broken stuff <-- ok, we will tell that qTox developers don't want to provide ubuntu 16.04 packages [20:45:39] nurupo, slow down. [20:45:46] zetok: problem solved :P [20:45:56] nurupo: as always, lies and deception, nothing less expected from Tox committee member [20:46:34] > nurupo, they are pretty much unmaintened since I don't have time for them, and they don't work well for some people <-- what doesn't work exactly though? i'm thinking of using pbuilder for my Qt projects, so it would be useful for me to know [20:47:08] nurupo, oh it's not pbuilder's fault, it's mostly bad/outdated build scripts/config [20:48:28] So about moving to OBS, I wanted to mirror OBS packages on pkg.tox.chat so we wouldn't have to mess with people's source.lists, but turns out that's a pain to do [20:48:32] > nurupo: as always, lies and deception, nothing less expected from Tox committee member <-- well, saying that "tox.chat" provides broken stuff sounds like that the Tox committee members provide broken stuff, when it's all managed and provided by qTox developers. there is no deception, i'm just avoiding the confusion, as people think that we are the ones managing qTox packages [20:49:11] So it kinda sounds more reasonnable to just send people over to OBS now [20:49:27] nurupo: again, lies and deception ? the only one managing the builds are you & tux3, no other qTox developer are involved [20:49:41] *ok, we will tell that qTox developers don't want to provide ubuntu 16.04 packages in tox.chat package repository [20:49:50] nurupo: if you want clarity, just say `tux3` [20:49:55] i think that might have fixed the issue you were having ^ [20:50:42] dunno about that [20:50:48] okay, i will say that only tux3 doesn't want to provide ubuntu 16.04 qtox packages [20:50:49] I wouldn't care if it worked [20:51:17] anyway, time for translations \o/ [20:51:42] > nurupo, oh it's not pbuilder's fault, it's mostly bad/outdated build scripts/config <-- oh, then it wouldn't affect me much [20:52:15] -qtox-git-spam/#qtox- [qTox] zetok closed pull request #3259: Translations from weblate (master...transl) https://git.io/vwxmb [20:52:35] tux3: what stops you from assigning maintainers of build scripts / configs to jenkins? or just having a build script in the git repo, that way there is no need to access jenkins at all [20:52:55] lol [20:52:57] nurupo, I don't know anyone who wants to maintain those packages [20:53:10] tux3: and how does OBS solves this? [20:53:33] Somebody maintains them, and they work for all relevant distros out of the box [20:53:49] oh, so a openSUSE maintainer does the job? [20:53:54] *an [20:54:04] that's pretty cool [20:54:11] I don't know if it's an OpenSuse maintener, but it's someone from the communit [20:54:25] *abbat* [20:54:30] the OBS community? [20:54:38] What zetok said. [20:54:57] nurupo: really, you should know the great people [20:55:03] oh, i see. the guy just doesn't like Jenkins and likes OBS more [20:55:09] ? [20:55:14] nurupo, to be fair OBS is pretty cool. [20:55:22] tux3: it is [20:55:29] tux3: they also support a lot of target distros [20:55:36] i was looking into it the other day [20:55:46] zetok, so weblate is spamming my mail with "qTox merge failures", are you on it or should I investigate? [20:55:52] zetok: nah, i know abbat [20:55:55] tux3: "on it" [20:56:00] Awesome [20:56:11] tux3: or rather, I'm waiting until it finishes with resetting to current master [20:56:34] * tux3 thinks .ts pull requests weren't that bad after all [20:56:48] tux3: then I'm going to unlock it, so that people could make some use of updated files & get better translations for qTox [20:56:50] zetok: if i'm not mistaking him with another buy whose nickname starts with "a", he is the guy wotking at Yandex internet company in Russia and posting about Tox on Russian IT blogs, maintaining community builds and a python tox bindings [20:56:58] tux3: no, they were *horrible* [20:56:58] great guy [20:57:20] zetok, well, let's have both [20:57:44] tux3: yes, I'm not saying that contributing translations via PR shouldn't happen [20:57:57] tux3: just saying that from translator PoV it's a horrible experience [20:58:36] Yeah I can see how sending PRs is pretty bad for someone who isn't a dev :) [20:59:02] But those fancy solutions are always a pain to set up.. [20:59:30] btw, I'm going to be squashing translation PRs, because of stuff like that: https://github.com/fr3ts0n/AndrOBD/commit/70f3e132ee2972dd7b7d59d65e40532489cdcf34 [20:59:38] s/PRs/commits/ [21:00:08] I want to blame Java on this one, but fair enough [21:00:26] actually, i think i was mistaking about him working in Yandex, that was soem other guy [21:08:32] tux3: is the travis guard set? [21:08:42] zetok, hell no :) [21:08:45] why? [21:09:23] I want people to think, not be limited by stupid software restrictions [21:09:38] that's not being limited [21:09:52] they're forced to think on how to make it work at least on travis [21:10:19] people are lazy, and without some stimuli they default to not thinking [21:10:43] Merging pull requests is not the time to be lazy [21:10:43] also, "thinking" in this case is a waste of time [21:11:25] if it builds on travis, then its at least worth time for review; doesn't build ? PR submitter knows what to do, or should ask for help [21:11:38] s/its/it's/ [21:12:03] We already have travis for that, no need to force it [21:12:06] If people are so lazy they can't check the BIG RED BOLD travis failure, then how do I know they won't merge bugs, blatant security vulnerabilies, or crap that doesn't even run? [21:12:09] > Merging pull requests is not the time to be lazy [21:12:44] This is the one time you need to be paying attention, when random people want to put their code in qTox. [21:12:54] also it's about "merging" own PRs, which people have to do, given that there's not enough active people with write access & time for review [21:13:19] tux3: so, is it right to say that you will remove all Linux builds of qTox from Jenkins once you have OBS figured out, keeping only Windows builds on it? [21:14:13] nurupo, probably! Or at least delete the release builds and keep some debug builds disabled. [21:14:19] tux3: and if you haven't noticed, people are lazy about reviewing the stuff they have written themselves, and this is not going to change, so at least there could be some protection [21:14:33] because "it should have worked" [21:15:10] zetok, if you're so lazy the code you wrote and are trying to merge doesn't even compile, AND you ignore travis and merge it anyways, then go on, merge it and see if I'm happy about it [21:15:26] ha. [21:15:35] you're too busy being away [21:15:52] I'll come back just to take care of you, don't you worry ;) [21:16:10] zetok: so, you are fine with tux3's decision of qTox-dev mailing list? [21:16:20] tux3: I won't, my commits are usually ~perfect ^^ [21:16:27] zetok, why, of course they are! [21:16:38] tux3: the use-case is other people [21:17:16] nurupo: dunno, I don't want to make this list feel exclusive to people [21:17:34] and naming it -dev would make it so [21:17:52] zetok, it's simple, if other people are really that stupid, then let them ignore Travis and we'll catch them. If they aren't, then there's no problem. The worst that can happen is we'll have to revert a commit. [21:18:04] tux3: reviewing commits is fun. my tox client got a 6k or so lines PR, with many many new files and entities. never go time to review the thing :\ [21:18:14] nurupo, I love when that happens.. [21:18:49] Almost as fun as having to rebase a pull request of 100 conflicting commits and you need to fix the same damn stupid conflicts every commit... [21:18:57] ? don't [21:19:08] that's why I've added `PR-rebase-required` ^^ [21:19:16] lol [21:19:21] make them suffer, you got other, working PRs to review/merge [21:19:50] True enough [21:20:25] zetok: well, then maybe you should talk about the mailing list among the qTox committee members and come to some conclusion, if there is uncertainty [21:20:37] tux3: ? ? [21:20:41] DaSpirit: ? ? [21:21:07] i will be bringing up the qTox ml during our meetings as qTox-dev, unless you want me to postpond brining it up until you got it sorted out [21:21:32] Imho call it qTox-dev and be done with it, it's not the one for user support, and if people just want to chat about their life, they can go on IRC [21:21:49] We'll be using this ML for qTox development/meetings so it fits [21:21:53] hm [21:21:58] ok [21:22:14] nurupo: yeah, that's fine with me [21:22:27] nurupo, can it be done? [21:29:25] * tux3 has quit (Quit: Leaving) -- Kind regards, Zetok Zalbavar ---- My Tox ID: 29AE62F95C56063D833024B1CB5C2140DC4AEB94A80FF4596CACC460D7BAA062E0A92C3424A0 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From zetok at openmailbox.org Sat May 14 20:29:44 2016 From: zetok at openmailbox.org (Zetok Zalbavar) Date: Sat, 14 May 2016 21:29:44 +0100 Subject: [General] qTox meeting #3 Message-ID: <57378AB8.2050708@openmailbox.org> qTox meeting 2016-05-14, #qtox @ freenode Maintainers present: * sudden6 * TheSpiritXIII (a.k.a. DaSpirit) * zetok Maintainers absent without notification of absence: * agilob (2nd absence without notification) * antis81 (2nd absence without notification) * tux3 (1st absence without notification Short summary: * CoC might be at some point added Not much, since tux3 was absent. In other news, there's a new mailing list `qTox-dev`. Every qTox maintainer should subscribe to it. Log from the meeting (log time UTC+1): ######################################################################## [18:53:34] hi, everybody [18:54:12] Hi sudden6 :) [18:57:35] * stvlker (~stvlker at unaffiliated/stvlker) has joined [19:01:07] :3 [19:01:20] https://i.imgur.com/1Dr0bAl.jpg :3 [19:01:24] https://i.imgur.com/nzu7jNj.jpg :3 [19:02:24] * zetok wonders whether tux3 will be late again [19:05:03] what do you think about getting some sort of Code of Conduct into place? [19:05:56] not much, I think people behaving like decent persons don't really need a code of conduct [19:06:05] https://github.com/tux3/qTox/issues/2218#issuecomment-219132319 [19:06:28] I think that installgen2 was trying to point out that CoC is missing [19:07:39] so I'm wondering whether something should be done about it [19:07:40] I think he was trying to troll [19:07:53] that too [19:07:55] typical installgen2 [19:10:00] a code of conduct won't stop trolls, it will only invite them to troll more IMHO [19:10:16] yes, a bad CoC will do that [19:10:36] e.g. like the one genesis proposed [19:11:33] link? [19:11:59] uh [19:12:08] * zetok goes to look through logs [19:12:18] s/look/grep/ [19:13:26] http://contributor-covenant.org/version/1/3/0/ [19:15:03] I think that there might exist an implementation of CoC that won't be bad, so if there's interest in it, I'd look into that [19:15:42] primary things to look into are Rust's and Gentoo's CoC [19:16:01] mhm, I don't think it's a bad idea to have one [19:16:28] but on the other side it makes me sad we need to have one :( [19:17:02] um [19:17:20] I don't think that we /need/ one /yet/ [19:17:55] it's just that when time will come, I'd like to be prepared [19:18:00] yes, but in the case we will need one, it's better to already have one [19:18:08] :) [19:18:29] else there'll be "you just invented that, because... " arguments [19:19:05] some much energy unneccessarily wasted because of trolls [19:20:20] about https://github.com/tux3/qTox/pull/3294 and 3293 why are they both open? [19:20:39] * zetok was just writing an answer to that [19:20:51] ^^ [19:21:18] CoCs are one of the most overrated things [19:22:53] sudden6: replied [19:23:59] I still don't understand it [19:25:15] 3294 does contain translation and code changes, which isn't like we normally do it [19:25:32] err [19:25:35] 3293 only code [19:25:46] which would be ok [19:25:47] no, 3294 contains *translation* [19:26:00] once 3293 gets merged, that is [19:26:16] "duplicated" commits will simply "disappear" [19:26:41] so after 3293 is merged you will rebase 3294 [19:26:45] ? [19:26:46] yep [19:26:59] + add a commit with update of all translations [19:27:35] this makes it really complicated [19:27:43] (at least for me) [19:28:18] why didn't you make the translation updates alone a separate PR? [19:28:30] they depend on the other PR [19:29:10] sudden6: um, don't worry about 3294 ? I'll take care of it myself once 3293 is merged [19:29:16] yes, but I think if a PR depends on another PR, it shouldn't contain the other PRs commits [19:29:27] eh [19:29:29] it doesn't [19:30:23] huh? gh shows 3 commits for 3294, the first 2 are already in 3293 [19:30:45] gh will show 1 commit in 3294 once 3293 gets merged [19:32:18] yes, once it's merged, but now it's showing all 3, which I think is confusing, since when I review it, I basically review the same changes twice [19:32:53] b-but you don't have to review it :( [19:32:58] only 3293 [19:33:22] unless you want to, then you don't have to review commits from 3293 anyway [19:33:38] my thought was, it changes code, I have to review it [19:33:48] >.< [19:33:59] * zetok wonders if [WIP] would have helped [19:34:17] I would prefer it if, translation PRs only contained commits changing ts files [19:34:42] I think this would make it much easier to review translation and code [19:34:52] :( [19:35:07] sorry, I just kinda don't get how it makes the review harder [19:35:32] i.e. code commits are the same [19:37:00] yes, but it's hard to notice that [19:37:48] * zetok notes to himself that not everyone checks commit hashes & messages [19:38:01] I interpret "depends on ..." like I have to merge that first, not that this PR also contains the mentioned changes [19:42:36] well, 3293 has to be merged before 3294 [19:44:21] uhm, I think it would be the same if I merged 3294? [19:44:26] nope [19:44:33] I mean [19:44:36] ugh [19:45:01] you could do that [19:45:14] but then I'll have to make yet another PR for updating translation files [19:45:35] ? and that's why I don't like this all :) [19:46:01] anyway, 3293 can be merged [19:46:05] ok [19:46:14] what about https://github.com/tux3/qTox/pull/3305 ? [19:46:27] uh wait, just spotted somethin [19:46:30] (also IIRC contains changes affecting translations) [19:46:33] My calls are dropping after about ~9 -> 15 minutes or so [19:46:44] Audio cuts out actually, not drop [19:46:57] it stays connected but there is no more sound on either side [19:47:08] mgoodwin: https://github.com/tux3/qTox/issues/2926 [19:47:18] Let's say it this way: qTox A/V should be rewritten from scratch [19:48:04] That's me, the last commenter [19:48:08] xenithorb [19:48:22] (5 hours ago) [19:48:53] I did a more recent test right now and no one was on the audio tab [19:51:01] sudden6: should I change that? [19:51:12] I also tested WAN/LAN so I don't think it's a internet issue at least (could be a local firewall issue but I doubt it) [19:51:15] I'm still researching [19:51:22] k [19:52:49] google says we should use nullptr since c++11 [19:54:51] * zetok goes to add commit [19:55:19] 3305 is fine [19:56:38] zetok: O' [19:56:49] I'd like to help with this sound cutout bug * [19:56:54] What can I do? [19:57:36] I think you would need some c++ skills for that [19:58:07] Are the specifics of the bug known then? No more logs necessary? [19:59:33] mgoodwin: probably not, but at this stage it's hard to tell what is needed :( [19:59:36] Side note, doesn't seem like the "reset to default settings button does anything" [20:01:34] mgoodwin: the way I would go for it, is to try reproduce the bug and use the debugger to find out if it's a qtox or toxcore problem [20:01:38] sudden6: um, note that I didn't test that last commit [20:02:57] zetok: this shouldn't change anything, nullptr is just a nice name for 0 most of the time [20:03:15] if it compiles it's fine [20:03:50] yep, compiles [20:04:03] then it's alright [20:04:22] real 0m14.768s [20:04:23] :D [20:04:29] #3215 what do you think about that? [20:04:48] 48 cores? xD [20:04:57] nah, just 8 [20:05:22] + CCACHE + cached files [20:05:42] I don't trust this caching stuff [20:05:54] tends to cause issues if I don't do a clean build... [20:06:01] dunno about that [20:06:07] never happened for me [20:06:27] and I've been using it to compile qTox for years by now [20:06:55] about the PR ? it has "changes-required" ? [20:07:10] yeah, I think of completely closing it [20:07:38] (in other words ? I usually don't test things that need changes, since I'd need to re-test them once they get changed) [20:07:45] I more meant the idea of it tough [20:07:59] idea doesn't sound bad [20:08:21] dunno about the implementation though [20:08:40] the implementation is only meh [20:08:58] would need a lot more work to do it properly [20:09:03] well, I'd leave it open ? perhaps they'd want to fix things :) [20:09:26] ok, do we have a limit for "stale" PRs yet? [20:09:52] no, and I wouldn't really want to have one [20:10:09] why? [20:10:23] unless it would be something like 1 year, or some other reasonably long time period [20:10:35] * Lord_Vlad has quit (Read error: Network is unreachable) [20:10:43] encouragement & visibility [20:11:20] * Lord_Vlad (~Vlad at 2a02:a03f:30ea:500:6e6a:e95d:3c36:62db) has joined [20:11:21] I don't know, if a PR doesn't recieve any attention during say 30 days it's probably pretty outdated already [20:11:45] PR submitter may feed discouraged when their PR will get closed for being "stale" ? perhaps they don't have time in their life to fix/improve things quickly, but they would find the time in a month or 2 [20:12:40] as for visibility ? open PRs that need changes are visible to people who would want to contribute, and if they want to help with some functionality that is implemented in PR but needs some fixes, they have a easy way to see those PRs [20:12:47] good point, tough most of the time PR submitters don't even care to mention they have no time [20:13:11] Main qTox developer doesn't care as well ;) [20:13:27] ovalseven8: b-but sudden6 cares? [20:13:27] well, he cares, but has no time [20:13:35] ? [20:13:38] ;D [20:14:03] ok, ok ;) [20:14:04] also zetok has 100+% uptime on IRC [20:14:28] sadly that's just my znc :f [20:15:09] speaking about time, I'll leave for today [20:15:16] bai [20:15:22] see you soon [20:15:28] sudden6: btw, merge if you can? [20:15:30] Good night [20:17:10] zetok: yes tomorrow [20:18:04] ok -- Kind regards, Zetok Zalbavar ---- My Tox ID: 29AE62F95C56063D833024B1CB5C2140DC4AEB94A80FF4596CACC460D7BAA062E0A92C3424A0 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From zetok at openmailbox.org Sun May 22 11:20:51 2016 From: zetok at openmailbox.org (Zetok Zalbavar) Date: Sun, 22 May 2016 12:20:51 +0100 Subject: [General] qTox meeting #4 Message-ID: <57419613.7090408@openmailbox.org> qTox meeting 2016-05-21, #qtox @ freenode Maintainers present: * TheSpiritXIII (a.k.a. DaSpirit) * tux3 * zetok Maintainers absent without notification of absence: * agilob (3rd absence without notification) * antis81 (3rd absence without notification) * sudden6 (1st absence without notification) Short summary: * users of qTox packages from tox.chat repo should get a notice in changelog that will point them to packages in the OBS community repo * most likely at some point those users will be transparently migrated to OBS repos Log from the meeting (log time UTC+1): ######################################################################## [18:54:22] https://i.imgur.com/UMz944E.jpg :3 [18:55:00] [21:08:32] tux3: is the travis guard set? [18:55:00] [21:08:42] zetok, hell no :) [18:55:00] [21:08:45] why? [18:55:00] [21:09:23] I want people to think, not be limited by stupid software restrictions [18:55:00] [21:09:38] that's not being limited [18:55:00] [21:09:52] they're forced to think on how to make it work at least on travis [18:55:00] [21:10:19] people are lazy, and without some stimuli they default to not thinking [18:55:00] [21:10:43] Merging pull requests is not the time to be lazy [18:55:23] tux3: and then you went & broke PRs [18:55:32] What [18:55:42] really, you didn't have to try that hard to prove that I was right [18:56:09] You're the last person to have merged something, what are you talking about? [18:56:15] https://github.com/tux3/qTox/commit/8d225a8c97a36838092b325ca830c14546f3a0c6 [18:56:47] What about it? [18:57:00] it broke PRs [18:57:21] I have a comment from a guy called "zetok" on this PR saying that it worked .... [18:57:22] https://github.com/tux3/qTox/pull/3283 [18:57:24] Just saying :) [18:57:47] tux3: yes, PR worked [18:57:54] tux3: your merge broke other PRs [18:58:18] What do you mean broke other PRs. The code compiled and worked, that's what the Travis guard was about. [18:58:28] tux3: you've proved yourself that your workflow is a bullshit and can't be trusted to do the job [18:58:46] travis also check commit messages [18:58:49] checks* [18:59:12] Will you please explain what you mean by "broke other PRs" [19:02:19] tux3: https://travis-ci.org/tux3/qTox/jobs/129079369#L168 ? there you go :) [19:03:49] Okay, so the name of the merge commit made your script fail, is that what you're getting at? [19:04:38] no [19:05:40] I'm pointing out that you yourself went and proved that your workflow can't be trusted to do the job [19:06:10] normally, I'd say that you should reflect on that [19:06:34] but I think that it's better to get to the point in this case [19:06:47] So, regarding your workflow: Change it. [19:07:02] You're not making any sense to me. It looks like you're trying to prove a point [19:07:17] nah, you proved my point quite well :) [19:07:36] I'm not interested in proving points, I'm trying to understand what the fuck you're getting at [19:07:37] You said "no" it's not the merge commit that's broken, then what's broken? [19:07:49] since my point was that there will be more mistakes made when one won't use the merge script :D [19:08:28] Okay so this is about the merge script now, not about the Travis guard. The travis guard has nothing to do with any of that, why'd you even bring it up if not for some misguided attempt at proving a point? [19:08:42] err? [19:09:08] travis guard is a effective way of verifying that no/less mistakes were made [19:09:18] Travis guard has nothing to do with this, if you look it hapilly greenlighted my PR. [19:09:26] Travis can't catch merge commits before they are made... [19:09:39] tux3: yes, I've corrected that part, and now it would fail your PR [19:09:44] s/pr/commit/ [19:09:57] oh wait, no [19:10:09] https://github.com/tux3/qTox/pull/3312 still not merged [19:10:48] tux3: that's why it's good to push to some other branch before --ff to master [19:10:54] That changes nothing, since merge commits are not done through the web interface [19:11:41] Either way, I changed my merge scripts so it follows your commit naming scheme, so this won't be a problem in the future. [19:11:50] err [19:12:06] that merge was made *after* you've changed your scripts, AFAIK [19:13:56] It was at the same time I was updating my script, so I must have used the wrong one at the time. It's definitely updated now. [19:15:25] Now the question I have is why does your script reject people's PRs if it's another commit that is named incorrectly? [19:15:41] This makes no sense, you should only check the PR's commits' names when building the PR [19:16:12] It looks like your script checks the whole history everytime instead [19:16:23] nope [19:16:32] it checks only commits in the supplied range [19:16:42] The supplied range should be only the PR. [19:16:44] now, it is travis that supplies the range.. [19:17:09] (and travis can't really supply range only from the PR) [19:17:21] Git should be able to tell you at which point the branch of the PR diverged, so the script could check it [19:18:46] so you'd want to have another script for that? [19:19:09] shouldn't master simply not break? [19:19:12] Couldn't the script detect when it's on a pull request branch automatically? [19:20:07] no [19:20:46] note that the scrip can easily be used standalone by people who would want to verify commits' compliance to the format [19:24:58] tux3: why would you prefer a workaround to the problem, rather than addressing the problem itself? [19:25:12] >tux3> Now the question I have is why does your script reject people's PRs if it's another commit that is named incorrectly? [19:25:19] that's not really the best question one could ask [19:25:27] Travis guard would not have stopped me from pushing that commit, would it? [19:25:28] the better one would be: why it shouldn't do that? [19:25:47] tux3: with the current workflow, no [19:26:22] * cisc has quit (Quit: Konversation terminated!) [19:26:44] zetok, fyi for any fedora24 beta users have them add https://unitedrpms.github.io/unitedrpms.repo for ffmpeg bits [19:29:05] * cisc (~cisc at unaffiliated/cisc) has joined [19:32:47] * abbat has quit (Ping timeout: 246 seconds) [19:34:14] * Dragofix has quit (Quit: Don't cry because IRC session is over, smile because it happened!) [19:35:19] > [...] I'm trying to understand what the fuck you're getting at <-- you just described every conversation ever i had with zetok [19:35:43] aw [19:40:26] * Dragofix (Dragofix at a91-155-20-164.elisa-laajakaista.fi) has joined [19:42:05] * abbat (~Anton at 109.188.127.28) has joined [19:43:21] nurupo: btw, are there any plans for pointing qTox users to the right repo on tox.chat? [19:43:57] (and generally not lying to users, but by now I don't really expect tox.chat to be that good) [19:44:05] ! [19:44:46] zetok: i would imagine tux3 would open a PR once you fully move to OBS for linux builds? [19:45:01] didn't you talk about this with oranges all the time? [19:45:22] did I? [19:45:46] zetok, we could edit the readme to point to OBS, but for the current tox.chat users there's no plan right now [19:46:17] tux3: done :) [19:46:28] zetok, Okay, good [19:46:47] nurupo: right, from what I remember I've said to oranges that at some point OBS will likely be used instead [19:46:48] Since I can watch for OBS build script changes, it's a good solution [19:47:18] tux3: what would be good, is to stop pointing users to the wrong repo [19:47:28] zetok: pretty sure i saw oranges talking about the move to OBS with someone in here on several different occasions [19:47:36] zetok, we can do that. For users already on tox.chat though it's not clear what to do [19:48:05] nurupo: yes, but most(?) of other talks weren't with me :) [19:48:19] oh, okay then [19:48:43] * abbat has quit (Quit: Leaving) [19:48:49] tux3: add a script that will give users notification to move to new repo [19:48:58] that is, for the tox.chat packages [19:49:01] Like a popup? [19:49:02] * abbat (~Anton at 109.188.127.28) has joined [19:49:15] um, I'm not quite sure if that qualifies as a pop-up [19:49:29] perhaps pop-up would be better than my idea [19:50:00] I thought about using that thing debian has for notifying users about ~breaking changes during updates [19:50:06] We can do a changelog with packages that would be shown by the package managers, but I don't know if people read that [19:50:27] Especially on the GUI update tool, I'm not sure it shows changelog warnings [19:50:35] (does it?) [19:50:39] they will, be it sooner or later, if you do changelog for every update :D [19:50:46] dunno about the GUI [19:50:50] Apper does show changelog [19:50:51] * zetok never really used it [19:50:58] Okay, that's an idea then [19:51:07] don't expect anyone to notice it though [19:51:20] Yeah, I'm not sure people will read it [19:52:05] well, as always, the alternative is to include a post-setup script that will add new repo, key, remove old qtox and install new qtox from the new repo [19:52:42] Maybe. I'm not fond of it, but I don't see a much better solution. [19:53:18] perhaps phases should be done [19:53:23] first with only changelog [19:53:45] some time after that, also adding the scrip for the people who can't be bothered to read "changelog" [19:54:36] (and warn in changelog that new versions will install new repo) [19:55:08] (that'll teach 'em to read the changelog ;D ) [19:55:13] #nsis [19:55:29] Changelog: [upstream] replace qTox with a potato (pop-up) [19:55:30] heh [20:00:05] tux3: do you have time to do the changelog thing now? [20:00:12] ~now [20:01:52] tux3: btw, what about dubslow? [20:03:30] I'll try to do the changelog thing [20:03:42] Dubslow, last I checked, was still kill. Any news? [20:03:56] no, but I haven't tried to contact him [20:04:25] tux3: I take that you too haven't tried to contact him? [20:05:48] tux3: and if so, could you try to do so, and ask what he thinks about ~stuff and whether he could consider helping with qTox again? [20:07:22] I think he's gone, if he wants to come back he'll come back. [20:07:28] But you can write him if you want [20:07:37] :/ [20:07:44] so, here's the thing [20:07:51] I mean I can't force him to work on qTox against his will.. [20:08:01] yes, but that's not about it [20:08:23] it's about whether he can considering helping again [20:08:24] > Dubslow, last I checked, was still kill. Any news? <-- i have seen him active on reddit [20:08:41] tux3: and me asking him about that probably wouldn't be good [20:08:53] so he is not kill, maybe just doesn't want to work on qtox anymore [20:08:53] s/considering/consider/ [20:09:21] tux3: instead, you asking most likely would be better [20:11:45] The last I know is that Dubslow quit because he got a job and was totally burned out on C++ stuff, I can understand that and I don't want to pressure him to work for us if he doesn't feel like it [20:11:51] it's kind of scary that someone who has been missing for over a year still has push access into master [20:12:20] tux3: yes, but the point is not to pressure [20:12:46] nurupo, yes maybe I should remove him. I still trust him, but it makes sense [20:14:09] hmm [20:14:25] * zetok wonders how to word that without the pressure [20:15:27] Feel free to ask him what's up if you want, but I'm sure he hasn't forgotten about us, if he wants to do something else that's his choice. [20:16:04] there are reasons why me asking most likely wouldn't be good [20:16:35] Then me asking on your behalf wouldn't be honest, because it's definitely your idea. [20:18:45] sorry, but for me: honesty < qTox [20:19:41] "Been a while, would you want to help with qTox again?" ? that should do :| [20:20:23] no pressure? [20:23:12] "No". I'll be doing the changelog update. [20:23:21] tux3: btw, have you subscribed to the ML [20:23:23] ? [20:23:45] The qTox ML was created? [20:23:48] yep [20:23:53] Neat, link pls [20:24:08] https://lists.tox.chat/listinfo/qtox-dev [20:24:52] you would have known if you read the mail about the previous meeting :( [20:25:26] Hm, I might have missed it. I sent a subscription request [20:26:07] zetok, is it solely devs or anyone wishing to help [20:26:16] linuxmodder: anyone :) [20:27:10] not that I need another noisy list but as I am trying to do more with wtox why not then :) [20:27:34] already have 76 filters for MLs :) [20:30:29] nurupo: so.. instructions on the tox.chat? [20:32:00] tux3: https://lists.tox.chat/pipermail/general/2016-May/000074.html to read later :) [20:32:17] zetok: > zetok: i would imagine tux3 would open a PR once you fully move to OBS for linux builds? [20:32:37] zetok, I definitely didn't receive the mail about that meeting [20:32:48] nurupo: imagination is a powerful thing [20:32:58] nurupo: yet alone, it doesn't make things happen [20:33:35] tux3: are you subscribed to `General` ML? [20:34:10] zetok, I imagine not, so I'm about to [20:36:49] nurupo: meanwhile, tox.chat is still misinforming users, and I heard that you're maintaining the stuff now [20:40:05] OBS is Osuse build system yes [20:40:34] open build system, instance of which openSUSE is running :) [20:40:45] ah [20:41:24] zetok: you are free to open PR if you have time as i don't have it [20:42:30] nurupo: ah, it was proven to me time ago, over and over again that I'd only waste my time if I've tried to improve things governed by Tox committee [20:42:49] so thanks, but no thanks, I prefer to not waste my time [20:43:42] so, you care enough to complain but not enough to fix? [20:44:14] I cared enough to fix, but that has been taken care of, now I'm just pointing out that you're misinforming users [20:46:25] zetok: what exactly is misinforming users, the download of qTox? [20:47:28] among stuff [20:47:45] I pushed the changelog entry that tells to go to https://software.opensuse.org/download.html?project=home%3Aantonbatenev%3Atox&package=qtox [20:47:59] tox.chat updates every day no? So we'll know if it worked tomorrow [20:48:33] nurupo: you might want to ponder on how I've complained about qTox issues not having labels until tux3 added me to collaborators, in which position I couldn't complain about that any longer, since I was the one responsible for fixing it :) [20:48:39] tux3: thanks :) -- Kind regards, Zetok Zalbavar ---- My Tox ID: 29AE62F95C56063D833024B1CB5C2140DC4AEB94A80FF4596CACC460D7BAA062E0A92C3424A0 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From david.burleigh at gmx.com Sun May 22 13:54:53 2016 From: david.burleigh at gmx.com (David Burleigh) Date: Sun, 22 May 2016 09:54:53 -0400 Subject: [General] Interface to telephone system? Message-ID: <20160522095453.55689c96@DZ> In my efforts to switch my organization over from Skype to Tox, I'm running into objections that it doesn't provide an interface to the telephone system, which Skype does. Is there any plan to add such an interface, whether via SIP or some other mechanism? From nurupocontributions at gmail.com Sun May 22 19:47:36 2016 From: nurupocontributions at gmail.com (nurupo) Date: Sun, 22 May 2016 15:47:36 -0400 Subject: [General] Interface to telephone system? In-Reply-To: <20160522095453.55689c96@DZ> References: <20160522095453.55689c96@DZ> Message-ID: Hello David, There is no plan on adding support for any telephone system. Regards, nurupo On Sun, May 22, 2016 at 9:54 AM, David Burleigh wrote: > In my efforts to switch my organization over from Skype to Tox, I'm > running into objections that it doesn't provide an interface to the > telephone system, which Skype does. Is there any plan to add such an > interface, whether via SIP or some other mechanism? > _______________________________________________ > General mailing list > General at lists.tox.chat > https://lists.tox.chat/listinfo/general > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lugarius at riseup.net Tue May 31 04:48:53 2016 From: lugarius at riseup.net (Lugarius Enerugi Albe) Date: Tue, 31 May 2016 06:48:53 +0200 Subject: [General] Repos are useless Message-ID: Why not adding the static binaries as default download? I am forced to use them anyway because the repos are not working. And the normal users just don't want adding repos after pressing an download button, reading a message '''Thanks for downloading '''. Without anything is downloading. ... then another link that shows you commands to make your computer able to install your stuff. ... and if the non geek user read 5min an document explaining how to use a Terminal, copy pastes the commands to it.... and still after 6min of trying to install, the user pressed an download button and Tox said ?"Thank you for downloading"... 80% off all normies continue to use there old messenger... Is this your goal? Baiting the potential user with " easy to use " and says after pressing the download button : " Haha, did you thought that you can just download our awesome software? LOL no. .. you have to add non working repos and we trolled you noob! " Is this for Tox "easy to use"? Can you please remove the repo joke? -------------- next part -------------- An HTML attachment was scrubbed... URL: From email at oranges.net.nz Tue May 31 04:52:47 2016 From: email at oranges.net.nz (oranges) Date: Tue, 31 May 2016 16:52:47 +1200 Subject: [General] Repos are useless In-Reply-To: References: Message-ID: <574D189F.50309@oranges.net.nz> On 31/05/16 16:48, Lugarius Enerugi Albe wrote: > Why not adding the static binaries as default download? > I am forced to use them anyway because the repos are not working. > > And the normal users just don't want adding repos after pressing an > download button, reading a message > > '''Thanks for downloading '''. Without anything is downloading. ... then > another link that shows you commands to make your computer able to > install your stuff. ... and if the non geek user read 5min an document > explaining how to use a Terminal, copy pastes the commands to it.... and > still after 6min of trying to install, the user pressed an download > button and Tox said > "Thank you for downloading"... > > 80% off all normies continue to use there old messenger... > > > Is this your goal? Baiting the potential user with " easy to use " and > says after pressing the download button : " Haha, did you thought that > you can just download our awesome software? LOL no. .. you have to add > non working repos and we trolled you noob! " > > Is this for Tox "easy to use"? > > Can you please remove the repo joke? I'm sorry you're incapable of carrying out basic instructions to install tox clients on your chosen os. I can direct you to a reputable windows or mac dealer as these OS seem better suited to your level of ability. From rugk at posteo.de Tue May 31 11:58:32 2016 From: rugk at posteo.de (rugk) Date: Tue, 31 May 2016 13:58:32 +0200 Subject: [General] Repos are useless In-Reply-To: References: Message-ID: Also there are static binary downloads for uTox (under "all platforms") --- I offer PGP support. To send me a PGP-encrypted mail, please ask for my private mail address. Am 31.05.2016 06:48 schrieb Lugarius Enerugi Albe: > Why not adding the static binaries as default download? > I am forced to use them anyway because the repos are not working. > > And the normal users just don't want adding repos after pressing an > download button, reading a message > > '''Thanks for downloading '''. Without anything is downloading. ... > then another link that shows you commands to make your computer able > to install your stuff. ... and if the non geek user read 5min an > document explaining how to use a Terminal, copy pastes the commands to > it.... and still after 6min of trying to install, the user pressed an > download button and Tox said > "Thank you for downloading"... > > 80% off all normies continue to use there old messenger... > > Is this your goal? Baiting the potential user with " easy to use " and > says after pressing the download button : " Haha, did you thought that > you can just download our awesome software? LOL no. .. you have to add > non working repos and we trolled you noob! " > > Is this for Tox "easy to use"? > > Can you please remove the repo joke? > _______________________________________________ > General mailing list > General at lists.tox.chat > https://lists.tox.chat/listinfo/general