text stringlengths 0 1.8k |
|---|
[3115.16 --> 3116.46] And that's a huge problem. |
[3116.82 --> 3124.76] And what you usually get is the people who have the budget will just say, yeah, we divide everything apart. |
[3125.06 --> 3128.16] And everybody gets the same amount. |
[3128.48 --> 3132.10] And then everybody is sort of happy. |
[3132.66 --> 3135.10] That's quite a bad thing you usually have. |
[3135.10 --> 3139.72] And the better thing is to have that participatory budgeting. |
[3139.80 --> 3140.60] That's an event. |
[3141.04 --> 3147.64] And in this event, everybody who wants to have a budget and is part of a value stream comes together. |
[3148.34 --> 3150.90] And they get allocated the budget. |
[3151.08 --> 3152.28] They sit on a table. |
[3152.64 --> 3155.06] They get the budget pot. |
[3155.06 --> 3160.50] And then they on the table need to pitch for their budget. |
[3160.88 --> 3170.40] And then they have together, participatory, a discussion on in which area are we going to invest the money. |
[3170.96 --> 3181.84] And that's a very, very cool thing because then the people are discussing about impact on value, how much value this topic brings. |
[3181.84 --> 3195.86] And especially when you have, of course, OKR or a strategy, they are also coming up with the strategy and are saying, hey, look, this initiative buys more into the strategy than the other one. |
[3195.86 --> 3200.32] So there is that entrepreneurial thinking which is coming up. |
[3200.76 --> 3205.86] And they start to think like it is their own enterprise. |
[3206.50 --> 3208.74] And they are more emotionally attached. |
[3208.92 --> 3210.96] And in the end, you get a better budget. |
[3210.96 --> 3212.94] That was a great summary. |
[3213.22 --> 3215.10] I know that you gave a whole talk on this. |
[3215.58 --> 3217.78] And based on that summary, I'm going to watch it. |
[3218.00 --> 3218.70] So thank you for that. |
[3220.54 --> 3220.98] Great. |
[3221.90 --> 3223.84] So we are just about to wrap up. |
[3224.10 --> 3226.48] I have one last very important question. |
[3227.00 --> 3230.88] What is the most important takeaway for our listeners from our conversation? |
[3231.32 --> 3232.68] What would you like them to remember? |
[3233.06 --> 3234.34] A very good question. |
[3234.34 --> 3240.04] I would say don't be afraid to take decisions. |
[3240.42 --> 3245.30] Don't be afraid to make a bad decision. |
[3245.70 --> 3250.82] Just constantly learn and react and constantly adapt. |
[3251.18 --> 3251.60] I love that. |
[3251.96 --> 3252.86] That's amazing, Romana. |
[3252.96 --> 3253.74] Thank you very much. |
[3254.00 --> 3254.58] This was a pleasure. |
[3254.84 --> 3255.40] Thank you also. |
[3255.40 --> 3261.64] Thank you for tuning in to another episode of Ship It. |
[3261.88 --> 3263.68] I enjoyed making it for you. |
[3263.96 --> 3267.42] This is just one of the podcasts for developers that we ship. |
[3267.80 --> 3271.12] Go to changelog.com forward slash master for the rest. |
[3271.50 --> 3276.64] You can join me and the rest of our community at changelog.com forward slash community. |
[3277.14 --> 3278.86] There are no imposters in our Slack. |
[3279.20 --> 3280.46] Everyone is welcome. |
[3280.46 --> 3284.76] Huge thanks to our partners Fastly, LaunchDarkly and The Note. |
[3285.08 --> 3288.30] Thank you Breakmaster Cylinder for all our awesome things. |
[3288.78 --> 3289.78] That's it for this week. |
[3290.04 --> 3290.66] See you next week. |
[3310.46 --> 3321.24] Game on. |
• Release engineering importance for open source projects |
• Relationship between developers and end users of open source software |
• Core infrastructure components (RabbitMQ) and their reliance on stable releases |
• Comparison of release engineering in RabbitMQ and FreeBSD operating system |
• Examples of release engineering gone wrong (security bugs, breaking changes, delayed shipping) |
• Consequences of poor release engineering (lost trust, reluctance to upgrade) |
• Importance of user confidence in software releases |
• Vicious cycle of developers struggling with updates leading to decreased user adoption |
• Relationship between end-user happiness and release engineering |
• Comparison of RabbitMQ and FreeBSD as core infrastructure components |
• Discussion of specific use cases where one or the other is more critical |
• Overview of the FreeBSD release engineering process, including a fixed interval between major releases and flexible planning |
• The FreeBSD development process involves a detailed calendar for planning and communication |
• The community can plan and test new versions in advance, with Netflix being one example |
• The release engineering timeline depends on whether it's a minor or major release |
• Minor releases typically take weeks to months, while major releases take 2-3 months or more |
• Major releases do not follow semantic versioning, but aim for compatibility between releases |
• Contributors can find tasks in the Bugzilla bug tracker and solve problems they encounter with FreeBSD to contribute |
• The community can participate by submitting patches through GitHub pull requests, mailing lists, or Bugzilla |
• Release engineering in FreeBSD |
• Calendar-based release cycles for major and minor releases |
• Communication and organization improvements through fixed intervals and advance announcements |
• Other open-source projects (Darktable, Mesa library) that implement similar release engineering strategies |
• Balance between shipping stable software and incorporating new features/drivers |
• Difficulty of testing complex graphics drivers and finding the right balance in shipping updates |
• Use of Erlang for web development and its benefits |
• Hot code reloading feature of Erlang and its challenges |
• RabbitMQ not using hot code reloading due to complexity |
• Packaging and configuration management issues with Erlang-based systems |
• Challenges of packaging and distributing complex distributed stateful systems like RabbitMQ |
• Benefits of containerization and Kubernetes in managing such systems |
• Challenges with databases in containerized environments |
• Limitations of RabbitMQ's current functionality compared to traditional systems |
• Discussion of implementing hot code reloading in RabbitMQ |
• Potential benefits and feasibility of implementing hot code reloading only for bug fixes |
• Release engineering practices and experiences shared by users of open-source projects |
**Gerhard Lazu:** So end of 2016 I have joined this new team of developers, and they were the RabbitMQ core developers. The context of that meeting was the RabbitMQ Summit, which is something that used to happen every six months, twice a year. But that stopped, obviously, since the pandemic and all the recent changes. |
The one person over the years that I really enjoyed working with is Jean-Sébastien. And if you're wondering who you can thank for all the makefile madness that I'm leaving in my trail, it's Jean-Sébastien. He's the one who introduced me to make, and the rest is history, as they say. Not only that, but he also introduce... |
\[04:16\] So for the listeners - I mean, you've made so far into this episode, and you're still wondering what do I do; for those that don't know yet, this is where I tell you that my dayjob is to work on RabbitMQ. I'm a RabbitMQ core developer, same as Jean-Sébastien. So welcome, Jean-Sébastien, joining me in this new... |
**Jean-Sébastien Pedron:** Thank you very much. |
**Gerhard Lazu:** You're very welcome. I was looking forward to this for a long time, actually... And one of the topics that are very relevant to this show are release engineering. And this is something that both you and me have been thinking about for years in the context of RabbitMQ, and have been working on it in di... |
I think it's an important part of a project, and in particular an open source project. The first reason is that you want to ship your code to end users to help them solve their own problems; you want those users to be happy with what you ship, and I think that to make that happen you need to communicate well with those... |
You also want those users to give you feedback on what you shipped, because that's how you can also improve your codebase and make the next version better than the current one. So yeah, that's what I would expect from a good release engineering, and I'd say that it's important for open source products, because you do n... |
**Gerhard Lazu:** I think that relationship is really important, right? ...the relationship of an open source developer with a user of open source... And that has gone through many ups and downs over the years. I don't know exactly where it stands now, but it is becoming increasingly important for these projects and pr... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.