Skip to content

Latest commit

 

History

History
113 lines (76 loc) · 10.6 KB

File metadata and controls

113 lines (76 loc) · 10.6 KB

Hackergarten

v1.0, 2023-06-05: Rohentwurf

Hackergarten is a craftmen’s workshop, classroom, a laboratory, a social circle, a writing group, a playground, and an artist’s studio. Our goal is to create something that others can use; whether it be working software, improved documentation, or better educational materials. Our intent is to end each meeting with a patch or similar contribution submitted to an open and public project. Membership is open to anyone willing to contribute their time.

It is 7 pm on a Wednesday evening, and we are gathered in Basel, Switzerland in the company of ten software engineers sharing their time and expertise to develop open source software. They have a passion for code, sharing knowledge and open source software, they may not be colleagues, some of them work for the same company, but today they are working together as a team to create something that can be used by others. The event had been scheduled for 15 November a few weeks earlier > to keep up to date with upcoming events, visit the Hackergarten site" [1]

The 341 Hackergarten meeting happened on a crisp evening, people were arriving slowly but surely, some joined around 5pm. Despite the apparent large size of the software community, many warm greetings were exchanged, such as "Hey!! So nice to seeyou again!", "hello!!" and "long time no see". Certain participants felt like they were reuniting with long-lost acquaintances, whereas others had the advantage of being regular attendees. It’s another wonderful evening among acquaintances, friends, and ex-colleagues or maybe even soon to be colleagues. As I sat in front of my computer, I overheard an intriguing conversation on documentation, templating and how to enforce a project structure. Several questions and suggestions were raised, including a helpful prompt to create a plugin for “Asciidoctor.” We noted it down to bring up during the brainstorming session later in the evening. At around six o’clock, Markus S walked towards the whiteboard and, with great enthusiasm, took attendance. "So many new faces!" he exclaimed. > You may be the next one, don’t forget to check the webpage! [1]

Marcus welcomed the new attendees and clarified the purpose of Hackergarten, explaining that the aim is to create a tangible outcome that can benefit others, whether it is functional software, enhanced documentation, or improved educational resources. The goal is to conclude each meeting with a patch or comparable contribution to an openly source and public project. Markus emphasised that contributing to open source does not always involve writing code. A contribution can take various forms, not all of which are technical. This article provides proof of this fact. Marcus Fihlon proposed an outstanding idea, and Tamari and Ixchel collaborated to execute it.

Within minutes, a list of topics began to take shape. Each person had the opportunity to introduce a project and a first idea of how they would like to contribute. If they are aware of a specific issue or a possible addition to their favourite open source project which they use at work, or simply one they wish to contribute to, they could elaborate on that. We are aware that several open-source projects have spent time welcoming new contributors, and you can find issues marked as "first contribution", but remember that we are in a room full of people who love to code, share knowledge and spend time with similarly minded people. However, it is precisely this that makes Hackergarten such a unique event. The event has a clear starting point, people with skills, knowledge, passion and a willingness to make the world a better place, one contribution at the time.

Here you can see the list of topics we proposed tonight:
  • Asciidoctor Plugin/ Antora Plugin

  • Mastodon setup on (h) Cloud ( Bash )

  • Article about Hakergarten for JavaAktuell

  • Apache Solr : 1st contrib issues

  • ZioNSON with DSON-LD (Scala)

  • JReleaser

  • RDiscount ( Ruby, C )

  • Pandoc Plant UML Filter (Python )

After a quick vote to gauge the interest of topics by each attendee and some coordination in order to find who will join each topic. In Hackergarten there are not many rules but is the intention of the organiser that people split in groups so nobody works alone.

The suggested projects are written in different programming languages. This is not by any means a limitation, as we all have preferences and sometimes dislikes and that is acceptable. Nonetheless, this is a distinct advantage of Hackergarten it’s surprising mix of interest, languages, platforms and even types of contributions. You can never predict how it’s going to turn out, or who you’re going to work with, or how far-reaching the inspiration will be. This article, for example, has been an exciting experience and one of the most fulfilling tasks I have undertaken in recent weeks, because I have had the privilege of sharing the work with Tamari.

