Feeds

We are happy to announce the release of Qt Creator 13.0.2!

Version 2.8 of the GNU Scientific Library (GSL) has been released.
Thank you to all who helped test the library prior to the release, and
thank you to everyone for using the library and giving feedback and
reports. The following changes have been added to the library:

• What is new in gsl-2.8:

** apply patch for bug #63679 (F. Weimer)

** updated multilarge TSQR method to store ||z_2|| and
   provide it to the user

** add routines for Hermite B-spline interpolation

** fix for bug #59624

** fix for bug #59781 (M. Dunlap)

** bug fix #61094 (reported by A. Cheylus)

** add functions:
   - gsl_matrix_complex_conjugate
   - gsl_vector_complex_conj_memcpy
   - gsl_vector_complex_div_real
   - gsl_linalg_QR_lssolvem_r
   - gsl_linalg_complex_QR_lssolvem_r
   - gsl_linalg_complex_QR_QHmat_r
   - gsl_linalg_QR_UR_lssolve
   - gsl_linalg_QR_UR_lssvx
   - gsl_linalg_QR_UR_QTvec
   - gsl_linalg_QR_UU_lssvx
   - gsl_linalg_QR_UD_lssvx
   - gsl_linalg_QR_UD_QTvec
   - gsl_linalg_complex_cholesky_{decomp2,svx2,solve2,scale,scale_apply}
   - gsl_linalg_SV_{solve2,lssolve}
   - gsl_rstat_norm

** add Lebedev quadrature (gsl_integration_lebedev)

** major overhaul to the B-spline module to add
   new functionality

Learn how to streamline your web application's user experience by running batch processes through AJAX requests. This approach prevents page redirection and keeps users on the current interface, enhancing usability and performance. The guide covers key techniques including setting up AJAX calls, handling server responses, and ensuring smooth operation without disrupting user interactions. Discover best practices for error handling, progress updates, and optimizing batch processing for a seamless and efficient workflow.

Contributing to Debian is part of Freexian’s mission. This article covers the latest achievements of Freexian and their collaborators. All of this is made possible by organizations subscribing to our Long Term Support contracts and consulting services.

DebConf Bursary updates, by Utkarsh Gupta

Utkarsh is the bursaries team lead for DebConf 24. Bursary requests are dispatched to a team of volunteers to review. The results are collated, adjusted and merged to produce priority lists of requests to fund. Utkarsh raised the team, coordinated the review, and issued bursaries to attendees.

/usr-move, by Helmut Grohne

More and more, the /usr-move transition is being carried out by multiple contributors and many performed around a hundred of the requested uploads. Of these, Helmut contributed five patches and two uploads. As a result, there are less than 350 packages left to be converted, and all of the non-trivial cases have patches. We started with three times that number. Thanks to everyone involved for supporting this effort.

For people interested in background information of this transition, Helmut gave a presentation at MiniDebConf Berlin 2024 (slides).

sbuild, by Helmut Grohne

While unshare mode of sbuild has existed for quite a while, it is now getting significant use in Debian, and new problems are popping up. Helmut looked into an apparmor-related failure and provided a diagnosis. While relevant code would detect the chroot nature of a schroot backend and skip apparmor tests, the unshare environment would be just good enough to run and fail the test. As sbuild exposes fewer special kernel filesystems, the tests will be skipped again.

Another problem popped up when gobject-introspection added a dependency on the host architecture Python interpreter in a cross build environment. sbuild would prefer installing (and failing) a host architecture Python to installing the qemu alternative. Attempts to fix this would result in systemd killing sbuild. ischroot as used by libc6.postinst would not classify the unshare environment as a chroot. Therefore libc6.postinst would run telinit which would kill the build process. This is a complex interaction problem that shall eventually be solved by providing triggers from libc6 to be implemented by affected init systems.

Salsa CI updates, by Santiago Ruano Rincón

Several issues arose about Salsa CI last month, and it is probably worth mentioning part of the challenges of defining its framework in YAML. With the upcoming end-of-support of Debian 10 “buster” as LTS, armel was removed from deb.debian.org, making the jobs that build images for buster/armel to fail. While the removal of buster/armel from the repositories is a natural change, it put some light on the “flaws” in the Salsa CI design regarding the support of the different Debian releases. Currently, the images are defined like these (from .images-debian.yml):

.all-supported-releases: &all-supported-releases - stretch - stretch-backports - buster - bullseye - bullseye-backports - bookworm - bookworm-backports - trixie - sid - experimental

And from them, different images are built according to the different jobs and how they are supported, for example:

images-prod-arm: stage: build extends: .build_template tags: - $SALSA_CI_ARM_RUNNER_TAG parallel: matrix: # Base image, all releases, all arches - IMAGE_NAME: base ARCH: - arm32v5 - arm32v7 - arm64v8 RELEASE: *all-supported-releases

The removal of buster/armel could be easily reflected as:

images-prod-arm: stage: build extends: .build_template tags: - $SALSA_CI_ARM_RUNNER_TAG parallel: matrix: # Base image, fully supported releases, all arches - IMAGE_NAME: base ARCH: - arm32v5 - arm32v7 - arm64v8 RELEASE: - stretch - buster - bullseye - bullseye-backports - bookworm - bookworm-backports - trixie - sid - experimental # buster only supports armhf and arm64 - IMAGE_NAME: base ARCH: - arm32v7 - arm64v8 RELEASE: buster

Evidently, this increases duplication of the release support data, which is of course not optimal and it is error prone when changing the data about supported releases. A better approach would be to have two different YAML lists, such as:

# releases that have partial support. E.g.: buster is transitioning to # Debian LTS, and buster armel is no longer found in deb.debian.org .old-releases: &old-releases - stretch - buster .currently-supported-releases: &currently-supported-releases - bullseye - bullseye-backports - bookworm - bookworm-backports - trixie - sid - experimental

and then a unified list:

.all-supported-releases: &all-supported-releases - *old-releases - *currently-supported-releases

that could be used in the matrix of the jobs that build all the images available in the pipeline container registry.

However, due to limitations in GitLab, it is not possible to expand the variables or mapping values in a parallel:matrix context. At least not in an elegant fashion.

This is the kind of issue that recently arose and that Santiago is currently working to solve, in the simplest possible way.

Astute readers would notice that stretch is listed in the fully supported releases. And there is no problem with stretch, because it is built from archive.debian.org. Otto actually has tried to fix the broken image build job doing the same, but it is still incorrect, because the security repository is not (yet) available in archive.debian.org.

Additionally, Santiago has also worked on other merge requests, such as:

1. support branch/tags as target head in the test projects,
2. build autopkgtest image on top of stable
3. Add .yamllint and make it happy in the autopkgtest-lxc project
4. enable FF_SCRIPT_SECTIONS to log multiline commands, among others.

Archiving DebConf Websites, by Stefano Rivera

DebConf, the annual Debian conference, has its own new website every year. These are typically complex dynamic web applications (featuring registration, call for papers, scheduling, etc.) Once the conference is over, there is no need to keep maintaining these applications, so we archive the sites off as static HTML, and serve them from Debian’s static CDN.

Stefano archived the websites for the last two DebConfs.

The schedule system behind DebConf 14 and 15’s websites was a derivative of Canonical’s summit system. This was only used for a couple of years before migrating to wafer, the current system. Archiving summit content has been on the “nice to have” list for years, but nobody has ever tackled it. The machine that served the sites went away a couple of years ago. After much digging, a backup of the database was found, and Stefano got this code running on an ancient Python 2.7. Recently Stefano put this all together and hooked in an archive export to finally get this content preserved.

Python 3.x and pypy3 security bug triage, by Stefano Rivera

Stefano Rivera triaged all the open security bugs against the Python 3.x and PyPy3 packages for Debian’s stable and LTS releases. Several had been fixed but this wasn’t recorded in the security tracker.

Linux livepatching support for Debian, by Santiago Ruano Rincón

