Category: News

Dear members of the F-Droid community,

I am happy to make the announcement of this year’s F-Droid Board of
Directors appointments. First and foremost, thank you to everyone who made
a nomination, and to all the nominees for their interest in contributing to
F-Droid’s governance. Juliana Sims, Peter Serwylo and myself, Sebastian
Crane, have been selected for two year terms on the Board. I feel honoured
to have been chosen and look forward to serving the F-Droid community, a
sentiment I share with my fellow new arrivals:

“As a passionate free software advocate and F-Droid user, I am delighted to bring my experience with community organizing and moderation to the Board in order to help the F-Droid project and community continue to grow equitably and inclusively into the future.”
– Juliana Sims

“F-Droid is an extremely important part of the free software ecosystem.
With so many people carrying powerful computers in their pockets, it is more important than ever to have a strong free software alternative to the proprietary app stores, walled gardens, and adware found elsewhere.
I’m constantly amazed by what the F-Droid team and community have achieved, and look forward to serving on the board, bringing my software development and computer science background to help the project grow.”
– Peter Serwylo

Not only will this bring new perspectives to the Board, but it will also
enhance its geographic diversity. Peter lives in Australia, Juliana is on
the USA’s Eastern Seaboard, and I hail from Britain. That means two
countries hitherto unrepresented on the Board of Directors, and our first
director from south of the Equator! This is especially welcome given how
F-Droid is part of the global movement of Free and Open Source Software
(FOSS).

As originally planned, Max Mehl, one the founding directors of the Board, is
leaving. I am sure I speak for the whole F-Droid community in wanting to
express gratitude for his service to the project. Max has a few words with
which to bid the Board farewell:

“I would like to thank the F-Droid community and my fellow Board members for giving me the opportunity to serve on the founding Board.
Having been an avid user since the early days of F-Droid, this role has made the often time-consuming and tedious background tasks much more transparent to me.
So my greatest appreciation goes to the volunteers who put so much long-term work into F-Droid!

My wish and hope is that the Board will continue to reduce the friction for current and future F-Droid contributors, while at the same time professionalising the handling of incidents and conflicts.
I am confident that the Board in its new composition has everything it takes to succeed.”
– Max Mehl

Andrew Lewman and Matthias Kirschner continue their two-year terms as
directors, and Hans-Christoph Steiner continues his two-year term as
Technical Lead (a non-director role advisory to the Board). Showing their
belief in F-Droid, Morgan Lemmer-Webber, John Sullivan and Michael Downey
volunteered to continue after their initial one-year terms and have
subsequently been re-elected. This will help to maintain continuity in what
is the first change to the Board’s composition since its founding, and
brings the total number of directors to eight, up from six directors during
the Board’s first year.

Since its formation, the F-Droid Board of Directors has had four designated
roles, namely that of Chair, Vice Chair, Clerk and Treasurer. Although none
of the directors holding these positions are leaving, the Board has chosen
to introduce one additional role and reassign an existing one: Peter will
take the newly-created position of Vice Clerk, and I will succeed Morgan as
the Chair. John, Andrew and Michael will continue in their capacities of
Vice Chair, Clerk and Treasurer respectively.

The Board is therefore now composed as follows:

• Sebastian Crane (Chair) – until 2026
• Michael Downey (Treasurer) – reappointed, until 2025
• Matthias Kirschner – until 2025
• Morgan Lemmer-Webber – reappointed, until 2025
• Andrew Lewman (Clerk) – until 2025
• Peter Serwylo (Vice Clerk) – until 2026
• Juliana Sims – until 2026
• Hans-Christoph Steiner – ex officio, until 2026
• John Sullivan (Vice Chair) – reappointed, until 2026

During 2024, the Board of Directors intends to form new subcommittees to
establish additional points of liaison between the Board and those
interested in specific aspects of F-Droid’s activities (fundraising, for
instance). If the prospect of participating in such discussions interests
you, please keep an eye out for further announcements! Board meetings
continue to be open to the entire community, and will be announced in
advance on the F-Droid Forum.

Best regards,

Sebastian Crane on behalf of the F-Droid Board of Directors