Whilst the preferred frequency of events can be once a month, it happens 'when it happens'. All you need for a Hackergarten is a friendly organisation to provide space and often refreshments. This evening, we are will be enjoying a very productive evening and pizza with beer at the Karakun office in Basel.

So you may be asking yourself why should I join the next Hackergarten ?

This article was written while listening to several conversations happening in the background. Many git commands can be heard! Surprised expressions about new shortcuts or tools. Learning is a natural occurrence in relax environments, when there are all the ingredients set to simple enjoy the art of coding. We put the same question to those of our team who attended the Hackergarten event today. You will probably be interested in the answers from experienced people.

Here are some of the comments we received from participants when we asked them why they were attending tonight:
  • “A sense of accomplishment, because the goal is to finish the contribution in one evening”

  • “Quick and easy introduction on how to contribute to open source, because someone can help you get started”

  • “Writing open source in a shared and personal environment is more rewarding, it’s working together to achieve a common goal”

  • “I was surprised by the welcoming environment and how easy it is to interact with other participants”

I can assure you that you may have had similar responses before, or perhaps you have specific intentions for joining us.

We have a clear message for you. Hackergarten gives you a possibility to work in a challenging projects and seeing yourself in a different light or a new way like you never have before.

Our warmest thank you and recognition to all attendees to Hackergarten #341:

Hackergarten

What is Hackergarten?

Hackergarten is a unique and dynamic gathering where individuals from diverse backgrounds come together in a collaborative environment. It functions as a workshop, a classroom, a lab, a social club, a writing society, a recreational space, and an artist’s studio all at once. The primary objective of Hackergarten is to create valuable contributions that others can benefit from - be it functional software, enhanced documentation, or improved educational resources.

At every meeting, members focus on producing a tangible outcome, be it a patch or a similar contribution to an open and public project. The aim is not only to learn, explore, and experiment but also to make a positive impact by actively participating in the open-source community.

Hackergarten embraces diversity and encourages anyone who is passionate and willing to dedicate their time and energy to join the community. It provides a platform for individuals to collaborate, share knowledge, and collectively work towards a common goal. By promoting active involvement and fostering a sense of camaraderie, Hackergarten aims to create a supportive and enriching environment for all its members.

How to organise a Hackergarten?

If you are considering organizing a Hackergarten for the first time, it is highly recommended that you attend one as a participant beforehand. This will give you valuable insight into how the event is structured and executed.

How to organise a succesful Hackergarten?

To host a successful Hackergarten, you will need a suitable venue with ample power plugs, as well as reliable WiFi access. It is also important to provide refreshments, snacks, and/or pizza during the event, as this will not only keep participants fueled ( perhaps even happy ) but also create an opportunity for networking and socializing during the break.

Pizza

A commonly used formula is to multiply the number of participants by 0.8, rounding up to the nearest whole number.

Social and Communication

To streamline your organization process, a platform like Meetup is highly recommended. It has proven to be effective for many events, including Hackergartens in places such as Basel and Lucerne. You can easily manage event registration, communication, and updates.

Join the list!

If you would like your Hackergarten event to be added to the Hackergarten official list, simply fork their repository, include the event details in the events.json file, and submit a pull request.

Media

If you are interested in using the Hackergarten logo, you can download it from their website’s download section. However, please make sure to agree to the license terms before using it.

Über den Autoren/die Autorin

Ix-chel Ruiz has developed software application & tools since 2000. Her research interests include Java, dynamic languages, client-side technologies and testing. Java Champion, Oracle ACE pro, Testcontainers Community Champion, CDF Ambassador, Hackergarten enthusiast, Open Source advocate, public speaker and mentor.

Tamari Gogebashvili is a Software Engineer with more than 5 years of experience in Java and various Front-End technologies. M.Sc in Computer Science and Hackergarten enthusiast. Her areas of interest are Data processing, Analytics and Intellectual Systems.