To test it you can do the following:

git version on stdout

> git --version 2> error 1> output 
> cat output
git version 2.51.0

ssh version on stderr

> ssh -V 2>> error 1>> output
> cat error
OpenSSH_9.9p1, OpenSSL 3.2.4 11 Feb 2025

Hope this will be helpful.

The first hurdle I faced was that there was no documented release process. What we had were release managers' private notes. It was over in personal repositories, internal Red Hat Google Docs, and personal code. Since all those past release managers left the organization (apart from one), it was very difficult to gather and figure out what, why, and how the release process worked. I had one supporter, my trainer (the then-release manager), Christian. He shared with me his notes and the steps he followed. He guided me on how he did the release.

Now we have a community release managers working group where contributors from the community also take part and release Ansible. And we have the two aforementioned GitHub actions.

• First one builds the package and also opens a PR to the repository, and then waits for human input.
• Meanwhile, the release manager can use the second action to create another PR to the Ansible documentation repository from the updated porting guide from the first PR.
• After the PRs are approved, the release manager can continue with the first action and release the Ansible wheel package and the source tarball to PyPI in a fully automated way using trusted publishing.

I would like to thank Felix, Gotmax and Sviatoslav for feedback during the journey, thank you.

Many say automation is bad. In many companies, management gets the wrong idea that, when good automation is in place, they can fire senior engineers and get interns or inexperienced people to get the job done. That works till something breaks down. The value of experience comes when we have to fix things in automation. Automation enables new folks to get introduced to things, and enables experienced folks to work on other things.

The above is an example of how to create a draft PR via GitHub Actions. We need to give permissions to the GitHub action to create PR in a repository (workflow permissions in the settings).

Hopefully, this blogpost will help my future self.

Day before the conference

What makes this PyCon, is that we were traveling there as a family and the conference days coincided with the Easter holidays. We utilized that to explore the city—the ancient cathedrals, palaces, old cafes, and of course the Lithuanian cuisine. Šaltibarščiai, Balandeliai and Cepelinai.

Tuesday

22nd, the day before the conference was all about practicing the talk and meeting with the community. We had the pre-conference mingling session with the speakers and volunteers. It was time to meet some old and many new people. Then it was time for PyLadies. Inga from PyLadies Lithuania, Nina from Pyladies London and I had a lovely dinner discussion—good food with the PyLadies community,technology, and us.

Wednesday

The morning started early for us on the day of the conference. All the 3 of us had different responsibilities during the conference. While Py was volunteering, I talked and Kushal was the morning keynoter A Python family in a true sense :)

I had my talk, “Using PyPI Trusted Publishing to Ansible Release” scheduled for the afternoon session. The talk was about automating the Ansible Community package release process with GitHub action using the trusted publisher in PyPI. The talk described - what is trusted publishing.I explanined the need for it and the usage of trusted publishing. I explained the Ansible manual release process in a nutshell and then moved to what the Ansible release process is now with  GitHub actions and Trusted Publishing. Then the most important part is, the lessons learned in the process and how other open-source communities can get help and benefit from it.Here is the link for the slides of my talk I had questions regarding trusted publishing, experience as a release manager, and of course Ansible.

It was the time to bid goodbye to PyCon Lt and come back home. See you next year. Congratulatios organizers for doing a great job in organizing the coference.

On October 10th, 2024, I had my talk at PyCon NL. I woke up early to practice. I saw an email from PyLadiesCon, titled "Invitation to be a Keynote Speaker at PyLadiesCon". The panic call went to Kushal Das. "Check if there is any attack in the Python server? I got a spamming email about PyLadiesCon and the address is correct. "No, nothing.", replied Kushal after checking. Wait then "WHAT???". PyLadiesCon wants me to give the keynote. THE KEYNOTE in PyLadiesCon.

Thank you Audrey for conceptualizing and creating PyLadies, our home.

And here I am now. I will give the keynote on 7 December 2024 at PyLadiesCon on how PyLadies gave me purpose. See you all there.

Dreams do come true.

My Talk: Intellectual Property Law 101

