<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Daniel Fahlke on Medium]]></title>
        <description><![CDATA[Stories by Daniel Fahlke on Medium]]></description>
        <link>https://medium.com/@Flyingmana?source=rss-3a203a12b346------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*F88IqprkDAcHj8ko.png</url>
            <title>Stories by Daniel Fahlke on Medium</title>
            <link>https://medium.com/@Flyingmana?source=rss-3a203a12b346------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 19:19:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Flyingmana/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[OpenMage 2023 — a personal recap]]></title>
            <link>https://medium.com/@Flyingmana/openmage-2023-a-personal-recap-2c4539a2a080?source=rss-3a203a12b346------2</link>
            <guid isPermaLink="false">https://medium.com/p/2c4539a2a080</guid>
            <category><![CDATA[openmage]]></category>
            <dc:creator><![CDATA[Daniel Fahlke]]></dc:creator>
            <pubDate>Sun, 03 Dec 2023 13:01:10 GMT</pubDate>
            <atom:updated>2023-12-05T18:35:24.755Z</atom:updated>
            <content:encoded><![CDATA[<h3>OpenMage 2023 — a personal recap</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/0*41FznNgaDv5DxuFL.jpg" /></figure><p>Another Year is close to ending, <a href="https://github.com/OpenMage/magento-lts">OpenMage </a>is still here, and also Iam still here and supporting the OpenMage Project and its Community.<br>Now looking at my<a href="https://medium.com/@Flyingmana/recap-2018-06-what-happened-in-the-openmage-project-a206d0579667"> last Recap from 2018</a>, or the last personal Post from 2019 about the <a href="https://medium.com/@Flyingmana/plan-for-the-time-after-magento-1-eol-magento-lts-9cbc15173121">Plan for the time after Magento 1 eol</a> its obvious that I had put less time into these Posts.<br>Now the thing is that life is constantly changing, new challenges appear, one gets older and everything goes slower and takes more energy, and also life priorities shift.<br>Also the low amount of donations I could collect via Patreon back then did their part in shifting focus to other things. (Nowdays you can support me directly via Github Sponsors, but thats another topic)</p><h3>The last few years</h3><p>One bigger thing I did in 2019 was <a href="https://www.openmage.org/2019/08/18/new-home-magento-connect-modules.html">securing most of the OpenSource Magento 1 modules</a> which were published on Magento Connect. Actually the Downloading was not me, but I wrote a script to publish them all as separate Repositories on Github. And also writing a base to run commands on all of them. Was fun and also challenging. I still remember how the pure number of repositories broke an Overview Page on Github.</p><p>in 2020 a bigger part I worked myself on was making the Magento Composer Installer compatible to Composer 2</p><p>There were also <a href="https://github.com/OpenMage/magento-lts/pulls?q=is%3Apr+author%3AFlyingmana+is%3Aclosed+created%3A2019-01-01..2023-01-01+">a few Pull Requests</a> I created in the last few years in OpenMage.</p><p>The bigger contributions were probably the non-code ones. For a long time I was doing the Public Relations work, spreading the word and forwarding and coordinating People and especially Contributors and Users. This had as a side effect that people started to see me as the Leader of the Project, despite me not even having a high position in the hierarchy for a long time.<br>But a healthy Community project needs ways to find a consent on topics without the need for a single Person. In parts introducing the <a href="https://github.com/OpenMage/rfcs/pulls?q=is%3Apr+is%3Aclosed+created%3A%3C2024-01-01+">current RFC process</a> did improve this, although the community did not make much use of it yet.<br>But also with Magento1 going out of support, the pressure to keep Backwards compatibility got lower and I did not feel so much pressure anymore to hold against bigger changes. (less work and stress for me, more freedoms for the contributors)</p><h3>What I did during 2023</h3><p>Most of what I did this year was transforming comments and mentions into organized and <a href="https://github.com/OpenMage/magento-lts/discussions?discussions_q=author%3AFlyingmana+created%3A2023-01-01..2024-01-01+">goal oriented discussions</a>. And while doing this trying to update our central repository for <a href="https://github.com/OpenMage/organizational">organizational informations</a> and giving more structure into our <a href="https://github.com/OpenMage/documentation/commits/main">documentation repository</a> and copying a few things from issues and chats into the documentation.</p><p>One part I like to highlight is making transparent how the roles and responsibilities are <a href="https://github.com/OpenMage/organizational/blob/main/Roles_and_Repsonsibilities.md">currently distributed</a> after there were <a href="https://github.com/OpenMage/magento-lts/discussions/2908">Requests to have turns</a> and more movement there.<br>The Reason I like to highlight this is, because all the empty ones are often still ending up with me needing to keep an eye on them.</p><p>Then recently I created an <a href="https://opencollective.com/openmage">OpenCollective </a>account after a <a href="https://github.com/OpenMage/magento-lts/discussions/3495">discussion </a>about options to enable Sponsoring for the Project. For context, the Maintainers discussed Sponsoring options already for over 3 years, but creating a legal entity involves some complexity and effort which in the end nobody was able to follow up on. With OpenCollective this is taken care of, as they legally host the money (but take a 10% fee for it), and then pay expenses on request and approval. But thats better explained on their website.<br>Anyway, there is still some work to spread the word about it, write a blog post, fill the page with a bit more content maybe, and gather more feedback on the <a href="https://github.com/OpenMage/organizational/blob/main/finance/expense_planning.md">spending plan</a>.</p><p>Another thing I still have on my list for this year is for our Website collecting all the User types, their entry points as well as their user flows to better Plan how to organize and link the content.<br>Thats especially needed to know which content might be not needed anymore on the websites, or which content is still missing.</p><p><em>Originally published at </em><a href="https://flyingmana.wordpress.com/2023/12/03/openmage-2023-a-personal-recap/"><em>http://flyingmana.wordpress.com</em></a><em> on December 3, 2023.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2c4539a2a080" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Plan for the time after Magento 1 eol — Magento-LTS]]></title>
            <link>https://medium.com/@Flyingmana/plan-for-the-time-after-magento-1-eol-magento-lts-9cbc15173121?source=rss-3a203a12b346------2</link>
            <guid isPermaLink="false">https://medium.com/p/9cbc15173121</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[openmage]]></category>
            <category><![CDATA[magento]]></category>
            <dc:creator><![CDATA[Daniel Fahlke]]></dc:creator>
            <pubDate>Sun, 20 Jan 2019 00:00:00 GMT</pubDate>
            <atom:updated>2019-01-20T20:07:13.764Z</atom:updated>
            <content:encoded><![CDATA[<h3>Plan for the time after Magento 1 eol — Magento-LTS</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/772/0*hJluG3aw_HoQRCpF.png" /></figure><p>As you probably have already heard, the eol (End of life) for “Magento 1” is set to June 2020. (as announced here: <a href="https://magento.com/blog/magento-news/supporting-magento-1-through-june-2020">https://magento.com/blog/magento-news/supporting-magento-1-through-june-2020</a> )</p><p>Already some time ago the OpenMage Project was started, to improve the bugfix situation for Magento 1, as even when a fix was already provided, they were often not integrated into official versions even years later. (this changed with Magento 2 a lot to the better)</p><p>This was only one of more than 5 forks I counted in the recent years(and there were probably even more). But it is the only one where a community formed around, and which got a wider range of users and contributors.</p><p>Lets talk some numbers, by now we are, and we have:</p><ul><li>9 + 3 Maintainer (9 with Admin Privilege)</li><li>68 Code Contributors</li><li>146 direct Forks on Github</li><li>Over 200 merged Pull Requests</li><li>273 Stars on Github</li><li>~80 daily visitors on the Github Repository</li><li>110 Follower on Twitter ( <a href="https://twitter.com/OpenMageProject">https://twitter.com/OpenMageProject</a> )</li></ul><p>We structured the Project into several phases, oriented on the official Support status of M1.<br> We are currently in Phase 2.</p><h3>Phase 1</h3><p>When there was no official EOL set.</p><p>Keep a maximum on Backwards Compatibility to the official Release, to make it possible to switch without losing any features. Also no new Features.</p><p>We Focused on Bug and Performance fixes.</p><h3>Phase 2</h3><p>An EOL was set, and is slowly approaching.</p><p>We start to accept minor Backwards Compatibility breaks. Cleaning up the code from Parts which are not recommended to use anymore as they are outdated or even harmful.</p><p>Examples are the removal of the View Logging (this thing, which writes on every pageview to the database, and is for nearly all cases better replaced by Google Analytics), and the removal of the Compiler Feature (which in Magento1 is not needed anymore, since PHP brings its own OpCache)</p><h3>Phase 3</h3><p>Archiving a proper Continuous Integration Environment to archive enough stability to beeing able for bigger internal changes (we have some performance improvements in the pipeline for eav related database queries and the Index Process in general)</p><p>Also in this phase we will set up a proper Release Schedule. The current Plan is to have a stable Major release each January, which includes new Features and possible Backwards Compatibility breaks. Maybe one bugfix release per month. We will probably establish an LTS release every 2 or 4 years depending on what the users have more interest in. First LTS release is the current Magento 1 release, which we will continue to provide with bug fixes for at least 2 LTS releases and then decide depending on where we have how many users.</p><p>That said, we will work together with existing extension vendors to make sure a later major release of OpenMage will not cause major breaks</p><h3>Phase 4</h3><p>When we reach this phase, all our processes are stable enough to approach actual Feature development.</p><p>Some of this may involve a lighter default theme, which is less javascript heavy, performs better in the google pagespeed insights and more mobile friendly.</p><p>Also an auto updater like established with WordPress may be possible, to improve the situation for the Shops which do prefer to self host and try to keep the maintenance cost low.</p><h3>Another big Point to keep in Mind is Security.</h3><p>While we have through the community contact to some of the security researchers, this only helps to fix Issues, which got already found. We will also keep contact to hosting companies, which are good in tracking security issues which are already used in the wild.</p><p>But the best way to find security issues has proven to be bug bounties. As this requires a certain amount of money flow, the OpenMage Project will not be able to provide this part.</p><p>Luckily there are some people who took this part over and build a company around this security Topic. You can find and follow them at <a href="https://mage-one.com/">https://mage-one.com/</a></p><h3>Some may wonder, why does the OpenMage Project try to compete with Magento.</h3><p>The missed point here is, that Magento 2 did up its game by several levels, and with doing this, also their target audience. Magento 1 is able to perform quite well, and also the development speed is better than with Magento 2. But it does not scale well. Magento 2 is designed for way bigger Merchants and Projects, and to scale even further to match future needs which will come.</p><p>Therefore the overlap in potential target audience got quite small.</p><p>Magento2 is now suitable for big projects, which could never run on Magento 1, or only with very big adjustments. Therefore Magento 2 is no longer suitable for many small merchants or for self hosting. With Magento 1 a merchant was able to install it on a webspace without needing a developer. Magento 2 is even for a single developer sometimes hard to install properly.</p><p>OpenMage does not compete with Magento 2.</p><p>OpenMage is competing with solutions like Shopware, Sylius and Shopify.</p><p>OpenMage is for Companies, which for diverse reasons would not switch to Magento 2 anyway, but would consider to switch to one of the other Platforms. For them, OpenMage is the more cost efficient solution, as it only leads to the price of an update, not a replatforming.</p><p><em>Originally published at </em><a href="https://openmage.github.io/2019/01/20/after-m1-eol.html"><em>openmage.github.io</em></a><em> on January 20, 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9cbc15173121" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[recap 2018–06 — What happened in the OpenMage Project]]></title>
            <link>https://medium.com/@Flyingmana/recap-2018-06-what-happened-in-the-openmage-project-a206d0579667?source=rss-3a203a12b346------2</link>
            <guid isPermaLink="false">https://medium.com/p/a206d0579667</guid>
            <category><![CDATA[magento]]></category>
            <category><![CDATA[openmage]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[php]]></category>
            <dc:creator><![CDATA[Daniel Fahlke]]></dc:creator>
            <pubDate>Sat, 21 Jul 2018 08:55:53 GMT</pubDate>
            <atom:updated>2018-07-21T08:55:53.115Z</atom:updated>
            <cc:license>http://creativecommons.org/publicdomain/zero/1.0/</cc:license>
            <content:encoded><![CDATA[<p>A lot of things happened this Quarter, especially the acquisition of Magento by Adobe. For now this seems to not affect the OpenMage Project.</p><p>Let me first mention again the Discord server of the project <a href="https://discord.gg/EV8aNbU">https://discord.gg/EV8aNbU</a><br>you can usually reach me there and if you have questions, suggestions, or you want to push a change request, there is a good place. (and Discord is made by and for Gamers, so the client on PC/Phone is quite resource efficient, as Gamers are a lot more picky there then developers)</p><p>Now to the Changes:</p><p>Sync from upstream version Magento 1.9.3.9</p><p>Added srcset support (wysiwyg editor)<br>* <a href="https://github.com/OpenMage/magento-lts/pull/481">https://github.com/OpenMage/magento-lts/pull/481</a></p><p>Remove empty JS file<br>* <a href="https://github.com/OpenMage/magento-lts/pull/461">https://github.com/OpenMage/magento-lts/pull/461</a><br>* this change removes a condition which leads the frontend to load an empty JS file</p><p>Add translation to note in product edition<br>* <a href="https://github.com/OpenMage/magento-lts/pull/490">https://github.com/OpenMage/magento-lts/pull/490</a></p><p>And here we are, only 4 merged changes in around 3 months. The Problem is not so much the missing of contributions, but we currently have nearly noone who is reviewing and testing changes. And the changes are not trivial enough to be safe by just looking at the change them self.</p><p>One of the main tasks in the next quarter is to make sure, the project is completely compatible with PHP 7.2</p><p>You like the regular writeups? support me via Patreon <a href="https://www.patreon.com/Flyingmana">https://www.patreon.com/Flyingmana</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a206d0579667" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[recap 2018–03 — What happened in the OpenMage Project]]></title>
            <link>https://medium.com/@Flyingmana/recap-2018-03-what-happened-in-the-openmage-project-c9e78901e559?source=rss-3a203a12b346------2</link>
            <guid isPermaLink="false">https://medium.com/p/c9e78901e559</guid>
            <category><![CDATA[magento]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[openmage]]></category>
            <dc:creator><![CDATA[Daniel Fahlke]]></dc:creator>
            <pubDate>Sat, 28 Apr 2018 20:28:23 GMT</pubDate>
            <atom:updated>2018-04-28T20:28:23.388Z</atom:updated>
            <cc:license>https://creativecommons.org/publicdomain/mark/1.0/</cc:license>
            <content:encoded><![CDATA[<p>Naming things is hard, like this Blogpost. Its actually 04, but I did not write one since 01. I wanted to name it Q1, but that would mix up with 01.<br>And as I saw, most commits were merged in 03, I now took this.</p><p>Also as I did not get so many Views on this posts yet, and also it seems I will not get much support for this via my patreon <a href="https://www.patreon.com/Flyingmana">https://www.patreon.com/Flyingmana</a><br>So I will reduce this to one Post per quarter for now.</p><p>So what did actually happen</p><p>Don’t allow quoted-string email format. <br>* <a href="https://github.com/OpenMage/magento-lts/issues/378">https://github.com/OpenMage/magento-lts/issues/378</a></p><p>Fix retrieval of payment child transactions<br>* <a href="https://github.com/OpenMage/magento-lts/pull/440">https://github.com/OpenMage/magento-lts/pull/440</a></p><p>Fix for Mage_Core_Controller_Varien_Exception::prepareRedirect<br>* <a href="https://github.com/OpenMage/magento-lts/pull/462">https://github.com/OpenMage/magento-lts/pull/462</a></p><p>Import of 1.9.3.8</p><p>Session validation failure<br>* <a href="https://github.com/OpenMage/magento-lts/issues/394">https://github.com/OpenMage/magento-lts/issues/394</a><br>* <a href="https://github.com/OpenMage/magento-lts/commit/36a0afb8937fd6c358c507b3a59b7cf119fc3e8b">https://github.com/OpenMage/magento-lts/commit/36a0afb8937fd6c358c507b3a59b7cf119fc3e8b</a></p><p>PHP 7.2 Fixes (method signature)<br>* <a href="https://github.com/OpenMage/magento-lts/pull/450">https://github.com/OpenMage/magento-lts/pull/450</a></p><p>[PHP-7] fix memory leak<br>* <a href="https://github.com/OpenMage/magento-lts/pull/451">https://github.com/OpenMage/magento-lts/pull/451</a></p><p>Fix rounding bug<br>* <a href="https://github.com/OpenMage/magento-lts/commit/2952af7ec112d8c58e7f300f619cb44d499c573f">https://github.com/OpenMage/magento-lts/commit/2952af7ec112d8c58e7f300f619cb44d499c573f</a></p><p>Fix 1.8 regression: Ensure StockId is set before saving cataloginventory/stock_item<br>* <a href="https://github.com/OpenMage/magento-lts/commit/b098b2153a9f99510dbb34460ede7a2965025081">https://github.com/OpenMage/magento-lts/commit/b098b2153a9f99510dbb34460ede7a2965025081</a></p><p>Cast handling fee to float<br>* <a href="https://github.com/OpenMage/magento-lts/commit/c270fb84b501ca601cf95068a87dedf7e5c0accd">https://github.com/OpenMage/magento-lts/commit/c270fb84b501ca601cf95068a87dedf7e5c0accd</a></p><p>catalog pricerules start and end date not respected<br>* <a href="https://github.com/OpenMage/magento-lts/pull/444">https://github.com/OpenMage/magento-lts/pull/444</a><br>* <a href="https://github.com/OpenMage/magento-lts/issues/443">https://github.com/OpenMage/magento-lts/issues/443</a></p><p>Fixes undefined classes<br>* <a href="https://github.com/OpenMage/magento-lts/pull/418">https://github.com/OpenMage/magento-lts/pull/418</a></p><p>Use describeTable and then use prepareColumnValue to actually prepare the value being used in the where section of select statements<br>* <a href="https://github.com/OpenMage/magento-lts/pull/383">https://github.com/OpenMage/magento-lts/pull/383</a></p><p>Fix admin create order shipping_as_billing is 0<br>* <a href="https://github.com/OpenMage/magento-lts/pull/306">https://github.com/OpenMage/magento-lts/pull/306</a></p><p>Make gender translatable<br>* <a href="https://github.com/OpenMage/magento-lts/pull/243">https://github.com/OpenMage/magento-lts/pull/243</a></p><p>SUPEE 7136 addition - change seassion cookie to http-only<br>* <a href="https://github.com/OpenMage/magento-lts/pull/236">https://github.com/OpenMage/magento-lts/pull/236</a></p><p>Fix possible option id/label collisions in getOptionId()<br>* <a href="https://github.com/OpenMage/magento-lts/pull/109">https://github.com/OpenMage/magento-lts/pull/109</a></p><p>Add option reindexallrequired<br>* <a href="https://github.com/OpenMage/magento-lts/pull/184">https://github.com/OpenMage/magento-lts/pull/184</a><br>* <a href="https://magento.stackexchange.com/questions/3028/permanent-solution-for-the-common-indexing-issue">https://magento.stackexchange.com/questions/3028/permanent-solution-for-the-common-indexing-issue</a></p><p>add Sitemap dispatch event for add custom data<br>* <a href="https://github.com/OpenMage/magento-lts/pull/248">https://github.com/OpenMage/magento-lts/pull/248</a><br>* <a href="https://github.com/OpenMage/magento-lts/pull/468">https://github.com/OpenMage/magento-lts/pull/468</a> (renaming it)</p><p>Fixes issue with wysiwyg editor re-creating thumbnails<br>* <a href="https://github.com/OpenMage/magento-lts/pull/261">https://github.com/OpenMage/magento-lts/pull/261</a></p><p>Typo in Product.php<br>* <a href="https://github.com/OpenMage/magento-lts/commit/4bb045f9657d02f3d891abe818b7e9a26838fa65">https://github.com/OpenMage/magento-lts/commit/4bb045f9657d02f3d891abe818b7e9a26838fa65</a></p><p>Missing hidden tax (will cause paypal to generate fraud error)<br>* <a href="https://github.com/OpenMage/magento-lts/commit/1e29f23a51a9da1f44224b484f8b108f79b0cd9f">https://github.com/OpenMage/magento-lts/commit/1e29f23a51a9da1f44224b484f8b108f79b0cd9f</a></p><p>Fix date selection when current date is disabled<a href="https://github.com/OpenMage/magento-lts/pull/327"><br>* https://github.com/OpenMage/magento-lts/pull/327</a></p><p>Use FONT_HELVETICA intsead of LinLibertineFont in PDF<br>* <a href="https://github.com/OpenMage/magento-lts/pull/425">https://github.com/OpenMage/magento-lts/pull/425</a></p><p>send PayPal new account mail in correct language<br>* <a href="https://github.com/OpenMage/magento-lts/pull/463">https://github.com/OpenMage/magento-lts/pull/463</a></p><p>So we got quite a bit of Patches merged in this timeframe. Some very nice ones I have to say.<br>It can be even more, if we get a few more volunteers to do Reviews.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c9e78901e559" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is #TakeTheExit]]></title>
            <link>https://medium.com/@Flyingmana/what-is-taketheexit-ecc8e95034eb?source=rss-3a203a12b346------2</link>
            <guid isPermaLink="false">https://medium.com/p/ecc8e95034eb</guid>
            <category><![CDATA[dontquitbutunionize]]></category>
            <category><![CDATA[taketheexit]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Daniel Fahlke]]></dc:creator>
            <pubDate>Wed, 21 Mar 2018 00:20:47 GMT</pubDate>
            <atom:updated>2018-03-23T08:12:58.397Z</atom:updated>
            <content:encoded><![CDATA[<p>I heard yesterday about #TakeTheExit the first time, or better said did read their Guerrilla marketing in form of spraying their advertising pitch on the ground in front of a comic book shop. Most notable the “CTRL-Q” part.<br>My first guess was, this is just some advertising for one of the Exit Game places which we have in Berlin.<br>Today morning I saw this advertising also directly aligned to a Bar entrance, and also of a more expensive Restaurant. So my next guess was, some anti capitalist movement. W̶h̶i̶c̶h̶ ̶w̶o̶u̶l̶d̶ ̶b̶e̶ ̶p̶r̶e̶t̶t̶y̶ ̶i̶r̶o̶n̶i̶c̶ ̶a̶s̶ ̶t̶h̶e̶y̶ ̶a̶r̶e̶ ̶o̶b̶v̶i̶o̶u̶s̶l̶y̶ ̶a̶l̶l̶ ̶A̶p̶p̶l̶e̶ ̶M̶a̶c̶B̶o̶o̶k̶ ̶u̶s̶e̶r̶s̶.̶ ̶A̶l̶l̶ ̶o̶t̶h̶e̶r̶s̶ ̶o̶n̶l̶y̶ ̶g̶e̶t̶ ̶a̶n̶ ̶“̶@̶”̶ ̶w̶h̶e̶n̶ ̶t̶h̶e̶y̶ ̶u̶s̶e̶ ̶t̶h̶i̶s̶ ̶k̶e̶y̶s̶.(UPDATE: I was made aware, “CTRL-Q” is App specific and used by for example Firefox, its not OS specific as I first believed. Sorry for that mix up)</p><p>So what is it really about. After looking trough their website, they want to advocate people to leave their bad workplaces.<br>What they describe is also known as (toxic) startup culture, but they prefer for yet unknown reasons the term “ventures” over “startups”.<br>On the other side is most of what they describe with their Pictures and Videos also a problem which can be found in older and bigger companies.</p><p>Lets Review their Webpage.<br>First, the typical Newsletter Subscribe, and additional a Countdown targeting the 9th of April (a monday)<br>Then a gallery of shortfilms showing how bad the live (mostly as a Developer) is inside such Companies. (I will comment them later)<br>Then a list of tweets which should show how unsatisfied people are. (I will comment on one example in a bit)<br>Next a funny online form to create a “dismissal notice” in 4 flavors.<br>Then the for me most important part (because it shows the money driven motivation behind this): a merchandising shop!!!<br>Then following a few more numbers.</p><p>While the Topic they speak about is a very important one, I dislike a lot the methods they use and Iam questioning their motives.<br>Also Iam questioning their competence, as they seem to have not a real good insight into this topic at all.<br>And most importantly, they want to trigger people to leave a company, but they dont show the slightest sign of wanting to actually help them.</p><p>The Campaign and the material show signs for a planned marketing and hyping strategy. But their marketing staff is focusing a lot on stereotypes and ignoring a lot of details.<br>First of all, they are typical MacUsers (MacUsers are fine, but dont expect everyone to be one or knowing your internal keyboard shortcuts). They are using Guerrilla marketing techniques but in parallel also start with billboard advertisements.<br>Their whole marketing focus Developers, so only the good paid and most demanded part of this companies. Still they fail on most basic parts. For example they seem to never have been a day in a real Co-Working space. They display it in such a negatively nonsense way, its just absurd.<br>Then there is this one Tweet (the reference from earlier is referring to this) where they actually tell someone to quit, because he is using his free time to work on open source. Like if they had no idea that people could and want to do this independent from their job.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/603/1*c5xQI1Wbfh0UL-MZbq4y7A.png" /></figure><p>They even highlight it on their website.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XpDFtv4mkKNuQ8wmvTXdRg.png" /></figure><p>They make it all sounding fun and cool to quit a job, but dont mention once the possible problems people are facing, which could prevent them mentally or financial to just quit.<br>A very good article about this out of my bookmarks: <a href="https://blog.valerieaurora.org/2018/01/17/getting-free-of-toxic-tech-culture/">https://blog.valerieaurora.org/2018/01/17/getting-free-of-toxic-tech-culture/</a><br><strong>Really! read it, completely, I cant describe it as good as it is there!!!!</strong></p><p>So in case you really want to quit, but dont feel ready yet: connect with people who have access to new Jobs. <br>This could be Recruiter (they may have a bad reputation, but there are enough out there, who really want to find a job you also feel good with, and they have access to a bigger list of companies)<br>This could be friends working in other Companies, they often hear about job offers and probably would also like to find a job you can feel good with.<br>Connect with more prominent people in your field of competence. I see it often (on twitter) that they get so many requests, that they are happy to connect people for new jobs.</p><p>But Quitting only helps this developers who can easy find a new job, there are whole departments which have it similar bad, but dont have this option.<br>The traditional, and also proven, way of improving work conditions permanently and in a big manner is to unionize. It may not be the easiest way, but it helps also the weaker departments and jobs, where there is not such a high demand as for Developers. <strong>#DontQuitButUnionize</strong></p><p>There may come a followup Post, which I will link here then.<br>Till then, <strong>let us take over</strong> the Hashtag <strong>#taketheexit</strong> and help each other.<br>Offer people help to find a Job with better work conditions. Offer them mentoring, training, support, advice, whatever you can which may help them to find a Job they can be happy with.<br>Lets make use of the money they put into advertising for this hashtag and actually offer help over it.</p><p>Other usefull more or less related Posts I found in my bookmarks:<br>* <a href="https://blog.valerieaurora.org/2018/01/17/getting-free-of-toxic-tech-culture/">https://blog.valerieaurora.org/2018/01/17/getting-free-of-toxic-tech-culture/</a> (yes, its the same from earlier, its good, read it)<br>* <a href="https://jell.com/blog/employee-burnout/">https://jell.com/blog/employee-burnout/</a><br>* <a href="https://jell.com/blog/poor-work-performance/">https://jell.com/blog/poor-work-performance/</a><br>* <a href="https://code.likeagirl.io/im-an-introverted-woman-in-tech-and-i-want-the-industry-to-accommodate-introverted-women-2f6a50856d08">https://code.likeagirl.io/im-an-introverted-woman-in-tech-and-i-want-the-industry-to-accommodate-introverted-women-2f6a50856d08</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ecc8e95034eb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[recap 2018–01 — What happened in the OpenMage Project]]></title>
            <link>https://medium.com/@Flyingmana/recap-2018-01-what-happened-in-the-openmage-project-a2420fba9ac?source=rss-3a203a12b346------2</link>
            <guid isPermaLink="false">https://medium.com/p/a2420fba9ac</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[openmage]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[magento]]></category>
            <dc:creator><![CDATA[Daniel Fahlke]]></dc:creator>
            <pubDate>Wed, 07 Feb 2018 00:00:00 GMT</pubDate>
            <atom:updated>2018-02-07T16:57:49.895Z</atom:updated>
            <cc:license>http://creativecommons.org/publicdomain/zero/1.0/</cc:license>
            <content:encoded><![CDATA[<p>And the first Month of the year is already over, lets see what happened</p><p>First: the OpenMage project did start a public Discord Server as communication channel You can join via <a href="https://discord.gg/EV8aNbU">https://discord.gg/EV8aNbU</a> In case you prefer a different one, suggest one at <a href="https://github.com/OpenMage/organizational/issues/2">https://github.com/OpenMage/organizational/issues/2</a></p><p>Second: Some but not all of you know, that you can support my Open Source Work via Patreon <a href="https://www.patreon.com/Flyingmana">https://www.patreon.com/Flyingmana</a> And you can not only follow me there, you can also influence what I should work on next.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/753/1*Xzk7yjhji1zsKaUoONrERw.png" /></figure><p>So back to what did change in January</p><p>Some code style cleanups</p><p>key/value Variables of a loop did reuse names from outside</p><p>fix: admin group_prices: disable is_percent input</p><p>Fix “Store View” field value empty when reloading form after failed save</p><ul><li><a href="https://github.com/OpenMage/magento-lts/pull/415">https://github.com/OpenMage/magento-lts/pull/415</a></li></ul><p>Session validation failure: Store session validator data once and validate only once.</p><p>Removed deprecated method _setAttribteValue()</p><ul><li><a href="https://github.com/OpenMage/magento-lts/pull/419">https://github.com/OpenMage/magento-lts/pull/419</a></li></ul><p>Missing break statement in Mage_Eav_Model_Attribute_Data_Multiselect-&gt;outputValue()</p><ul><li><a href="https://github.com/OpenMage/magento-lts/pull/398">https://github.com/OpenMage/magento-lts/pull/398</a></li></ul><p>Fixed php error in file, usage of undefined variable</p><p>gTLD list for Zend Hostname Validator — update tld list from iana</p><ul><li><a href="https://github.com/OpenMage/magento-lts/pull/387">https://github.com/OpenMage/magento-lts/pull/387</a></li><li>3 years of TLDs</li></ul><p>Fixed/added doc blocks @deprecated annotations</p><ul><li><a href="https://github.com/OpenMage/magento-lts/pull/441">https://github.com/OpenMage/magento-lts/pull/441</a></li></ul><p>Fix undefined var in Mage_Core_Model_Url_Rewrite::removeTag()</p><ul><li><a href="https://github.com/OpenMage/magento-lts/pull/436">https://github.com/OpenMage/magento-lts/pull/436</a></li></ul><p>A big thank you to @sreichel for working and merging so many Pull Requests, and to @LeeSaferite for reviewing a lot of them. And also to the others. Does someone have tooling ready to create statistics for this?</p><p>If you like this posts, give me some claps (thats how medium calls the like functionality, you can even give more then one. I suggest one clap for every mentioned patch you liked).<br>Also, it would be great if you additionally <a href="https://www.patreon.com/Flyingmana">support me</a> via Patreon, so I can put more Time into the OpenMage project and surrounding tasks.</p><p><em>Originally published at </em><a href="https://communitycommerceframework.github.io/2018/02/07/recap.html"><em>communitycommerceframework.github.io</em></a><em> on February 7, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a2420fba9ac" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[recap 2017–11 (and 12) — What happened in the OpenMage Project]]></title>
            <link>https://medium.com/@Flyingmana/recap-2017-11-and-12-what-happened-in-the-openmage-project-ade6cf68ec39?source=rss-3a203a12b346------2</link>
            <guid isPermaLink="false">https://medium.com/p/ade6cf68ec39</guid>
            <category><![CDATA[openmage]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[php]]></category>
            <category><![CDATA[magento]]></category>
            <dc:creator><![CDATA[Daniel Fahlke]]></dc:creator>
            <pubDate>Sun, 21 Jan 2018 16:43:30 GMT</pubDate>
            <atom:updated>2018-01-21T16:47:09.789Z</atom:updated>
            <cc:license>https://creativecommons.org/publicdomain/mark/1.0/</cc:license>
            <content:encoded><![CDATA[<p>This time a bit late, as I was quite busy with my job.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/757/1*LJpOqXn0B2YGwSvER1D-uA.png" /></figure><h3>Some of the patches which were merged</h3><p>Fix slow url_rewrite query on MySQL 5.7 <br>* <a href="https://github.com/OpenMage/magento-lts/pull/303">OpenMage-PR #303</a><br>* <a href="https://github.com/OpenMage/magento-lts/issues/295">OpenMage-Issue #295</a></p><p>Make Mage registry related methods consistent<br>* <a href="https://github.com/OpenMage/magento-lts/pull/369">OpenMage-PR #369</a></p><p>Added missing functionality for <br>Mage_Catalog_Helper_Product-&gt;getThumbnailUrl <br>* <a href="https://github.com/OpenMage/magento-lts/pull/160">OpenMage-PR #160</a></p><p>fix used ssl version in downloader<br>* <a href="https://github.com/OpenMage/magento-lts/pull/302">OpenMage-PR #302</a></p><p>creditmemo bundle inventory calculation error <br>* <a href="https://github.com/OpenMage/magento-lts/pull/275">OpenMage-PR #275</a></p><p>Set sane default session_cookie_lifetime (3 hours) <br>was previously unset and therefore unlimited(?)<br>* <a href="https://github.com/OpenMage/magento-lts/pull/300">OpenMage-PR #300</a></p><p>set email as sent only if customer notified <br>* <a href="https://github.com/OpenMage/magento-lts/pull/297">OpenMage-PR #297</a><br>* related to: <a href="https://github.com/OpenMage/magento-lts/issues/267">OpenMage-Issue #267</a></p><p>Add possibility to remove link from customer navigation via layout.xml<br>* <a href="https://github.com/OpenMage/magento-lts/pull/321">OpenMage-PR #321</a></p><p>cloudflare reset current path in file manager<br>(adds an additional check for isPost)<br>* <a href="https://github.com/OpenMage/magento-lts/pull/331">OpenMage-PR #331</a></p><p>Infinite loop for certain cart price rules<br>initially only provided for EE(as SUPEE-4814), but problem was identical to a CE one<br>* <a href="https://github.com/OpenMage/magento-lts/pull/262">OpenMage-PR #262</a></p><p>Fixed removeAccents method for german umlauts<br>* <a href="https://github.com/OpenMage/magento-lts/pull/345">OpenMage-PR #345</a></p><p>Fixes system config dependencies for multiselect fields<br>* <a href="https://github.com/OpenMage/magento-lts/pull/317">OpenMage-PR #317</a><br>* OpenMage-PR #371 (Added missing comma)</p><p>fix localisation whitelist for swiss french<br>* <a href="https://github.com/OpenMage/magento-lts/pull/266">OpenMage-PR #266</a></p><p>Patch — SUPEE-10415 / 1.9.3.7<br>* <a href="https://github.com/OpenMage/magento-lts/pull/393">OpenMage-PR #393</a></p><p>Codestyle and comment fixes<br>* OpenMage-PR #404<br>* OpenMage-PR #391<br>* OpenMage-PR #402<br>* OpenMage-PR #346<br>* OpenMage-PR #399<br>* OpenMage-PR #395<br>* OpenMage-PR #397<br>* OpenMage-PR #395</p><p>Add quotes to numeric incrementIds<br>* <a href="https://github.com/OpenMage/magento-lts/pull/388">OpenMage-PR #388</a></p><p>allow to change (customer) suffix- and prefix options per storeview<br>* <a href="https://github.com/OpenMage/magento-lts/pull/400">OpenMage-PR #400</a></p><p>Add Progressive option for jpeg images<br>* <a href="https://github.com/OpenMage/magento-lts/pull/197">OpenMage-PR #197</a></p><p>Escape strings in grids by default (already happened in January)<br>* OpenMage-Issue #375<br>* OpenMage-PR #376<br>* OpenMage-PR #377</p><h3>Organizational</h3><p>in <a href="https://github.com/OpenMage/magento-lts/issues/416">OpenMage-Issue #416</a> a discussion started how to cleanup the project by removing several unused parts and some other steps to take in the next future.</p><p>To speak for myself, after changing the Name of the OpenMage project did not get much support, I try out an alternative plan and started a new fork which is based on the OpenMage-LTS.<br>It is available at <a href="https://github.com/CommunityCommerceFramework">GitHub</a> and will hopefully establish under the Brand “CommunityCommerceFramework”.<br>I will regularly pull the changes of the OpenMage-LTS. Additionally the project will be a bit more aggressive with BC breaks by removing outdated parts.<br>But the primary focus will be publicity and providing the whole surrounding with a proper website, easy to install Demos, an existing CI pipeline and also a simplified docker environment.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ade6cf68ec39" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Magento Community Adventcalendar]]></title>
            <link>https://medium.com/@Flyingmana/the-magento-community-adventcalendar-3246e4dabd67?source=rss-3a203a12b346------2</link>
            <guid isPermaLink="false">https://medium.com/p/3246e4dabd67</guid>
            <category><![CDATA[holidays]]></category>
            <category><![CDATA[christmas]]></category>
            <category><![CDATA[magento]]></category>
            <category><![CDATA[community]]></category>
            <dc:creator><![CDATA[Daniel Fahlke]]></dc:creator>
            <pubDate>Sat, 09 Dec 2017 10:54:09 GMT</pubDate>
            <atom:updated>2017-12-09T10:54:09.573Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<p>Its this time of the year again, and you wonder how the year could be near the end so suddenly.<br>In the Magento Community there is a tradition for a notable number of years now, that there will be a Blog which collects guest Posts for every Day from the 1th to 23th of December.</p><p>This year, the Host is the Blog of the <a href="https://firegento.com/">Firegento e.V.</a>, which is one of the community organizations which have been build inside the Magento Community.</p><ul><li><a href="https://firegento.com/blog/2017/12/01/to-earn-more-money-we-need-faster-shops-lizards-and-pumpkins/">The opening Post for 2017</a></li><li>My small contribution to it: <br><a href="https://firegento.com/blog/2017/12/08/what-to-do-with-your-new-created-opensource-module-after-a-hackathon/">What to do with your new created OpenSource module after a hackathon</a>.</li></ul><p>But the Magento Community is not the only one, which is using the Christmas season to ask for contributions. A more general Developer community comes each year together at <a href="https://24pullrequests.com/">https://24pullrequests.com/</a> to provide big and small contributions to several Github Repositories.</p><p>What other holiday seasons(independent where it originated from) would you like to see referenced in such Community efforts?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3246e4dabd67" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to decide which software/library to use]]></title>
            <link>https://medium.com/@Flyingmana/how-to-decide-which-software-library-to-use-6710e7ededf6?source=rss-3a203a12b346------2</link>
            <guid isPermaLink="false">https://medium.com/p/6710e7ededf6</guid>
            <category><![CDATA[php]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Daniel Fahlke]]></dc:creator>
            <pubDate>Sat, 18 Nov 2017 15:30:23 GMT</pubDate>
            <atom:updated>2017-11-18T15:30:23.230Z</atom:updated>
            <cc:license>http://creativecommons.org/publicdomain/zero/1.0/</cc:license>
            <content:encoded><![CDATA[<p>When I started with my programming career, PHP was already quite established and mature. Version 5.2 was just released. It was stable, had no major memory leaks, had all the basic OOP features, supported process forking and with php-gtk you could even write desktop applications.</p><p>I learned, when you know a programming language to a certain degree, you can do everything with it. And in most cases its even doing well enough.<br>And since I realized this, I stopped focusing on what a language or tool is good in, but instead looked and asked for what it is bad in.<br>Because, even if its not the best tool for something, it needs maybe just some workarounds or dirty hacks and so on, and is producing good enough results.</p><p>The problematic part are the pain points, because they are, what is in the end costing most of the time, and therefore money.<br>The best tool does not automatically mean, it has the least pain points. Actually I experienced quite the opposite for many things.</p><p>Example MongoDB:<br>For a longer time, it had the image of the best Database out there. More flexible, better performance and easier multi machine setups then any SQL database.<br>Let me first say, its really a great tool and scales quite well. And mostly, its holding its promised features.<br>What they dont tell you about is the non existing search functionality, and that everything filter and sort related is strongly tied to the indices you need to configure yourself. The pain point I found for MongoDB is the increased need for maintenance work and depending on the requirements, to have a second tool for searching.<br>Knowing this pain points helps a lot more then the feature list for doing the decision for or against it. (and maybe would have prevented some smaller projects of deciding for it)</p><p>So next time you need to decide between two or more software projects, dont only look at the features, but also the pain points and downsides. They may have the bigger impact on your project.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6710e7ededf6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What happened in October in the OpenMage Project | Flyingmana on Patreon]]></title>
            <link>https://medium.com/@Flyingmana/what-happened-in-october-in-the-openmage-project-flyingmana-on-patreon-fb9b4375d1b6?source=rss-3a203a12b346------2</link>
            <guid isPermaLink="false">https://medium.com/p/fb9b4375d1b6</guid>
            <category><![CDATA[magento]]></category>
            <category><![CDATA[openmage]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[patreon]]></category>
            <dc:creator><![CDATA[Daniel Fahlke]]></dc:creator>
            <pubDate>Tue, 31 Oct 2017 12:39:24 GMT</pubDate>
            <atom:updated>2017-10-31T12:39:24.125Z</atom:updated>
            <cc:license>http://creativecommons.org/publicdomain/zero/1.0/</cc:license>
            <content:encoded><![CDATA[<p>My work here this Month was more in the background.</p><h3>Naming</h3><p>There is still the open Issue with the Naming ( <a href="https://github.com/OpenMage/organizational/issues/1">https://github.com/OpenMage/organizational/issues/1</a> ) which partially continued in the background. If you know a Lawyer which can offer a qualified opinion (for free?) please get in touch with me.<br>You can see in my comments on this Github Issue, I am a big supporter to get a new name, but to keep the community together and not lose people over hasty decisions, it is important to take the other side seriously.Sadly the other side did not show initiative yet to show keeping the Name is free of risk, so I currently need to also fill out their side of the discussion.Still, I expect we will take a new Name in the end, which as mentioned in the Github Issue, does not contain something with mage or -gento in its name. I linked the Case Facebook vs Teachbook as example why this is needed.</p><p>So, if you have proper suggestions, feel free to help us with suggestions. To google the name before would be helpful, as we should not collide with another brand.(you know, SEO and stuff)</p><h3>Versioning and Roadmap</h3><p>Just today I wrote up my idea for the release planning and versioning <a href="https://github.com/OpenMage/organizational/issues/9">https://github.com/OpenMage/organizational/issues/9</a> and hope to get some feedback soon. Do you think a year based major version number like approach is a good idea? Being more inflationary with version numbers did seem to have a positive effect for Browser Vendors.</p><h3>performance testing</h3><p>In the long run we will need a way to make sure the performance gets better instead of worse. And also a way to actual test that Changes like <a href="https://github.com/OpenMage/magento-lts/pull/347">https://github.com/OpenMage/magento-lts/pull/347</a> have a positive effect. For this one I know it has, I saw the differences in production systems. But having a general system to measure this is better for the long run.<br>And thats what Iam currently working on.</p><p>My approach is to have a simple docker setup to create a reproducible and clear defined environment, and also have the benchmark tools as part of a docker container, to make them easier to use for others.I also thought about having some additional monitoring which tracks memory usage during every request. But that may delay the readiness to much. So I may postpone this part to a later iteration.</p><p>Maybe iam ready with this end of November, as iam lacking some experience with docker and need still to learn a lot there.</p><p>But this is only what I was working on, should I in the future also publish a summary of all the issues and PRs which happened over a month?</p><p><em>Originally published at </em><a href="https://www.patreon.com/posts/15136381"><em>www.patreon.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb9b4375d1b6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>