Open source is a flourishing and beneficial ecosystem that publicly solves problems in communities and industries using software developed through a decentralized model and community contributions. Over the years, this ecosystem has grown in number and strength among hobbyists and professionals alike. It's mainstream now—even proprietary companies use open source to build software. With the ecosystem booming, many developers want to get in and build new open source projects. The question is: How do you achieve that successfully? This article will demystify the lifecycle and structure of open source projects. I want to give you an overview of what goes on inside an open source project and show you how to build a successful and sustainable project based on my personal experience.
Open source software (OSS), once a niche segment of the development landscape, is now ubiquitous. This growth is fantastic for the open source community. However, as the usage of OSS increases, so do concerns about security. Especially in mission-critical applications— think medical devices, automobiles, space flight, and nuclear facilities—securing open source technology is of the utmost priority. No individual entity, whether developers, organizations, or governments, can single-handedly solve this problem. The best outcome is possible when all of them come together to collaborate. The Open Source Security Foundation (OpenSSF) formed to facilitate this collaboration.
In August 2022 the Office of the National Coordinator for Health Information Technology (ONC) launched the 2022 Public Health Data Systems Task Force as a subcommittee of the Health Information Technology Advisory Committee (HITAC). The task force will meet through the beginning of November to present recommendations continuing and building upon the work of the 2021 task force. Members of the task force include individuals from various levels of government, relevant public health associations, and industry partners. Specifically, the task force is focused on the certification criteria for EHR products certified under the ONC Health IT Certification Program that cover transmission of data from EHRs to public health in these domains...
When I was around 5 years old, my father brought home our first computer. From that moment on, I knew I wanted to pursue a career in computers. I haven't stopped hanging around them since. During high school, when considering which specific area I wanted to focus on, I started experimenting with hacking, and that was the moment I decided to pursue a career as a security engineer. I'm now a software engineer on the security compliance team. I've been at Red Hat for over two years, and I work remotely in the Czech Republic. Outside of my day job, I play blind football, and I'm involved in various projects connecting visually impaired and sighted people together, including working in a small NGO that runs activities for blind and visually impaired people. I'm also working on an accessible Fedora project currently called Fegora, an unofficial Linux distribution aimed at visually impaired users.
Open source is critical in data analysis while providing long-term benefits for the users, community members, and business. 
Amazing though it may seem, we each experience the world differently. That's one reality with over 6 billion interpretations. Many of us use computers to broaden our experience of the world, but a computer is part of reality and so if you experience reality without, for instance, vision or sound, then you also experience a computer without vision or sound (or whatever your unique experience might be). As humans, we don't quite have the power to experience the world the way somebody does. We can mimic some of the surface-level things (I can close my eyes to mimic blindness, for example) but it's only an imitation, without history, context, or urgency. As a result of this complexity, we humans design things primarily for ourselves, based on the way we experience the world. That can be frustrating, from an engineering and design viewpoint, because even when you intend to be inclusive, you end up forgetting something "obvious" and essential, or the solution to one problem introduces a problem for someone else, and so on. What's an open source enthusiast, or programmer, or architect, or teacher, or just everyday hacker, supposed to do to make software, communities, and processes accessible?
To be an effective leader in an open source community, you need a lot of information. How do I know who the most active members in my community are? Which companies are making the most contributions? Which contributors are drifting away and becoming inactive? Who in the community is knowledgeable about a specific topic? These were just a few of the questions I had when I started leading the Mautic community at Acquia. But the problem was not a shortage of information. On the contrary, there were so many places our community interacted and so many things to track that I was drowning in data. I could access plenty of data sources, but they were not helping me manage the community effectively or answering my questions.
Public health information systems have always been a key component of the healthcare ecosystem. Links between clinical care and public health have only been increasing, propelled by the pandemic. As defined by the Public Health Informatics Institute (PHII) in its 2021 Immunization Information System (IIS) Core Competency Model, information systems management is the “application and administration of technologies to securely and effectively meet IIS program and user needs”. The pandemic highlighted the need for public health information systems to collect, track, and monitor vaccine administration for ages newborn through adulthood, and mandated data to be reported or accessible to a broad range of recipients at the local, state and federal level.
Open source is one of the most important technology trends of our time. It’s the lifeblood of the digital economy and the preeminent way that software-based innovation happens today. In fact, it’s estimated that over 90% of software released today contains open source libraries. There's no doubt the open source model is effective and impactful. But is there still room for improvement? When comparing the broader software industry’s processes to that of open source communities, one big gap stands out: productivity management. By and large, open source project leads and maintainers have been slow to adopt modern productivity and project management practices and tools commonly embraced by startups and enterprises to drive the efficiency and predictability of software development processes. It’s time we examine how the application of these approaches and capabilities can improve the management of open source projects for the better.
The Free Software Foundation (FSF) started promoting the idea of sharing code way back in 1985, and since then it's defended the rights of computer users and developers. The FSF says that the terms "open" and "closed" are not effective words when classifying software, and instead considers programs either freedom-respecting ("free" or "libre") or freedom-trampling ("non-free" or "proprietary"). Whatever terminology you use, the imperative is that computers must belong, part and parcel, to the users, and not to the corporations that owns the software the computers run. This is why the GNU Project, and the Linux kernel, Freedesktop.org, and so many other open source projects are so important.
Understanding the basics and best practices for establishing and maintaining a Site Reliability Engineering (SRE) program in an organization...SREs are responsible for maximizing reliability, performance availability, latency, efficiency, monitoring, emergency response, change management, release planning, and capacity planning for both infrastructure and software. As applications and infrastructure grow more complex, SRE teams help ensure that these systems can evolve.
Opensource.com has surveyed the landscape of popular open source project management tools. We've done this before—but this time we've added a twist. This time, we're looking specifically at tools that support agile methodology, including related practices such as Scrum, Lean, and Kanban. The growth of interest in and use of agile is why we've decided to focus on these types of tools this year. A majority of organizations say they are using agile approaches at least sometimes. In addition, agile projects are 28% more successful than projects managed with traditional approaches. For this roundup, we looked at the project management tools we covered in 2014, 2015, and 2016 and plucked the ones that support agile, then did research to uncover any additions or changes. Whether your organization is already using agile or is one of the many planning to adopt agile approaches, one of these seven open source project management tools, in no particular order, may be exactly what you're looking for.
It's not a secret that maintaining an open source project is often thankless and time-consuming work. However, I've learned that there's one shared joy among open source maintainers: They love building with a group of technologists who passionately believe in their vision...Check out these methods that open source maintainers can use to attract contributors in a genuine manner.