De-mystifying contributing to PostgreSQL Saturday 12:00 H.1302 (Depage)
Twitter: @l_avrot LinkedIn: lætitia-avrot
I'm Lætitia Avrot. I first worked with PostgreSQL in 2007 for the Géoportail project. (Géoportail is a comprehensive web mapping service of the French government that publishes maps and geophysical aerial photographs for France and its territories.) Then my company offered a DBA job and I took it.
I first learnt on PostgreSQL and 6 months later, I had to work with Oracle and SQL Server too.
I had the chance to work in environment with high avialability constraints, high loads, high confidentiality and high security projects.
Last year, I decide to focus on my PostgreSQL skills and I became a teacher and consultant for Loxodata, a PostgreSQL experts company.
I first came to FOSDEM last year and I really enjoyed it. I also went to pgconf.eu in 2009 in Paris and in Warsaw in 2017. It's always a great experience to meet the community!
Last year, I decided to strengthen my involvement to the PostgreSQL community.
So I started reading about how to contribute, what I could do and so on. But I didn't wanted to mess up with the great job that PostgreSQL is... So I had a hard job learning I could produce a patch.
Once I understood there was no magic mumbo jumbo in the process to create a patch, I created a very simple one.
I decided to share that experience with others, assuming there might be other people out there that don't dare producing a patch or that don't know how to help such a beautiful project as PostgreSQL.
Anyone can follow that talk, as you don't need to be a developper to be able to help the PostgreSQL project.
No need to have any knowledge to follow that talk. You just need to be curious!