Anyone who has spent any time recently using non-GNOME GTK desktop environments, like Cinnamon, MATE, or Xfce, has had to deal with the unfortunate reality of a lot of GTK applications becoming GNOME applications instead, using GNOME’s own libadwaita. These applications are hard to theme, and do not integrate at all with the proper GTK applications non-GNOME desktop environments ship with. With how popular GNOME is, this has meant that the number of non-GNOME GTK applications has been dwindling. Linux Mint, the popular Linux distribution that also develops the Cinnamon desktop environment, has long made a bundle of GTK applications called XApps – basically forks of various core GNOME 3.x applications to ensure they would have access to non-GNOME GTK applications. With GNOME effectively forking GTK into its own, unique, GNOME-specific style (like libaidwaita), other GTK environments have suffered, and XApps were intended to close that gap. That hasn’t really happened though, as XApps remained mostly a Mint-only thing, managed by Mint, as part of the Mint/Cinnamon GitHub projects. Other distributions and GTK desktop environments, such as Xfce, MATE, Budgie, and so on, didn’t really pick them up. The Linux Mint project intends to change that, and will ‘spin off’ the XApps into its own, dedicated, independent project to facilitate cross-distribution and cross-DE collaboration, decision-making and development, all in an effort to ensure the long-term viability of non-GNOME GTK desktop environments. They also intend to fork a lot more of the GNOME 3 applications, for the same reason I mentioned earlier: GNOME applications are no longer GTK applications, but GNOME applications – they look and feel horribly out of place in environments that don’t use the GNOME-specific libadwaita. As such, Celluloid, GNOME Calculator, Simple Scan, Baobab, System Monitor, GNOME Calendar, File Roller, and Zenity were recently downgraded in Linux Mint to their last GTK 3 versions, and will most likely be forked in the near future. In addition, the Adwaita theme, the default GNOME/GTK theme, will be removed from the list of available themes in Cinnamon 6.2. Adwaita, too, has become increasingly GNOME-only, and thus, increasingly broken on non-GNOME desktop environments. Flat-our removing Adwaita altogether is not possible, since it’s a GTK dependency, but hiding it from the theme selector is not an issue, of course. As project lead Clément Lefèbvre writes: libAdwaita is for GNOME and GNOME only. We can’t blame GNOME for this, they’ve been very clear about it from the start. It was made specifically for GNOME to have more freedom and build its own ecosystem without impacting GTK. We want to send a strong signal upstream and towards other projects. We cannot and will not support applications which do not support our users and environments. We can’t promote applications to our users which don’t support our users. The software manager will be vigilant towards that going forward and list compatible software by default. ↫ Clément Lefèbvre All of this is great news to hear. I’ve been making extensive use of Xfce on OpenBSD lately, and on the Fedora Xfce spin in the weeks before that, and the situation has become almost comical. If you install any GNOME application on Xfce, theming just breaks down completely, as most themes are either not made to support the massive headerbars GNOME uses, or they do support it but still look horribly out of place compared to the more sane titlebar plus menubar plus toolbar layout of traditional desktop environments like Xfce. I’ve long been saying that the non-GNOME GTK desktop environments need to work together to formulate an answer to the onslaught of libadwaita and the GNOME-ification of GTK, because each of them risks becoming entirely tied to whatever GNOME and libadwaita decides to do, for better or worse. It seems the Linux Mint team has finally realised this as well, and I really hope – and strongly suggest – Xfce, MATE, and others join them as well. If they don’t, there won’t be an Xfce in a few years. What’s the point in developing Xfce if you’re at the mercy of whatever choices GNOME makes?

Grand Theft Auto:San Andreas 2024 new gameplay Fighting With People Part 11

Welcome to the adrenaline-pumping world of Grand Theft Auto: San Andreas! In this action-packed gameplay series, we dive deep into the streets of San Andreas as we take on intense combat scenarios against various opponents.

Grand Theft Auto:San Andreas 2024 new gameplay Fighting With People Part 11

“Fighting With People,” we unleash the raw power of CJ as we engage in fierce brawls, street fights, and epic showdowns with rival gangs and street thugs. With an arsenal of punches, kicks, and melee weapons at our disposal, every encounter is a test of skill and strategy.

Grand Theft Auto:San Andreas 2024 new gameplay Fighting With People Part 11

Join us on this thrilling journey as we navigate through the dangerous alleys and urban landscapes of San Andreas, showcasing intense combat sequences, close-quarters combat tactics, and jaw-dropping moments of action-packed mayhem.

Grand Theft Auto:San Andreas 2024 new gameplay Fighting With People Part 11

Get ready to witness intense battles, epic takedowns, and adrenaline-fueled combat like never before in Grand Theft Auto: San Andreas Fighting With People !

Grand Theft Auto:San Andreas 2024 new gameplay Fighting With People Part 11

Don’t forget to like, subscribe, and hit the notification bell to stay updated with the latest episodes. Let the brawl begin!

Grand Theft Auto:San Andreas 2024 new gameplay Fighting With People Part 11

28 avril 2 024
Entrevue entre Abigaëlle Richard & Elena Danaan
Canada, Irlande => Univers

