├── 2022 ├── README.md ├── schedule.md ├── moderators.md ├── cfp.md └── submission.md ├── 2023 ├── readme.md └── submission.md ├── 2024 ├── readme.md └── submission.md ├── readme.md ├── LICENSE └── submission.md /2024/readme.md: -------------------------------------------------------------------------------- 1 | # nim-fosdem 2 | 3 | repo to collect material for Nim Devroom submission at [Fosdem](https://fosdem.org). 4 | 5 | Current material is for [Fosdem2024](https://fosdem.org/2024/). See folders [2022](2022/README.md) and [2023](2023/readme.md) for previous years. 6 | 7 | ## Timeline 8 | 9 | * [Sep 29] [Call for Devrooms](https://fosdem.org/2024/news/2023-09-29-devrooms-cfp/) published 10 | * [Oct 16 Mon] Deadline for devroom proposal 11 | * [Oct 31] accepted developer rooms announced 12 | * [Nov 5 (or earlier)] developer rooms issue Calls for Participation 13 | * [Dec 15 (or earlier)] developer rooms publish complete schedules 14 | * **Event:** Saturday 3rd and Sunday 4th February 2024 in Brussels, Belgium 15 | 16 | ## Submission 17 | 18 | See [submission.md](submission.md) 19 | 20 | * This year is in person like last year 21 | * We should ask for half a day 22 | -------------------------------------------------------------------------------- /readme.md: -------------------------------------------------------------------------------- 1 | # nim-fosdem 2 | 3 | repo to collect material for Nim Devroom submission at [Fosdem](https://fosdem.org). 4 | 5 | Current material is for [Fosdem2025](https://fosdem.org/2025/). See folders [2022](2022/README.md), [2023](2023/readme.md), and [2024](2024/readme.md) for previous years. 6 | 7 | ## Timeline 8 | 9 | * [Sep 23] [Call for Devrooms](https://fosdem.org/2025/news/2024-09-23-devrooms-cfp/) published 10 | * [Oct 10 Thu] Deadline for devroom proposal 11 | * [Oct 21] accepted developer rooms announced 12 | * [Oct 30 (or earlier)] developer rooms issue Calls for Participation 13 | * [Dec 15 (or earlier)] developer rooms publish complete schedules 14 | * **Event:** Saturday 1st and Sunday 2nd February 2025 in Brussels, Belgium 15 | 16 | ## Submission 17 | 18 | See [submission.md](submission.md) 19 | 20 | * This year is in person like last year 21 | * We should ask for half a day 22 | -------------------------------------------------------------------------------- /2023/readme.md: -------------------------------------------------------------------------------- 1 | # nim-fosdem 2 | 3 | repo to collect material for Nim Devroom submission at [Fosdem](https://fosdem.org). 4 | 5 | Current material is for [Fosdem2023](https://fosdem.org/2023/). See folder [2022](2022/README.md) for previous year. 6 | 7 | ## timeline 8 | 9 | * [Sep 29] [call for devrooms](https://fosdem.org/2023/news/2022-09-29-call_for_devrooms/) published 10 | * [Oct 17] [forum post](https://forum.nim-lang.org/t/9534#62632) for visibility 11 | * [Oct 18 Tue] deadline for devroom proposal 12 | * [Oct 31] accepted developer rooms announced 13 | * [Nov 5 (or earlier)] developer rooms issue Calls for Participation 14 | * [Dec 15 (or earlier)] developer rooms publish complete schedules 15 | * **Event:** Saturday 4th and Sunday 5th February 2023 in Brussels, Belgium 16 | 17 | ## submission 18 | 19 | see [submission.md](submission.md) 20 | 21 | * this year is in person 22 | * we should ask for half a day 23 | -------------------------------------------------------------------------------- /2022/README.md: -------------------------------------------------------------------------------- 1 | # fosdem2022 2 | 3 | repo to work towards a Nim Devroom at fosdem2022: https://fosdem.org/2022/schedule/track/nim_programming_language/ 4 | 5 | timeline: 6 | 7 | * [Nov 10-14] interest about this was raised first in discord/irc and then in this forum post https://forum.nim-lang.org/t/8621 8 | * [Nov 14-15] work on submitting a proposal was finalized as in [submission.md](submission.md) 9 | * [Nov 15-Dec 2] proposal of Nim was accepted and Call For Proposal officially published ([forum post](https://forum.nim-lang.org/t/8671#56429) + [nim blog post](https://nim-lang.org/blog/2021/12/02/fosdem-2022-cfp.html)) 10 | * [Dec 2-23] community proposed talks 11 | * [Dec 23-31] proposed talks reviewed and accepted 12 | * [Jan 1-22] Video prepared by speakers and submitted (some late submissions and one cancellation) 13 | * [Jan 22-Feb 3] Reviewing videos and preparing for event. [final schedule](schedule.md) adjusted and roles for host/video reviewer assigned (see [moderators.md](moderators.md)) 14 | * [Feb 4] _todo_ blogpost to publicize the event? 15 | * [Feb 5] _todo_ running the event! 16 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2021 Pietro Peterlongo 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. 22 | -------------------------------------------------------------------------------- /2022/schedule.md: -------------------------------------------------------------------------------- 1 | ## schedule 2 | 3 | this is a draft schedule prepared before finalizing the schedule in FOSDEM's pentabarf system. The official schedule will be the one in pentabarf. 4 | At the end of every talk there is a 5' Q&A session where participants can interact with the speaker (which should be available). 5 | 6 | **Note that all times are Brussels Time, CET (=UTC+1)** 7 | 8 | | Who | What | Video duration | Total Duration | Q&A duration (approx) | When | 9 | |-----|------|----------|---|-------------|---| 10 | | araq | Nim concurrency Past, Present and Future | 25:34 | 35' | 9' |12:30 - 13:05 | 11 | | pmunch | Next generation micro-controller programming | 29:38 | 35' | 5' | 13:05 - 13:40 | 12 | | arthurrasmusson | LibVF.IO: vGPU & SR-IOV on Consumer GPUs using Nim | 31:29 | 40' | 9' | 13:40 - 14:20 | 13 | | rlipsc | Polymorph: a compile time approach to entity-component-systems in Nim | _up to 35'_ | 40' | | 14:20 - 15:00 | 14 | | scott wadden | Potato Zombies - Helping a 6 year old build a 3d game using Enu and Nim | 36:26 | 45' | 9' | 15:00 - 15:45 | 15 | | oakes | Pararules - A Nim rules engine for reactive programs and games | 36:04 | 45' | 9' | 15:45 - 16:30 | 16 | | ayman-albaz | From Python to Nim, a preliminary introduction to performance optimization | 25:00 | 30' | 5' | 16:30 - 17:00 | 17 | | treeform | Real World Metaprogramming with Nim | 31:16 | 40' | 9' | 17:00 - 17:40 | 18 | -------------------------------------------------------------------------------- /2022/moderators.md: -------------------------------------------------------------------------------- 1 | This is the finalized list of moderators/host/reviewer as discussed in https://github.com/pietroppeter/fosdem2022/issues/9 2 | 3 | | Who | What | Hosts | Video Reviewer 4 | |-----|------|----------|----------| 5 | | araq | Nim concurrency Past, Present and Future | @dom96 | @pietroppeter | 6 | | pmunch | Next generation micro-controller programming | @pietroppeter | @dom96 | 7 | | arthurrasmusson | LibVF.IO: vGPU & SR-IOV on Consumer GPUs using Nim | @dom96 | @pietroppeter | 8 | | rlipsc | Polymorph: a compile time approach to entity-component-systems in Nim | @pietroppeter | @dom96 | 9 | | scott wadden | Potato Zombies - Helping a 6 year old build a 3d game using Enu and Nim | @moigagoo | @pmunch | 10 | | oakes | Pararules - A Nim rules engine for reactive programs and games | @pietroppeter | @dom96 | 11 | | ayman-albaz | From Python to Nim, a preliminary introduction to performance optimization | @PMunch | @moigagoo | 12 | | pietroppeter | State of Scientific Computing in Nim 2022 | @moigagoo | @PMunch | 13 | | treeform | Real World Metaprogramming with Nim | @PMunch | @moigagoo | 14 | 15 | So under this list, the responsibilities are as follows: 16 | 17 | * Video Reviewer - The person who is expected to review the video. 18 | * Host - The person that will moderate the live session, hosting the Q&A and moderating the chat. 19 | 20 | In terms of FOSDEM's roles this means we will all still be "coordinators" of every talk (which should give us all the ability to moderate at any time in case it's needed). 21 | The "host" role was added for each person that is hosting each talk. 22 | 23 | ### video review links and instructions 24 | 25 | We need to watch the talks and check that they are okay. This is mainly checking for: 26 | - Audio issues 27 | - Video issues (ie. if the video suddenly goes black or distorted) 28 | - Content violation (just make sure no-one have snuck porn or copyrighted material into a talk) 29 | 30 | To review a video you simply go to the page for the event you are reviewing: 31 | - [HPC from Python to Nim](https://penta.fosdem.org/submission/FOSDEM22/event/12770) 32 | - [Nim concurrency](https://penta.fosdem.org/submission/FOSDEM22/event/12796) 33 | - [Next generation micro-controller programming](https://penta.fosdem.org/submission/FOSDEM22/event/12844) 34 | - [State of scientific computing in Nim 2022](https://penta.fosdem.org/submission/FOSDEM22/event/12845) 35 | - [Pararules](https://penta.fosdem.org/submission/FOSDEM22/event/12840) 36 | - [LibVF.IO: vGPU & SR-IOV on Consumer GPUs using Nim](https://penta.fosdem.org/submission/FOSDEM22/event/12538) 37 | - [Polymorph: a compile time approach to entity-component-systems in Nim](https://penta.fosdem.org/submission/FOSDEM22/event/12839) 38 | - [Nim Metaprogramming in the real world](https://penta.fosdem.org/submission/FOSDEM22/event/12500) 39 | - [Potato Zombies](https://penta.fosdem.org/submission/FOSDEM22/event/12849) 40 | 41 | Then scroll down to the video section, it will either be under the "Review" button or the "Final version" button (the uploader can also review their talk, this is a system that was originally built for reviewing the recording of the live talks which you where expected to do yourself as a speaker). If the video looks good make sure it is accepted and available under the "Final version" button. If the video has problems we need to contact the speaker and have them upload a fixed version. 42 | -------------------------------------------------------------------------------- /2022/cfp.md: -------------------------------------------------------------------------------- 1 | # Call for participation - Nim at FOSDEM22 2 | Nim has participated at FOSDEM for a number of years now. In the beginning as a 3 | stand, then as multiple talks across various rooms, and in organising the room 4 | "Minimalistic, Experimental and Emerging Languages devroom" along with other 5 | communites. This year however we are happy to announce that we have our own 6 | developer room! 7 | 8 | ## What is FOSDEM? 9 | FOSDEM is the "Free and Open Source Developers European Meetup". It is an annual 10 | meeting place for developers of free and open source software from across all of 11 | the world, hosted normally in Brussels in Belgium. The event itself is a massive 12 | conference spanning two days with thousands of visitors and hundreds of talks on 13 | various topics. This year, as last year, the conference will be completely 14 | online. 15 | 16 | ## Call for Participation 17 | Since we now have our own room to fill we invite our great community to submit 18 | their talks. The event will be online and all presentations will be pre-recorded, 19 | but you are required to be present during your presentation and for some time 20 | after to answer any questions. This is similar to how we have run NimConf for the 21 | past two years so we have no doubt that this will work very well and that we will 22 | have the same excellent level of quality that we have come to expect from you! 23 | 24 | To submit your talk you will need to create a pentabarf account (if you do not already have one) 25 | and make the submission through the [FOSDEM 26 | pentabarf](https://penta.fosdem.org/submission/) system. 27 | Pentabarf is the official name of the FOSDEM talk submission and management system 28 | (see [beginner's guide](https://medium.com/@maartjeme/beginners-guide-to-pentabarf-78808a1ce5bf)). 29 | Make sure to select "Nim 30 | Programming Language" when submitting (otherwise we will not be able to find it). 31 | 32 | ### What are we looking for? 33 | Pretty much anything related to Nim! From compiler development to projects 34 | written in it, to more generalised topics around Nim and the community. 35 | Inspiration can of course be found in this list of previous FOSDEM talks, along 36 | with our [NimConf 37 | talks](https://www.youtube.com/channel/UCDAYn_VFt0VisL5-1a5Dk7Q): 38 | 39 | - [(2021) Nim meta-programming for 0-cost abstraction on microcontrollers](https://archive.fosdem.org/2021/schedule/event/nimdsl/) 40 | - [(2020) Nim on everything, from microcontrollers to web-sites, C and JS as intermediary languages](https://archive.fosdem.org/2020/schedule/event/nimoneverything/) 41 | - [(2020) Move semantics in Nim, Deterministic Memory Management](https://archive.fosdem.org/2020/schedule/event/nimmovesemantics/) 42 | - [(2020) Designing an ultra low-overhead multithreading runtime for Nim, Exposing fine-grained parallelism for 32+ cores hardware via message passing](https://archive.fosdem.org/2020/schedule/event/nimultralowoverheadruntime/) 43 | - [(2020) Async await in Nim, A demonstration of the flexibility metaprogramming can bring to a language](https://archive.fosdem.org/2020/schedule/event/asyncawaitnim/) 44 | - [(2019) Metaprogramming with Nim](https://archive.fosdem.org/2019/schedule/event/nim_metaprogramming/) 45 | - [(2019) How to build your own Ethereum client, The development story of Nimbus](https://archive.fosdem.org/2019/schedule/event/nimbus/) 46 | 47 | ### Requirements 48 | To be able to submit a talk you _must_ fulfil these formal requirements: 49 | 50 | - you should target a **talk duration** of 15 or 30 minutes. We are also open to durations up to 45 minutes for talks with a bigger scope, but we would encourage sticking to 15/30 minute durations. 51 | We should be able to accommodate for durations that do not exactly hit the target. 52 | - Be able to pre-record a talk in advance. In order for us to verify the content 53 | all videos must be submitted by January 22nd. 54 | - Since FOSDEM is held during European day hours you need to be available for your 55 | presentation and the ensuing Q&A. 56 | 57 | ### Deadlines 58 | - Submission of talk: Dec 23rd, 2021 59 | - Selected talks announced: Dec 31st 2021 60 | - Conference dates 5 & 6 February 61 | - The Nim language devroom is on the 5th 62 | - Video recording submission: January 22nd 63 | 64 | All deadline times are 23:59 UTC. 65 | 66 | ### Final remarks 67 | 68 | - Make sure to check out the [FOSDEM Code of Conduct](https://fosdem.org/2022/practical/conduct/). 69 | - For any questions about this call for participation you can reach out to us in the [#fosdem channel](https://discord.com/channels/371759389889003530/909464670098833409) on our Nim Discord (also available through Matrix as "[Nim FOSDEM](https://matrix.to/#/#nim-fosdem:matrix.org)"). 70 | -------------------------------------------------------------------------------- /2023/submission.md: -------------------------------------------------------------------------------- 1 | 2 | The details for submission as in: https://submission.fosdem.org/submission/devroom 3 | 4 | todo: 5 | - [ ] decide on which half day (Sat or Sun)? 6 | - [ ] decide if physical only or we would accept also virtual 7 | - [ ] primary and secondary account? 8 | - [ ] other volounters? (add pentabarfs?) 9 | - [ ] review text of submission 10 | 11 | ## Project Details 12 | 13 | **Title of devroom**: Nim Programming Language 14 | 15 | **Elaborate description of proposed devroom (including possible topics)**: 16 | 17 | Nim is a versatile language that can be both compiled to low-level languages 18 | like C/C++/ObjC and to the web-oriented language JavaScript. This, along with 19 | its rich, static type system, optional and tunable GC, and its extensive 20 | meta-programming system, means that the language offers something for everyone. 21 | And it's being used for everything from programming the tiniest 22 | micro-controllers to high-performance applications and even creating rich 23 | interactive websites. Its unique combination of features and the aforementioned 24 | meta-programming makes it feel at home in pretty much every programming niche. 25 | 26 | Looking back at the talks FOSDEM has had about Nim in the past we expect a 27 | varied selection of talks ranging from the design of the language and compiler 28 | itself by the core developers all the way to talk by the many developers who 29 | use Nim for the aforementioned use-cases for such a language. For an example of 30 | talk topics see the talks from previous iterations of the devroom: 31 | - [Schedule of Nim Programming Language devroom at FOSDEM 2022](https://archive.fosdem.org/2022/schedule/track/nim_programming_language/) 32 | - [Schedule of co-organized Declarative and Minimalistic Computing devroom at FOSDEM 2021](https://archive.fosdem.org/2021/schedule/track/declarative_and_minimalistic_computing/) 33 | - [Schedule of co-organized Minimalistic, Experimental, and Emerging Languages devroom at FOSDEM 2020 (physical)](https://archive.fosdem.org/2020/schedule/track/minimalistic_experimental_and_emerging_languages/) 34 | 35 | **Why does it fit FOSDEM?** 36 | 37 | The Nim programming language first saw the light of day in 2008, and has been 38 | developed actively as an open source project ever since. In more recent years 39 | it has reached the milestone 1.0 release in 2019 and version 2.0 is coming 40 | along well. The language has been open source since its very beginning, and is 41 | being developed by a group of volunteers along with a core team of developers 42 | paid by donations from the community. The Nim community itself has 43 | traditionally been very Euro-centric, with most of the core developers and 44 | users from Europe. So FOSDEM has naturally become an annual meeting ground for 45 | Nim users where many have been able to put a face to the nicknames we interact 46 | with every day for the first time. In 2022 we succesfully organized a virtual 47 | devroom dedicated to Nim at Fosdem and we would like to have the opportunity to 48 | go back to meeting at a physical event. 49 | 50 | The Nim community has also organised its own conference (with editions in 2020, 51 | 2021 and an upcoming edition in October 2022) and the people behind this 52 | proposal have already organized a Nim Devroom at FOSDEM 2022 and co-organized 53 | both a virtual and physical room in the past. This makes us confident that the 54 | Nim language devroom at FOSDEM 2023 will be a great success with high quality 55 | talks offering something for everyone, not only existing Nim programmers. 56 | 57 | **Preferred slot**: Half Day, Sunday morning 58 | **Preferred devroom kind**: Physical 59 | 60 | ## Contact Information 61 | 62 | ### Primary contact 63 | 64 | **Pentabarf username of devroom primary**: PMunch 65 | 66 | **First name**: Peter 67 | 68 | **Last name**: Munch-Ellingsen 69 | 70 | **E-mail**: *we can skip this in this repo* 71 | 72 | **Submitter’s affinity to the topic of the devroom**: Long time user and contributor, organizer of various events 73 | 74 | ### Secondary contact 75 | 76 | **First name**: Pietro 77 | 78 | **Last name**: Peterlongo 79 | 80 | **E-mail**: *we can skip this in this repo* 81 | 82 | *(At least the pentabarf username for the secondary contact should be added. If you want to add multiple contacts, write their pentabarf username, one per line.)* 83 | 84 | **Additional pentabarf ids:** 85 | 86 | _none yet_ 87 | 88 | ## Additional information 89 | 90 | **Relevant URLs**: 91 | 92 | - [Nim Devroom at Fosdem 2022](https://archive.fosdem.org/2022/schedule/track/nim_programming_language/) 93 | - [Declarative and Minimalistic Computing devroom at FOSDEM 2021](https://archive.fosdem.org/2021/schedule/track/declarative_and_minimalistic_computing/) 94 | - [Minimalistic, Experimental, and Emerging Languages devroom at FOSDEM 2020 (physical)](https://archive.fosdem.org/2020/schedule/track/minimalistic_experimental_and_emerging_languages/) 95 | - [Nim website](https://nim-lang.org) 96 | - [Nim Conf 2022](https://conf.nim-lang.org/) 97 | - [Nim Conf 2021](https://conf.nim-lang.org/2021/) 98 | - [Nim Conf 2020](https://conf.nim-lang.org/2020/) 99 | 100 | **Special requirements**: 101 | 102 | -------------------------------------------------------------------------------- /2022/submission.md: -------------------------------------------------------------------------------- 1 | 2 | Below are the details we used for submission as in: https://submission.fosdem.org/submission/devroom 3 | 4 | Todo: 5 | 6 | - [x] create room in Matrix/Discord: https://matrix.to/#/#nim-fosdem:matrix.org 7 | - [x] improve description of devroom 8 | - [x] improve why does it fit fosdem 9 | - [x] who is Primary Contact? Dom 10 | - [x] fill in "Submitter’s affinity to the topic of the devroom" for Primary Contact 11 | - [x] who is Secondary Contact? Pmunch 12 | - [x] additional pentabarf ids? ok for now 13 | - [x] more relevant links? nothing more comes to mind 14 | - [x] special requirements? no 15 | - [x] **Submit by 23.59 UTC of Nov 15 2021** 🥳 16 | 17 | ## Project Details 18 | 19 | **Title of devroom**: Nim Programming Language 20 | 21 | **Elaborate description of proposed devroom (including possible topics)**: 22 | 23 | Nim is a versatile language that can be both compiled to low-level languages 24 | like C/C++/ObjC and to the web-oriented language JavaScript. This, along with 25 | it's rich, static type system, optional and tunable GC, and its rich 26 | meta-programming system, means that the language offers something for everyone. 27 | Being used for everything from programming the tiniest micro-controllers to 28 | high-performance applications and even creating rich interactive websites. Its 29 | unique combination of features and the aforementioned meta-programming makes it 30 | feel at home in pretty much every programming niche. 31 | 32 | Looking back at the talks FOSDEM has had about Nim in the past we expect a 33 | varied selection of talks ranging from the design of the language and compiler 34 | itself by core developers all the way to the many aforementioned use-cases for 35 | such a language. Previous FOSDEM talks: 36 | 37 | - [(2021) Nim meta-programming for 0-cost abstraction on microcontrollers](https://archive.fosdem.org/2021/schedule/event/nimdsl/) 38 | - [(2020) Nim on everything, from microcontrollers to web-sites, C and JS as intermediary languages](https://archive.fosdem.org/2020/schedule/event/nimoneverything/) 39 | - [(2020) Move semantics in Nim, Deterministic Memory Management](https://archive.fosdem.org/2020/schedule/event/nimmovesemantics/) 40 | - [(2020) Designing an ultra low-overhead multithreading runtime for Nim, Exposing fine-grained parallelism for 32+ cores hardware via message passing](https://archive.fosdem.org/2020/schedule/event/nimultralowoverheadruntime/) 41 | - [(2020) Async await in Nim, A demonstration of the flexibility metaprogramming can bring to a language](https://archive.fosdem.org/2020/schedule/event/asyncawaitnim/) 42 | - [(2019) Metaprogramming with Nim](https://archive.fosdem.org/2019/schedule/event/nim_metaprogramming/) 43 | - [(2019) How to build your own Ethereum client, The development story of Nimbus](https://archive.fosdem.org/2019/schedule/event/nimbus/) 44 | 45 | **Why does it fit FOSDEM?** 46 | 47 | The Nim programming language first saw the light of day in 2008, and has been 48 | developed actively as an open source project ever since. In more recent years 49 | it has reached the milestone 1.0 release in 2019, with latest version 1.6.0 50 | released late 2021. The language has been open source since it's very 51 | beginning, and is being developed by a group of volunteers along with a core 52 | team of developers paid by donations from the community. The Nim community 53 | itself has traditionally been very Euro-centric, with most of the core 54 | developers and users from Europe. FOSDEM has previously been an annual meeting 55 | ground for Nim users where many have been able to put a face to the nicknames 56 | we interact with every day for the first time. With this userbase there is also 57 | the possibility to transition into a physical room once FOSDEM is back 58 | to being a physical event. 59 | 60 | The Nim community has also organised its own conference, NimConf2020 and 61 | NimConf2021, and the people behind this proposal have already helped out with 62 | organising the "Minimalistic, Experimental and Emerging Languages devroom" at 63 | FOSDEM 2020. This means that we're confident that the Nim language devroom at 64 | FOSDEM 2022 will be a great success with high quality talks offering something 65 | for everyone, not only existing Nim programmers. 66 | 67 | ## Contact Information 68 | 69 | ### Primary contact 70 | 71 | **Pentabarf username of devroom primary**: dom96 72 | 73 | **First name** Dominik 74 | 75 | **Last name** Picheta 76 | 77 | **E-mail**: *we can skip this in this repo* 78 | 79 | **Submitter’s affinity to the topic of the devroom**: Core Developer 80 | 81 | ### Secondary contact 82 | 83 | **First name** Peter 84 | 85 | **Last name** Munch-Ellingsen 86 | 87 | **E-mail**: *we can skip this in this repo* 88 | 89 | *(At least the pentabarf username for the secondary contact should be added. If you want to add multiple contacts, write their pentabarf username, one per line.)* 90 | 91 | **Additional pentabarf ids:** 92 | 93 | - PMunch 94 | - pietroppeter 95 | - federico3 96 | - moigagoo 97 | - xigoi 98 | 99 | ## Additional information 100 | 101 | **Relevant URLs**: 102 | 103 | - [Nim website](https://nim-lang.org) 104 | - [Nim Conf 2021](https://conf.nim-lang.org) 105 | - [Nim Conf 2020](https://conf.nim-lang.org/2020/) 106 | 107 | **Special requirements**: 108 | 109 | -------------------------------------------------------------------------------- /2024/submission.md: -------------------------------------------------------------------------------- 1 | The details for submission as in: https://pretalx.fosdem.org/fosdem-2024-call-for-devrooms/cfp 2 | 3 | Todo: 4 | - [ ] Decide on which half day (Sat or Sun)? I propose Sunday 5 | - [ ] Primary and secondary account? Same as last year 6 | - [ ] Other volounters? (add pentabarfs?) Anyone from the moderator team who 7 | wants to join? 8 | - [ ] Review text of submission 9 | 10 | ## Project Details 11 | 12 | **Title of devroom**: Nim Programming Language 13 | 14 | **Elaborate description of proposed devroom (including possible topics)**: 15 | 16 | Nim is a versatile language that can be both compiled to low-level languages 17 | like C/C++/ObjC and to the web-oriented language JavaScript. This, along with 18 | its rich, static type system, optional and tunable GC, and its extensive 19 | meta-programming system, means that the language offers something for everyone. 20 | And it's being used for everything from programming the tiniest 21 | micro-controllers to high-performance applications and even creating rich 22 | interactive websites. Its unique combination of features and the aforementioned 23 | meta-programming makes it feel at home in pretty much every programming niche. 24 | 25 | Looking back at the talks FOSDEM has had about Nim in the past we expect a 26 | varied selection of talks ranging from the design of the language and compiler 27 | itself by the core developers all the way to talks by the many developers who 28 | use Nim for the aforementioned use-cases for such a language. For an example of 29 | talk topics see the talks from previous iterations of the devroom: 30 | - [Schedule of Nim Programming Language devroom at FOSDEM 2022](https://archive.fosdem.org/2022/schedule/track/nim_programming_language/) 31 | - [Schedule of co-organized Declarative and Minimalistic Computing devroom at FOSDEM 2021](https://archive.fosdem.org/2021/schedule/track/declarative_and_minimalistic_computing/) 32 | - [Schedule of co-organized Minimalistic, Experimental, and Emerging Languages devroom at FOSDEM 2020 (physical)](https://archive.fosdem.org/2020/schedule/track/minimalistic_experimental_and_emerging_languages/) 33 | 34 | **Why does it fit FOSDEM?** 35 | 36 | The Nim programming language first saw the light of day in 2008, and has been 37 | developed actively as an open source project ever since. In more recent years 38 | it has reached the milestone 1.0 release in 2019 and version 2.0 in 2023. The 39 | language has been open source since its very beginning, and is being developed 40 | by a group of volunteers along with a core team of developers paid by donations 41 | from the community. The Nim community itself has traditionally been very 42 | Euro-centric, with most of the core developers and users from Europe. So FOSDEM 43 | has naturally become an annual meeting ground for Nim users where many have 44 | been able to put a face to the nicknames we interact with every day for the 45 | first time. We have worked together with the Minimalistic and Declarative 46 | devroom organizers two years in a row with great success, and in 2022 we 47 | organised our own devroom. Albeit not getting a devroom for last years physical 48 | FOSDEM we try again this year and hope for either a half day for ourselves or 49 | to be paired with our great friends, or some new ones. 50 | 51 | The Nim community has also organised its own conference (with editions in 2020, 52 | 2021, and 2022) and the people behind this proposal have already organized a 53 | Nim Devroom at FOSDEM 2022 and co-organized both a virtual and physical room in 54 | the past. This makes us confident that the Nim language devroom at FOSDEM 2024 55 | will be a great success with high quality talks offering something for 56 | everyone, not only existing Nim programmers. 57 | 58 | **Preferred slot**: Half Day, Sunday morning 59 | 60 | ## Contact Information 61 | 62 | ### Primary contact 63 | 64 | **Pentabarf username of devroom primary**: PMunch 65 | 66 | **First name**: Peter 67 | 68 | **Last name**: Munch-Ellingsen 69 | 70 | **E-mail**: *we can skip this in this repo* 71 | 72 | **Submitter’s affinity to the topic of the devroom**: Long time user and contributor, organizer of various events and presenter of talks. 73 | 74 | ### Secondary contact 75 | 76 | **First name**: Pietro 77 | 78 | **Last name**: Peterlongo 79 | 80 | **E-mail**: *we can skip this in this repo* 81 | 82 | *(At least the pentabarf username for the secondary contact should be added. If you want to add multiple contacts, write their pentabarf username, one per line.)* 83 | 84 | **Additional pentabarf ids:** 85 | 86 | pietroppeter 87 | 88 | ## Additional information 89 | 90 | **Relevant URLs**: 91 | 92 | - [Nim Devroom at Fosdem 2022](https://archive.fosdem.org/2022/schedule/track/nim_programming_language/) 93 | - [Declarative and Minimalistic Computing devroom at FOSDEM 2021](https://archive.fosdem.org/2021/schedule/track/declarative_and_minimalistic_computing/) 94 | - [Minimalistic, Experimental, and Emerging Languages devroom at FOSDEM 2020 (physical)](https://archive.fosdem.org/2020/schedule/track/minimalistic_experimental_and_emerging_languages/) 95 | - [Nim website](https://nim-lang.org) 96 | - [Nim Conf 2022](https://conf.nim-lang.org/) 97 | - [Nim Conf 2021](https://conf.nim-lang.org/2021/) 98 | - [Nim Conf 2020](https://conf.nim-lang.org/2020/) 99 | 100 | **Special requirements**: 101 | N/A 102 | -------------------------------------------------------------------------------- /submission.md: -------------------------------------------------------------------------------- 1 | The details for submission as in: https://pretalx.fosdem.org/fosdem-2025-call-for-devrooms/cfp 2 | 3 | Todo: 4 | - [x] Decide on which half day (Sat or Sun)? Sunday morning was chosen 5 | - [x] Primary and secondary account? Same as last year 6 | - [ ] Other volounters? (add pentabarfs?) Anyone from the moderator team who 7 | wants to join? 8 | - [ ] Review text of submission. Can be changed until the deadline 9 | 10 | ## Project Details 11 | 12 | **Title of devroom**: Nim Programming Language 13 | 14 | **Elaborate description of proposed devroom (including possible topics)**: 15 | 16 | The Nim programming language devroom has been a big hit with our community in 17 | the years we have been so fortunate as to be allowed to host it. Featuring a 18 | wide selection of talks ranging from core developers talking about the language 19 | and its design, all the way to users showing off cool projects and ways Nim 20 | benefit them in their work or hobby it has something for everyone. For many the 21 | devroom works as a meeting place where people come together and discuss Nim in 22 | real life, and as a great place for new users to come and dip their toes in to 23 | the language and community. The project itself has been open source since the 24 | begining and is driven forwards by companies and volounteers who use it in open 25 | and closed source projects. 26 | 27 | **Why does it fit FOSDEM?** 28 | 29 | In the past we have worked together with the Minimalistic and Declarative 30 | devroom organizers with great success, and in 2022 we organised our own devroom 31 | in the online version of FOSDEM. Albeit not getting a devroom for the first few 32 | years of physical FOSDEM after this we try again this year and hope for either 33 | a half day for ourselves or to be paired with our great friends, or some new 34 | ones. 35 | 36 | Looking back at the talks FOSDEM has had about Nim in the past we see a 37 | selection of the fascinating talks the room provides: 38 | - [Schedule of Nim Programming Language devroom at FOSDEM 2022](https://archive.fosdem.org/2022/schedule/track/nim_programming_language/) 39 | - [Schedule of co-organized Declarative and Minimalistic Computing devroom at FOSDEM 2021](https://archive.fosdem.org/2021/schedule/track/declarative_and_minimalistic_computing/) 40 | - [Schedule of co-organized Minimalistic, Experimental, and Emerging Languages devroom at FOSDEM 2020 (physical)](https://archive.fosdem.org/2020/schedule/track/minimalistic_experimental_and_emerging_languages/) 41 | 42 | The language itself is a versatile language that can be both compiled to 43 | low-level languages like C/C++/ObjC and to the web-oriented language 44 | JavaScript. This, along with its rich, static type system, optional and tunable 45 | GC, and its extensive meta-programming system, means that the language offers 46 | something for everyone. And it's being used for everything from programming 47 | the tiniest micro-controllers to high-performance applications and even 48 | creating rich interactive websites. Its unique combination of features and the 49 | aforementioned meta-programming makes it feel at home in pretty much every 50 | programming niche attracting developers from many different fields. 51 | 52 | 53 | The Nim programming language first saw the light of day in 2008, and has been 54 | developed actively as an open source project ever since. In more recent years 55 | it has reached the milestone 1.0 release in 2019 and version 2.0 in 2023. The 56 | language has been open source since its very beginning, and is being developed 57 | by a group of volunteers along with a core team of developers paid by donations 58 | from the community and companies using the language. The Nim community itself 59 | has traditionally been very Euro-centric, with most of the core developers and 60 | users from Europe. So FOSDEM has naturally become an annual meeting ground for 61 | Nim users where many have been able to put a face to the nicknames we interact 62 | with every day for the first time. Since the language doesn't have as many big 63 | commercial sponsors as other languages it relies on the open source community 64 | both for getting work done and for donations. This makes open source meeting 65 | grounds like FOSDEM an important part of the Nim community culture. 66 | 67 | **Preferred slot**: Half Day, Sunday morning 68 | 69 | ## Contact Information 70 | 71 | ### Primary contact 72 | 73 | **Pentabarf username of devroom primary**: PMunch 74 | 75 | **First name**: Peter 76 | 77 | **Last name**: Munch-Ellingsen 78 | 79 | **E-mail**: *we can skip this in this repo* 80 | 81 | **Submitter’s affinity to the topic of the devroom**: Long time user and contributor, organizer of various events and presenter of talks. 82 | 83 | ### Secondary contact 84 | 85 | **First name**: Pietro 86 | 87 | **Last name**: Peterlongo 88 | 89 | **E-mail**: *we can skip this in this repo* 90 | 91 | *(At least the pentabarf username for the secondary contact should be added. If you want to add multiple contacts, write their pentabarf username, one per line.)* 92 | 93 | **Additional pentabarf ids:** 94 | 95 | pietroppeter 96 | 97 | ## Additional information 98 | 99 | **Relevant URLs**: 100 | 101 | - [Nim website](https://nim-lang.org) 102 | - [Schedule of Nim Programming Language devroom at FOSDEM 2022](https://archive.fosdem.org/2022/schedule/track/nim_programming_language/) 103 | - [Schedule of co-organized Declarative and Minimalistic Computing devroom at FOSDEM 2021](https://archive.fosdem.org/2021/schedule/track/declarative_and_minimalistic_computing/) 104 | - [Schedule of co-organized Minimalistic, Experimental, and Emerging Languages devroom at FOSDEM 2020 (physical)](https://archive.fosdem.org/2020/schedule/track/minimalistic_experimental_and_emerging_languages/) 105 | 106 | **Special requirements**: 107 | N/A 108 | --------------------------------------------------------------------------------