Skip to content

Regular Project Meeting #1582

@Nebukadneza

Description

@Nebukadneza

meeting link: https://jitsi.fem.tu-ilmenau.de/MailuDevCollab

We just had our first Mailu-Project-Video-Meeting! 🎉🎉🎉🎉🎉

It was great to be able to talk about the project, and @HorayNarea, @ofthesun9 and myself were able to discuss and sort out quite a chunk of work for the upcoming 1.8-release-candidate.

We not only agreed on trying to have follow-up meetings, possibly even regularly, but we also wanted to share the meeting-notes we took with everyone. In an open/free/libre project, the communication going on should also be visible and open/free.

So, from now on, this issue will serve as a drop-off point for the meeting notes. We don’t have a good idea how to best structure meeting/agenda-planning, so for now we agreed that we set a rough agenda for the next date at the end, and if someone wants to bring up an additional topic, this issue can be used to comment.

The voting for finding the next date is up on: https://nextcloud.ghostdub.de/apps/polls/s/UcyBGlzHMRrno9NG

Thanks to everyone involved!

2020-08-09

Attendees

Agenda

  • Went through PRs sorted in 1.8-rc milestone
    • »Mob«-Merge the clearer portion
    • Discuss and comment on others
  • Discuss alpine vs. debian
    • Gut-feeling: Most alpine issues sorted out
    • ClamAV-issue probably(?) related to swap rather than alpine/musl
    • Xapian solves missing/broken FTS on alpine
    • ⇒ Conclusion: For now, don’t invest the work/time to migrate to debian, stick with alpine
    • ⇒ Alpine update makes sense (approved)
  • Agree @KaiyouS idea of posting »voting« messages in unclear-state-PRs/issues is a good idea
  • Agree to introduce "Later" milestone to capture stuff that is imminently useful, but disregarded for current milstone due to scoping only.
  • Agreed to have regular meetings from now on

Follow-up topics

  • Staying up to date with upstream versions
  • Discussing HA for setup.mailu.io
  • Triaging and scoping of biggest open issues
    • Open Relay issues when (incorrectly) using IPv6
    • Recurring BORS/Build&Test-Pipeline issues
    • (?) … Whatever other big issues currently are open (?)

Metadata

Metadata

Assignees

No one assigned

    Labels

    status/wipWork in progress. This will block mergify until the label is removed.type/discussion

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions