Following the Croatia All Hands Nim session a few CCs have expressed the desire to establish a regular technical forum where Nim developers on IFT teams can share knowledge, troubleshoot issues, discuss roadmap priorities, and collaborate on technical initiatives.
Format
Frequency: Bi-monthly (once every two months), beginning around mid-June
Thanks so much @chair !
Let me suggest another possible structure
100% agree will Benefits/Implementation sections
For each participating project, we may have the following:
As per Jarrad’s all hands presentation, developers and contributors become the key metrics to track.
When considering contributor onboarding, the usage of Nim language needs to be taken in account due to its limited popularity. Hence, it becomes our mandate to ensure that contributors onboarding in the Waku ecosystem, are easily onboarded in the Nim ecosystem too. This needs to go beyond onboarding docs for core contributors (remember when I say those should be public?). It’s onboarding docs for everyone.
Thus, I suggest to encompass this nim forum initiative in a bigger initiative. I also believe that the nwaku team has now acquired enough expertise to drive said initiative.
Here is a wall of ideas. We can prioritize what we think would make most impact first, and for the Waku team to commit to those with clear ownership.
Fostering the Nim Community
To foster an inclusive environment where nim developers of all skill levels can connect, collaborate, and grow together; by sharing knowledge, promoting best practices, building and improving tools and libraries to grow the Nim ecosystem beyond IFT.
Initiatives
Regular call meet-up: as defined in OP post.
Regular “week in ethereum” style news
Anything interesting in Nim seen this month
Nim core merged PRs or release
Popular (IFT or not) lib release
Conference, talks (heard nim was the subject of several talks at recent opensource conference)
Including interesting IFT related news. Ie, nwaku c-binding achievement, some interesting merged PR in our libs, etc. which does mean asking Codex, Logos core, Nimbus about cool stuff they did.
Maintain IFT-wide nim guideline, consult teams to get input, update it
Hi guys, awesome Idea. I banged my head a few months back on how to help some of the new joiners prepare for their “first date” with Nim. I tried to put something together with suggested sources and to manage expectations. Unsure of how helpful it is/was, leaving it here for you to see.
It would be awesome if we could have everything in one place, as suggested - Maintain IFT-wide nim guideline. Maybe the “style guide” is a good space to repurpose and use. These are just my two non-dev cents. I’m happy to get involved and help with anything you need.
+1 to use the style guide for this purpose - it was created with this in mind and the idea of having a PR process for it is also to ensure the quality of the content - the aim is for the guide to be relevant also to people outside of the org, much like the google style guides are often referenced by others that don’t want to write their own.
Eventually I’ve also wanted to add a section not unlike the rustonomicon that explains in-depth topics rather than just style items.
My recommendation would also be to liberal with what’s included in the style guide - should something grow large enough that it becomes its own topic, it can easily be split out in the future (this is for example why the language interop chapters where placed there, rather than a separate book - to ease maintenance).
I’m happy to help in editorial and technical review, though at some point this is also something that we should create a council for - ie 2-3 developers that edit the recommendation in the guide and that have a smaller set of agreed core principles from which they work and according to which recommendations can be formed.
