3 ms·

Once we'd add "new issue by email", you could do this with a workaround: You can mention groups in GitLab. Create a group translators, devs, etc and then menti

Once we'd add "new issue by email", you could do this with a workaround: You can mention groups in GitLab. Create a group translators, devs, etc and then mention them: "@translators can you have a look at this?" Would then create a new issue and notify all members in the @translators group. Would that suffice? How else?

scrollaway 11y ago
> Would that suffice? How else? I think it's a great feature and very useful for smaller projects especially, but it doesn't replace mailing lists for larger ones. In open source projects especially, it's standard procedure to create one or more topical mailing lists with archives. Take a look at the Wine lists for example - active lists with forum mirroring: https://www.winehq.org/forums https://www.winehq.org/forums This is something that really improves some workflows - especially FOSS projects with a lot of outside contributions. Email is super friendly to newcomers to a project, and forums/archives let you get a feel for the general social tone as well as look at older issues matching your own. I don't think you can just replace this with a tracker.
- sytse 11y ago
  We use mailinglists ourselves with https://groups.google.com/forum/#!forum/gitlabhq https://groups.google.com/forum/#!forum/gitlabhq (hosted outside of GitLab) but we think the best thing for newcomers is a Slack/Gitter like forum. We've added Mattermost to the GitLab Omnibus packages and we're working with Rocket Chat. When that is done it will be easy to give each project its own room or something like that. What do you think?
  - scrollaway 11y ago
    I think if you yourself use mailing lists, you understand when and why mailing lists can't be replaced by slack/gitter and by extension you understand my point ;) Eat your own dog food, as they say. :)
    - sytse 11y ago
      We certainly try to use our own products as much as possible. We see that the chat is more popular. Integrating a mailinglist is not easy and we prefer to spend time on chat instead.

scrollaway 11y ago

> Would that suffice? How else? I think it's a great feature and very useful for smaller projects especially, but it doesn't replace mailing lists for larger ones. In open source projects especially, it's standard procedure to create one or more topical mailing lists with archives. Take a look at the Wine lists for example - active lists with forum mirroring: https://www.winehq.org/forums https://www.winehq.org/forums This is something that really improves some workflows - especially FOSS projects with a lot of outside contributions. Email is super friendly to newcomers to a project, and forums/archives let you get a feel for the general social tone as well as look at older issues matching your own. I don't think you can just replace this with a tracker.

sytse 11y ago
We use mailinglists ourselves with https://groups.google.com/forum/#!forum/gitlabhq https://groups.google.com/forum/#!forum/gitlabhq (hosted outside of GitLab) but we think the best thing for newcomers is a Slack/Gitter like forum. We've added Mattermost to the GitLab Omnibus packages and we're working with Rocket Chat. When that is done it will be easy to give each project its own room or something like that. What do you think?
- scrollaway 11y ago
  I think if you yourself use mailing lists, you understand when and why mailing lists can't be replaced by slack/gitter and by extension you understand my point ;) Eat your own dog food, as they say. :)
  - sytse 11y ago
    We certainly try to use our own products as much as possible. We see that the chat is more popular. Integrating a mailinglist is not easy and we prefer to spend time on chat instead.