In collaboration with Emmanuel Arias, Santiago filed ITP bug #1070494. As stated in the bug, more than an Intent to Package, it is an Intent to Design and Implement live patching support for the Linux kernel in Debian. For now, Emmanuel and Santiago have done exploratory work and they are working to understand the different possibilities to implement livepatching. One possible direction is to rely on kpatch, and the other is to package the modules using regular packaging tools. Also, it is needed to evaluate if it is possible to rely on distributing the modules via packages, or instead as a service, as it is done by some commercial distributions.

Miscellaneous contributions

• Thorsten Alteholz uploaded cups-bjnp to improve packaging.
• Colin Watson tracked down a baffling CI issue in openssh to unblock several merge requests, removed the user_readenv=1 option from its PAM configuration, and started on the first stage of his plan to split out GSS-API key exchange support to separate packages.
• Colin did his usual routine work on the Python team, upgrading 26 packages to new upstream versions, and cherry-picking an upstream PR to fix a pytest 8 incompatibility in ipywidgets.
• Colin NMUed a couple of packages to reduce the need for explicit overrides in Packages-arch-specific, and removed some other obsolete entries from there.
• Emilio managed various library transitions, and helped finish a few of the remaining t64 transitions.
• Helmut sent a patch for enabling piuparts to work as a regular user building on earlier work.
• Helmut sent patches for 7 cross build failures, 6 other debian bugs and fixed an infrastructure problem in crossqa.debian.net.
• Nicholas worked on a sponsored package upload, and discovered the blhc tool for diagnosing build hardening.
• Stefano Rivera started and completed the re2 transition. The release team suggested moving to a virtual package scheme that includes the absl ABI (as re2 now depends on it). Adopted this.
• Stefano continued to work on DebConf 24 planning.
• Santiago continued to work on DebConf24 Content tasks as well as Debconf25 organisation.

Friday, 7 June 2024

KDE today announces the release of KDE Frameworks 6.3.0.

KDE Frameworks are 72 addon libraries to Qt which provide a wide variety of commonly needed functionality in mature, peer reviewed and well tested libraries with friendly licensing terms. For an introduction see the KDE Frameworks release announcement.

This release is part of a series of planned monthly releases making improvements available to developers in a quick and predictable manner.

New in this version Baloo

• Qml: don't do blocking DBus calls in Baloo.Monitor. Commit. Fixes bug #487064
• Remove explicit maintainer from metainfo. Commit.

Bluez Qt

• Remove explicit maintainer from metainfo. Commit.

Breeze Icons

• Use normal resource adding, big resource variant has issue with LTO. Commit.
• Kmahjongg app icon: drop broken entries href'ing to non-existing id. Commit.
• Fix remaining missing semicolons. Commit.
• Fix missing semicolon. Commit.
• Fix path styling. Commit.
• Treat hicolor as "no fallback theme set" too. Commit.
• Ensure we fallback to breeze, if no user fallback is set. Commit.
• Fix dark icon generation. Commit.
• Revert "ensure we fallback to breeze, if no user fallback is set". Commit.
• Ensure we fallback to breeze, if no user fallback is set. Commit.
• Avoid to generate dead links. Commit.
• Remove duplicate of window.svg. Commit.
• Better duplicate checking. Commit.
• Stricter external link check. Commit.
• Integrate better test for whitespace of any kind. Commit.
• Fix escape sequences. Commit.
• Do full link checking for git win links, too. Commit.
• Do full symlink checking during resource creation. Commit.
• Better name for windows link resolving. Commit.
• Remove recently-added process-working-symbolic icons. Commit.
• Replace dialog-* icons with data-* icons. Commit.
• Add symbolic icons as symlink to existing monochrome icons. Commit.
• Remove explicit maintainer from metainfo. Commit.
• Remove copy/pasted 16px go/lua/scala icons from mimetypes/22. Commit.
• Fix actions/22/fingerprint viewBox. Commit.
• Include duplication check. Commit.
• Let Qt do the simple XML linting. Commit.
• Add my copyright, too. Commit.
• Add more comments and use better function name. Commit.
• Reenable x24 icons on Windows. Commit.
• Try to ensure we really run late enough. Commit.
• Run resource file generator on dark, too, for checks. Commit.
• Generate icon 24 gen dir always. Commit.
• Move more helpers to same dir. Commit.
• Split files to avoid dep cycles. Commit.
• Pack in generated icons. Commit.
• Add symlinks for new ISO MIME type names. Commit.
• Use rcc like we do it in other frameworks. Commit.
• Move helper, simplify deps searching. Commit.
• Avoid the copying. Commit.
• Add back BINARY_ICONS_RESOURCE for breeze only. Commit.
• Fix qrc generation for system with symlinks and always build the library. Commit.
• Remove BINARY_ICONS_RESOURCE. Commit.

Extra CMake Modules

• Skip app template packaging when cross-compiling. Commit.
• Remove explicit maintainer from metainfo. Commit.
• ECMQueryQt: Provide better error message when Qt6 qpaths is not found. Commit.

Framework Integration

• Remove wrong note from metainfo. Commit.
• Remove explicit maintainer from metainfo. Commit.

KAPIDox

• Don't show maintainers for frameworks. Commit.
• Don't show framework type in frameworks list. Commit.

KArchive

• Require unit tests to pass on Windows. Commit.
• It compiles fine without qt6.7 deprecated methods. Commit.
• Add missing includes. Commit.

KAuth

• Remove explicit maintainer from metainfo. Commit.

KBookmarks

• It compiles fine without qt6.7 deprecated methods. Commit.
• Use ellipsis character instead of three dots in UI strings. Commit.

KCalendarCore

• Tests: Remove workaround not needed anymore after 80f7731c591dfe656d8c6769fa2efba9256a60f4. Commit.
• CI: Require passing tests on Linux and Windows. Commit.
• Adapt date/time output for tests to Qt 6.7 formatting behavior changes. Commit.
• Remove explicit maintainer from metainfo. Commit.

KCMUtils

• It compiles fine without qt6.7 deprecated methods. Commit.
• AbstractKCM,SimpleKCM: Stop overlapping the 1px of content with a header Separator. Commit.
• SimpleKCM: Port header's wrapper from QQC2.Control to Kirigami.Padding. Commit.
• SimpleKCM: Drop unnecessary id qualifier from the bindings at the top-level component. Commit.
• AbstractKCM,SimpleKCM: Unify header/footer content swapping. Commit.
• AbstractKCM,SimpleKCM: Unify OverlaySheet detection, port to cool iterators. Commit.

KColorScheme

• Allow to bundle color schemes with applications inside resources. Commit.
• Remove explicit maintainer from metainfo. Commit.

KCompletion

• It compiles fine without qt6.7 deprecated methods. Commit.
• Remove explicit maintainer from metainfo. Commit.

KConfig

• Ensure test works with Qt 6.7 on Windows. Commit.
• Use QT_TRANSLATE_NOOP instead of QT_TR_NOOP for KStandardActions. Commit.
• Add helper method to fully move a group to another. Commit.
• Deprecate ctor that takes a backend. Commit.
• Move parts of KStandardAction to KConfigGui. Commit.
• Remove KConfigBackend abstraction. Commit.
• Add a mutex to protect globalData. Commit.
• Kconfigxt: Remove docs for SourceExtension parameter which was removed in KF6. Commit.
• Remove explicit maintainer from metainfo. Commit.
• Use ellipsis character instead of three dots in UI strings. Commit.

KConfigWidgets

• Add api to have a style chooser. Commit.
• KStandardAction: reduce allocation by using view type. Commit.
• Add KStyleManager::initStyle to enforce proper application style. Commit.
• KConfigDialogManager: port to non-deprecated QCheckBox signal. Commit.
• KCommandBar: Better UI. Commit.

KContacts

