open source

The new Mercedes-Benz E 450 e 4MATIC MANUFAKTUR Interior Design in Alpine Grey

by
The generous dimensions of the passenger compartment are partly due to the wheelbase, which is 22 millimetres longer than that of the preceding model (2961 millimetres).

The E-Class is permitted to tow a braked trailer load of up to 2100 kilograms. The maximum unbraked towing capacity is 750 kilograms. Thanks to a tongue weight of up to 84 kilograms, the carrying of e-bikes is allowed.

The illuminated surround of the radiator grille (optional extra) has two optical fibres behind the chrome strips. Light is fed into the glass-fibre bundles via LED modules.

With two display styles (Classic and Sporty) and three modes (Navigation, Assistance, Service), the graphics of the screens can be individualised. The new MBUX is accompanied by a change in the presentation of the main icons on the displays. They are presented in a simpler way, and based on the colours used for smartphone tiles.

Depending on the market, a communication module with 5G as the transmission technology is used. This mobile phone standard makes much faster data rates possible than LTE/UMTS.

With the Digital Vehicle Key, the iPhone and Apple Watch become a car key. If the driver is carrying a compatible device, it can be used to start and lock the E-Class. Key sharing is also possible: The Digital Vehicle Key can be shared with up to 16 people. In those markets where Mercedes me connect services are available, Pre-installation for the Digital Vehicle Key forms part of the KEYLESS-GO Comfort Package. This equipment combination is available in the new E-Class from the Premium Package onwards.

Tech/News/2023/31

by
Tech/News/2023/31
Other languages: Bahasa Indonesia, Deutsch, English, Tiếng Việt, Türkçe, español, français, italiano, magyar, polski, svenska, čeština, български, русский, עברית, العربية, فارسی, हिन्दी, বাংলা, ಕನ್ನಡ, 中文,…

Drupal Core News: Bug Smash Initiative 3-year update

by

Bug Smash Initiative 3-year update

The Bug Smash community initiative started in May 2020 with the goal of reducing the number of open bugs against Drupal core.

Following advice from Gábor Hojtsy that ‘an initiative should have an exit strategy’, the initiative’s definition of done was a 5% reduction in bugs in Drupal core.

Over the past three years, we’ve smashed this goal and passed our definition of done with a 27% reduction in bugs! 

Priority

Initial – 2020-04-21

Goal

% Diff

Recent – 2023-05-09

Actual Reduction

% Diff

Minor

338

300

-11%

311

-27

-8%

Normal

6205

6000

-3%

4397

-1808

-29%

Major

1113

1000

-10%

896

-217

-20%

Critical

57

50

-12%

47

-10

-18%

Total

7713

7350

-5%

5651

-2062

-27%

Next steps

So the question is – where to next for the initiative? We’ve discussed this in our fortnightly meetings and see two paths forward:

  • We announce the initiative goals are complete and wind up our operations

  • We reframe our goals and start again.

Let’s explore what those two look like.

Option 1: Winding up the initiative

This option may seem drastic, especially given there are still bugs in core. This wouldn’t mean we’d stop trying to fix them or that we’d stop working together as a collective. It would just mean we would wind up the formal administrative tasks that go with an initiative, such as regular meetings and minutes and our twice-daily triage goal. 

Winding up the initiative doesn’t mean that the  #bugsmash slack channel or the BugSmash table at sprints would cease to exist. Nor does it mean the like-minded folks who’ve worked together in the initiative would cease collaborating. 

It just means we’d drop the formal parts of the initiative and revert back to being a loose collective with a shared goal.

Option 2: Reframing our goals

This option would allow us to reset our goals and decide on our focus for the next couple of years. We need to ask ourselves if we still have the same passion AND if we think we can make as much progress as fast as we did.

There is much less low-hanging fruit than when the initiative started. This means that many of the remaining bugs are difficult to fix. This can have an impact on morale and participation. Lately, our daily triage tasks are receiving less interest – most likely because the bugs are harder or require a specialist..

Share your thoughts

Do you have thoughts on which option we should take? Or is there an alternative that we’ve missed? 

Please take part in our community survey and let us know.

Ubuntu Touch OTA-2 Focal Release released

by
UBPorts has released the second update for the Ubuntu Touch version based on Focal Fossa. In this new version, the System Settings application has been improved in various places, the physical camera button now works (on devices that have one, I presume), and a whole load of bugs have been fixed. Device support has also improved, with the F(x)tec Pro1 X, Fairphone 3, and Vollaphone X23 now being supported by the Focal releases.