Gajim - 2019-07-10


  1. andy Heh, yesterday I wanted to make an issue for wakeup problem, but Gajim works :D I think, that problem happens when Gajim have a lot of messages to catch up from MAM.
  2. wurstsalat andy: maybe you get lucky with loggin another time :D
  3. andy maybe ;)
  4. andy btw, when catch up few large images from http-upload Gajim are a little unresponsive
  5. wurstsalat Yeah, image preview can sometimes be resource heavy
  6. zinid process them in a separate thread?
  7. andrey.g Related: https://dev.gajim.org/gajim/gajim-plugins/issues/320
  8. zinid python 🙂
  9. wurstsalat asterix, I *do* miss the bot
  10. nico Is there an eta when the next Gajim version will released?
  11. Eduard When it's ready ™
  12. lovetox Hm we should do a list what we want to fix before the next release
  13. lovetox i think we have done a lot, maybe its time to stop implementing new stuff and work now on making everything smooth
  14. wurstsalat a list would definitively be a good start
  15. lovetox I think main points are to finish the whole MUC usability thing we started
  16. lovetox and look that plugins works, and specifically look at what we still have to do with omemo
  17. wurstsalat alright, sounds good!
  18. MattJ MUC usability <3
  19. wurstsalat maybe we can put that ToDo wiki page to good use.
  20. lovetox hmm a issue would be nicer
  21. lovetox lets do this 1.3 release issue now correctly before we release instead of after what we usually do
  22. wurstsalat That's probably better :) there we could add a list of separate issues to resolve before release
  23. asterix wurstsalat, yes, I'll check ASAP
  24. wurstsalat asterix: thanks!
  25. wurstsalat There it is, lovetox: https://dev.gajim.org/gajim/gajim/issues/9756
  26. bot Yann Leboulanger pushed 3 commits to branch _refs/heads/master_ of _gajim_ < https://dev.gajim.org/gajim/gajim >: https://conference.gajim.org:5281/pastebin/bb250ad6-b184-4ec8-89d5-a56ee6a13651
  27. asterix It is back
  28. Zash https://cerdale.zash.se/upload/1dltQO3mVbPspMdc/gajim-menu.png
  29. Zash "Add Contact..." twice?
  30. lovetox Zash its known and work in progress
  31. Zash Ack
  32. wurstsalat asterix, it is indeed, thank you! Is it enabled for the website repo as well?
  33. asterix Yep, should be. Else tell me
  34. andrey.g > there we could add a list of separate issues to resolve before release Maybe creating "Milestone" "1.3" and mark corresponding issues to belong there so that Gitlab could auto account them would be better.
  35. lovetox tried it, does not work :D
  36. andrey.g I've just created Milestone 1.3 https://dev.gajim.org/ag/gajim/-/milestones Then a test issue https://dev.gajim.org/ag/gajim/issues/1 And there Milestone -> Edit -> choose 1.3
  37. lovetox So are you saying you offer to set the milestone on all issues correctly in the future?
  38. lovetox would be great :)
  39. andrey.g Maybe I've misunderstood what exactly does not work. Instead of putting an issue into a list, setting the milestone seems to work. For existing issues it works. I've set the milestone *not* during creating the issue (since it is generally not known at that moment) but afterwards.
  40. lovetox i was refering that it does not work because it takes some dedication to set the milestones on each issue
  41. lovetox and the gain is absolute minimal
  42. lovetox if you do it only on half the issues its even more worthless
  43. andrey.g Good. I thought that if one searches for the issues to be resolved for the next realease it would be better then not to copy them but just to mark them (and it is not harder). Then everyone asking "when" could open the milestone page and see how many percent are missing. Would be nice.
  44. andrey.g Now the issue for release cotains somehow "sub-"issues.
  45. andrey.g as if Gitlab wouldn't yet have native support for milestones
  46. lovetox Of course we could add now the 20 points in the issue, each as its own issue
  47. lovetox but dont you see that having a list is 10 times easier and needs less work
  48. lovetox every issue i open, i have to label, i have to eventually close
  49. lovetox here is point my mouse at a checkbox
  50. lovetox and the only gain is that somebody on the internet sees a percentage of completeness?
  51. andrey.g Well, yes, all that is not worth to be opened as issue, is better to track as "task". I mean only not adding real issues (already closed or still opened) as tasks either.
  52. lovetox but we didnt?
  53. andrey.g Or perhaps Gitlab became tooooo Enterprise-isch...
  54. lovetox where is a real issue?
  55. lovetox at the moment we have 2 things to do
  56. lovetox Finish group chat workflow Finish string rewording (see !384)
  57. lovetox review a merge request, and a bigger task that is not defined
  58. lovetox i get what you want to say, we could use tools that gitlab provides to solve this
  59. lovetox but what i want to tell you is, using these tools also creates new work
  60. lovetox labeling, setting milestones, moving milestones if they are wrong, keeping track of all the issues etc etc
  61. lovetox so yes would do it, if there is a big benefit
  62. lovetox i dont see it
  63. andrey.g That's why I thought about Enterprise, since tools are there to make less work, not more.
  64. lovetox in enterprises that use issues trackers there are dedicated people whos only work is to maintain the issue tracker
  65. dragneel1994 hi guys ! i want to know how much time still for 1.1.4 verion release ?
  66. andrey.g Yeah, issues that could not be resolved for the targeted milestone would need to be bumped to the next one. Interesting, whether Gitlab provide a feature of "auto-bump all not resolved now" and whether there is some poor-man Gitlab-like software...
  67. wurstsalat lovetox, we can try for 1.2 and if it's too much work for the gain we abandon the idea? I'd volunteer to add the 1.2 milestone on the closed issues as well (perfect for generating the changelog). Then we'd just have to add the 1.2 milestone on currently open issies we want to solve for release.
  68. andrey.g 👍 Looking at previous Gajim milestones reveales that this was the way it worked before switching to Gitlab.
  69. wurstsalat always needs one to maintain this
  70. wurstsalat but I'm labeling each issue anyway
  71. wurstsalat lovetox, should I give it a try?
  72. bot Daniel Brötzmann modified an issue in _gajim_ < https://dev.gajim.org/gajim/gajim/issues/9747 >: #9747: < sqlite3.OperationalError: attempt to write a readonly database >
  73. lovetox yeah, but only assign closed ones to the milestone
  74. lovetox everything else results only in moving them again and again
  75. wurstsalat Some issues are referenced in MRs, these could be tagged as well (if you think the corresponding MR would make it)
  76. bot Daniel Brötzmann modified an issue in _gajim_ < https://dev.gajim.org/gajim/gajim/issues/9728 >: #9728: < Roster Item Exchange window too small, especially on large additions >
  77. bot Daniel Brötzmann updated a merge request for _gajim/master_ < https://dev.gajim.org/gajim/gajim/merge_requests/494 >: Remove YesNoDialog and its usage
  78. bot Daniel Brötzmann modified an issue in _gajim_ < https://dev.gajim.org/gajim/gajim/issues/9696 >: #9696: < Enabling an existing account only comes into effect by restarting Gajim >
  79. bot Daniel Brötzmann modified an issue in _gajim_ < https://dev.gajim.org/gajim/gajim/issues/9655 >: #9655: < Permit copying certificate details >
  80. bot Daniel Brötzmann modified an issue in _gajim_ < https://dev.gajim.org/gajim/gajim/issues/9661 >: #9661: < [HTTP Upload] display filename, upload speed and ETA >
  81. bot Daniel Brötzmann modified an issue in _gajim_ < https://dev.gajim.org/gajim/gajim/issues/9652 >: #9652: < Embedded IPython interactive shell failed to start >
  82. bot Daniel Brötzmann modified an issue in _gajim_ < https://dev.gajim.org/gajim/gajim/issues/9649 >: #9649: < Trying to save nonexistent avatar results in error >
  83. bot Daniel Brötzmann modified an issue in _gajim_ < https://dev.gajim.org/gajim/gajim/issues/9645 >: #9645: < zeroconf_bonjour can not resolve services over IPv6 >
  84. bot Daniel Brötzmann modified an issue in _gajim_ < https://dev.gajim.org/gajim/gajim/issues/9623 >: #9623: < 'NoneType' object has no attribute 'get_index' in Start New Chat dialog >
  85. bot Daniel Brötzmann modified an issue in _gajim_ < https://dev.gajim.org/gajim/gajim/issues/9621 >: #9621: < Gajim doesn't tell which MUC is the cause of an error dialog >
  86. bot Daniel Brötzmann modified an issue in _gajim_ < https://dev.gajim.org/gajim/gajim/issues/9610 >: #9610: < ValueError: Namespace Avahi not available during startup >
  87. bot Daniel Brötzmann modified an issue in _gajim_ < https://dev.gajim.org/gajim/gajim/issues/9608 >: #9608: < vCard possibility in "Add a contact" box and "Send simple message" box >
  88. bot Daniel Brötzmann modified an issue in _gajim_ < https://dev.gajim.org/gajim/gajim/issues/9580 >: #9580: < Gajim stays in "edit-mode" between closing & re-opening a MUC >
  89. bot Daniel Brötzmann modified an issue in _gajim_ < https://dev.gajim.org/gajim/gajim/issues/9549 >: #9549: < IndexError when dragging file on contact list >
  90. bot Daniel Brötzmann modified an issue in _gajim_ < https://dev.gajim.org/gajim/gajim/issues/9544 >: #9544: < Unreadable highlighted text in history with the dark theme enabled >
  91. bot Daniel Brötzmann modified an issue in _gajim_ < https://dev.gajim.org/gajim/gajim/issues/9535 >: #9535: < Jingle Audio: Update codecs (Patch) >
  92. bot Daniel Brötzmann modified an issue in _gajim_ < https://dev.gajim.org/gajim/gajim/issues/9437 >: #9437: < Plugin manager: disable or hide "Install plugin from zip" when running as flatpak >
  93. bot Daniel Brötzmann updated a merge request for _gajim/master_ < https://dev.gajim.org/gajim/gajim/merge_requests/458 >: WIP: ChatToMUC: Rework dialog
  94. bot Daniel Brötzmann updated a merge request for _gajim/master_ < https://dev.gajim.org/gajim/gajim/merge_requests/407 >: Open 1:1 chat instead of private message when doubleclicking a participant in a non-anonymous group chat
  95. bot Daniel Brötzmann updated a merge request for _gajim/master_ < https://dev.gajim.org/gajim/gajim/merge_requests/384 >: WIP: Revise some text strings
  96. bot Daniel Brötzmann updated a merge request for _gajim/master_ < https://dev.gajim.org/gajim/gajim/merge_requests/492 >: Add View Certificate menu item to account context menu
  97. bot Daniel Brötzmann updated a merge request for _gajim/master_ < https://dev.gajim.org/gajim/gajim/merge_requests/488 >: AdvancedConfig: Layout changes and code cleanup
  98. bot Daniel Brötzmann updated a merge request for _gajim/master_ < https://dev.gajim.org/gajim/gajim/merge_requests/493 >: Gajim installer: Fix some german strings and rework graphics