Open-source News

x86 Raspberry Pi Desktop is a great way to revive an old PC  The Register

While no new X.Org "katamari" releases are planned for a collection of all the X.Org component updates combined, this weekend longtime X.Org contributor Alan Coopersmith of Oracle issued many new updates to various old, seldom-maintained X.Org projects...

One of the newest extensions now supported by the RADV Vulkan driver is VK_KHR_performance_query, which can be used by RenderDoc and other utilities...

In gearing up for the GNOME 43 Alpha release coming out soon, this weekend marked the release of the new alpha versions of GNOME Shell and Mutter...

Linode + Kali Linux: Added security for cloud instances  Help Net Security

Rob Clark as the lead developer of the MSM DRM kernel driver and the Freedreno/TURNIP Mesa drivers for open-source Qualcomm Adreno graphics driver support has submitted the Direct Rendering Manager driver changes for the upcoming Linux 5.20 merge window...

9to5Linux Weekly Roundup: July 10th, 2022  9to5Linux

Calibre 6.0 Released with Full-Text Search, ARM64 Support on Linux, Qt 6 Port  9to5Linux

An open conversation about open societies Bryan Behrenshausen Mon, 07/11/2022 - 03:00 2 readers like this 2 readers like this

Throughout the course of human history, why have some societies endured and evolved while others have struggled and disappeared? According to author Johan Norberg, being "open" might have something to do with it.

Learn about open organizations Download resources Join the community What is an open organization? How open is your organization?

Norberg is the author of Open: The Story of Human Progress, a book several members of the Open Organization community found so compelling that we decided to publish a four-part series of reviews on it.

Happily, we were recently able to sit down with the author and continue our discussion. We wondered exactly what "being open" is in the context of global governance and international relations today. And how might we locate guidelines and approaches that will move everyone toward a greater good for the entire global community?

We recorded our conversation, are delighted to share it, and hope you find it as insightful as we did.

Check out the articles below to read the series.

Watch our interview with Johan Norberg, author of Open: The Story of Human Progress.

Image by:

Opensource.com

The Open Organization What to read next Open exchange, open doors, open minds: A recipe for global progress Making the case for openness as the engine of human progress 4 questions about the essence of openness The path to an open world begins with inclusivity This work is licensed under a Creative Commons Attribution-Share Alike 4.0 International License. 2434 points Tokyo, Japan

Ron McFarland has been working in Japan for over 40 years, and he's spent more than 30 of them in international sales, sales management training, and expanding sales worldwide. He's worked in or been to more than 80 countries. Over the most recent 17 years, Ron had established distributors in the United States and throughout Europe for a Tokyo-headquartered, Japanese hardware cutting tool manufacturer. More recently, he's begun giving seminars in English and Japanese to people interested in his overseas travels and expanding business overseas. You can find him on LinkedIn.

| Follow RonmcfarlMc Open Source Champion Author Open Organization Ambassador Contributor Club 2 Comments Register or Login to post a comment. Ron McFarland | July 11, 2022

In my article the path to an open world begins with inclusivity, I mention six steps to promote inclusivity in societies, namely, 1-Recognition, 2-Respect, 3-Understanding, 4-Tolerance, 5-Optimism, and 6-Patience. In this discussion two other concerns were mentioned:

The issue of overcoming fear of others is another concern that should be address.

Furthermore, the issue of values also came up. Based on our personal values, there are societies or even communities that we don’t want to be a part of. This could be included in those steps I write about.

Bryan Behrenshausen | July 11, 2022

I really enjoyed this conversation and hope we can do it again some time!

Why Agile coaches need internal cooperation Kelsea Zhang Mon, 07/11/2022 - 03:00 3 readers like this 3 readers like this

If you're an Agile coach, you probably seek to inspire and empower others as an external member of your team or department. However, many Agile coaches overlook the importance of internal cooperation. That's not necessarily a term you are familiar with, so allow me to explain.

What is internal cooperation?

As an Agile coach, you don't work alone. You try to find a partner in the team you're taking care of. This partner is expected to:

• Undertake all or most of the Agile transformation in the future.
• Find all possible opportunities for systematic improvement and team optimization.
• Be self-motivated.
• Not be managed by you; you delegate your enthusiasm and vision to them.

Of course, maybe you don't need such a person because, theoretically speaking, everyone in the team is your ideal candidate, and everyone is self-driven. Or maybe your whole team will magically become what you want it to be overnight.

Reality check: most of the time, you need a partner, an inside agent. Somebody to keep the spirit of Agile alive, whether you're there to encourage it or not.

More DevOps resources What is DevOps? The ultimate DevOps hiring guide DevOps monitoring tools guide A guide to implementing DevSecOps Download the DevOps glossary eBook: Ansible for DevOps Latest DevOps articles Internal cooperation is required

Getting buy-in from the team you are coaching isn't a luxury; it's a requirement. If you're the only Agile practitioner on your team, then your team isn't Agile! So how do you cultivate this internal cooperation?

Clarify responsibility