I had my talk on Intellectual Property Law, on the first day. After a long time, I was giving a talk on the legal topic. This talk was dedicated to the developers. So, I concentrated on only those issues which concerned the developers. Tried to stitch the concerned topics Patent, Trademarks, and Copyright together. For the smooth flow of the talk, since it becomes easier for the developers to understand and remember for all the practical purposes for future use. I was concerned if I would be able to connect with people. Later, people came to  me with several related questions, starting from

• Why should I be concerned about patents?

• Which license would fit my project?

• Should I be scared about any Trademarks granted to other organizations under some other jurisdiction?

So on and so forth. Though I could not finish the whole talk due to time constraints, I am happy with the overall review.

Panel: Open Source Sustainability

On Day 1 of the main conference, we had the panel on Open Source Sustainability. This topic lies at the core of open-source ecosystem sustainability for the projects and community for the future and stability. The panel had Deb Nicholson, Armin Ronacher Çağıl Uluşahin Sönmez,Deb Nicholson, Samuel Colvin, and me and Artur Czepiel as  the moderator.  I was happy to represent my community's side. It was a good discussion, and hopefully, we could give answers to some questions of the community in general.

Birds of Feather session: Open Source Release Management

This Birds of Feathers (BoF) session is intended to deal with the Release Management of various Open Source projects, irrespective of their size. The discussion includes all projects, from a community-led project to projects maintained/initiated by big enterprises, from a project maintained by one contributor to a project with several hundred contributors.

• What methods do we follow regarding versioning, release cadence, and the process?

• Do most of us follow manual processes or depend on automated ones?

• What works and what does not, and how can we improve our lives?

• What are the significant points that make the difference?

We discussed and covered the following topics: different aspects of release management of Open-Source projects, security, automation, CI usage, and documentation. We followed the Chatham House Rules during the discussion to provide the space for open, frank, and collaborative conversation.

PyLadies Lunch

And then comes my favorite part of the conference: PyLadies Lunch. It was my seventh PyLadies lunch, and I was moderating it for the fifth time. But this time, my wonderful friends [Laís] and Çağıl were by my side, holding me up when I failed. I love every time I am at a PyLadies lunch. This is where I get my strength, energy, and love.

Workshop

I attended two workshops organized by Anezka Muller , Mia Bajić and all amazing PyLadies organizers

• Self-defense workshop where the moderators helped us navigate challenging situations we face in life, safeguard ourselves from them, and overcome them.

• I AM Remarkable workshop, where we learned to tell people about our successes.

Representing Ansible Community

I always take the chance to meet the Ansible community members face-to-face. Euro Python gave me another opportunity to do that. I learned about different user stories that we do not get to hear from our work corners, and I learned about these unique problems and their solutions in Ansible. 
Fun fact : Maarten gave a review after knowing I am Anwesha from the Ansible project. He said, 'Can you Ansible people slow down in releasing new versions of Ansible? Every time we get used to it, we have a new version.'

Acknowledging mental health issues

The proudest moment for me personally was when I acknowledged my mental health issues and later when people came to me saying how they relate to me and how they felt empowered when I mentioned this.

PyLadies network at Red Hat

A network of PyLadies within Red Hat has been my dream since I joined Red Hat. She also agreed when I shared this with Karolina at last year's DevConf. And finally, we initiated on day 2 of the conference. We are so excited for the future to come.

Meeting friends

Conference means friends. It was so great to meet so many friends after such a long time Tylor, Nicholas, Naomi, Honza, Carol, Mike, Artur, Nikita, Valerio and many new ones Jannis Joana,[Chirstian], Martina Tereza , Maria, Alyona, Mia, Naa , Bojanand Jodie. A special note of love to Jodie, you to hold my hand and take me out of the dark.

The best is saved for the last. Euro Python 2024 made 3 of my dreams come true.

• Gender Neutral Washrooms

• Sanitary products in restrooms (I remember carrying sanitary napkins in my bag pack in PyCon India and telling girls if they needed it, it was available in the PyLadies booth).

• Neo-diversity bag (which saved me at the conference; thank you, Karolina, for this)

I cannot wait for the next Euro Python; see you all at Euro Python 2025.

PS: Thanks to Lias, I will always have a small piece of Euro Python 2024 with me. I know I am loved and cared for.

Day 0 of the main conference