• Add SPDX license/copyright information for new CMakeLists.txt as well. Commit.
• Properly expose address format API to QML. Commit.
• Add qml module. Commit.
• Update feature documentation. Commit.
• Remove explicit maintainer from metainfo. Commit.

KCoreAddons

• Not all distros have /bin/true, e.g. NixOS lacks it. Commit.
• Bundle license texts inside resource. Commit.
• Remove explicit maintainer from metainfo. Commit.
• Kfilesystem: recognize nfs4 as KFileSystemType::Nfs. Commit.
• Replace KAboutDialog with KAboutApplicationDialog. Commit.

KCrash

• Handle kwin's wayland qpa as wayland platform. Commit.

KDBusAddons

• It compiles fine without qt6.7 deprecated methods. Commit.

KDeclarative

• KeySequenceItem: Fix height management. Commit.
• Remove useless note from metainfo. Commit.
• Fix tier in metainfo. Commit.
• Remove explicit maintainer from metainfo. Commit.

KDNSSD

• Remove explicit maintainer from metainfo. Commit.

KDocTools

• Remove explicit maintainer from metainfo. Commit.

KFileMetaData

• Remove explicit maintainer from metainfo. Commit.

KGlobalAccel

• Improve metainfo.yaml. Commit.

KGuiAddons

• Deprecated KColorCollection. Commit.

KHolidays

• Remove custom definitions of pi. Commit.
• Proofreading. Commit.
• Remove explicit maintainer from metainfo. Commit.
• Latvia holiday grammar corrections. Commit.

KI18n

• Remove explicit maintainer from metainfo. Commit.

KIconThemes

• Add missing include. Commit.
• KIconDialog: Prevent briefly visible mini-window from showing up. Commit. Fixes bug #487762
• Update file kicontheme.cpp. Commit.
• Include only if needed, avoid extra define. Commit.
• Set QML module base version to 1.0. Commit.
• Windows tests work now. Commit.
• Use Qt to fill in the generic mime-type icon information. Commit.
• Use Qt to fill in the generic mime-type icon information. Commit.
• Ensure tests pass locally with KDE platform theme, too. Commit.
• Ensure we not clash with breeze from resource. Commit.
• Adapt test to fact we now have Breeze with hicolor inherits. Commit.
• Remove not used files. Commit.
• Remove my old rcc test, no longer done. Commit.
• Always require the icon library. Commit.
• Add KIconTheme::initTheme() to configure proper icon set as opt-in. Commit.

KImageformats

• Remove explicit maintainer from metainfo. Commit.
• Ensure dependencies are provided on Android. Commit.

KIO

• KAbstractFileItemActionPlugin: Remove wrong sentence in documentation. Commit. See bug #425997
• Don't install header for pure dbus class if no dbus. Commit.
• Disable dbus not only for android but windows & mac, too. Commit.
• Drop errorpage handling from worker. Commit.
• [http] Implement resuming at offset again. Commit. Fixes bug #480506
• CI: Require passing tests on Linux and FreeBSD. Commit.
• Deprecate KFileWidget::readConfig. Commit.
• SSL Info UI file: use notr="true" instead of old comment="KDE::DoNotExtract". Commit.
• Kfileitem: cache group names. Commit. Fixes bug #486956
• Move HAVE_STATX cmake test to core. Commit. Fixes bug #487015
• Remove unused includes. Commit.
• Properties dialogue URL tab: Fix vertical alignment. Commit.
• Systemdprocessrunner: change the order launchmodes are returned. Commit.
• Systemdprocessrunner: change env var names. Commit.
• Use ellipsis character instead of three dots in UI strings. Commit.
• Kprocessrunner: add third parameter to a connect. Commit.

Kirigami

• Revert "icon: Remove the node with lowest opacity when animation end". Commit. Fixes bug #487577
• ImageColors: Rework the example app. Commit.
• ImageColors: Remove unused QTimer member. Commit.
• ImageColors: Remove an unused variable. Commit.
• ImageColors: Disconnect the old QFutureWatcher. Commit.
• ImageColors: Mark internal function as static. Commit.
• ImageColors: Do not grab an item without a window or with an invisible window. Commit.
• ImageColors: Port QVariantList to a typed and named gadget. Commit.
• ImageColors: Fix multi-threading crash. Commit.
• Use consistent import alias for QtQuick.Controls. Commit.
• Drop all QML import versions. Commit.
• Doc: Improve FormData.label example. Commit.
• Fix typo in docs. Commit.
• Introduce the layouts submodule. Commit.
• SearchDialog: Expose search field placeholder text. Commit.
• Per default DBus only enabled on systems that use it. Commit.
• SearchDialog: Add page up/page down key navigation. Commit.
• Move dialog stuff in a new dialogs submodule. Commit.
• Card: emit toggled() when the user clicks on the header checkbox. Commit. Fixes bug #481461
• SearchDialog: Improve up/down item navigation. Commit.
• PromptDialog: adjust label spacing to conform to new HIG. Commit.
• Icon: Remove the node with lowest opacity when animation end. Commit.
• Remove custom backgrounds. Commit.
• Add SearchDialog. Commit.
• Always color icons. Commit. Fixes bug #485801
• PromptDialog: Fix regression where content is not scrollable. Commit.
• Add README.md for delegates and primitives modules. Commit.
• Delegates: Use relative imports for types from the same module. Commit.
• Delegates: Use Platform/Primitives directly instead of main Kirigami module. Commit.
• Add Platform and Primitives modules as dependencies for Delegates module. Commit.
• Introduce a "primitives" submodule that contains primitive types. Commit.
• Move ColorUtils to Platform. Commit.
• CMake: Change variable name for install() command. Commit.
• FormLayout: Compare types against base TextEdit instead of styled QQC2 component. Commit.
• Improve metainfo.yaml. Commit.
• TitleSubtitle Title Accessiblity. Commit.
• Don't include CPack. Commit.
• Don't include quiet package in feature_summary. Commit.
• Revert "PageRow: Rework page component caching". Commit.
• Revert "Dialog: Always use an overlay as visual parent". Commit.
• GlobalDrawer: Fix up code example in docs. Commit.
• OverlaySheet: Fix typo in docs. Commit.
• [inlineviewheader] Qualify property lookup. Commit.
• Add frame contrast. Commit.
• [dialog] Qualify property access. Commit.
• [dialog] Fix signal handler. Commit.
• FormLayout: Fix QML imports in doc example. Commit.
• FormLayout: Annotate function parameters. Commit.
• FormLayout: Qualify property access. Commit.
• PageRow: Rework page component caching. Commit.
• KirigamiPrivatePlugin: Reformat CMake into multi-line statements. Commit.
• Fix Dialog parenting. Commit.
• Dialog: Expand past preferred size to implicit size, as documented. Commit.
• Fix all occurrence of UnusedImports. Commit.
• Add config file for qmllint. Commit.
• PromptDialog: Don't use qualified property access in top-level expressions. Commit.
• Add support for global smooth scroll setting. Commit.
• Fix scrollable dialogs. Commit.
• Revert change to OverlaySheet. Commit.
• Update design of dialogs. Commit.
• GlobalDrawer: Clip content in more cases to fix overflowing header. Commit.

KItemModels

• Revert "KSelectionProxyModelTest: Skip tests broken by upstream changes". Commit.

KItemViews

• KWidgetItemDelegatePoolPrivate: remove unused allocatedWidgets member. Commit.
• Remove explicit maintainer from metainfo. Commit.
• Use ellipsis character instead of three dots in UI strings. Commit.

KJobWidgets

• KUiServerV2JobTracker: prevent a crash. Commit. Fixes bug #471531. Fixes bug #483582

KNewStuff

