Autumn update
Published on October 15, 2024 by Florian Verdonck
Hi folks,
It's been a while since our last update here on Open Collective. We would like to thank our backers for your continued support! Our goal has always been to be transparent about the funds we have collected. This update is part of that commitment, and we want to provide you with some honest insights into Amplifying F#.
Our aim has always been to spend the limited funds we have efficiently, using them to benefit the community in ways they may not even realize they need. We don’t want to hoard money, and it may seem that way in recent months. Our last effort was in June, and from the outside, it may look like we are no longer actively pursuing our Open Collective plans. Rest assured, this is not the case, but we have encountered some setbacks in the past few months.
Behind closed doors, we attempted to set up two contracting gigs to enhance the F# ecosystem. Unfortunately, neither came to fruition due to personal time constraints. No one is to blame; sometimes things just don’t work out, and perhaps they can be revisited in the future.
To provide more detail, we tried to create a new Learn F# tool in the browser. Our plan was to establish a solid foundation for the community to easily share knowledge — a one-stop shop for newcomers to find everything they need about F# and the wider ecosystem.
Another idea we had was to improve the developer experience for newcomers in VSCode. We wanted to provide better guidance for users who may not have the right version of .NET installed or who encounter issues when project cracking fails. We believe newcomers to F# will likely attempt to use VSCode first and may give up if the tooling isn’t responsive. That first contact experience is crucial, and we are keen to improve it.
Aside from our unsuccessful attempts, the core team has been busy with life in general. This is why we previously posted about looking for new contributors (https://amplifyingfsharp.io/join-the-core/). So far, we haven’t received any responses. Please share this message within your network, as we can really use the extra help!
Overall, we are still able to keep the ship running. At a slower pace, we continue to host our online sessions (the next one is on https://amplifyingfsharp.io/sessions/2024/10/18/). We’re managing okay, just not in a "let's conquer the world" mode.
If you ever want to reach out to us about anything, please contact [email protected]. We are always happy to chat via a call!
Amplified greetings,
David, Edgar, Florian & Jimmy
It's been a while since our last update here on Open Collective. We would like to thank our backers for your continued support! Our goal has always been to be transparent about the funds we have collected. This update is part of that commitment, and we want to provide you with some honest insights into Amplifying F#.
Our aim has always been to spend the limited funds we have efficiently, using them to benefit the community in ways they may not even realize they need. We don’t want to hoard money, and it may seem that way in recent months. Our last effort was in June, and from the outside, it may look like we are no longer actively pursuing our Open Collective plans. Rest assured, this is not the case, but we have encountered some setbacks in the past few months.
Behind closed doors, we attempted to set up two contracting gigs to enhance the F# ecosystem. Unfortunately, neither came to fruition due to personal time constraints. No one is to blame; sometimes things just don’t work out, and perhaps they can be revisited in the future.
To provide more detail, we tried to create a new Learn F# tool in the browser. Our plan was to establish a solid foundation for the community to easily share knowledge — a one-stop shop for newcomers to find everything they need about F# and the wider ecosystem.
Another idea we had was to improve the developer experience for newcomers in VSCode. We wanted to provide better guidance for users who may not have the right version of .NET installed or who encounter issues when project cracking fails. We believe newcomers to F# will likely attempt to use VSCode first and may give up if the tooling isn’t responsive. That first contact experience is crucial, and we are keen to improve it.
Aside from our unsuccessful attempts, the core team has been busy with life in general. This is why we previously posted about looking for new contributors (https://amplifyingfsharp.io/join-the-core/). So far, we haven’t received any responses. Please share this message within your network, as we can really use the extra help!
Overall, we are still able to keep the ship running. At a slower pace, we continue to host our online sessions (the next one is on https://amplifyingfsharp.io/sessions/2024/10/18/). We’re managing okay, just not in a "let's conquer the world" mode.
If you ever want to reach out to us about anything, please contact [email protected]. We are always happy to chat via a call!
Amplified greetings,
David, Edgar, Florian & Jimmy