News
How to encrypt sensitive data in playbooks with Ansible Vault
Ansible Vault lets you keep sensitive data, such as passwords and keys, in encrypted files. Here’s how to use it in playbooks to improve automation workflow safety. Read More at Enable Sysadmin
The post How to encrypt sensitive data in playbooks with Ansible Vault appeared first on Linux.com.
Parabola GNU/Linux-libre: [nonsystemd] NetworkManager, dbus and display managers require manual intervention
We have recently began a repackaging of [nonsystemd] packages (see #3290). The displaymanager-openrc package has been removed and specific init scripts have been added for their respective display manager (e.g. sddm-openrc for sddm, gdm-openrc for gdm and so on with lxdm, xdm and lightdm)
Regarding NetworkManager and dbus, their nonsystemd builds used to ship with their corresponding OpenRC init scripts, but now they were separated into networkmanager-openrc and dbus-openrc. Please install these when upgrading those packages.
Android removes much of Fuchsia-related code as Starnix project progresses
Request Spec Realistic Error Response
health @ Savannah: GNU Health project to implement REUSE compliance
The REUSE initiative[1] is a Free Software Foundation Europe program that facilitates the documentation of licenses of Libre projects like GNU Health.
After several meetings with our friends from FSFE, we have decided to implement REUSE in all GNUHealth components, that is:
- Hospital Management System
- MyGNUHealth Personal Health Record
- Thalamus
- GH Federation Portal
We believe that for large projects like GNUHealth, with multiple files of different kinds (code, graphics, data, ..) REUSE will be a great companion.
Peoples BLOG: Read Data to Paragraph Template in Drupal Application
Glimmer DSL for SWT v4.24.0.2
rush @ Savannah: GNU rush version 2.3
GNU rush version 2.3 is available for download. This is a bug-fixing release.
Community Working Group posts: Code of Conduct team update: July 13, 2022
As previously reported, the Community Health Team has started to have regular, bi-weekly meetings in an effort to develop and update the Code of Conduct (CoC) for the Drupal community.
Community Health Team members present at this week’s meeting were
We began the meeting with a review and updates related to our community outreach plans. We also briefly discussed how best to collect feedback, especially from individuals who want to provide anonymous feedback. We also discussed some additional Drupal community groups we want to reach out to for this effort.
In an effort to continue familiarizing ourselves with other communities’ Codes of Conduct, we decided that we’d ask our community members which Codes of Conduct they’d like us to review. If you have any thoughts on this, please let us know at drupal-cwg at drupal dot org. We will also utilize the @drupalcommunity Twitter account for this effort.
We discussed what the next few steps in this process should be. One option is to figure out the “categories” of Code of Conducts that exist for open source communities, review relevant examples and categorize them. With this research, we’ll be in a much better position to decide on the category(ies) of CoC we envision for Drupal. After that, we’ll draft a list of elements we feel should be included in our updated CoC.
Finally, we set a goal for the completion of a new, revised, ready-to-adopt CoC: December 14, 2022.
A number of Drupal-related groups and individuals have confirmed their willingness to provide feedback to this effort as the process proceeds. If you, or a Drupal-related group, is interested in being part of this process, please let us know at drupal-cwg at drupal dot org.