12 Matching Annotations
  1. May 2020
    1. I wish you would have contributed back to this project instead of forking or at picked a different name
    2. Forking is the only way to contribute to the project, since I don't have commit access... That's why I posted here, to contribute. I picked the name "Page Translator Revised" since AMO has policies about duplicate add-on names, if you have a better name I'd be happy to use it.
  2. Apr 2020
  3. Mar 2020
    1. Piwik PRO uses a fork of Piwik open-source software (similarly to RedHat using the Linux kernel and multiple open source tools), however we currently seamlessly integrate a part of open source Piwik in our proprietary platform via APIs. Moreover, Piwik PRO controls all the changes to the code used in its Analytics Suite and since 2016 has been maintaining and developing its own fork of “Piwik” alongside the proprietary modules of Analytics Suite.
  4. Nov 2019
    1. the main reason we built a new multiprocess architecture is that Chromium's multiprocess support was never contributed to the WebKit project. It has always lived in the separate Chromium tree, making it pretty hard to use for non-Chrome purposes.Before we wrote a single line of what would become WebKit2 we directly asked Google folks if they would be willing to contribute their multiprocess support back to WebKit, so that we could build on it. They said no.
  5. Aug 2019
    1. With now more than 3000 modules, there are huge gaps in the quality of things you find in the npm registry. But more often than not, it's easy to find a module that is really close to what you need, except if it wasn't for that one bug or missing feature.
    1. The problem occurs when the maintainer of the package is too busy to merge my PR, so I'm just stuck with my fork.
    2. I often find myself in the situation where an npm package does exactly what I need, but has a bug or missing feature that blocks me from using it directly. So I fork it and make a pull request with what I need.