• Remove explicit maintainer from metainfo. Commit.
• Action: Fix type of transientParent property. Commit.
• Use ellipsis character instead of three dots in UI strings. Commit.
• ItemsModel: Fix up docs after refactoring. Commit.
• Fix the "Use" label on certain delegates. Commit.
• QuestionAsker: Remove broken sizing bindings. Commit.
• Explicitly set QQC2.Overlay.overlay as a parent for popups. Commit.
• DownloadItemsSheet: Port from OverlaySheet to Kirigami.Dialog for file selection dialog. Commit.
• DownloadItemsSheet: Wrap the file names of entries instead of eliding. Commit.
• ProvidersModel: Redo the engine property in a way which doesn't break ABI. Commit.
• Register properties as properly typed. Commit.
• Qtquick: Clean up unused #includes. Commit.
• UploadPage: Fix engine property binding. Commit.
• UploadsPage: Fix punctuation in a user-visible string. Commit.
• Comments: Manage ListView's delegate width & position correctly. Commit.
• ConditionalLoader: Drop meaningless checks and unused root id. Commit.
• Don't manage visibility of a BusyIndicator. Commit.
• QML: Don't abuse implicit casting of binding values to bool property. Commit.
• QML: Port Qt.rgba to the new Qt.alpha. Commit.
• QML: Port to strict === JavaScript equality operator. Commit.
• QML: Drop import alias for QtQuick.Layouts module. Commit.
• QML: Normalize QtQuick.Templates import aliases as T. Commit.
• QML: Normalize QtQuick.Controls import aliases as QQC2. Commit.
• QML: Add missing Kirigami import alias. Commit.
• QML: Normalize QtQuick.Controls import aliases as QQC2. Commit.
• QML: Remove unused imports. Commit.
• QML: Drop all import versions. Commit.
• QML: Drop major version from Kirigami imports. Commit.
• QML: Throw QtQuick.Window out of the window. Commit.
• QML: Clean up whitespace-related code style issues. Commit.
• QML: Remove superfluous trailing semicolons from bindings. Commit.
• QML: Explicitly specify arguments in signal handlers. Commit.

KNotifications

• Don't include quiet package in feature_summary. Commit.
• Notifybysnore: correct action buttons. Commit. Fixes bug #486911
• Remove explicit maintainer from metainfo. Commit.

KNotifyConfig

• Remove explicit maintainer from metainfo. Commit.

KPackage

• It compiles fine without qt6.7 deprecated methods. Commit.
• Remove explicit maintainer from metainfo. Commit.

KParts

• Only use KDirNotify if existing. Commit.
• Docs: KMimeTypeTrader no longer exists. Commit.
• Use QUrl::PreferLocalFile for URL emitted with Part::setWindowCaption. Commit.

KPeople

• Fix tier information. Commit.
• Remove explicit maintainer from metainfo. Commit.
• Port to ecm_add_qml_module and declarative type registration. Commit.

KQuickCharts

• Set a better default size for the example application. Commit.
• Don't crash if we try to access an item from an empty ArraySource. Commit.
• Enable highlighting for most pages in the charts example. Commit.
• Port example pages to use ChartPage. Commit.
• Add a common base type for pages in the chart example. Commit.
• Remove API selection from charts example. Commit.
• Convert chart example to use an executable QML module. Commit.
• Expose highlight property on PieChartControl. Commit.
• Support highlighting in LineChartControl. Commit.
• Controls: Add support for highlighting hovered items in Legend. Commit.
• Fix normalized line size calculation in LineChartNode. Commit.
• Support highlight in BarChart. Commit.
• Support highlight in PieChart. Commit.
• Support highlight property in LineChart. Commit.
• Add a protected method to Chart to deemphasise non-highlighted items. Commit.
• Add a highlight property to Chart. Commit.
• Remove explicit maintainer from metainfo. Commit.
• Controls: Ceil all components of preferredWidth in LegendDelegate contents. Commit. Fixes bug #486411

KRunner

• Fix X-KDE-ConfigModule not working for DBus runners. Commit.
• Fix same query not yielding results in new match session. Commit.
• Remove explicit maintainer from metainfo. Commit.
• Templates/runner6python: Only depend on shebang line for executing. Commit.
• Rename entrypoint file to always be main.py. Commit.
• Document krunner-plugininstallerrc file. Commit.
• Document how AbstractRunner::config is resolved. Commit.
• Runnercontext: Fix saving the launch counts. Commit.

KSVG

• Support for fractional scaling. Commit.
• Color also absolute path images. Commit. Fixes bug #485801
• Reapply "Port to declarative type registration". Commit.

KTextEditor

• Ensure the color name text is visible. Commit. Fixes bug #487068
• Ensure we not reset the dynamic word wrap state. Commit. Fixes bug #487216
• Port to KStandardActions. Commit.
• Never remove trailing spaces on diff file type. Commit.
• Remove explicit maintainer from metainfo. Commit.
• Screenshot dialog: support drag of image. Commit.
• Make tests independent of the user's environment. Commit.
• Modernize use designated init. Commit.
• Do not display diff result in script tests when -silent is used. Commit.
• Fix raw string indentation with cstyle + C++. Commit.
• Screenshot dialog: omit ellipsis from window title. Commit.
• Screenshot dialog: use default QFileDialog::getSaveFileName window title. Commit.
• Use ellipsis character instead of three dots in UI strings. Commit.

KTextTemplate

• Remove explicit maintainer from metainfo. Commit.

KTextWidgets

• Use ellipsis character instead of three dots in UI strings. Commit.

KUnitConversion

• Remove explicit maintainer from metainfo. Commit.

KUserFeedback

• CI: Require tests to pass on Linux and FreeBSD. Commit.
• Add homepage url, CI was complaining. Commit.
• Fix target names in metainfo. Commit.
• Remove explicit maintainer from metainfo. Commit.
• Use ellipsis character instead of three dots in UI strings. Commit.

KWallet

• Fix secrets portal wallet access. Commit. Fixes bug #487348
• Remove explicit maintainer from metainfo. Commit.

KWidgetsAddons

• Fix KMessageWidget background color. Commit.
• KMessageWidget: Avoid calling polish() inside of palette update. Commit. Fixes bug #487247
• Revert "KMessageWidget: Set the palette to work with non-KStyle styles". Commit.
• KMessageWidget: Set the palette to work with non-KStyle styles. Commit.
• Use ellipsis character instead of three dots in UI strings. Commit.
• Skip tests that need GUI on Windows CI. Commit.
• KViewStateSerializer: fix docu: setTreeView -> setView. Commit.
• KBusyIndicatorWidget: fix warning when hiding on startup. Commit.

KWindowSystem

• Update to plasma window management v17. Commit.

KXMLGUI

• It compiles fine without qt6.7 deprecated methods. Commit.
• [kactioncollection] Add addAction for KStandardActions without name. Commit.
• Add KStandardActions::StandardActions overload. Commit.
• Remove icon fallback setting. Commit.
• Use ellipsis character instead of three dots in UI strings. Commit.
• Work with a local copy of container when removing elements. Commit.
• Skip tests that need GUI on Windows CI. Commit.

Prison

• Restore compatibility with older ZXing versions. Commit.
• It compiles fine without qt6.7 deprecated methods. Commit.
• Remove explicit maintainer from metainfo. Commit.
• Enable exceptions where needed by ZXing. Commit.
• Add image barcode scanning API. Commit.

Purpose

• Remove explicit maintainer from metainfo. Commit.

QQC2 Desktop Style

• Fix rendering the focus of our items. Commit. Fixes bug #486041
• Update background of Dialog. Commit.
• TreeViewDelegate: Replace top/bottom padding with vertical. Commit.
• TreeViewDelegate: Add return type annotations to methods. Commit.
• TreeViewDelegate: Make it actually vertically centered. Commit.
• Remove explicit maintainer from metainfo. Commit.
• TextArea, TextField: Fix position of a "selection end" cursor. Commit.
• TextField: Fix mobile cursor positioning for fields with custom padding. Commit.
• Context Menus: Port to pragma ComponentBehavior: Bound. Commit.
• Context Menus: Use controls directly instead of via QQC2. Commit.
• MobileTextActionsToolBar: Slightly refactor expressions. Commit.
• MobileTextActionsToolBar: Set text and display mode for action buttons. Commit.
• MobileTextActionsToolBar: Use symbolic versions of icons. Commit.
• ComboBox: Clip the ListView when its relevant. Commit.
• ComboBox: Use strict === equality operator. Commit.
• ComboBox: Replace magic numbers with standard named units. Commit.
• [TextArea] Access controlRoot directly. Commit.
• [TextArea] Enabled ComponentBehavior: Bound. Commit.
• [Combobox] Use Popup directly instead of via QQC2. Commit.
• DialogButtonBox: Use largeSpacing as padding. Commit.

Sonnet

• Remove explicit maintainer from metainfo. Commit.
• Use ellipsis character instead of three dots in UI strings. Commit.

Syndication

• Remove explicit maintainer from metainfo. Commit.

Syntax Highlighting

• Updates to Catppuccin themes. Commit.
• Nix: Version 2 -> 3. Commit.
• Nix: Correctly highlight first key in set when it is quoted. Commit.
• Nix: Correctly highlight bare ${}. Commit.
• Nix: More correctly model inherit syntax. Commit.
• Build with QT_NO_CONTEXTLESS_CONNECT. Commit.
• Remove explicit maintainer from metainfo. Commit.
• Use ellipsis character instead of three dots in UI strings. Commit.
• Xml: add fictionbook format. Commit.

Threadweaver

• Remove explicit maintainer from metainfo. Commit.

The diffoscope maintainers are pleased to announce the release of diffoscope version 271. This version includes the following changes:

[ Chris Lamb] * Drop Build-Depends on liblz4-tool. Thanks, Chris Peterson. (Closes: #1072575) * Update tests to support zipdetails version 4.004 shipped with Perl 5.40. (Closes: reproducible-builds/diffoscope#377)

You find out more by visiting the project homepage.

I'm pleased to announce the release of Python 3.12.4:

https://www.python.org/downloads/release/python-3124/

 This is the third maintenance release of Python 3.12

Python 3.12 is the newest major release of the Python programming language, and it contains many new features and optimizations. 3.12.4 is the latest maintenance release, containing more than 250 bugfixes, build improvements and documentation changes since 3.12.3.

 Major new features of the 3.12 series, compared to 3.11  New features

• More flexible f-string parsing, allowing many things previously disallowed (PEP 701).
• Support for the buffer protocol in Python code (PEP 688).
• A new debugging/profiling API (PEP 669).
• Support for isolated subinterpreters with separate Global Interpreter Locks (PEP 684).
• Even more improved error messages. More exceptions potentially caused by typos now make suggestions to the user.
• Support for the Linux perf profiler to report Python function names in traces.
• Many large and small performance improvements (like PEP 709 and support for the BOLT binary optimizer), delivering an estimated 5% overall performance improvement.

Type annotations

• New type annotation syntax for generic classes (PEP 695).
• New override decorator for methods (PEP 698).

Deprecations

• The deprecated wstr and wstr_length members of the C implementation of unicode objects were removed, per PEP 623.
• In the unittest module, a number of long deprecated methods and classes were removed. (They had been deprecated since Python 3.1 or 3.2).
• The deprecated smtpd and distutils modules have been removed (see PEP 594 and PEP 632. The setuptools package continues to provide the distutils module.
• A number of other old, broken and deprecated functions, classes and methods have been removed.
• Invalid backslash escape sequences in strings now warn with SyntaxWarning instead of DeprecationWarning, making them more visible. (They will become syntax errors in the future.)
• The internal representation of integers has changed in preparation for performance enhancements. (This should not affect most users as it is an internal detail, but it may cause problems for Cython-generated code.)

For more details on the changes to Python 3.12, see What’s new in Python 3.12.

 More resources

• Online Documentation.
• PEP 693, the Python 3.12 Release Schedule.
• Report bugs via GitHub Issues.
• Help fund Python directly or via GitHub Sponsors, and support the Python community.

 Enjoy the new releases

Thanks to all of the many volunteers who help make Python Development and these releases possible! Please consider supporting our efforts by volunteering yourself or through organization contributions to the Python Software Foundation.

Your release team,
Thomas Wouters
Łukasz Langa
Ned Deily
Steve Dower 

I'm pleased to announce the release of Python 3.13 beta 2.

https://www.python.org/downloads/release/python-3130b2/

 

This is a beta preview of Python 3.13

Python 3.13 is still in development. This release, 3.13.0b2, is the second of four beta release previews of 3.13.

Beta release previews are intended to give the wider community the opportunity to test new features and bug fixes and to prepare their projects to support the new feature release.

We strongly encourage maintainers of third-party Python projects to test with 3.13 during the beta phase and report issues found to the Python bug tracker as soon as possible. While the release is planned to be feature complete entering the beta phase, it is possible that features may be modified or, in rare cases, deleted up until the start of the release candidate phase (Tuesday 2024-07-30). Our goal is to have no ABI changes after beta 4 and as few code changes as possible after 3.13.0rc1, the first release candidate. To achieve that, it will be extremely important to get as much exposure for 3.13 as possible during the beta phase.

Two particularly noteworthy changes in beta 2 involve the macOS installer we provide:

• The minimum supported macOS version was changed from 10.9 to 10.13 (High Sierra). Older macOS versions will not be supported going forward.
• The macOS installer package now includes an optional additional build of Python 3.13 with the experimental free-threading feature enabled. The free-threaded version, python3.13t, is separate from and co-exists with the traditional GIL-only installation. The free-threaded build is not installed by default; use the Customize option of the installer as explained in the installer readme. Since this is an experimental feature, there may be late-breaking issues found; see the free-threaded macOS build issue on GitHub for the most recent status.

Please keep in mind that this is a preview release and its use is not recommended for production environments.

 Major new features of the 3.13 series, compared to 3.12

Some of the new major new features and changes in Python 3.13 are:

New features

• A new and improved interactive interpreter , based on PyPy’s, featuring multi-line editing and color support, as well as colorized exception tracebacks .
• An experimental free-threaded build mode , which disables the Global Interpreter Lock, allowing threads to run more concurrently.
• A preliminary, experimental JIT , providing the ground work for significant performance improvements.
• The (cyclic) garbage collector is now incremental , which should mean shorter pauses for collection in programs with a lot of objects.
• A modified version of mimalloc is now included, optional but enabled by default if supported by the platform, and required for the free-threaded build mode.
• Docstrings now have their leading indentation stripped, reducing memory use and the size of .pyc files. (Most tools handling docstrings already strip leading indentation.)
• The dbm module has a new dbm.sqlite3 backend that is used by default when creating new files.

Typing

• Support for type defaults in type parameters.
• A new type narrowing annotation , typing.TypeIs.
• A new annotation for read-only items in TypeDicts .

Removals and new deprecations

• PEP 594 (Removing dead batteries from the standard library) scheduled removals of many deprecated modules: aifc, audioop, chunk, cgi, cgitb, crypt, imghdr, mailcap, msilib, nis, nntplib, ossaudiodev, pipes, sndhdr, spwd, sunau, telnetlib, uu, xdrlib, lib2to3.
• Many other removals of deprecated classes, functions and methods in various standard library modules.
• C API removals and deprecations. (Some removals present in alpha 1 were reverted in alpha 2, as the removals were deemed too disruptive at this time.)
• New deprecations, most of which are scheduled for removal from Python 3.15 or 3.16.

(Hey, fellow core developer, if a feature you find important is missing from this list, let Thomas know.)

For more details on the changes to Python 3.13, see What’s new in Python 3.13 . The next pre-release of Python 3.13 will be 3.13.0b3, currently scheduled for 2024-06-25.

 More resources

• Online Documentation
• PEP 719 , 3.13 Release Schedule
• Report bugs at Issues · python/cpython · GitHub .
• Help fund Python directly (or via GitHub Sponsors), and support the Python community.

 Enjoy the new releases

Thanks to all of the many volunteers who help make Python Development and these releases possible! Please consider supporting our efforts by volunteering yourself or through organization contributions to the Python Software Foundation.

Your release team,
Thomas Wouters
Łukasz Langa
Ned Deily
Steve Dower 

 

Here's what I've been working on for my LocalGov Drupal contributions this week. Thanks to Big Blue Door for sponsoring the time to work on these.

The journey of testing methodologies underscores the importance of ensuring code reliability and functionality, especially in the complex landscape of Drupal development.

Monday was a U.S. holiday, which meant I was able to go full-steam ahead on the storage MR for Experience Builder (XB) that I started the prior week. On Tuesday, I continued that work, and spun off a second MR that allows changing the source type and source value … for which I shared a 2.5-minute screencast in #experience-builder late on Tuesday.

In it, you’ll see a hacky-as-hell UI. It’s currently named TwoTerribleTextAreasWidget to convey in no uncertain terms that this is throwaway code :D Its purpose: help stand up infrastructure and get the back-end pieces in place to power the UI (see last week’s screenshot), which is currently using hardcoded data.

Missed a prior week? See all posts tagged Experience Builder.

Goal: make it possible to follow high-level progress by reading ~5 minutes/week. I hope this empowers more people to contribute when their unique skills can best be put to use!

For more detail, join the #experience-builder Slack channel. Check out the pinned items at the top!

The video is the first step in visualizing all the pieces of Alex “effulgentsia”’s data model proposal in #3440578. In a nutshell, you can see that for each placed component, this video proves:

• it is possible to exactly match Single Directory Components (SDC) props against Drupal field types (to be precise: props inside those fields)
• while allowing those values to be:
  • either dynamic: reuse of structured data that already exists on the entity (XB aims to embrace that strength of Drupal, not to diminish it)
  • or static: fixed values stored in JSON-in-the-database as described in #3440578 1
• crucially, we can automatically surface only sensible choices, and present the choices in an order that encourages best practices, using only schema matching2 (SDCs use JSON schema, whereas the Drupal entity/field system uses Typed Data + validation constraints)

I was relieved to see that effulgentsia indicated this indeed matches his vision :)

Just those two source types (dynamic and static) are insufficient, which is why Felix has been hard at work to bring us a working PoC of adapters too, which are able to

1. adapt data into a shape that Drupal does not provide a field type for (for example: the type: string, format: time)
2. combine multiple data sources (any combination of static and dynamic) into a single shape (for example: combine an image + Image Style inputs and to adapt them into an image that uses that style

Adapters were merged on Friday!

That was more technical than previous weeks. The more technical readers might, if they squint again just like last week for the UI, be able to see how Lauri “lauriii”, effulgentsia and I see the different pieces connect. I know that many of you are longing for detailed architectural diagrams. They do not exist today. We had to first prove what we envisioned was feasible. There’s a bit more proving to be done first, but then such documentation & diagrams will be my top priority.

Before sharing that video on Tuesday, I met with Cristina “ckrina”, Jared “jponch”, Mateu “e0ipso” and Mike “mherchel”, about design tokens, which is another crucial part of XB. e0ipso had already been working on a PoC for bringing design tokens to SDC, whereas ckrina felt it was important to start defining which design tokens should exist. We ended up concluding unanimously that building a few concrete components and making them use design tokens would help define that — so ckrina, jponch and mherchel are tackling that next.

The meeting was recorded and shared and sparked a lively discussion, where Pierre “pdureau” chimed in with interesting UI Suite-based opinions

It’s great to see this work in motion, because both the exploratory “how should it work from a design POV?” and the concrete SDC support work are necessary, and both will inform the direction of #3444424: [META] Configuration management: define needed config entity types.

On Wednesday, #3450586: [META] Early phase back-end work coordination and #3450592: [META] Early phase front-end work coordination were created, to start making it possible for any Drupal contributor to 1) see what’s happening, 2) find issues to contribute to. (The list of available issues is sparse at this early stage, because there barely is a codebase, and not all architectural puzzle pieces exist yet.)

Later that day, I rode my bicycle over to meet with 4 people of the Dropsolid team. They’re very eager to contribute to XB (their CEO, Dominique “domidc” almost didn’t let me leave the DrupalCon venue when it was closing, that’s how enthusiastic they are :D), and they bring a unique perspective: they focus on “mid-market” and have hundreds (thousand?) of sites using Layout Builder. Thanks to to that, they intimately know some of Layout Builder’s architectural choices that XB should avoid. On the code contribution side, I was able to point them to the 2 meta issues above that had been created only hours prior. On the UX/product side of XB, they’re coordinating with lauriii next, so expect to hear more in a future update.

Perhaps the best place to contribute to XB today is actually in SDC! Kyle “ctrlADel” Einecker discovered an SDC bug during DrupalCon Portland (#3446933) that definitely will block XB. e0ipso worked on a fix and penyaskito RTBC‘d it on Thursday. This also connects with #3446083 and #3446722 which focuses on defining different ways of composing components out of existing SDCs for XB to support.

Also on Wednesday, Lee “larowlan” helped the UI transition from miragejs to msw.

To round the week out, Ben “bnjmnm” finished his epic battle with the CI gods on Friday and won!: he got Cypress working on XB’s GitLab CI pipeline. Both Ben and Jesse were raving about the excellent DX that Cypress has compared to other (end-to-end) testing frameworks for JS. With the CI pieces in place, we’re ending this week on a strong note: future UI work will be able to move faster thanks to Cypress, and Cypress-on-CI!

Thanks to Lauri for reviewing this!

1. To generate field widgets for these, we conjure instances of those field types out of thin air! ↩︎

2. Schema matching basically is a fancy word for shape matching. ↩︎

• Drupal
• Acquia
• Experience Builder

At DrupalCon Portland 2024, members of the Drupal Community Working Group were pleased to announce the winner of the 2024 Aaron Winborn Award, Mike Anello (ultimike.)

About Mike Anello

Mike Anello winner of the Aaron Winborn Award 2024

Mike has been an integral part of the Drupal Community for nearly 20 years. His leadership is evident through his long-term involvement with the Community Working Group and its Conflict Resolution Team, as well as his role as the lead organizer of Florida Drupal Camp. As a co-founder and educator at DrupalEasy, he continues to mentor and inspire numerous community members, helping to lower barriers to entry. Mike consistently shares his expertise as a presenter and facilitator at many Drupal events. His contributions inspire many, both directly and indirectly, throughout our community.

Heartfelt Nominations

Each year many individuals are nominated for the award. But this year, one nomination seemed to sum the rest up with a simple, “You damned well know why Mike Anello deserves this award more than anyone else. Seriously.”  

Other nominations were less direct but full of grace and patience, much like Mike’s contribution to Drupal over the years. Here are a few others:

“Mike is a model community member who has had an exponential impact on the success of our community. I can't think of anyone more deserving of this award.”

“I believe hundreds of folks have been impacted positively by Mike over their career.”

“Without Mike Anello, I don't know if I would have been as enthralled with Drupal as I became. I still remember the first time I met Mike at DrupalCamp Atlanta in 2013. He inspired me to do more than work with Drupal; he inspired me to join the Drupal community. His work with DrupalEasy continues to build an education pipeline that brings in new community members and levels those who may already be involved so that they can grow their careers.”

The CWG has contacted all nominees to let them know of their nomination and shared some details about what their nominators wrote about them, thanking them for their continued work in the community. 

About the Aaron Winborn Award

The 2024 Aaron Winborn Award

The award is named after a long-time Drupal contributor who lost his battle with ALS in 2015. This award recognizes an individual who, like Aaron, demonstrates personal integrity, kindness, and an above-and-beyond commitment to the Drupal project and community.

Previous winners of the award are  Cathy Theys, Gabór Hojtsy, Nikki Stevens, Kevin Thull, Leslie Glynn, Baddý Breidert, AmyJune Hineline, Angie Byron, and Randy Fay. Current CWG Conflict Resolution Team members, along with previous winners, selected the winner based on nominations submitted by Drupal community members.

Nominations for next year's award will open in early 2025.

File attachments:  ma-24-awa.jpeg awa2024-award.png

We are happy to have been selected to host a side-event of the PointZeroForum in Biel, Switzerland from 10-12am on July 1st where we will be presenting GNU Taler and related technologies. Attendance is gratis and open to the general public (not just PZF attendees). You can find more information and register for the event on the BFH event page.

We’re excited to announce the June 2024 release of the Python and Jupyter extensions for Visual Studio Code!

This release includes the following announcements:

• VS Code Native REPL for Python with Intellisense and syntax highlighting
• Pytest improvements in the testing rewrite

If you’re interested, you can check the full list of improvements in our changelogs for the Python, Jupyter and Pylance extensions.

VS Code Native REPL for Python with Intellisense and syntax highlighting

Starting in this release, we are experimenting with a new REPL in the Python extension which includes features such as Intellisense and syntax highlighting to make your Python development experience more efficient. For those familiar with Jupyter’s Interactive Window, this REPL may look similar; however, it has two key differentiators: it does not rely on the Jupyter extension, nor does it require a kernel to be installed in your development environment. This VS Code Native REPL for Python also adheres to principles present in the REPL built-in to Python itself, in that history is immutable.

To enable this feature, set "python.REPL.sendToNativeREPL": true in your settings.json file. This will execute code in the VS Code Native REPL on Shift+Enter and Run Selection/Line. Moreover, the Native REPL will smartly execute on Enter, similar to Python’s original interactive interpreter, if you add the setting "interactiveWindow.executeWithShiftEnter": false, in your settings.json. You can opt to continue to use the REPL built-in to Python located in the terminal ( >>> ) by setting "python.REPL.sendToNativeREPL": false in your settings.json.

As we continue iterating on this feature, all feedback is welcomed and can be made as issues in our GitHub repository.

Pytest improvements in the testing rewrite

The experience with pytest when using the Python Testing Rewrite has been improved to better support setting pytest’s cwd (current working directory) when it is adjacent to the VS Code workspace root, and for displaying parameterized tests on the Test Explorer when function names are repeated across classes. Additionally, we reduced test discovery failure scenarios by adding the system configuration script path to PATH to enable shells for test execution.

As we continue to add improvements to the testing experience under the rewrite to make the experience more stable and performant, we will begin adopting the rewrite as default in the upcoming month on pre-release of the Python extension.

Other Changes and Enhancements

We have also added small enhancements and fixed issues requested by users that should improve your experience working with Python and Jupyter Notebooks in Visual Studio Code. Some notable changes include:

• You can now enable/disable auto-indent with Pylance without having to restart the server (pylance-release#5778)
• “Implement all inherited abstract classes” Code Action is now available as a Quick Fix for the reportAbstractUsage diagnostic (pylance-release#5757)

We would also like to extend special thanks to this month’s contributors:

• @LouisGobert Show PyPi links in requirements.txt in @vscode-python#23288
• @andybbruno Fix KeyError: 'params' when running tests in @vscode-python#23397

Call for Community Feedback

As we are planning and prioritizing future work, we value your feedback! Below are a few issues we would love feedback on:

• Design proposal for test coverage in (@vscode-python#22827)

Try out these new improvements by downloading the Python extension and the Jupyter extension from the Marketplace, or install them directly from the extensions view in Visual Studio Code (Ctrl + Shift + X or ⌘ + ⇧ + X). You can learn more about Python support in Visual Studio Code in the documentation. If you run into any problems or have suggestions, please file an issue on the Python VS Code GitHub page.

The post Python in Visual Studio Code – June 2024 Release appeared first on Python.

Recently, Dries Buytaert announced the Drupal Starshot leadership team. Lullabot's Cristina Chumillas will be the UX lead. In this role, Cristina will "define the design and user experience vision" for the product.

In this episode, Mike has Alex Clark on the show. Alex is the leading developer of the fork of the Python Imaging Library (PIL), known as Pillow.

We chatted about the following topics:

• The origins of Pillow

• Lessons learned in open source development

• Surprising use cases for Pillow

• AI and Pillow

• and much more!

Show Links

• Django - https://www.djangoproject.com/

• Wagtail - https://wagtail.org/

• Faker - https://github.com/joke2k/faker

• django-allauth - https://allauth.org/

• django-extensions - https://github.com/django-extensions/django-extensions

• django-sql-explorer - https://www.sqlexplorer.io/

• logfire - https://pydantic.dev/logfire

• Pillow demo - https://github.com/python-pillow/pillow-demo

• https://www.jeremykun.com/2012/01/01/random-psychedelic-art/

• python-pillow/Pillow#1888

• https://github.com/readme/featured/nasa-ingenuity-helicopter

• Alex’s band - https://headstraightband.com

Although my blog has been quiet, a lot has happened with the Drupal Starshot project since its announcement a month ago. We provided an update in the first Drupal Starshot virtual meeting, which is available as a recording.

Today, I am excited to introduce the newly formed Drupal Starshot leadership team.

Meet the leadership team Product Lead: Dries Buytaert

I will continue to lead the Drupal Starshot project, focusing on defining the product vision and strategy and building the leadership team. In the past few weeks, I have cleared other responsibilities to dedicate a significant amount of time to Drupal Starshot and Drupal Core.

Technical Lead: Tim Plunkett (Acquia)

Tim will oversee technical decisions and facilitate contributions from the community. His role includes building a team of Drupal Starshot Committers, coordinating with Drupal Core Committers, and ensuring that Drupal Starshot remains stable, secure, and easy to upgrade. With 7 years of engineering leadership experience, Tim will help drive technical excellence. Acquia is providing Tim the opportunity to work full-time on the Drupal Starshot project.

User Experience Lead: Cristina Chumillas (Lullabot)

Cristina will define the design and user experience vision for Drupal Starshot. She will engage with contributors to initiate research activities and share the latest UI/UX best practices, ensuring a user-centric approach. She has been leading UX-related Drupal Core initiatives for over 7 years. Lullabot, Cristina's employer, has generously offered her the opportunity to work on Drupal Starshot full-time.

Product Owner: Pamela Barone (Technocrat)

Pam will help ensure alignment and progress among contributors, including defining and prioritizing work. She brings strong communication and organizational skills, having led Drupal projects for more than 12 years.

Contribution Coordinator: Gábor Hojtsy (Acquia)

Gábor will focus on making it easier for individuals and organizations to contribute to Drupal Starshot. With extensive experience in Open Source contribution and community engagement, Gábor will help communicate progress, collaborate with the Drupal Association, and much more. Acquia will provide Gábor with the opportunity to work full-time on the Drupal Starshot project.

Starshot Council (Advisory Board)

To support the leadership team, we are establishing the Starshot Council, an advisory board that will include:

1. Three end-users (site builders)
2. Three Certified Drupal Partners
3. Two Drupal Core Committers (one framework manager and one release manager)
4. Three Drupal Association board members, one from each of the following Board Working Groups: Innovation, Marketing, and Fundraising
5. Two staff members from the Drupal Association

The council will meet monthly to ensure the leadership team remains aligned with the broader community and strategic goals. The Drupal Association is leading the effort to gather candidates, and the members of the Starshot Council will be announced in the coming weeks.

More opportunities to get involved

There are many opportunities for others to get involved as committers, designers, developers, content creators, and more.

We have specific tasks that need to be completed, such as finishing Project Browser, Recipes and Automatic Updates. To help people get involved with this work, we have set up several interactive Zoom calls. We'll update you on our progress and give you practical advice on where and how you can contribute.

Beyond the tasks we know need to be completed, there are still many details to define. Our next step is to identify these. My first priority was to establish the leadership team. With that in place, we can focus on product definition and clarifying the unknowns. We'll brief you on our initial ideas and next steps in our next Starshot session this Friday.

Conclusion

The Drupal Starshot project is off to an exciting start with this exceptional leadership team. I am grateful to these talented individuals for stepping up to drive this important project. Their combined expertise and dedication will drive excitement and improvements for the Drupal platform, ultimately benefiting our entire community. Stay tuned for updates as we continue to make strides in this ambitious initiative.

Every PSF voting-eligible Member (Supporting, Managing, Contributing, and Fellow) needs to affirm their membership to vote in this year’s election.

If you wish to vote in this year’s election, you must affirm your intention to vote no later than Tuesday, June 25th, 2:00 pm UTC to participate in this year’s election. This year’s Board Election vote begins Tuesday, July 2nd, 2:00 pm UTC and closes on Tuesday, July 16th, 2:00 pm UTC. You should have received an email from "psf@psfmember.org <Python Software Foundation>" with subject "[Action Required] Affirm your PSF Membership voting status" that contains information on how to affirm your voting status. If you were expecting to receive the email but have not (make sure to check your spam!), please email psf-elections@pyfound.org and we’ll assist you.

PSF Bylaws

Section 4.2 of the PSF Bylaws requires that “Members of any membership class with voting rights must affirm each year to the corporation in writing that such member intends to be a voting member for such year.”

The PSF did not enforce this before 2023 because it was technically challenging. Now that we can track our entire voting membership on psfmember.org, we are implementing this requirement.

Our motivation is to ensure that our elections can meet quorum as required by Section 3.9 of our bylaws. As our membership has grown, we have seen that an increasing number of Contributing, Managing, and Fellow members with indefinite membership do not engage with our annual election, making quorum difficult to reach. 

An election that does not reach quorum is invalid. This would cause the whole voting process to be re-held as well as create an undue amount of effort on the part of the PSF Staff.

Need to check your membership status?

You can see your membership record and status on your PSF Member User Information page (note you must be logged in to psfmember.org to view that page). If you are a voting-eligible member (active Supporting, Managing, Contributing, and Fellow members of the PSF) and do not already have a login, please create an account on psfmembership.org first and then email psf-donations@python.org so we can link your membership to your account. Please ensure you have an account linked to your membership so that we can have the most up-to-date contact information for you in the future.

What happens next?

You’ll get an email from OpaVote with a ballot on or before July 2nd and then you can vote!

Check out our PSF Membership page to learn more. If you have questions about membership or nominations please email psf-donations@python.org. Join the PSF Discord for the Board Office Hours, June 11th, 4-5 PM UTC, and June 18th, 12-1 PM UTC. You are also welcome to join the discussion about the PSF Board election on our forum.

Monday was a U.S. holiday, which meant I was able to go full-steam ahead on the storage MR for Experience Builder (XB) that I started the prior week. On Tuesday, I continued that work, and spun off a second MR that allows changing the source type and source value … for which I shared a 2.5-minute screencast in #experience-builder late on Tuesday.

In it, you’ll see a hacky-as-hell UI. It’s currently named TwoTerribleTextAreasWidget to convey in no uncertain terms that this is throwaway code :D Its purpose: help stand up infrastructure and get the back-end pieces in place to power the UI (see last week’s screenshot), which is currently using hardcoded data.

The video is the first step in visualizing all the pieces of Alex “effulgentsia”’s data model proposal in #3440578. In a nutshell, you can see that for each placed component, this video proves:

• it is possible to exactly match Single Directory Components (SDC) props against Drupal field types (to be precise: props inside those fields)
• while allowing those values to be:
  • either dynamic: reuse of structured data that already exists on the entity (XB aims to embrace that strength of Drupal, not to diminish it)
  • or static: fixed values stored in JSON-in-the-database as described in #3440578 1
• crucially, we can automatically surface only sensible choices, and present the choices in an order that encourages best practices, using only schema matching2 (SDCs use JSON schema, whereas the Drupal entity/field system uses Typed Data + validation constraints)

I was relieved to see that effulgentsia indicated this indeed matches his vision :)

Just those two source types (dynamic and static) are insufficient, which is why Felix has been hard at work to bring us a working PoC of adapters too, which are able to

1. adapt data into a shape that Drupal does not provide a field type for (for example: the type: string, format: time)
2. combine multiple data sources (any combination of static and dynamic) into a single shape (for example: combine an image + Image Style inputs and to adapt them into an image that uses that style

Adapters were merged on Friday!

That was more technical than previous weeks. The more technical readers might, if they squint again just like last week for the UI, be able to see how Lauri “lauriii”, effulgentsia and I see the different pieces connect. I know that many of you are longing for detailed architectural diagrams. They do not exist today. We had to first prove what we envisioned was feasible. There’s a bit more proving to be done first, but then such documentation & diagrams will be my top priority.

Before sharing that video on Tuesday, I met with Cristina “ckrina”, Jared “jponch”, Mateu “e0ipso” and Mike “mherchel”, about design tokens, which is another crucial part of XB. e0ipso had already been working on a PoC for bringing design tokens to SDC, whereas ckrina felt it was important to start defining which design tokens should exist. We ended up concluding unanimously that building a few concrete components and making them use design tokens would help define that — so ckrina, jponch and mherchel are tackling that next.

The meeting was recorded and shared and sparked a lively discussion, where Pierre “pdureau” chimed in with interesting UI Suite-based opinions

It’s great to see this work in motion, because both the exploratory “how should it work from a design POV?” and the concrete SDC support work are necessary, and both will inform the direction of #3444424: [META] Configuration management: define needed config entity types.

On Wednesday, #3450586: [META] Early phase back-end work coordination and #3450592: [META] Early phase front-end work coordination were created, to start making it possible for any Drupal contributor to 1) see what’s happening, 2) find issues to contribute to. (The list of available issues is sparse at this early stage, because there barely is a codebase, and not all architectural puzzle pieces exist yet.)

Later that day, I rode my bicycle over to meet with 4 people of the Dropsolid team. They’re very eager to contribute to XB (their CEO, Dominique “domidc” almost didn’t let me leave the DrupalCon venue when it was closing, that’s how enthusiastic they are :D), and they bring a unique perspective: they focus on “mid-market” and have hundreds (thousand?) of sites using Layout Builder. Thanks to to that, they intimately know some of Layout Builder’s architectural choices that XB should avoid. On the code contribution side, I was able to point them to the 2 meta issues above that had been created only hours prior. On the UX/product side of XB, they’re coordinating with lauriii next, so expect to hear more in a future update.

Perhaps the best place to contribute to XB today is actually in SDC! Kyle “ctrlADel” Einecker discovered an SDC bug during DrupalCon Portland (#3446933) that definitely will block XB. e0ipso worked on a fix and penyaskito RTBC‘d it on Thursday. This also connects with #3446083 and #3446722 which focuses on defining different ways of composing components out of existing SDCs for XB to support.

Also on Wednesday, Lee “larowlan” helped the UI transition from miragejs to msw.

To round the week out, Ben “bnjmnm” finished his epic battle with the CI gods on Friday and won!: he got Cypress working on XB’s GitLab CI pipeline. Both Ben and Jesse were raving about the excellent DX that Cypress has compared to other (end-to-end) testing frameworks for JS. With the CI pieces in place, we’re ending this week on a strong note: future UI work will be able to move faster thanks to Cypress, and Cypress-on-CI!

Thanks to Lauri for reviewing this!

1. To generate field widgets for these, we conjure instances of those field types out of thin air! ↩︎

2. Schema matching basically is a fancy word for shape matching. ↩︎

This blog has been re-posted and edited with permission from Wim Leer's blog

Explore Drupaljam 2024 with Drop Times, the media partner! Discover sponsorship opportunities and delve into an insightful keynote session on the future of open source. Secure your spot for June 12th now!