Unpacking the mailing list: Discourse, Slack = Mailing list
Hi everyone, We had a chat Ralf, Stéfan and I about moving away from the mailing list. The idea would be to move over Discourse under the umbrella of https://discuss.scientific-python.org <https://discuss.scientific-python.org/> Stéfan proposes to do the migration work and I can also provide some help if needed (the complete history would be imported). I also propose to help administrate/moderate this space. As Serge expressed during the meetup, we should be careful when moving to Discourse as some people might be reluctant to come. Which would fragment the community. Hence, we should force the move by sunsetting the mail list. On the same topic, I would discuss the possibility to use Slack (or another platform for real-time chat). This has proven to be helpful for NumPy and other projects and we should also see the benefits. Let us know what you think. Cheers, Pamphile
On 20/05/2021 11:40, Pamphile Roy wrote:
Let us know what you think.
Personally, I'm all for less emails, in general. Discourse and Slack are both widely-used tools, so I don't think it creates a real hurdle to the engagement of community members. That being said, I'm myself very much inactive, so my opinion shouldn't weight much :-) Cheers, -- Romain Jacob Postdoctoral Researcher ETH Zurich - Networked Systems Group (NSG) www.romainjacob.net <https://www.romainjacob.net/> @RJacobPartner <https://twitter.com/RJacobPartner> Gloriastrasse 35, ETZ G78 8092 Zurich +41 7 68 16 88 22
On Thu, May 20, 2021 at 11:41 AM Pamphile Roy <roy.pamphile@gmail.com> wrote:
Hi everyone,
We had a chat Ralf, Stéfan and I about moving away from the mailing list.
The idea would be to move over Discourse under the umbrella of
https://discuss.scientific-python.org
Stéfan proposes to do the migration work and I can also provide some help if needed (the complete history would be imported). I also propose to help administrate/moderate this space.
As Serge expressed during the meetup, we should be careful when moving to Discourse as some people might be reluctant to come. Which would fragment the community. Hence, we should force the move by sunsetting the mail list.
On the same topic, I would discuss the possibility to use Slack (or another platform for real-time chat). This has proven to be helpful for NumPy and other projects and we should also see the benefits.
Hi Pamphile, Do you happen to have know if there might be any accessibilty issues with discourse, slack and the like? I have both accessibility in the traditional sense in mind, as well as things like governments that censor internet access. I have no idea about either of these things, and for all I know the alternatives might be perfect replacements, so this is just an aspect that should also be considered for such a switch :) András
Let us know what you think.
Cheers, Pamphile _______________________________________________ SciPy-Dev mailing list SciPy-Dev@python.org https://mail.python.org/mailman/listinfo/scipy-dev
Hi András,
On 20.05.2021, at 12:20, Andras Deak <deak.andris@gmail.com> wrote:
Do you happen to have know if there might be any accessibilty issues with discourse, slack and the like? I have both accessibility in the traditional sense in mind, as well as things like governments that censor internet access. I have no idea about either of these things, and for all I know the alternatives might be perfect replacements, so this is just an aspect that should also be considered for such a switch :)
Interesting question. My understanding is that both platforms have accessibility policy or are looking at it: https://slack.com/intl/en-at/accessibility-plan <https://slack.com/intl/en-at/accessibility-plan> https://meta.discourse.org/tag/accessibility <https://meta.discourse.org/tag/accessibility> As for being blocked, Slack is not accessible (or inconsistently) in some countries. Discourse seems ok and depends on your IP and your content. Cheers, Pamphile
Hi, I have strong preference for being able to avoid Slack: https://blogs.sap.com/2018/10/26/why-i-dont-like-slack-anymore-for-public-us... Cheers, Matthew On Thu, May 20, 2021 at 11:38 AM Pamphile Roy <roy.pamphile@gmail.com> wrote:
Hi András,
On 20.05.2021, at 12:20, Andras Deak <deak.andris@gmail.com> wrote:
Do you happen to have know if there might be any accessibilty issues with discourse, slack and the like? I have both accessibility in the traditional sense in mind, as well as things like governments that censor internet access. I have no idea about either of these things, and for all I know the alternatives might be perfect replacements, so this is just an aspect that should also be considered for such a switch :)
Interesting question. My understanding is that both platforms have accessibility policy or are looking at it:
https://slack.com/intl/en-at/accessibility-plan https://meta.discourse.org/tag/accessibility
As for being blocked, Slack is not accessible (or inconsistently) in some countries. Discourse seems ok and depends on your IP and your content.
Cheers, Pamphile _______________________________________________ SciPy-Dev mailing list SciPy-Dev@python.org https://mail.python.org/mailman/listinfo/scipy-dev
About 6 months ago we transitioned MNE-Python from a traditional GNU Mailman mailing list <https://mail.nmr.mgh.harvard.edu/pipermail//mne_analysis/> (almost 15 years old) to Discourse <https://mne.discourse.group/>, including porting the old mailing list posts so they are directly searchable there <https://mne.discourse.group/search?q=mne_setup_source_space>. It has been a pretty smooth transition and the reply rate has gone up -- I think the forum setting is much more inviting for most people, and the threading is better than what you get from slack or gitter. My 2c, Eric On Thu, May 20, 2021 at 6:54 AM Matthew Brett <matthew.brett@gmail.com> wrote:
Hi,
I have strong preference for being able to avoid Slack:
https://blogs.sap.com/2018/10/26/why-i-dont-like-slack-anymore-for-public-us...
Cheers,
Matthew
On Thu, May 20, 2021 at 11:38 AM Pamphile Roy <roy.pamphile@gmail.com> wrote:
Hi András,
On 20.05.2021, at 12:20, Andras Deak <deak.andris@gmail.com> wrote:
Do you happen to have know if there might be any accessibilty issues with discourse, slack and the like? I have both accessibility in the traditional sense in mind, as well as things like governments that censor internet access. I have no idea about either of these things, and for all I know the alternatives might be perfect replacements, so this is just an aspect that should also be considered for such a switch :)
Interesting question. My understanding is that both platforms have
accessibility policy or are looking at it:
https://slack.com/intl/en-at/accessibility-plan https://meta.discourse.org/tag/accessibility
As for being blocked, Slack is not accessible (or inconsistently) in
some countries.
Discourse seems ok and depends on your IP and your content.
Cheers, Pamphile _______________________________________________ SciPy-Dev mailing list SciPy-Dev@python.org https://mail.python.org/mailman/listinfo/scipy-dev
SciPy-Dev mailing list SciPy-Dev@python.org https://mail.python.org/mailman/listinfo/scipy-dev
+1 for discourse -0 for sunsetting the ML -1 for slack. My 2c, Evgeni чт, 20 мая 2021 г., 14:19 Eric Larson <larson.eric.d@gmail.com>:
About 6 months ago we transitioned MNE-Python from a traditional GNU Mailman mailing list <https://mail.nmr.mgh.harvard.edu/pipermail//mne_analysis/> (almost 15 years old) to Discourse <https://mne.discourse.group/>, including porting the old mailing list posts so they are directly searchable there <https://mne.discourse.group/search?q=mne_setup_source_space>. It has been a pretty smooth transition and the reply rate has gone up -- I think the forum setting is much more inviting for most people, and the threading is better than what you get from slack or gitter.
My 2c, Eric
On Thu, May 20, 2021 at 6:54 AM Matthew Brett <matthew.brett@gmail.com> wrote:
Hi,
I have strong preference for being able to avoid Slack:
https://blogs.sap.com/2018/10/26/why-i-dont-like-slack-anymore-for-public-us...
Cheers,
Matthew
On Thu, May 20, 2021 at 11:38 AM Pamphile Roy <roy.pamphile@gmail.com> wrote:
Hi András,
On 20.05.2021, at 12:20, Andras Deak <deak.andris@gmail.com> wrote:
Do you happen to have know if there might be any accessibilty issues with discourse, slack and the like? I have both accessibility in the traditional sense in mind, as well as things like governments that censor internet access. I have no idea about either of these things, and for all I know the alternatives might be perfect replacements, so this is just an aspect that should also be considered for such a switch :)
Interesting question. My understanding is that both platforms have
accessibility policy or are looking at it:
https://slack.com/intl/en-at/accessibility-plan https://meta.discourse.org/tag/accessibility
As for being blocked, Slack is not accessible (or inconsistently) in
some countries.
Discourse seems ok and depends on your IP and your content.
Cheers, Pamphile _______________________________________________ SciPy-Dev mailing list SciPy-Dev@python.org https://mail.python.org/mailman/listinfo/scipy-dev
SciPy-Dev mailing list SciPy-Dev@python.org https://mail.python.org/mailman/listinfo/scipy-dev
_______________________________________________ SciPy-Dev mailing list SciPy-Dev@python.org https://mail.python.org/mailman/listinfo/scipy-dev
Hello all, One option I haven’t seen mentioned is GitHub discussions. Is that being evaluated at all as a possibility? Best regards, Hameer Abbasi
Am 20.05.2021 um 11:40 schrieb Pamphile Roy <roy.pamphile@gmail.com>:
Hi everyone,
We had a chat Ralf, Stéfan and I about moving away from the mailing list.
The idea would be to move over Discourse under the umbrella of
https://discuss.scientific-python.org <https://discuss.scientific-python.org/>
Stéfan proposes to do the migration work and I can also provide some help if needed (the complete history would be imported). I also propose to help administrate/moderate this space.
As Serge expressed during the meetup, we should be careful when moving to Discourse as some people might be reluctant to come. Which would fragment the community. Hence, we should force the move by sunsetting the mail list.
On the same topic, I would discuss the possibility to use Slack (or another platform for real-time chat). This has proven to be helpful for NumPy and other projects and we should also see the benefits.
Let us know what you think.
Cheers, Pamphile _______________________________________________ SciPy-Dev mailing list SciPy-Dev@python.org https://mail.python.org/mailman/listinfo/scipy-dev
On 20/5/21 12:40 pm, Pamphile Roy wrote:
Hi everyone,
We had a chat Ralf, Stéfan and I about moving away from the mailing list.
The idea would be to move over Discourse under the umbrella of
https://discuss.scientific-python.org <https://discuss.scientific-python.org>
Stéfan proposes to do the migration work and I can also provide some help if needed (the complete history would be imported). I also propose to help administrate/moderate this space.
As Serge expressed during the meetup, we should be careful when moving to Discourse as some people might be reluctant to come. Which would fragment the community. Hence, we should force the move by sunsetting the mail list.
On the same topic, I would discuss the possibility to use Slack (or another platform for real-time chat). This has proven to be helpful for NumPy and other projects and we should also see the benefits.
Let us know what you think.
Cheers, Pamphile
Among criteria for a community forum might be: - permanence: can we find a discussion in ten years when we went to figure out what led to a particular decision - transparency: will the discussions be archived in a public manner with little need for logins or signups - searchability: is there a good way to search the discussions for relevant fragments (single words are often not enough). So for me slack is not a good option for a community forum, but it could be an additional side channel, as long as it is clear what goes where. NumPy's use of slack is limited to short informal chats between developers or chats with newcomers who might be intimidated by the permanence of the community forum. I am not sure how long discourse promises to preserve discussions. I am a dinosaur and prefer email. Discourse -> email seems to work OK for the python forums I monitor. Matti
On Thu, May 20, 2021 at 1:26 PM Matti Picus <matti.picus@gmail.com> wrote:
On 20/5/21 12:40 pm, Pamphile Roy wrote:
Hi everyone,
We had a chat Ralf, Stéfan and I about moving away from the mailing list.
The idea would be to move over Discourse under the umbrella of
https://discuss.scientific-python.org <https://discuss.scientific-python.org>
Stéfan proposes to do the migration work and I can also provide some help if needed (the complete history would be imported). I also propose to help administrate/moderate this space.
Thanks Pamphile and Stéfan for offering to do the heavy lifting here.
As Serge expressed during the meetup, we should be careful when moving to Discourse as some people might be reluctant to come. Which would fragment the community. Hence, we should force the move by sunsetting the mail list.
+1, if the decision is to move - then we should move (= migrate content, leave the mailing list behind).
On the same topic, I would discuss the possibility to use Slack (or another platform for real-time chat). This has proven to be helpful for NumPy and other projects and we should also see the benefits.
Let us know what you think.
Cheers, Pamphile
Among criteria for a community forum might be:
- permanence: can we find a discussion in ten years when we went to figure out what led to a particular decision
- transparency: will the discussions be archived in a public manner with little need for logins or signups
- searchability: is there a good way to search the discussions for relevant fragments (single words are often not enough).
So for me slack is not a good option for a community forum, but it could be an additional side channel, as long as it is clear what goes where. NumPy's use of slack is limited to short informal chats between developers or chats with newcomers who might be intimidated by the permanence of the community forum.
+1 to this point. It's probably best to leave Slack for a separate discussion at a later time, since it serves a very different purpose from a mailing list or forum like Discourse.
I am not sure how long discourse promises to preserve discussions.
I think forever? You can always export an archive, in case the hosted Discourse ever shuts up shop. I am a dinosaur and prefer email. Discourse -> email seems to work OK for
the python forums I monitor.
Same here. The Python packaging Discourse I follow seems to work well though, and is searchable. So while for me personally email / mailing lists works okay, I think it's more important to provide a better experience for newcomers and the generation that didn't grow up with old school mailing lists. Cheers, Ralf
-1 for sunsetting the mailing list +1 for having any alternative solutions only "informal--" if people want to go there and interact with newcomers that's fine IMO, but I'd strongly prefer not to have more things/technologies/channels to monitor for decision making On Thu, 20 May 2021 at 06:11, Ralf Gommers <ralf.gommers@gmail.com> wrote:
On Thu, May 20, 2021 at 1:26 PM Matti Picus <matti.picus@gmail.com> wrote:
Hi everyone,
We had a chat Ralf, Stéfan and I about moving away from the mailing
On 20/5/21 12:40 pm, Pamphile Roy wrote: list.
The idea would be to move over Discourse under the umbrella of
https://discuss.scientific-python.org <https://discuss.scientific-python.org>
Stéfan proposes to do the migration work and I can also provide some help if needed (the complete history would be imported). I also propose to help administrate/moderate this space.
Thanks Pamphile and Stéfan for offering to do the heavy lifting here.
As Serge expressed during the meetup, we should be careful when moving to Discourse as some people might be reluctant to come. Which would fragment the community. Hence, we should force the move by sunsetting the mail list.
+1, if the decision is to move - then we should move (= migrate content, leave the mailing list behind).
On the same topic, I would discuss the possibility to use Slack (or another platform for real-time chat). This has proven to be helpful for NumPy and other projects and we should also see the benefits.
Let us know what you think.
Cheers, Pamphile
Among criteria for a community forum might be:
- permanence: can we find a discussion in ten years when we went to figure out what led to a particular decision
- transparency: will the discussions be archived in a public manner with little need for logins or signups
- searchability: is there a good way to search the discussions for relevant fragments (single words are often not enough).
So for me slack is not a good option for a community forum, but it could be an additional side channel, as long as it is clear what goes where. NumPy's use of slack is limited to short informal chats between developers or chats with newcomers who might be intimidated by the permanence of the community forum.
+1 to this point. It's probably best to leave Slack for a separate discussion at a later time, since it serves a very different purpose from a mailing list or forum like Discourse.
I am not sure how long discourse promises to preserve discussions.
I think forever? You can always export an archive, in case the hosted Discourse ever shuts up shop.
I am a dinosaur and prefer email. Discourse -> email seems to work OK for
the python forums I monitor.
Same here. The Python packaging Discourse I follow seems to work well though, and is searchable. So while for me personally email / mailing lists works okay, I think it's more important to provide a better experience for newcomers and the generation that didn't grow up with old school mailing lists.
Cheers, Ralf
_______________________________________________ SciPy-Dev mailing list SciPy-Dev@python.org https://mail.python.org/mailman/listinfo/scipy-dev
Hi, On Thu, May 20, 2021 at 3:37 PM Tyler Reddy <tyler.je.reddy@gmail.com> wrote:
-1 for sunsetting the mailing list +1 for having any alternative solutions only "informal--" if people want to go there and interact with newcomers that's fine IMO, but I'd strongly prefer not to have more things/technologies/channels to monitor for decision making
Speaking as a dinosaur - like Matti - I personally prefer email, but I would say that, despite reservations, my experience with Discourse hasn't been too bad. You can ask it to send emails, so you don't have to monitor it separately. I have heard Eric L's comment from others, about greater traffic from Discourse than using email. When I went to check for one project, the traffic looked to be of reasonable quality. Cheers, Matthew
Just keep the discourse stuff for onboarding/mentoring/informal stuff and mailing list for "votes"/substantive decisions IMO. On Thu, 20 May 2021 at 08:46, Matthew Brett <matthew.brett@gmail.com> wrote:
Hi,
On Thu, May 20, 2021 at 3:37 PM Tyler Reddy <tyler.je.reddy@gmail.com> wrote:
-1 for sunsetting the mailing list +1 for having any alternative solutions only "informal--" if people want
to go there and interact with newcomers that's fine IMO, but I'd strongly prefer not to have more things/technologies/channels to monitor for decision making
Speaking as a dinosaur - like Matti - I personally prefer email, but I would say that, despite reservations, my experience with Discourse hasn't been too bad. You can ask it to send emails, so you don't have to monitor it separately. I have heard Eric L's comment from others, about greater traffic from Discourse than using email. When I went to check for one project, the traffic looked to be of reasonable quality.
Cheers,
Matthew _______________________________________________ SciPy-Dev mailing list SciPy-Dev@python.org https://mail.python.org/mailman/listinfo/scipy-dev
On Thu, May 20, 2021, at 04:26, Matti Picus wrote:
Among criteria for a community forum might be:
- permanence: can we find a discussion in ten years when we went to figure out what led to a particular decision
That's certainly the idea. The server is hosted by NumFOCUS, which should give it some permanency. We have backups set up to Backblaze, and someone from SciPy will get credentials to that so SciPy can extract their data at any time.
- transparency: will the discussions be archived in a public manner with little need for logins or signups
Yes, the discussions can be browsed (but not added to) without logging in.
- searchability: is there a good way to search the discussions for relevant fragments (single words are often not enough).
It's as searchable as any site; Discourse also has a built-in search.
I am not sure how long discourse promises to preserve discussions. I am a dinosaur and prefer email. Discourse -> email seems to work OK for the python forums I monitor.
I am also on the email train, but I have heard from enough people about their preference for Discourse that I find it compelling. A good example to check out is: https://discuss.python.org/ (Python moved away from a mailing list to Discourse a while ago.) I mentioned to Pamphile and Ralf that, for SciPy, there is one further consideration. If you use discuss.scientific-python.org, SciPy gets its own category and subcategories. If you launch your own entire server, then you get something more like discuss.python.org (you can set your own categories). Personally, I would like to see our entire community come together in one place for discussions (similar to https://forum.image.sc/) , but this is obviously up to each project to decide for themselves. Best regards, Stéfan
- Discord is blocked for me, both web and application; discourse seems "ok" for the site you point to - whitelists/blacklists exist even if you can browse the web - Why don't you just add a read-only mirror for the SciPy mailing list if you really want to use discourse (or whatever) and then add separate channels for the other discussions you want? (looks possible: https://meta.discourse.org/t/creating-a-read-only-mailing-list-mirror/77990 )
On Thu, May 20, 2021, at 12:10, Tyler Reddy wrote:
- Why don't you just add a read-only mirror for the SciPy mailing list if you really want to use discourse (or whatever) and then add separate channels for the other discussions you want? (looks possible: https://meta.discourse.org/t/creating-a-read-only-mailing-list-mirror/77990 )
I think that's the way to do it, yes. Stéfan
I'm also on the email wagon, but it looks like discourse can import a mailing list archive, and if it can be configured to send a email, it may be considered as a modern view on a mailing list. I'm 100% fine with that.
+1 what Serge said, maintaining the existing email workflow would reduce the barrier of entry for me. On Thu, May 20, 2021 at 1:16 PM Stefan van der Walt <stefanv@berkeley.edu> wrote:
On Thu, May 20, 2021, at 12:10, Tyler Reddy wrote:
- Why don't you just add a read-only mirror for the SciPy mailing list if you really want to use discourse (or whatever) and then add separate channels for the other discussions you want? (looks possible: https://meta.discourse.org/t/creating-a-read-only-mailing-list-mirror/77990 )
I think that's the way to do it, yes.
Stéfan
_______________________________________________ SciPy-Dev mailing list SciPy-Dev@python.org https://mail.python.org/mailman/listinfo/scipy-dev
Discourse and emails have the same issue for me that I can't track who said what to whom; for example https://discuss.python.org/t/pep-632-deprecate-distutils-module/5134/4 I spent way too much time following who replied to Matti and then who reacted back etc. (discourse has this weird habit showing the reply both in reply window and in the flow later in the page but maybe that's on me) but moving away from email seems the right thing for me. Especially when a discussion doesn't converge to a point it is just a useless pile of text that promotes misunderstanding as can be seen from many discussion in many places (linux kernel being the notorious) and starts to have those >>>>>>>>>>> trains. I don't mind the next tech though I share the same concern for Slack as mentioned. I still think that github discussions would help a lot in not-so-strategic decisions as I'm seeing it used within the GitHub beta repos. Obvious disclosure, this is my personal view on it for what its worth. I get that there is still a huge dependence on email on different sectors and academia apparently. On Fri, May 21, 2021 at 4:57 PM Nicholas McKibben <nicholas.bgp@gmail.com> wrote:
I'm also on the email wagon, but it looks like discourse can import a mailing list archive, and if it can be configured to send a email, it may be considered as a modern view on a mailing list. I'm 100% fine with that.
+1 what Serge said, maintaining the existing email workflow would reduce the barrier of entry for me.
On Thu, May 20, 2021 at 1:16 PM Stefan van der Walt <stefanv@berkeley.edu> wrote:
On Thu, May 20, 2021, at 12:10, Tyler Reddy wrote:
- Why don't you just add a read-only mirror for the SciPy mailing list if you really want to use discourse (or whatever) and then add separate channels for the other discussions you want? (looks possible: https://meta.discourse.org/t/creating-a-read-only-mailing-list-mirror/77990 )
I think that's the way to do it, yes.
Stéfan
_______________________________________________ SciPy-Dev mailing list SciPy-Dev@python.org https://mail.python.org/mailman/listinfo/scipy-dev
_______________________________________________ SciPy-Dev mailing list SciPy-Dev@python.org https://mail.python.org/mailman/listinfo/scipy-dev
On Thu, May 20, 2021 at 11:13:51AM -0700, Stefan van der Walt wrote:
On Thu, May 20, 2021, at 04:26, Matti Picus wrote:
Among criteria for a community forum might be:
- permanence: can we find a discussion in ten years when we went to figure out what led to a particular decision
That's certainly the idea. The server is hosted by NumFOCUS, which should give it some permanency. We have backups set up to Backblaze, and someone from SciPy will get credentials to that so SciPy can extract their data at any time.
- transparency: will the discussions be archived in a public manner with little need for logins or signups
Yes, the discussions can be browsed (but not added to) without logging in.
- searchability: is there a good way to search the discussions for relevant fragments (single words are often not enough).
It's as searchable as any site; Discourse also has a built-in search.
I am not sure how long discourse promises to preserve discussions. I am a dinosaur and prefer email. Discourse -> email seems to work OK for the python forums I monitor.
I am also on the email train, but I have heard from enough people about their preference for Discourse that I find it compelling. A good example to check out is:
(Python moved away from a mailing list to Discourse a while ago.)
I mentioned to Pamphile and Ralf that, for SciPy, there is one further consideration. If you use discuss.scientific-python.org, SciPy gets its own category and subcategories. If you launch your own entire server, then you get something more like discuss.python.org (you can set your own categories).
Personally, I would like to see our entire community come together in one place for discussions (similar to https://forum.image.sc/) , but this is obviously up to each project to decide for themselves.
I'm also on the email wagon, but it looks like discourse can import a mailing list archive, and if it can be configured to send a email, it may be considered as a modern view on a mailing list. I'm 100% fine with that.
On Thu, May 20, 2021 at 11:40:28AM +0200, Pamphile Roy wrote:
Let us know what you think.
As someone who was hit by the DMARC hammer on the mailing list, a good web forum might lower the barrier to entry. One show-stopper I've always found with the various bulletin boards is the inability to get an overview of the reply tree (or DAG) for a given topic: Ensuring that it's easy to follow a particular thread. Mailman does this okay-ish, but from a quick attempt, Discourse seems to offer limited improvement over e.g. phpBB, while e.g. the comment sections on Reddit or Hacker News work better. This is getting off-topic, but I wonder if there's a service that offers bulletin board style topics a la Discourse but with comment sections a la Reddit and modern commenting facilities (Markdown/non-text content/...) a la Slack? Best, Søren
participants (15)
-
Andras Deak -
Eric Larson -
Evgeni Burovski -
Hameer Abbasi -
Ilhan Polat -
Matthew Brett -
Matti Picus -
Nicholas McKibben -
Pamphile Roy -
Ralf Gommers -
Romain Jacob -
Serge Guelton -
Stefan van der Walt -
Søren Fuglede Jørgensen -
Tyler Reddy