FLR
Communication strategy for FLR #2
Replies: 18 comments 2 replies
-
|
Hi Iago, Thanks for starting this discussion. At the ICES MSE training course last week, we used FLR and possibly exposed FLR to a broader audience than usual. There, we also promoted the two ways of interacting with FLR you mentioned: GitHub issues and directly contacting developers (but being considerate of limited availability for support). I think using GitHub as a platform for support and documentation will not stop people from using FLR. At the course, we also saw that some people had never used GitHub before but were willing to sign up to get access to documentation. One issue that keeps coming back is that changes of FLR packages can break code or cause incompatibilities between FLR packages. This can even affect some of the FLR tutorials on flr-project.org. I would be happy to support FLR more here on GitHub or outside if required. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the feedback. On the second point, we could work on being a bit more careful when updating or extending packages, but we are doing research, so code is bound to change, for the better. Maybe a more complete set of tests on the main packages could help too. We could also help users making use of different ways of keeping packages associated with a project. I have turned it into an issue #3 for those interested. |
Beta Was this translation helpful? Give feedback.
-
|
would this help? https://datacolada.org/95
Laurie
…On 02/09/2021 09:48, Simon Fischer wrote:
Hi Iago,
Thanks for starting this discussion.
At the ICES MSE training course last week, we used FLR and possibly
exposed FLR to a broader audience than usual. There, we also promoted
the two ways of interacting with FLR you mentioned: GitHub issues and
directly contacting developers (but being considerate of limited
availability for support).
I think using GitHub as a platform for support and documentation will
not stop people from using FLR. At the course, we also saw that some
people had never used GitHub before but were willing to sign up to get
access to documentation.
One issue that keeps coming back is that changes of FLR packages can
break code or cause incompatibilities between FLR packages. This can
even affect some of the FLR tutorials on flr-project.org.
I would be happy to support FLR more here on GitHub or outside if
required.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAM2VJYPTOV7VXAEHSVPRFDT7426XANCNFSM5DDNTIUA>.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Beta Was this translation helpful? Give feedback.
-
|
Hi Iago,
Great you are initiating this communication.
I would be happy to tackle updating and extending the FLR-Project
tutorials, eg mse and some of the recent evolutions in FLBRP.
A comprehensive set of tests would certainly be very beneficial for
advanced users at least. I can offer support to review existing ones.
Another useful tool to get more people started would be a FLCore 'Cheat
Sheet' and some sort of map of FLCore functions 'where is what'. I keep
stumbling over useful FLCore functions, often wishing I'd been aware of
them earlier.
Cheers
Henning
…On Thu, Sep 2, 2021, 23:32 Iago Mosqueira ***@***.***> wrote:
Thanks for the feedback. On the second point, we could work on being a bit
more careful when updating or extending packages, but we are doing
research, so code is bound to change, for the better. Maybe a more complete
set of tests on the main packages could help too.
We could also help users making use of different ways of keeping packages
associated with a project. I have turned it into an issue #3
<#3> for those interested.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2 (reply in thread)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADSPQOIEIT27LI5IIZ2CYELT77UOPANCNFSM5DDNTIUA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Beta Was this translation helpful? Give feedback.
-
|
Hi All,
All the best, |
Beta Was this translation helpful? Give feedback.
-
|
Added a new issue linked to the work of a communication manager #4 . |
Beta Was this translation helpful? Give feedback.
-
|
Hi Iago et al. I think this discussion is a great start to share the load and information amongst the community.
I was wondering if we should try and setup a Workshop in Q1 of 2021 to discuss issues arising from this discussion in person (hopefully) or virtually. I would be ok with trying to organise that workshop. /C |
Beta Was this translation helpful? Give feedback.
-
|
Hi Iago, I'm also interested in helping. I don't know how much time I can invest in this but I will be happy to support in different tasks if time allows. Cheers, Ale |
Beta Was this translation helpful? Give feedback.
-
|
Ciao ragazzi,
More than happy to help. Count me in.
Best
EJ
…On 09/03/2021 10:15, Alessandro Orio wrote:
Hi Iago,
I'm also interested in helping. I don't know how much time I can
invest in this but I will be happy to support in different tasks if
time allows.
Cheers,
Ale
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAC7BPYUU65B7SRIKD6PBU3UAB73BANCNFSM5DDNTIUA>.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Beta Was this translation helpful? Give feedback.
-
|
Hi Iago, |
Beta Was this translation helpful? Give feedback.
-
|
Hi Iago
Am more than happy to help, especially with tutorial side of things, if needed.
Thanks
José
From: Iago Mosqueira ***@***.***>
Sent: 31 August 2021 08:02
To: flr/FLR ***@***.***>
Cc: Jose De Oliveira (Cefas) ***@***.***>; Mention ***@***.***>
Subject: [flr/FLR] Communication strategy for FLR (#2)
Communication across the FLR community has been generally patchy, specially once the FLR mailing list fell silent. I suggest a quick discussion on the strategies and tools we could use to establish a richer dialogue among users and developers.
At the moment we have:
* Github issues for package bugs, requests and questions. This works well, although the number of issues raised is quite low. Is the github-based interface not ideal for more novice users?
* Direct email contact, either to flr-team or to an individual developer. This is not ideal, but again the number of messages is low, so it is not a problem. Messages of general interest could be converted into github issues on the relevant package.
What other ways could we establish to build up the interaction in the FLR community?
* This new repository could be used to host general documentation and this discussion forum, as a way of encouraging a wider discussion on the future development of FLR and FLR packages.
* Each FLR release could have a minimal set of notes, mostly taken from the github logs and the NEWS.md files, listing changes and additions to the packages, maybe with at least the examples added in the documentation.
* Any other ideas?
A more successful community requires some effort, so it would be necessary for one or two people to take on the role of actively taking care of this side of the project. This should be a light task, but obviously with little academic impact. Any volunteers?
PS: Tagging here a number of people, based on a quick check of their recent presence on the FLR repositories, to get their attention pointed here. Feel free to bring in anybody that could be willing to take part in this discussion or play a role in the communication side of FLR.
@ejardim<https://github.com/ejardim> @dorleta<https://github.com/dorleta> @laurieKell<https://github.com/laurieKell> @colinpmillar<https://github.com/colinpmillar> @AgurtzaneUrtizberea<https://github.com/AgurtzaneUrtizberea> @brune001<https://github.com/brune001> @jaado<https://github.com/jaado> @JanJaapPoos<https://github.com/JanJaapPoos> @michaelgras<https://github.com/michaelgras> @mintoc<https://github.com/mintoc> @niknikos<https://github.com/niknikos> @Henning-Winker<https://github.com/Henning-Winker> @shfischer<https://github.com/shfischer> @ChrKo1<https://github.com/ChrKo1> @marchtaylor<https://github.com/marchtaylor> @aleorio<https://github.com/aleorio>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#2>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABXGT7I42FWNLWMBRLVC25TT7R45RANCNFSM5DDNTIUA>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
…________________________________
This email and any attachments are intended for the named recipient only. Its unauthorised use, distribution, disclosure, storage or copying is not permitted. If you have received it in error, please destroy all copies and notify the sender. In messages of a non-business nature, the views and opinions expressed are the author's own and do not necessarily reflect those of Cefas. Communications on Cefas’ computer systems may be monitored and/or recorded to secure the effective operation of the system and for other lawful purposes. All messages sent and received by the Centre for Environment, Fisheries and Aquaculture Science may be monitored in line with relevant UK legislation . <https://www.gov.uk/government/organisations/centre-for-environment-fisheries-and-aquaculture-science/about/personal-information-charter>
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks so much for the feedfback, and sorry it has taken so long to come back to his. I have started contacting some of you individually about taking care of particular issues or areas, but if anybody else has something in mind, or wants to get some suggestion, drop me a line. Would a 1-2 day FLR meeting, maybe towards the end of Q1 or in Q2 of 2022, work for most of you? I fear it will have to be electronic, but maybe with sufficient exchange before hand it could work. Mostly to discuss strategy and ideas, plus iron out team structure and workflow (who does what and how). |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Hi Iago and All, |
Beta Was this translation helpful? Give feedback.
-
|
Count me in. I am interested in capacity limited applications.
Laurie
…On 07/01/2022 11:53, Iago Mosqueira wrote:
Thanks so much for the feedfback, and sorry it has taken so long to
come back to his.
I have started contacting some of you individually about taking care
of particular issues or areas, but if anybody else has something in
mind, or wants to get some suggestion, drop me a line.
Would a 1-2 day FLR meeting, maybe towards the end of Q1 or in Q2 of
2022, work for most of you? I fear it will have to be electronic, but
maybe with sufficient exchange before hand it could work. Mostly to
discuss strategy and ideas, plus iron out team structure and workflow
(who does what and how).
—
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAM2VJ77OORTXFD25EKQFDLUU3H45ANCNFSM5DDNTIUA>.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Hi Iago - sure, I would be happy to participate. Q1 is generally less crowded for me. -Marc |
Beta Was this translation helpful? Give feedback.
-
|
Ciao, count me in. Best. EJ
…On Sun, 9 Jan 2022 at 14:10, Marc Taylor ***@***.***> wrote:
Hi Iago - sure, I would be happy to participate. Q1 is generally less
crowded for me. -Marc
—
Reply to this email directly, view it on GitHub
<#2 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAC7BP7YPONPKRDTHEG5BDDUVGCK7ANCNFSM5DDNTIUA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
I'm also in. |
Beta Was this translation helpful? Give feedback.
-
|
I am also up for it!
/C
…On Mon, 10 Jan 2022 at 09:00, Alessandro Orio ***@***.***> wrote:
I'm also in.
Cheers,
Ale
—
Reply to this email directly, view it on GitHub
<#2 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACBMRAVZPJX6QDAAPWU47SDUVKGZBANCNFSM5DDNTIUA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Dr. Christoph Konrad
email: ***@***.***
skype: christoph.konrad.101
|
Beta Was this translation helpful? Give feedback.
-
|
I'm happy to be involved as much as I can (a combination of the 11 hour
time difference and imminent paternity leave might make it tricky...)
Cheers
Finlay
On Mon, Jan 10, 2022 at 8:33 PM Christoph Konrad ***@***.***>
wrote:
… I am also up for it!
/C
On Mon, 10 Jan 2022 at 09:00, Alessandro Orio ***@***.***>
wrote:
> I'm also in.
> Cheers,
> Ale
>
> —
> Reply to this email directly, view it on GitHub
> <#2 (comment)>, or
> unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/ACBMRAVZPJX6QDAAPWU47SDUVKGZBANCNFSM5DDNTIUA
>
> .
> Triage notifications on the go with GitHub Mobile for iOS
> <
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
>
> or Android
> <
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub
>.
>
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
--
Dr. Christoph Konrad
email: ***@***.***
skype: christoph.konrad.101
—
Reply to this email directly, view it on GitHub
<#2 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKB7FWT6QVFIJNNQZHLCXLUVKRXBANCNFSM5DDNTIUA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Communication across the FLR community has been generally patchy, specially once the FLR mailing list fell silent. I suggest a quick discussion on the strategies and tools we could use to establish a richer dialogue among users and developers.
At the moment we have:
What other ways could we establish to build up the interaction in the FLR community?
A more successful community requires some effort, so it would be necessary for one or two people to take on the role of actively taking care of this side of the project. This should be a light task, but obviously with little academic impact. Any volunteers?
PS: Tagging here a number of people, based on a quick check of their recent presence on the FLR repositories, to get their attention pointed here. Feel free to bring in anybody that could be willing to take part in this discussion or play a role in the communication side of FLR.
@ejardim @dorleta @laurieKell @colinpmillar @AgurtzaneUrtizberea @brune001 @jaado @JanJaapPoos @michaelgras @mintoc @niknikos @Henning-Winker @shfischer @ChrKo1 @marchtaylor @aleorio
Beta Was this translation helpful? Give feedback.
All reactions