~

Titre & source originels
« Divulgation galactique, contacts physiques et connexions du coeur. Discussion avec Elena Danaan »
https://www.youtube.com/watch?v=CdJshMvqNKM

~

Dans cette entrevue en français sous-titrée adéquatement en anglais, Elena Danaan fait des distinctions cruciales entre les différents groupes impliqués dans la divulgation galactique et dans la sphère spirituelle.

Elle discute également de la différence entre les informations apportées par les contactés qui ont des contacts physiques directs avec les ET et les crypto-terrestres, ce qui implique d’avoir des preuves directes, physiques et corroborantes, versus les autres starseeds qui ne sont pas des contactés physiques en soi, mais qui sont également encouragés à partager leur cheminement, cependant dans des contextes différents (et moins officiels) (avec moins ou pas d’attentes de preuves), puisqu’il s’agit d’une connexion télépathique ou du cœur avec notre propre âme, sa matrice d’âme et notre groupe d’âmes.

Enfin, Elena présente les grands risques et la confusion associés à la « canalisation ».

Joignez-vous à mon canal Telegram: https://t.me/+b9C5G6kohfY3YWMx
Chaîne Youtube en français d’Elena:
/ @elenadanaanfrance8228
Chaîne YouTube en anglais d’Elena:
/ @elenadanaan
Webinaires d’Elena: https://www.elenadanaan.org/webinars
Site web d’Elena: https://www.elenadanaan.org/
Livres d’Elena en français et en anglais: https://www.elenadanaan.org/elena-danaan-author
Entrevue précédente (en anglais) avec Elena: https://www.abigaellerichard.com/post/being-elena-danaan-a-more-personal-interview-video-on-the-youtube-channel-the-grounded-starseed

~

♥ . . .

~

Listes de lecture connexes :

● Elena Danaan
https://www.dailymotion.com/playlist/x7tyif

● Retrouver sa Souveraineté ֎ 1
https://www.dailymotion.com/playlist/x7hilg

● Retrouver sa Souveraineté ֎ 2
https://www.dailymotion.com/playlist/x823ic

● Dans les coulisses du monde ֎ 1
https://www.dailymotion.com/playlist/x75jq1

● Dans les coulisses du monde ֎ 2
https://www.dailymotion.com/playlist/x7y0mr

~

} Si lecture impossible de vidéo, désactiver le bloqueur de publicité ABP icône panneau routier « Stop » en haut à droite de la barre d’adresse dans Google Chrome.
} Si le lecteur indique « vidéo réservée aux adultes » alors désactiver le Filtre Parental en bas de la page de présentation de la vidéothèque.
} Afin de préserver de la calcification la glande pinéale qui est l’un des éléments corporels permettant la reliance au spirituel, il est nécessaire, certes d’utiliser des dentifrices sans fluor comme ceux à l’argile mais également de porter des lunettes spécial écran d’ordinateur afin de réduire la réception de la lumière bleue.

Aryna Sabalenka continued her Madrid Open title defence with a win over the in-form Danielle Collins

I’m assuming you are reading this because you are already convinced that migrating your Drupal 7 site to Drupal 10 is not just a proactive measure but a strategic move for your organization. But to anyone else on your team it looks like an unnecessary big project to rebuild the website when it’ll look and feel the same (we always recommend redesigns or additional features during a D7 to D10 Migration).
We get it. For folks not in the know, this seems like a waste of funds. However, with Drupal 7 coming to an end in about 9 months (January 5th, 2025), the urgency to transition becomes increasingly stressful. We know you know, but you still have your team members (or your boss!) left to convince. Let’s make it easier for you with this article.

Understanding the impact of Drupal 7 End of Life
Before you talk to your team about why you need to migrate to Drupal 10, let’s examine some of the implications of persisting with Drupal 7. 

No more security updates or advisories for core, contributed modules and themes. The Drupal Security Team may publicly post moderate to less critical issues affecting Drupal 7 in the public issue queue for resolution, provided they are not widely exploitable.
Unsupported Drupal 7 contributed modules or themes won’t be eligible for new maintainership or reclassification as supported. If you’re currently using them, it is a good idea to take ownership or be a maintainer of those projects.
PHP version 5.5 and below will now be supported. This lack of support could lead to compatibility issues, security vulnerabilities, and potential performance drawbacks.
If your Drupal 7 website is running on Windows, you will no longer receive security fixes for Windows-related issues. It is recommended to move to a different operating system.
You will no longer receive assistance for tasks associated with Drupal 7, such as documentation navigation, automated testing, packaging, and other related activities.

