21 Matching Annotations
  1. Mar 2021
    1. Microlibraries are easier to understand, develop and test. They make it easier for new people to get involved and contribute. They reduce the distinction between a “core module” and a “plugin”, and increase the pace of development in D3 features.
    1. I'd be happy to open a PR for this, but I'm not sure exactly what code needs to change. default_source_map.rb and source_map_utils.rb seem like candidates, but I'd appreciate guidance
  2. Feb 2021
    1. note that TRB source code modifications are not proprietary

      In other words, you can build on this software in your proprietary software but can't change the Trailblazer source unless you're willing to contribute it back.

      loophole: I wonder if this will actually just push people to move their code -- which at the core is/would be a direction modification to the source code - out to a separate module. That's so easy to do with Ruby, so this restriction hardly seems like it would have any effect on encouraging contributions.

  3. Dec 2020
    1. Everything Lives in GitWith a Jamstack project, anyone should be able to do a git clone, install any needed dependencies with a standard procedure (like npm install), and be ready to run the full project locally. No databases to clone, no complex installs. This reduces contributor friction, and also simplifies staging and testing workflows.
  4. Oct 2020
  5. Sep 2020
  6. Jul 2020
  7. Jun 2020
  8. May 2020
  9. Apr 2020
    1. Our hope is that once a formal specification for these extensions is settled, this patchset can be used as a base to upstream the changes in the original project.

      What does "can be used as a base to upstream the changes in the original project" mean here?

  10. Mar 2020
  11. Feb 2020
    1. There are two things that you can help me out: time and motivation. This is the place where you can find out how to do that.
  12. 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.
  13. Sep 2019
    1. Feel free to send small pull requests. Please discuss new features or big changes in a GitHub issue first.


    1. When opening new issues, provide the setup of your form in a CodeSandbox. These issues, and the ones which provides also PR with failing tests will get higher priority.
  14. Aug 2019
  15. Sep 2018