After a long time, I will give a legal talk. We are going to dig into some basics of Intellectual Property. What is it? Why do we need it? What are the different kinds of intellectual property? It is a legal talk designed for developers. So, anyone and everyone from the community with previous knowledge can understand the content and use it to understand their fundamental rights and duties as developers.Intellectual Property 101, the talk is scheduled at 11:35 hrs.

Day 1 of the main conference

Day 1 is PyLadies Day, a day dedicated to PyLadies. We have crafted the day with several different kinds of events. The day opens with a self-defense workshop at 10:30 hrs. PyLadies, throughout the world, aims to provide and foster a safe space for women and friends in the Python Community. This workshop is an extension of that goal. We will learn how to deal with challenging, inappropriate behavior.
In the community, at work, or in any social space. We will have a trained Psychologist as a session guide to help us. This workshop is so important, especially today as it was yesterday and may be in the future (at least until the enforcement of CoC is clear). I am so looking forward to the workshop. Thank you, Mia, Lias and all the PyLadies for organizing this and giving shape to my long-cherished dream.

Then we have my favorite part of the conference, PyLadies Lunch. I crafted the afternoon with a little introduction session, shout-out session, food, fun, laughter, and friends.

After the PyLadies Lunch, I have my only non-PyLadies session, which is a panel discussion on Open Source Sustainability. We will discuss the different aspects of sustainability in the open source space and community.

Again, it is PyLady's time. Here, we have two sessions.

