Discussion: Organization of PurelyFunctional Event

[Daniel-Boll]

As we begin planning for the upcoming PurelyFunctional event, there are a few important questions we need to address regarding the organization of the event. I've created this issue to start a discussion around the following topics:

• Should we keep the event closed to only our group, or should we consider opening it up to other participants who are interested in functional programming?
• Which project format should we adopt for the event? Should we pursue a shared project that everyone contributes to, individual projects that participants work on independently, or group projects that participants collaborate on in teams?
• Should we explore the use of the Rust programming language for our projects during the event? Rust has been gaining popularity in the functional programming community for its emphasis on performance and safety, and could be an interesting language to explore in the context of the event. Besides it's cool 🦀.
• Should we consider changing the name of the event? The current name, PurelyFunctional, is subject to change if we feel that a different name would better reflect the goals and themes of the event.

I welcome everyone to share their thoughts and ideas on these topics, as well as any other suggestions for the organization of the PurelyFunctional event. Let's work together to make this a successful and rewarding event for all participants.

Best regards,
Daniel Boll. 🎴

[Mulling]

Open it to everyone, keep the name, and use rust.

[Daniel-Boll]

Open it to everyone

Thanks for your input! Opening the event to a wider audience could certainly help us reach more people and foster a stronger community around functional programming. But, considering this possibility, what would the scope be? UNIOESTE? Cascavel? Brazil? World-wide? Should we publish it in Facebook groups or something?

and use rust.

That's a valid input. While Rust is a powerful language with many benefits, it may not be the best fit for every project or use case. Before we choose a language, we should consider the goals and format of the event, as well as the interests and expertise of our participants. That said, Rust is certainly worth considering as a language option, as it has been gaining popularity in the functional programming community for its safety and performance features.

In addition, I think it would be helpful to decide on the project format before selecting a language. If we decide to work on individual projects, for example, participants could choose the language they feel most comfortable with. On the other hand, if we choose a shared project or group project format, we could choose a language that is well-suited to that particular project.

---

Thanks again for your feedback, let's keep discussing and make sure we choose the best options for the event!

Best regards,
Daniel Boll. 🎴

[Mulling]

But, considering this possibility, what would the scope be? UNIOESTE? Cascavel? Brazil? World-wide? Should we publish it in Facebook groups or something?

Yes.

If we decide to work on individual projects, for example, participants could choose the language they feel most comfortable with. On the other hand, if we choose a shared project or group project format, we could choose a language that is well-suited to that particular project.

Individual and shared at the same time, make groups IDC, as we did in LambdaPET 2021.

[Tomcat-42]

Should we keep the event closed to only our group, or should we consider opening it up to other participants who are interested in functional programming?

We definitely should open the event. About the scope, I think we should first ask UNIOESTE community first for some feedback and get the number of interested people. If we got a low number then we consider opening to the external people. I said that because we haven't much experience in organizing somewhat "largy" events.

Which project format should we adopt for the event? Should we pursue a shared project that everyone contributes to, individual projects that participants work on independently, or group projects that participants collaborate on in teams?

In my opinion we should adopt the teams projects format ( one or more person per project).

Should we explore the use of the Rust programming language for our projects during the event? Rust has been gaining popularity in the functional programming community for its emphasis on performance and safety, and could be an interesting language to explore in the context of the event. Besides it's cool crab.

Despite loving rust, I dont think that We should limit the event to that. Despite being a very powerful lang with a lot of functional features, My opinion is that in a PurelyFunctional context Rust isnt the best option(e.g. no closure recursion ).

Should we consider changing the name of the event? The current name, PurelyFunctional, is subject to change if we feel that a different name would better reflect the goals and themes of the event.

I like that name,

[]'s

[Daniel-Boll]

Dear colleagues,

I would like to propose that we organize a meeting to discuss and define a clear roadmap for our project. This will help us stay focused and ensure that we are all working towards the same goals.

To make scheduling easier, I suggest we use When2Meet, a user-friendly online tool that allows us to see everyone's availability and choose a time that works for everyone. Please follow this link (https://www.when2meet.com/?19003966-ubWaS) to access the When2Meet page.

I look forward to seeing you all at the meeting and working together to achieve our project objectives.

Best regards,
Daniel Boll 🎴

[Mulling]

I think we should also try to pick up some of the things we left with ls-g.

[Daniel-Boll]

Wdym?

Best regards,
Daniel Boll 🎴

[Mulling]

LINUX2