This gem is now entering passive maintenance mode; I will not be actively maintaining it anymore.

I could find the time to maintain it despite being "boring"

Maintaining open source software requires energy and a "want"/"passion". I've not been using this project myself for years, and I mainly work in other things than Rails at this point. That means I'm far removed from this project and see no personal gain in maintaining the energy to keep this going.

I'm still pretty proud of the project and I don't want to see it gone, so I want to keep updating it when needed. But on the other hand, the feature set is pretty stable and well working now (AFAIK) so I also don't see the need to pretend to be actively maintaining it.

Please: Prompt me when things break and I will probably fix it. I won't guarantee how fast I'll move, but I'll try to make the effort sometimes. The bigger the issue, the more likely it is that I'll do something about it.

[temporarily not maintained]

While the code may live online somewhere forever, an open source project only truly survives if someone maintains it.

Frankly, if the Ubuntu Desktop team “switch” from making a deb of Chromium to making a snap, I doubt they’d switch back. It’s a tremendous amount of work for developer(s) to maintain numerous debs across all supported releases. Maintaining a single snap is just practically and financially more sensible.

This example of the chromium really shows that unless snaps or other similar format was used, applications would have to be sometime very heavily patched to work on older versions of systems to the point that it generates so much work that it would not be worth do to it otherwise, or at least not worth when the snap option exists and doesn’t require that much more work.

Material Design Lite is now in limited support, with development having moved to the Material Components for the web repository. No further development is taking place in MDL by the core team, but we are happy to review PRs, fix critical bugs and push out new releases. No breaking changes will be accepted.

Less developer maintenance burden: The existing (Kuma) platform is complex and hard to maintain. Adding new features is very difficult. The update will vastly simplify the platform code — we estimate that we can remove a significant chunk of the existing codebase, meaning easier maintenance and contributions.

I'm still deeply working on it every day, i'm around 1/2 month away for a first preview release.

@monkeythedev I am curious how do you "organize" your work - You forked https://github.com/hperrin/svelte-material-ui and https://github.com/hperrin/svelte-material-ui is not very active. Do you plan an independent project ? I hope the original author would return at some times, if not, i'll see

Maybe @hperrin would be able to make an appearance and select a few additional maintainers to help out.

If everyone did this, the repair shops would be out of business.

Intercepting proxies are commonly used in businesses to enforce acceptable use policy, and to ease administrative overheads since no client browser configuration is required.

Looking at a few isolated examples doesn’t really represent the enormity of the maintenance problem when you modify objects that you shouldn’t. To understand this point of view, it’s helpful to take a step back and look at moral philosophy (aka ethics).

It also aims to support only modern browsers to keep things simple.

Useful mass transportation doesn’t suddenly appear. It is carefully nurtured from a tiny seedling of a good idea to a fully-formed organism that breathes life into a city. It is a process that takes time and effort and patience as well as money.

Maintenance Status Active: Formidable is actively working on this project, and we expect to continue work on this project for the foreseeable future.

I can't add special props and keywords to every single component I have and will ever create for this to work.

Explicitly exposing any attributes that might get overridden by a parent seems impractical to me.