[IAmRemarkable](https://ep2024.europython.eu/pyladies-events#iamremarkable), to help you learn to empower you by celebrating your achievements and to fight your impostor syndrome. The workshop will help you celebrate your accomplishments and improve your self-promotion skills.

The second session is a 1:1 mentoring event, Meet & Greet with PyLadies. Here, the willing PyLadies will be able to mentor and be mentored. They can be coached in different subjects, starting with programming, learning, things related to job and/or career, etc.

Birds of feather session on Release Management of Open Source projects

It is an open discussion related to the release Management of the Open Source ecosystem.
The discussion includes everything from a community-led project to projects maintained/initiated by a big enterprise, a project maintained by one contributor to a project with several hundreds of contributor bases. What are the different methods we follow regarding versioning, release cadence, and the process itself? Do most of us follow manual processes or depend on automated ones? What works and what does not, and how can we improve our lives? What are the significant points that make the difference? We will discuss and cover the following topics: release management of open source projects, security, automation, CI usage, and documentation. In the discussion, I will share my release automation journey with Ansible. We will follow Chatham House Rules during the discussion to provide the space for open, frank, and collaborative conversation.

So, here comes the days of code, collaboration, and community. See you all there.

PS: I miss my little Py-Lady volunteering at the booth.

What is Event Driven Ansible?

What is Event Driven Ansible? In simple terms, some action is triggered by some events. The idea of EDA comes from Event driven architecture. Event driven ansible runs code automatically based on received event notifications.

Some important terms:

What is event in Event Driven Ansible?

The event is the notification of a certain incident.

Where do we get the events from?

We get the events from event sources. Ansible EDA provides different pulgins to support various event sources. There are several event source plugins such as :
url_check (checking the http status code), webhook (providing and checking events from webhook), journald (monitoring the journald logs) and the list goes on.

When to take actions?

Rulebook defines conditions and actions in case of fulfilling those actions. Conditions use operators as strings, boolean and numerical data. And actions are occurrence of events once the conditions are met. Running a playbook, setting a fact, running a module etc.

Small example Project

Here is a small example of Event Driven Ansible and how it is run. The idea is on receiving of a message (here the number 42) a playbook will run in the host. There are the following 3 files :

demo_rule.yml

---
- name: Listen for events on a webhook
  hosts: all

  sources:
    - ansible.eda.webhook:
        host: 0.0.0.0
        port: 8000

  rules:
    - name: Say thank you
      condition: event.payload.message == "42"
      action:
        run_playbook:
          name: demo.yml

This is the rulebook. We are using the webhook plugin here as the event source. As a rule in the event of receiving the message 42 as json payload in the webhook, we run the playbook called demo.yml

demo.yml

- hosts: localhost
  connection: local
  tasks:
    - debug:
        msg: "Thank you for the answer."

demo.yml, the playbook which run on the occurrence of the event mentioned in the rulebook and prints a debug message.

---
local:
  hosts:
    localhost

inventory.yml mentions the hosts to run the action against.

Further there are 2 files to one to test 42.json and 43.json to test the code.

{
  "message" : "42"
}

{
  "message" : "43"
}

First we have to install all related dependencies before we can run the rulebook.

$ python -m venv .venv
$ source .venv/bin/activate
$ python -m pip install ansible ansible-rulebook ansible-runner psycopg
$ ansible-galaxy collection install ansible.eda
$ ansible-rulebook --rulebook demo_rule.yml -i inventory.yml --verbose

Go to another terminal and on the same directory path and run the following command to test the Rulebook. After receiving the message, the playbook runs.

curl -X POST -H "Content-Type: application/json" -d @42.json 127.0.0.1:8000/endpoint

Output

2024-06-07 16:48:53,868 - ansible_rulebook.app - INFO - Starting sources
2024-06-07 16:48:53,868 - ansible_rulebook.app - INFO - Starting rules

...

TASK [debug] *******************************************************************
ok: [localhost] => {
    "msg": "Thank you for the answer."
}

PLAY RECAP *********************************************************************
localhost                  : ok=2    changed=0    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0   
2024-06-07 16:50:08,224 - ansible_rulebook.action.runner - INFO - Ansible runner Queue task cancelled
2024-06-07 16:50:08,225 - ansible_rulebook.action.run_playbook - INFO - Ansible runner rc: 0, status: successful

Now if we run the other json file 43.json we see that the playbook does not run even after the http status code being 200.

curl -X POST -H "Content-Type: application/json" -d @43.json 127.0.0.1:8000/endpoint

Output :

2024-06-07 18:20:37,633 - aiohttp.access - INFO - 127.0.0.1 [07/Jun/2024:17:20:37 +0100] "POST /endpoint HTTP/1.1" 200 159 "-" "curl/8.2.1"

You can try this yourself follwoing this git repository.

• Base, includes the following

  • fedora base image
  • ansible core
  • ansible collections : The following set of collections
    ansible.posix
    ansible.utils
    ansible.windows

• Minimal, includes the following

  • fedora base image
  • ansible core

I have been the release manager for Ansible Execution Environments. After building the images I perform certain steps of tests to check if the versions of different components of the newly built correct or not. So I wrote eercheck to ease the steps of tests.

What is eercheck?

eercheck is a command line tool to test Ansible community execution environment before release. It uses podman py to connect and work with the podman container image, and Python unittest for testing the containers.

eercheck is a command line tool to test Ansible Community Execution Environment before release. It uses podman-py to connect and work with the podman container image, and Python unittest for testing the containers. The project is licensed under GPL-3.0-or-later.

How to use eercheck?

Activate the virtual environment in the working directory.

python3 -m venv .venv
source .venv/bin/activate
python -m pip install -r requirements.txt

Activate the podman socket.

systemctl start podman.socket --user

Update vars.json with correct version numbers.Pick the correct versions of the Ansible Collections from the .deps file of the corresponding Ansible community package release. For example for 9.4.0 the Collection versions can be found in here. You can find the appropriate version of Ansible Community Package here. The check needs to be carried out each time before the release of the Ansible Community Execution Environment.

Execute the program by giving the correct container image id.

./containertest.py image_id

Happy automating.

Ansible has historically been released by Red Hat employees. We planned to open up the release to the community. And I was asked about that. My primary goal was releasing Ansible, which should be dull and possible for the community. This was my first time dealing with Github actions. There is still a lot to learn. But we are there now.

The Release Management working group started releasing the Ansible Community package using GitHub Actions workflow from Ansible version 9.3.0 . The recent 9.4.0 release has also been released following the same workflow.

Thank you Felix Fontein, Maxwell G, Sviatoslav Sydorenko and Toshio for helping out in shaping the workflow with you valuable feedback, doing the actual release and giving answers to my enumerable queries.

I released the Ansible 8.3.0 on 15th August, 2023. This is the Ansible stable release. You can read the full Changelog here

You can install it via pip.

python3 -m pip install ansible==8.3.0 --user

You can have a look at the announcement.

Fun fact while working on the release Github worked below 30 KiB/s speed the whole day.

To follow all our updates on Ansible project and community susbcribe to Bullhorn, our weekly Newsletter. Join us in our community discussion at this Matrix room.

After coming from DevConf.cz, on 22nd of June I released Ansible Community Package 7.7.0 and 8.1.0. This is the last release of the Ansible 7 series and first minor release of the Ansible 8 series.

Ansible Community Package 7.7.0

Ansible 7.7.0 requires latest version of ansible-core 2.14 and includes a curated set of Ansible collections that provides a vast number of modules and plugins.

One can have a look at the full Changelog.

You can install it via pip.

pip install ansible==7.7.0 --user

Ansible Community Package 8.1.0

Ansible 8.1.0 requires latest version of ansible-core 2.15.1 and includes a curated set of Ansible collections providing a huge number of modules and plugins.

You can get the Changelog here.

One can install Ansible 8.1.0 via pip

$ python3 -m pip install ansible==8.1.0 --user

Roadmap for future releases

You can read our Roadmap for the Ansible 8 release cycle here and the changelog here To follow all our updates on Ansible project and community susbcribe to Bullhorn, our weekly Newsletter. ETA for next Ansible Community Package release, i.e 8.2.0, is 18th July, 2023.

The PyCon Italy, 2023 discussion started in PyCon Sweden 2022, when Valerio invited me for the keynote. From disbelief (since my talk at PyCon Sweden was not good) to believing, from searching for talk topics to preparation and multiple rounds of rehearsals and feedback sessions, I was finally ready for the talk.

The day before the travel

And it was one of the bustiest days on my calendar. I did two Ansible releases (7.6.0 and 8.0.0rc1), attended an event on Inner Source, participated (and got elected) in the board meeting of the Python Sweden Board, last minute prep of the talk, not forget the never-ending packing and finally the day arrived for the travel.

Arrival at Florance

After a 10-hour + journey, we reached Florence. It is a beautiful city. There was history everywhere, in every corner. Fun fact, when checking out from the first hotel to the conference venue, we figured out the hotel was only 500+ years old.

Meeting the community

PyCons always gives me the feeling of meeting family. It was my time to meet my friends whom I am never met post-pandemic. I met many friends from online first time in real life during the conference. And, of course, like always meeting and making new friends.

Meeting Audrey

In PyCon 2017, when I met Carol, she once said, "Anwesha, I would really like you to meet Jessica and Audrey. I believe you will be able to connect." I longed for this to happen for so long. This time I finally got to meet Audrey and how Carol was right about us connecting :). I look up to her for all her work in and for the Python and broader open-source community. More than anything, her work in setting up PyLadies has been the catalyst to change the direction of my life. But now I got know what a wonderful human being she is. Thank you, Audrey, for being you, just you :).