Making the case for Drupal 7 to 10 migration to your team
Let’s give you some powerful pointers to discuss with your team to get buy-in on the Drupal 7 to 10 migration.
Remarkably Enhanced User Experience for Content Editors and Site Builders in D10
There are 3 things that matter a lot to content editors and site builders :  

User-friendly admin interface – It should allow for efficient content creation, editing, and site management without requiring extensive technical knowledge.
Customization – This includes options for customizing layouts, adding new features, and integrating third-party tools and services.
Media management – To upload, organize, and embed images, videos, and other multimedia content within articles.

Claro admin theme
Drupal 10’s new Claro admin theme (a part of core) offers a clean, modern and user-friendly interface to help organize and find what you need easily. Olivero is the new default front-end theme now and it comes with a modern look and feel. The theme integrates seamlessly with all of Drupal’s features and is the most accessible theme (WCAG level AA compliant) till now. The flexible Layout builder module is now in core and it is now easier to create pages and customize layouts the way you want. The modern and functional media management system makes it simpler to upload, reuse, and manage media assets on your Drupal site.
Optimized Website Performance and SEO Improvements
With every new release, Drupal is getting better at delivering performance. With Drupal 10’s new and improved caching mechanisms, BigPipe technology, optimized codebase, and effective content delivery mechanisms, your website can now load faster and offer a great user experience. It incorporates various enhancements to boost performance in content rendering and HTTP responses. With Drupal 10, you can implement lazy loading for embedded content and responsive images, significantly enhancing load times. Additionally, the introduction of the new JS minification feature dynamically reduces code and markup, thereby further improving performance. The new Single Directory Component (SDC) approach of theming your website is a revolutionary step towards frontend development which also greatly improves website performance by groupong together files necessary to render components (Twig, CSS, JS). And don’t forget, better website performance also means a better SEO ranking on search engines.
Managing Content is Easier
Now that you’ve settled into using Drupal 7 for a while, you might feel like managing content is pretty straightforward. But hold on – let me tell you about Drupal 10, where things get even smoother and more user-friendly. With Drupal 10, organizing your content consistently becomes much simpler. You can reuse existing fields easily and create new ones more smoothly, all in one place. Editing content is smoother too, with text fields that ensure your text looks just right. Plus, managing older versions of your content, whether it’s in blocks or pages, is a breeze with the new unified editing experience. The new CKEditor 5 version offers an enhanced content editing experience. Its features like drag-and-drop image insertion, real-time collaboration, and seamless integration with Drupal’s content management system make creating and editing content very simple. Its customizable toolbar allows you to tailor the editing experience to suit your specific needs. You also easily copy and paste content from Word/Google Docs to the editor without worrying about formatting as it automatically removes any markup.
Improved Security
And no, we’re not just talking about the lack of security support for Drupal 7 after Jan 2025. Because of the way it has been built and due to its many modern dependencies, Drupal 10 is now more secure than it has ever been.
As you may already be aware, Drupal has been aligning its release cycles with its dependencies, including PHP and Symfony, since version 8. This means that as PHP versions continue to evolve, older versions like Drupal 7 may become incompatible with the latest PHP releases. This lack of compatibility can leave your Drupal 7 site vulnerable to security risks and other issues. Drupal 10 relies on the latest versions of Symfony (6) and PHP (8.1), making it more secure and better performing. 
Twig, Drupal 10’s default template engine, not only simplifies the development process but also enhances security by preventing direct database interactions within the code. This prevents vulnerabilities such as cross-site scripting and code injections.
By default, Drupal 10 strengthens website security by suggesting users choose stronger passwords, minimizing unauthorized access risks through parameters like minimum length and complexity.
The Time is Now!
The urgency for you to address the Drupal 7 migration depends on the complexity of your website. The more extensive your site’s content and features, the longer the migration process will likely take. It’s going to take even longer if you have many custom modules and features. But you don’t want to rush the process. We have seen (and fixed) a lot of bad migrations (like a lot!), most of them done in haste or without proper planning. With a 9-month window to Drupal 7 end-of-life starting now, we believe this is the optimal time to initiate your migration process. A Drupal 7 to 10 migration is going to be a complete rebuild (which is why it takes time) but once you’re on Drupal 10, future upgrades are going to be very, very easy. 
Don’t forget to check out this article that features our Drupal experts discussing what’s new in Drupal 10 in detail. You can even catch up with the video of this panel discussion.
Final Thoughts
If you’re thinking this migration (Drupal 7 to Drupal 10) is going to be your last big transition, you are absolutely right. Because even though Drupal continues to innovate, progress and release further versions, your website will now only need effortless and straightforward upgrades. Yes, upgrades will remain easy forever. So what next? Start looking for a Drupal certified migration partner (like Specbee) and get a site audit (we’ll do it for you for free!) so you know how much time you have to start the migration process.