Being Agile is supposed to be a team effort. The beneficiary is the team itself, but the team must also bear the burden of transformation. An Agile coach is meant to be inspiring and empowering, but the change doesn't happen in just one person. That's why teams must learn to consider and solve problems on their own. A team must have its own engine (your Agile partner is such an engine) rather than relying on the external force of the Agile coach. It's the engines that want to solve problems, and with the help of Agile coaches, their abilities and ways of thinking can be enriched and improved.

It's best to have an engine from the beginning, but that's not always possible. The earlier, the better, so look for allies from the start.

Know the team

When you find a partner, you gain someone who understands the team's situation better than you do. A good partner knows the team from the inside and communicates with it on a level you cannot. No matter how good you are as an Agile coach, you must recognize that an excellent Agile partner has a unique advantage in "localization."

The best approach is not An Agile coach makes a customized implementation plan for the team, and then the team is responsible for execution. In my opinion, with the support of the Agile coach, the Agile partner should work with the team to make plans that best fit its needs. Next, try to implement those plans with frequent feedback and keep adjusting them as needed.

You continue to observe progress, whether the team members falter in Agile principles, and give them support at the right moments. Of course, when there's something wrong, you often want to stay silent, let the team hit a wall, and learn from their setbacks. Other times, stepping in to provide guidance is the right thing.

[ Related read: Agile adoption: 6 strategic steps for IT leaders ]

Is an Agile coach still necessary?

In a word: Absolutely!

Agile is a team effort. Everyone must collaborate to find processes that work. Solutions are often sparked by the collision of ideas between the Agile coach and the partner. Then the partner can accurately get how an Agile theory is applied in the daily work. The partner understands the essence of Agile theories through the solutions.

As an Agile coach, you must have a solid theoretical foundation and the ability to apply that theory to specific scenarios. On the surface, you take charge of the theory while your Agile partner is responsible for the practice. However, an Agile coach must not be an armchair strategist, and teams aren't supposed to assume that the Agile coach is a theorist. In fact, an Agile coach must consciously let go of the practice part so the Agile partner can take over.

The significance of accompanying a team is not supposed to be pushing the team to move passively toward the Agile coach's vision. The amount of guidance required from you will fluctuate over time, but it shouldn't and can't last forever.

Find an Agile partner

How do you find your Agile partner? First of all, observe the team you are coaching and notice anyone who is in charge of continuous improvement, whether it's their defined job role or not. That person is your Agile partner.

If there's nobody like that yet, you must cultivate one. Be sure to choose someone with a good sense of project management. I have observed that team leaders or project managers who perform well in the traditional development model may not be good candidates in the Agile environment. In an Agile management model, you must have an open mind, a sense of continuous pursuit of excellence, a flexible approach, extensive knowledge, and strong self-motivation.

Be Agile together

Don't be shy about bringing on a partner to help you with your work and communication. Instead, find willing partners, and work together to make your organization an Agile one.

This article is translated from Xu Dongwei's Blog and is republished with permission.

An Agile coach is only as successful as their Agile partner. Here's how to foster internal cooperation and create an Agile team.

Image by:

Image by Mapbox Uncharted ERG, CC-BY 3.0 US

DevOps Agile Careers What to read next 5 agile mistakes I've made and how to solve them This work is licensed under a Creative Commons Attribution-Share Alike 4.0 International License. Register or Login to post a comment.

The post How to Install MariaDB in RHEL and Debian Systems first appeared on Tecmint: Linux Howtos, Tutorials & Guides .

MariaDB is a binary drop-in replacement for MySQL, developed by the original authors of MySQL Project and fully compatible with MySQL having more features and better performance enhancement. Why should I Use MariaDB? As

The post How to Install MariaDB in RHEL and Debian Systems first appeared on Tecmint: Linux Howtos, Tutorials & Guides.

SolidRun's 64-bit Renesas RZ/G2 based SOMs  Aerospace Manufacturing and Design

And they still wonder why linux isn't more popular.  HardForum

Linus Torvalds just announced the availability of Linux 5.19-rc6 as the latest routine test release for the upcoming Linux 5.19...

Audacious 4.2 Adds Initial Support for Ogg FLAC Streams, Winamp UI Enhancements  9to5Linux

A set of proposed patches promise to make the Linux kernel's memchr() implementation faster for locating a character within a block of memory. In tests carried out by the developer, the new implementation can be nearly four times faster on large searches...

Intel's open-source Compute Runtime for providing OpenCL and oneAPI Level Zero support on their graphics hardware appears to be in roughly good shape now for DG2/Alchemist based on external/independent monitoring of the effort...

AMD Ryzen Pro chips with Microsoft Pluton won't boot Linux  KitGuru

The Linux kernel has long honored the "nordrand" kernel parameter to disable kernel use of the Intel RDRAND and RDSEED instructions if not trusting them -- either out of security concerns that they could be compromised by the vendor or running into hardware/firmware issues around RdRand usage. But the Linux kernel is preparing to drop that kernel parameter with users encouraged to use the more generic "random.trust_cpu" parameter...

Linux To Drop "nordrand" Option - Users Should Instead Switch To "random.trust_cpu"  Phoronix