Py, the youngest volunteer

My kid has always been a conference child. She started attending conferences when she was ten months old and volunteering as a toddler. But what I noticed this time was how dutiful and serious she had become. She used to get up every day on time (no matter how tired she was from the last day) and report to her duty at the Registration desk. It felt good when she did my registration :).

Day 0 of the leading conference

It started with a bang with a great opening session by Valerio and Ester. This is one of the best conference opening presentations I have ever seen. It was well-crafted presentation. It is informative, fun, and even explains the Pacman rule. It established the tone of the conference to the community-first approach.

Then was the time for Carlton's keynote "Open Source for the long-haul." It should be a must-watch list for anyone who wants a sustainable career and life in the Open Source ecosystem. It depicts the true picture of our world.

The day of the keynote

My talk was on the first day of the main conference, ending the keynote. I had a rehearsal of my talk with Carol. She gave me two vital pieces of advice "Take a deep breath every time you start." The second is, 'As a keynote speaker, you are just expected to concentrate on your talk and nothing else.' I followed them religiously. Generally, during the conferences, I run around, meet new people, talk to everyone, and throw myself into some or other voluntary work. But this time, for the first two days' conference, till my talk was done, I was away saving my energy and practicing. My biggest worry was if I could finish it within time and the technology should not fail me. And finally, the time came for me to go up on stage. It was nerve-racking (and it is so visible from how I was dancing on the stage before the talk :). I ticked all the major boxes in the talk. Never froze during the talk, saying all the things which I wanted to and finish the on time. Only one thing I could not do was to wear my Red Hat during the talk. It seems I have become to Scandinavian to wear it during the spring in Italy. Everything ended well with a standing ovation at the end :).