The JRuby community is pleased to announce the release of JRuby 9.4.7.0.

• Homepage: https://www.jruby.org/
• Download: https://www.jruby.org/download

JRuby 9.4.x targets Ruby 3.1 compatibility.

Thank you to our contributors this release, you help keep JRuby moving forward! @kares, @ryannevell, @jsvd

Ruby Compatibility

• Many edge cases in language compatibility have been fixed. #7440, #8128, #8192, #8193, #8195, #8197, #8198

Standard Library

• jruby-openssl is updated to 0.14.5
• rdoc is updated to 6.4.1.1
• Warnings due to method aliasing in the ostruct library have been mitigated. #8200, #8206

JVM Integration

• Ruby classes that are “reified” into a Java class and later redefined can be “re-reified” to a new Java class with an incrementing version number. #8141, #8185
• Java objects from other classloaders can pollute the Java:: namespace. This behavior can be disabled now, and will be disabled by default in JRuby 10. #8156, #8208

53 Github Issues resolved for 9.4.7.0

• #7440 Multiple assignment evaluation order consistency
• #8112 update this ancient lockfile
• #8113 Remove long dead torquebox from template Gemfile and update to newer …
• #8114 one last update to puma version for sample Gemfile
• #8119 Possible Keyword Argument Regression in 9.4.6.0
• #8121 Prepending a module to a subclass changes it representation in the superclass#subclasses array
• #8122 Handle prepend in subclasses
• #8123 lutimes was passing huge wrong values to function
• #8124 Method.clone of frozen should stay frozen
• #8125 Proc#clone of frozen proc should stay frozen
• #8126 UnboundMethod#clone of frozen UnboundMethod should stay frozen
• #8127 EncodingError should be SyntaxError for bad symbols?
• #8128 parameters value for **nil should be nokey
• #8130 Return proper encoding error string for String#to_c
• #8131 frozen error handling for remove_instance_variable
• #8132 test flags for stats need to handle file instances as well as strings
• #8133 Implement string/eval form of trace_var
• #8134 Fix various kwarg-related specs in IO#open, File#open and Kernel#open.
• #8135 Cannot install latest rubocop
• #8136 Redo java commandline calculation to work with newer Java’s
• #8138 [deps] update joda-time to 2.12.7
• #8139 to_time raise an exception. (class org.jruby.ext.date.RubyDate cannot be cast to class org.jruby.ext.date.RubyDateTime)
• #8141 can not re-reify sub-class of a Java sub-class
• #8142 Add-Opens for complete -jar runs as expected in later Java’s
• #8144 Allow extended DateTime to still be constructed using DateTime
• #8148 Profiler raises ‘wrong number of arguments for constructor (ArgumentError)’ for the march_hare gem
• #8155 Concurrently requiring a file from multiple threads may “succeed” even if the file raises an error
• #8156 JRuby adds Java proxy classes to the Java module even if they are not from JRubyClassLoader
• #8157 Incorrect case tree selection when comparing Symbols during compiled Ruby code execution
• #8167 Some simple refactoring but removing some mysterious classcast guards
• #8173 Coverage doesn’t cover begin
• #8179 Thread#pending_interupt? crashes
• #8185 [ji] support re-reifying class hierarchy
• #8186 [fix] LoadError on require should not complete load
• #8191 Rearrange cond0 to behave more like MRI did in 3.1
• #8192 lhs of compound const would crash if not a Module/Class
• #8193 side-effects in const op element assign by exec parent of lhs twice
• #8195 use left to right evaluation
• #8196 [deps] update jruby-openssl to 0.14.5
• #8197 END was not getting parents lvars
• #8198 Give same error message for duplicated case arms
• #8199 Enumerator#next_values behavior does not match MRI or docs
• #8200 Warnings emitted by requiring ‘ostruct’
• #8201 Fix issue#8199
• #8202 do not emit labels which are not used while constructing loops + IGV enhancements
• #8203 rename all closures to more closely match a name you can read vs CLOSURE_2
• #8204 bump rdoc dependency to 6.4.1.1
• #8205 begin node coverage line should not get added if it has been removed
• #8206 Mark frame-aware method names with bang suffix for ostruct
• #8207 Partially undo kwarg optz from #8095
• #8208 Only set up Java:: constants when accessed directly
• #8209 opted case needs to use updated ints when loaded into new runtime.
• #8211 Always unwrap old initialize methods