Svelte will not offer a generic way to support style customizing via contextual class overrides (as we'd do it in plain HTML). Instead we'll invent something new that is entirely different. If a child component is provided and does not anticipate some contextual usage scenario (style wise) you'd need to copy it or hack around that via :global hacks.

Explicit interfaces are preferable, even if it places greater demand on library authors to design both their components and their style interfaces with these things in mind.

You can help ensure your RFC is reviewed in a timely manner by putting in the time to think through the various details discussed in the template. It doesn't scale to push the thinking onto a small number of core contributors.

the internet remembers

Even as machine-readable data begins to permeate the web, it is typically distributed in a separate file, with a separate format, and very limited correspondence between the human and machine versions.

The development of OOo has been almost completely abandoned - there are almost 300 developers for LibreOffice, and less than 20 for OpenOffice - and IBM's contribution to this project is waning like the setting sun.

The content should always be the same. For news articles, specify the “NewsArticle” type. The headline should match your article’s title. The image object refers to the hero image of the article.

If you can, use AMP like any other JavaScript library to build your site and forget about the canonical linking. Using AMP to build a whole website dramatically reduces your maintenance burden.

Not only do changes need to be tested against Ice Cream Sandwich's codebase, it is also often necessary to use workarounds due to API restrictions.

But I love it, and so I plan to keep it alive.

you honestly don’t have the time to decide which of these options is better.

Despite our best efforts to deal with all of those issues, over the course of time we fall behind. When you look at an issue it's sometimes unclear whether or not we intent to provide the functionality you propose, whether or not we fix the bug, whether or not the issue is a duplicate of another one. In order to restore a reasonable level of clarity we annually perform a House Keeping Iteration in which we go through all open issues. We categorize, label, fix, and close issues. This results in a wave of notification which is hard to deal with (our apologies) but in the end there is better understanding of what will happen to your ideas.

backstage Issues and merge request related to improvements like refactorings, tests, maintenance etc

However, since problems are only addressed when they arise, maintenance is reactive rather than proactive. Small problems left unaddressed can balloon into major failures due to focus on cost.

Most traditional (monolithic) CMS systems are “coupled”, meaning that the content management application (CMA) and the content delivery application (CDA) come together in a single application, making back-end user tools, content editing and taxonomy, website design, and templates inseparable. Coupled systems are useful for blogs and basic websites as everything can be managed in one place. But this means that the CMS code is tightly connected to any custom code and templates, which means developers have to spend more time on installations, customizations, upgrades, hotfixes, etc. and they cannot easily move their code to another CMS.

But, I was no longer using the gem, the issue activity was overwhelming, and the codebase in serious need of reworking.

Potential for political focus on building new features over technical improvements (such as refactoring)

The partial pressure of carbon dioxide (PCO2) should be maintained in a normal range (35–40 mmHg), but for temporary management of acute intracranial hypertension, inducing cerebral vasoconstriction by hyperventilation to a PCO2 of <30 mmHg is occasionally warranted.

Yes, it’s been deprecated. Why? Because too few people were using it to make it worth the time, money, and energy to maintain. In truth, although I sometimes disagree with the operator changes, I happen to agree with this one. Maintaining ALL of the synonyms takes real time and costs us real money. Supporting this operator also increases the complexity of the code base. By dropping support for it we can free up a bunch of resources that can be used for other, more globally powerful changes.

This project is looking for maintainers, see this issue.

that big disclaimer that it's unmaintained is a put-off.

This project is actively maintained. Please report issues and/or create pull requests if you face any issues.

Using versions is a maintenance burden on the preset, and we made this mistake with Neo. By specifying a version, we are forced to track with React when their version changes, possibly falling behind.

I had to upgrade my other project from Webpack 2 / Angular 5 to Webpack 4/Angular 7 and it was a complete nightmare! I lost a ton of hours and can't really justify charging my client for the weeks worth of time to figure it out.

Website Maintenance Packages that specially designed for your growing business.

WordPress Maintenance Services

I second that and recommend the typings be moved to DefinitelyTyped. It’s an unreasonable burden for a library maintainer to manage them when they aren’t using TypeScript.

Everything that gets launched gets shuttered.

Must those not presentlyidentified as creative be shown in fact to be inventors in order tobe fully recognized? Thisquestion suggests that we need to pay close attention to the tensions and contradictionsthat arise when we adopt a strategy that distributes practices previously identifiedexclusively with certain people and places (for example, with privileged white menworking in elite institutions of science and technology) across a wider landscape (one thatincludes women). In distributing those practices more widely, they are givencorrespondingly greater presence. A counter project, therefore, is to question the valueplaced on innovation itself. The aim is to understand how a fascination with change andtransformation might not be universal, but rather specifically located and with particularpolitical consequences for women, both in termsof the possibilities that are available tothem, and the visibility of their already existing contributions.

Recent research on the actual work involved in putting technologies into usehighlights the mundane forms of inventive yet taken for granted labor, hidden in thebackground, that are necessary to the success of complex sociotechnical arrangements.

If your website looks good, your goods look good.

4 Again, the sight and sound of these services is a quintessential everyday urban experience.