I could only deliver the talk with help from my friends. Tom who made me believe that my journey is inspiring and worth giving a keynote about, others wise I was thinking of talking about legal stuff. Saptak for his help with the slides and for answering my random 2 am calls and requests for the last couple of months. Brett, Carol , Andrea, and Kushal for helping me to stick to the idea, for sitting with me for rehearsal sessions and listing to my unfiltered blabbering, And not forgetting Py for sitting with Mummy for days, and pointing out to my mistakes. I could mention one line she requested, but quoting her here, "Not all the flowers are to be treated equally, so should not be the lawyers and developers." This is to elaborate on the difference between law and technology.

And day 0 ended for me with a glass of wine :).

Day 1 of the main conference

Day 1 started with the keynote by Marlene, "Transcendence: The Power of Representation". It had his life lessons, the state of the community, and how we can make things better in the community. Thank you, Marlene, for echoing many of our thoughts. Then it was my time to mingle with the community. I was trying to meet new people from different parts of the world and to know what happens in the part of the community there. I met several Ansible Users, so Python and PyCon Italia allowed me to meet the global Ansible community. A surprise awaited me in the second half of the day. I got to meet Tyler for the first time. It was unexpected, I did not know she is coming. It was a nice surprise. From Red Hat to community we had a good conversation :).

Day 1 ended with a fantastic conference dinner, a local band performance, and some great conversations with friends.

Day 2 of the main conference

On day 2 Emily, in her keynote on "Stay Curious: Reflections on Passion, Risk-Taking, and Re-Invention", shared the importance of self-care, time out, and prioritization for a sustainable career. She further shared how to silence "the hum" of being there or doing things. My gratitude to Emily for stressing the point that burnout is genuine.

I fixed meetings for the last day on the first two days of the main conference. So my day two was filled with meetings regarding several different things, starting with feedback on the Ansible Project and Community with some users, then discussions on Python Community, including PyLadies and Pycon Sweden Organization and state of Trademark at PSF.

PyCon Italia 2023 came to an end with an ending talk by Ernesto. I was surprised to know a few statistics, especially that people from 42 countries attended the conference. The best moment of the day was when Py went up on stage as part of the volunteering team :).

Thank you PyCon Italia team for giving us such a great conference. I hope to meet the community again at PyCon Italia 2024, cheers to that.

Since I moved to Stockholm, I hated the weather more than the practice behavior of the Sun. But today, it did some good; it woke me up at 4:40 and felt like 7:00, so I started working. And what a productive day it was :).

I have been doing Ansible Release for three months, and before that, I was shadowing Christian to learn more about the process. But today was special. Today, I did two releases on the same day, Ansible 7.5.0 and Ansible 8.0.0a2. It is the second Alpha of the Ansible 8 series.

I did the Ansible 7.5.0 release first. It is the Ansible stable release. You can read the complete Changelog here

You can install it via pip.

pip install ansible==7.5.0 --user

Ansible 8.0.0a2 was my next target.
You can read our Roadmap for the Ansible 8 release cycle here and the Changelog here.

To follow all our updates on the Ansible project and community susbcribe to Bullhorn, our weekly Newsletter. Fun fact this week will be the 100th edition of Bullhorn.

My friend Dr. Brett Canon, CPython Core Dev, once said, "Came for the language and stayed for the community." It is a little different for me. I Came for the community and stayed for the love of it.

I joined the open source community as a lawyer to up my legal skills. Instead, I am now a community member who knows law.

My journey in the Open Source world has been a sail of happiness, tears, achievements, sweats, and more than anything os dreams. A dream of something which I never saw any of my friends, let alone achieving but even dreaming. Honestly, I do not consider my story to be unique, but some people think otherwise. What do you think? You can figure it out for yourself. I will be talking about this in my keynote at PyCon Italia, 2023.

I will be talking about stories, my favorite PyLadies,Python for Everyone program and how an innocent piece of technology and small initiatives from and by the community can alter the lives of real people.

Join us in PyCon Italia, 2023, for 4 days of learning, togetherness, fun, and, not to forget, good food. See you all there.