This is why I like Zulip. Its two tiered threading model keeps conversations organized without the chaos of infinitely deep email threads.

As for GitLab, I still want to switch to it in the future, but for now it would not work for us. While they provide 50,000 minutes per month on their shared CI servers to public open source projects for free, those servers only run Linux. So we would still have to set up our own Windows and macOS build servers with the GitLab Runner software. However, there currently is not a good way to have those project-specific build servers make builds for merge requests from forks. This is one of the most highly requested features for GitLab Community Edition and it is assigned to their vague "Next 3-6 months" milestone, so I anticipate it will get implemented soonish. If people could give this issue a thumbs up, that would be nice:
https://gitlab.com/gitlab-org/gitlab-ce/issues/23902

On 12/31/2017 03:16 AM, Ferran Pujol Camins wrote:
It's ironic that to read this conversation I've needed to look into four different email threads. Now I'm not even sure this is the last one.

I Just wanted to add that if we move from email to a new tool as our main communication channel, we should make sure that the new tool has a good mobile app. Also that people not wanting to install yet another app can get a reasonable good experience with mail alerts.

On 19 Nov 2017 12:36 p.m., "Daniel Schürmann" <dasch...@mixxx.org <mailto:dasch...@mixxx.org>> wrote:

    Am 19.11.2017 um 11:46 schrieb Josep Maria Antolin:

    [...]

        I think it could be really helpful to make a GitLab repository
        for controller mappings. We could use its issue tracker to
        take requests for controller mappings so users could vote for
        mappings they want. That would give us data on what hardware
        is important to map, which could guide us on what to ask
        manufacturers for and/or what to spend donations on.


    As we did it for manuals, we may split out mappings from the main
    repo.
    [...]

    Now that you mention this, does Git have the concept of externals
    like Subversion has?  If it does, controllers, skins and manual
    could be separated repos and the Mixxx repo could use them as
    externals, so those that work on Mixxx have everything, and other
    contributors can focus on the manual, skins or controllers.

    Yes it has. We did experiment with it, but It was annoying to use.


    
------------------------------------------------------------------------------
    Check out the vibrant tech community on one of the world's most
    engaging tech sites, Slashdot.org! http://sdm.link/slashdot
    _______________________________________________
    Get Mixxx, the #1 Free MP3 DJ Mixing software Today
    http://mixxx.org


    Mixxx-devel mailing list
    Mixxx-devel@lists.sourceforge.net
    <mailto:Mixxx-devel@lists.sourceforge.net>
    https://lists.sourceforge.net/lists/listinfo/mixxx-devel
    <https://lists.sourceforge.net/lists/listinfo/mixxx-devel>



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot



_______________________________________________
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org


Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org


Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel

Reply via email to