Author: Michael G
Drupal Association blog: Helping maintain high value Drupal contributions
Drupal’s contribution credit system continues to be unique in open source, in that it provides an attribution and incentive system to encourage greater contribution to the Drupal project, both from individuals and organizations.
Recently, there’s been discussion within the Drupal community on what makes a ‘high’ vs ‘low-value’ contribution. There’s a perception from some community members that some contributors may be using low effort, low value contributions to gain a more favorable placement within the Drupal Marketplace. Some examples of low-value contributions that people have given include posting unnecessary screenshots to issues, or running automated tooling against many projects to fix minor code quality issues.
As we evaluate these concerns, it’s important to remember that contribution recognition is not a zero-sum game. There is no ‘winning’ contribution.
We very much want many people to be recognized for their contributions, and we want to see new faces in the issue queues. Some contributions which may seem simplistic or low-value may also just be good entry points for someone first beginning a contribution journey, and we should always use these examples as an opportunity to help an individual or organization ‘level-up’ their contribution skills.
At the same time though, we want recognition to be proportional to the effort put in, and we want our project maintainers, who ultimately control who gets credit for contributions to their projects, to feel encouraged by seeing new faces and not burnt out by policing the system.
How did we get here
The Drupal Marketplace is intended to showcase organizations that contribute back to Drupal. This includes not only code, but non-code contributions such as testing functionality, event organizing, speaking, volunteering, and more.
The more work an organization contributes, the higher they will be ranked within the marketplace. This, in turn, leads to more job opportunities and leads.
Inevitably, contributors will try to maximize their contributions to gain a higher ranking. Is that okay? It certainly can be okay – this incentive exists because we want to further encourage contribution, but those contributions need to be authentic, and we hope to see new contributors develop their skills and increase the scope of their contributions over time.
Today, we are seeing a recent pattern with providing a lot of test screenshots. These can be valuable, but in some cases the users posting them aren’t even checking if they have a properly applied patch, so it’s difficult to rely on. This is partly because file attachments automatically pre-check the contribution box when users post them to issues, so that’s an area where we can use a technical solution to try and correct the situation.
A quick fix
The Drupal Association Engineering Team is making changes to the issue queues so that contributors that upload images will no longer be automatically assigned credit. By not having this auto-populate, the maintainer won’t have to spend time deselecting drive-by contributions of screenshots that were inauthentically posted or otherwise unhelpful.
Are we running into Goodhart’s law?
Goodhart’s law is an adage often stated as, “When a measure becomes a target, it ceases to be a good measure”. Often invoked when discussing economics, it’s directly related to the issue at hand. Any deliberately designed incentive structure is going to result in people figuring out ways to maximize their results – that’s only to be expected.
But our firm belief is that with careful management, the system can still provide a good measure of contribution. Contribution credit is central to the Drupal ecosystem to help motivate contributors.
How can we encourage high value contribution?
It’s difficult, if not impossible, to evaluate the quality of a contribution algorithmically, although there are some heuristics we can use. It is impossible to algorithmically determine the intend behind a contribution: was it an authentic first effort, or was it a cynical reach for low-hanging fruit.
We always want to assume good intent, and to use any opportunity we can as a teaching moment. But with collaboration across so many projects and so many people, we do need community standards and guidance to help.
The first step is to define what is high-value and what is low-value (or perhaps even to decide if these are the right terms!). The Drupal Association is putting together a small group composed of community members, DA board, and staff to create some documentation for exactly this. We have existing documentation that gives guidance on granting credit, but none that is oriented toward the contributor.
The goal of this documentation is to guide contributors on how they can help, and how to avoid being unhelpful through well thought out examples, and processes. This documentation can then be linked to within Drupal issues when a maintainer feels that a contribution was unhelpful.
Our hope is that reading the documentation will be enough for any new contributors to realize when they are posting unnecessary and unhelpful contributions, and give them a clear pathway to making contributions that have a greater impact.
Next steps
The Drupal Association is committed to making contributions as fair and equitable as possible. If you’d like to participate in a discussion to create documentation, please reach out by October 1st.
Ruby 3.2.0 Preview 2 Released
We are pleased to announce the release of Ruby 3.2.0-preview2. Ruby 3.2 adds many features and performance improvements.
WASI based WebAssembly support
This is an initial port of WASI based WebAssembly support. This enables a CRuby binary to be available on Web browser, Serverless Edge environment, and other WebAssembly/WASI embedders. Currently this port passes basic and bootstrap test suites not using Thread API.
Background
WebAssembly (WASM) is originally introduced to run programs safely and fast in web browsers. But its objective – running programs efficinently with security on various environment – is long wanted not only by web but also by general applications.
WASI (The WebAssembly System Interface) is designed for such use cases. Though such applications need to communicate with operating systems, WebAssembly runs on a virtual machine which didn’t have a system interface. WASI standardizes it.
WebAssembly/WASI Support in Ruby intends to leverage those projects. It enables Ruby developers to write applications which runs on such promised platform.
Use case
This support encourages developers can utilize CRuby in WebAssembly environment. An example use case of it is TryRuby playground’s CRuby support. Now you can try original CRuby in your web browser.
Technical points
Today’s WASI and WebAssembly itself has some missing features to implement Fiber, exception, and GC because it’s still evolving and also for security reasons. So CRuby fills the gap by using Asyncify, which is a binary transformation technique to control execution in userland.
In addition, we built a VFS on top of WASI so that we can easily pack Ruby apps into a single .wasm file. This makes distribution of Ruby apps a bit easier.
Related links
Regexp timeout
A timeout feature for Regexp matching is introduced.
Regexp.timeout = 1.0
/^a*b?a*$/ =~ "a" * 50000 + "x"
#=> Regexp::TimeoutError is raised in one second
It is known that Regexp matching may take unexpectedly long. If your code attempts to match an possibly inefficient Regexp against an untrusted input, an attacker may exploit it for efficient Denial of Service (so-called Regular expression DoS, or ReDoS).
The risk of DoS can be prevented or significantly mitigated by configuring Regexp.timeout
according to the requirements of your Ruby application. Please try it out in your application and welcome your feedback.
Note that Regexp.timeout
is a global configuration. If you want to use different timeout settings for some special Regexps, you may want to use timeout
keyword for Regexp.new
.
Regexp.timeout = 1.0
# This regexp has no timeout
long_time_re = Regexp.new("^a*b?a*$", timeout: nil)
long_time_re =~ "a" * 50000 + "x" # never interrupted
The original proposal is https://bugs.ruby-lang.org/issues/17837
Other Notable New Features
No longer bundle 3rd party sources
-
We no longer bundle 3rd party sources like
libyaml
,libffi
.-
libyaml source has been removed from psych. You may need to install
libyaml-dev
with Ubuntu/Debian platfrom. The package name is different each platforms. -
libffi will be removed from
fiddle
at preview2
-
Language
-
Anonymous rest and keyword rest arguments can now be passed as
arguments, instead of just used in method parameters.
[Feature #18351]def foo(*) bar(*) end def baz(**) quux(**) end
-
A proc that accepts a single positional argument and keywords will
no longer autosplat. [Bug #18633]proc{|a, **k| a}.call([1, 2]) # Ruby 3.1 and before # => 1 # Ruby 3.2 and after # => [1, 2]
-
Constant assignment evaluation order for constants set on explicit
objects has been made consistent with single attribute assignment
evaluation order. With this code:foo::BAR = baz
foo
is now called beforebaz
. Similarly, for multiple assignments
to constants, left-to-right evaluation order is used. With this
code:foo1::BAR1, foo2::BAR2 = baz1, baz2
The following evaluation order is now used:
foo1
foo2
baz1
baz2
-
Find pattern is no longer experimental.
[Feature #18585] -
Methods taking a rest parameter (like
*args
) and wishing to delegate keyword
arguments throughfoo(*args)
must now be marked withruby2_keywords
(if not already the case). In other words, all methods wishing to delegate
keyword arguments through*args
must now be marked withruby2_keywords
,
with no exception. This will make it easier to transition to other ways of
delegation once a library can require Ruby 3+. Previously, theruby2_keywords
flag was kept if the receiving method took*args
, but this was a bug and an
inconsistency. A good technique to find the potentially-missingruby2_keywords
is to run the test suite, for where it fails find the last method which must
receive keyword arguments, useputs nil, caller, nil
there, and check each
method/block on the call chain which must delegate keywords is correctly marked
asruby2_keywords
. [Bug #18625] [Bug #16466]def target(**kw) end # Accidentally worked without ruby2_keywords in Ruby 2.7-3.1, ruby2_keywords # needed in 3.2+. Just like (*args, **kwargs) or (...) would be needed on # both #foo and #bar when migrating away from ruby2_keywords. ruby2_keywords def bar(*args) target(*args) end ruby2_keywords def foo(*args) bar(*args) end foo(k: 1)
Performance improvements
YJIT
- Support arm64 / aarch64 on UNIX platforms.
- Building YJIT requires Rust 1.58.1+. [Feature #18481]
Other notable changes since 3.1
- Hash
- Hash#shift now always returns nil if the hash is
empty, instead of returning the default value or
calling the default proc. [Bug #16908]
- Hash#shift now always returns nil if the hash is
- MatchData
- MatchData#byteoffset has been added. [Feature #13110]
- Module
- Module.used_refinements has been added. [Feature #14332]
- Module#refinements has been added. [Feature #12737]
- Module#const_added has been added. [Feature #17881]
- Proc
- Proc#dup returns an instance of subclass. [Bug #17545]
- Proc#parameters now accepts lambda keyword. [Feature #15357]
- Refinement
- Refinement#refined_class has been added. [Feature #12737]
- Set
- Set is now available as a builtin class without the need for
require "set"
. [Feature #16989]
It is currently autoloaded via theSet
constant or a call toEnumerable#to_set
.
- Set is now available as a builtin class without the need for
- String
- String#byteindex and String#byterindex have been added. [Feature #13110]
- Update Unicode to Version 14.0.0 and Emoji Version 14.0. [Feature #18037]
(also applies to Regexp) - String#bytesplice has been added. [Feature #18598]
- Struct
- A Struct class can also be initialized with keyword arguments
withoutkeyword_init: true
onStruct.new
[Feature #16806]
- A Struct class can also be initialized with keyword arguments
Compatibility issues
Note: Excluding feature bug fixes.
Removed constants
The following deprecated constants are removed.
Fixnum
andBignum
[Feature #12005]Random::DEFAULT
[Feature #17351]Struct::Group
Struct::Passwd
Removed methods
The following deprecated methods are removed.
Dir.exists?
[Feature #17391]File.exists?
[Feature #17391]Kernel#=~
[Feature #15231]Kernel#taint
,Kernel#untaint
,Kernel#tainted?
[Feature #16131]Kernel#trust
,Kernel#untrust
,Kernel#untrusted?
[Feature #16131]
Stdlib compatibility issues
Psych
no longer bundles libyaml sources.
Users need to install the libyaml library themselves via the package
system. [Feature #18571]
C API updates
Removed C APIs
The following deprecated APIs are removed.
rb_cData
variable.- “taintedness” and “trustedness” functions. [Feature #16131]
Standard libraries updates
-
The following default gem are updated.
- TBD
-
The following bundled gems are updated.
- TBD
-
The following default gems are now bundled gems. You need to add the following libraries to
Gemfile
under the bundler environment.- TBD
See NEWS
or commit logs
for more details.
With those changes, 2393 files changed, 168931 insertions(+), 113411 deletions(-)
since Ruby 3.1.0!
Download
-
https://cache.ruby-lang.org/pub/ruby/3.2/ruby-3.2.0-preview2.tar.gz
SIZE: 19816780 SHA1: 2106c77fc1600daf41ae137ecc4cf7937e27f67f SHA256: 8a78fd7a221b86032f96f25c1d852954c94d193b9d21388a9b434e160b7ed891 SHA512: 5e9ddcb1a43cff449b0062cc716bfb80a9ebbb14a1b063f34005e2998c2c5033badb44e882232db9b2fceda9376f6615986e983511fda2575d60894752b605cc
-
https://cache.ruby-lang.org/pub/ruby/3.2/ruby-3.2.0-preview2.tar.xz
SIZE: 14578112 SHA1: 538b3ea4dc0d99f60f8bd6f71e65a56ceeb41c18 SHA256: 01fac0929dccdabc0686c1109da6c187897a401da9ff8851242befa92f7fd430 SHA512: 0f4cc919284fdfa1a42b6381760d1b3a4660da4b0fcdd2adf01ea04a425548b3c5ac090866915675db73964a1055090e54dd97cf4628cbb69403e541c71c28ff
-
https://cache.ruby-lang.org/pub/ruby/3.2/ruby-3.2.0-preview2.zip
SIZE: 24150109 SHA1: 69ffffc52cad626166f73f21f25c29c9d73fe0e8 SHA256: 67f9ad3110be1975b3ce547c0a6e2c910dfc1945fd6e9bb1bd340568897c6554 SHA512: 1447e099e7a8da0ff206fda6f4e466640d6e86e9da8148315ab0154684b1fd22c02c0022b5a2f4d3fc00103b4e8cef8e35a770174921fd8c6abeca9ad41c1818
What is Ruby
Ruby was first developed by Matz (Yukihiro Matsumoto) in 1993,
and is now developed as Open Source. It runs on multiple platforms
and is used all over the world especially for web development.
Posted by naruse on 9 Sep 2022
Automate network testing with this open source Linux tool
Use iperf3 to troubleshoot bandwidth, timing, protocol, and other problems on your TCP/IP network. Read More at Enable Sysadmin
The post Automate network testing with this open source Linux tool appeared first on Linux.com.
OSI Executive Director to speak at Open Source Summit Europe
We are slowly, but surely starting to return to in person events. Our next stop…
The post OSI Executive Director to speak at Open Source Summit Europe first appeared on Voices of Open Source.
Destiny 2 walkthrough Part 7
Video by via Dailymotion Source Follow me on Twitter : https://twitter.com/cageofragetvFollow my Tiktok : https://www.tiktok.com/@cageofrage Follow me on Twitter : https://twitter.com/cageofrage1Follow my Dlive: https://dlive.tv/CageofRageCheck me on Twitch :https://www.twitch.tv/cageofragemy discord server! https://discord.gg/kp8ZeFyMy walkthrough of Destiny 2#cageofrage #vtuber #destiny2 #destiny #gaming #funny Go to Source
Najib remains MP while review of conviction ongoing, says Azhar
Video by via Dailymotion Source Dewan Rakyat Speaker says Najib Razak will remain the Pekan MP pending Federal Court review of decision to affirm his conviction and sentence in SRC International case. Read More: https://www.freemalaysiatoday.com/category/nation/2022/09/08/najib-remains-mp-while-review-of-conviction-ongoing-says-azhar/ Laporan Lanjut: https://www.freemalaysiatoday.com/category/bahasa/tempatan/2022/09/08/najib-kekal-ahli-parlimen-hingga-proses-pengampunan-semakan-kehakiman-selesai-kata-azhar/ Free Malaysia Today is an independent, bi-lingual news portal with a focus on Malaysian current affairs. Subscribe…
Tutorial 183 | Controlling background color in RadarScreen | TradeStation EasyLanguage tutorials
Video by via Dailymotion Source It is not possible to change the background color of a RadarScreen cell in the symbol column using TradeStation EasyLanguage. The background color of this column can be set as a property of the RadarScreen settings page but not programmatically. But what if you needed more control over the plot…
Gantikan Almeida Latih Arema FC, Javier Roca Akan Kembalikan Karakter Malangan
Video by via Dailymotion Source MALANG, KOMPAS.TV- Setelah resmi menggantikan Almeida melatih Arema FC, Javier Roca langsung turun tangan melatih punggawa Singo Edan. Di latihan perdananya, Rabu (07/09/2022) sore di Stadion Gajayana Kota Malang, Roca menyebut banyak yang harus diperbaiki dalam tim, namun meski demikian hal tersebut merupakan tantangan bagi dirinya. Mengembalikan Arema FC kepada…
Judge recuses himself in Azeez’s appeal against defamation ruling
Video by via Dailymotion Source Justice Vazeer Alam Mydin Meera recuses himself in hearing appeal over Azeez Abdul Rahim’s defamation case against Lim Guan Eng, says he represented one of the parties while he was a lawyer Read More: https://www.freemalaysiatoday.com/category/nation/2022/09/08/judge-recuses-himself-in-azeezs-appeal-against-defamation-ruling/ Laporan Lanjut: https://www.freemalaysiatoday.com/category/bahasa/tempatan/2022/09/08/hakim-tarik-diri-dengar-rayuan-saman-azeez/ Free Malaysia Today is an independent, bi-lingual news portal with a focus…