Programming Leftovers

-
Jussi Pakkanen: The Nine Phases of an Open Source Project Maintainer
There is more to running an open source project than writing code. In fact most of all work has to do with something else. This places additional requirements to project maintainers that are often not talked about. In this post we'll briefly go over nine distinct phases each with a different hat one might have to wear. These can be split into two stages based on the lifetime and popularity of the project.
[...]
Phase Eight: The Overseer
This phase begins when the project maintainer realizes that they are no longer the person who knows most about the code base. Other people have done most of the coding work for so long that they are the actual experts on it. This causes yet another change in the type of work one needs to do. Up until now the work has been about solving problems and making decisions on things you are intimately familiar with. As an overseer you need to make decisions on things you don't really know about. Earlier decisions were based on code and implementation details, but now decisions are based mostly on what other people say in their merge requests and design discussions.
This is something nobody really prepares you for. Making big decisions based on imperfect information can be really difficult for someone who has gotten used to going through every detail. Once a project gets over a certain size this is just not possible as the human brain is incapable of holding that many details in active memory at the same time. Even if it could, having a single person review everything would be a huge bottleneck. It is (more than) a full time job, and getting someone to pay for a full time maintainer review job is very rare.
Finally, even if this were possible, reviewing is a very tiring job that very few people can keep on doing as their only task for very long. Eventually the mind will start screaming for something else, even for a while. Finally even if someone could do that, contributors would eventually get very annoyed by getting micromanaged to death and just leave.
Phase Nine: The Emeritus
All good things eventually come to an end and so will open source project maintainership. Eventually the project will either become irrelevant or the torch will be passed to someone else. This is, in a way, the greatest thing a project maintainer could hope for: being able to create a new entity that will keep on being used even after you have stopped working on it.
Open source maintainership is a relatively young field and most projects at the end of their life cycle either become unmaintained zombies or get replaced by a new project written from scratch. Ee don't have that much experience on what emerituses do. Based on other fields these may range from "nothing" to doing conference talks, advising current maintainers on thorny issues.
-
GCC 11.0.0 Status Report (2020-11-16), Stage 3 in effect now
Status ====== GCC trunk which eventually will become GCC 11 is now in Stage 3 which means open for general bugfixing. We have accumulated quite a number of regressions, a lot of the untriaged and eventually stale. Please help in cleaning up. Quality Data ============ Priority # Change from last report -------- --- ----------------------- P1 37 + 4 P2 257 + 1 P3 94 + 20 P4 184 - 1 P5 24 -------- --- ----------------------- Total P1-P3 388 + 25 Total 596 + 24
-
GCC 11 Ends Feature Development While Still Waiting For AMD Znver3 Support
As was expected, formal feature development is now over for GCC 11 and it's time for bug fixing.
Longtime GCC developer Richard Biener of SUSE announced today that the development trunk has shifted to stage three development. This shift means the focus now is on general bug fixing rather than adding of new features.
And plenty of bug fixing there will be. Biener noted in the status update, "We have accumulated quite a number of regressions, a lot of the untriaged and eventually stale. Please help in cleaning up."
-
Teaching QLocale more about number formats
QLocale looks after all localisation (or L10n) within Qt; while Qt 6 has swept away a few last fragments of L10n built into other things, that now consistently use the C locale (and advise you to use QLocale if you need L10n), it's also seen some significant improvements to how QLocale does those things, particularly in relation to numeric texts and surrogate pairs.
[...]
In QString and friends we represent text using UTF-16; the size() of a string reported by these types is the number of UTF-16 code units. However, Unicode is bigger than fits into 16 bits, so there are code points (roughly what one normally thinks of as characters in written text, although there are further complications) that can't be represented as a single UTF-16 code unit; these are represented as surrogate pairs, in which two UTF-16 code units encode a single code point. When these are needed, the UTF-16-size reported by QString, in code units, is greater than the code-point size, which a native reader of the text is more likely to consider to be its length. In particular, a single character may need to be represented by a QString of length two.
Characters in Unicode's Basic Multilingual Plane (BMP) can be represented by single UTF-16 code-points but the rest need surrogate pairs; and CLDR does contain some locales that use characters outside the BMP. Normally this isn't an issue, since QString can handle surrogate pairs just fine.
-
I founded a company called Perl Research Institute, Ltd.
I founded a company called Perl Research Institute, Ltd in Japan.
The main purpose of the Perl Research Institute is to restore Perl's honor.
Its reputation was miserable compared to the excellence of Perl's features.
-
Rakudo Weekly News: 2020.46 Coercion Renewed
Months of work by Vadim Belman, implementing the new type coercion protocol, was finally merged in time for the 2020.11 Rakudo compiler release. This makes coercion types such as Str() first class citizens. And allows custom classes to define their behaviour when used in coercions.
-
1.48.0 pre-release testing
The 1.48.0 pre-release is ready for testing. The release is scheduled for this Thursday, November 19th. Release notes can be found here.
-

- Login or register to post comments
Printer-friendly version- 3088 reads
PDF version
More in Tux Machines
- Highlights
- Front Page
- Latest Headlines
- Archive
- Recent comments
- All-Time Popular Stories
- Hot Topics
- New Members
digiKam 7.7.0 is released
After three months of active maintenance and another bug triage, the digiKam team is proud to present version 7.7.0 of its open source digital photo manager. See below the list of most important features coming with this release.
|
Dilution and Misuse of the "Linux" Brand
|
Samsung, Red Hat to Work on Linux Drivers for Future Tech
The metaverse is expected to uproot system design as we know it, and Samsung is one of many hardware vendors re-imagining data center infrastructure in preparation for a parallel 3D world.
Samsung is working on new memory technologies that provide faster bandwidth inside hardware for data to travel between CPUs, storage and other computing resources. The company also announced it was partnering with Red Hat to ensure these technologies have Linux compatibility.
|
today's howtos
|








.svg_.png)
Content (where original) is available under CC-BY-SA, copyrighted by original author/s.

Recent comments
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago