27 Matching Annotations
  1. May 2023
    1. You have come for your Mistress Darling, but that beautiful bird is no longer sitting in her nest, nor is she singing any more. The cat got her, and will scratch your eyes out as well.

      4 -- Rhetorical Strategies

      Frequently, tales of Rapunzel include typical characters or archetypes such as the distressed damsel, the wicked captor, and the gallant savior striving for freedom. These familiar archetypes add to the genre's essence and lay a basis for investigating dynamics between characters.

    2. Rapunzel recognized him, and crying

      4 -- Rhetorical Strategies

      Rapunzel as a type of literature often incorporates opposing elements to generate a sense of unease and emphasize important messages. This is shown through the juxtaposition of the cramped tower and the vastness of the world outside, the purity of Rapunzel in contrast with the wickedness of her captor, or even in how her vulnerability transforms into resilience. Vulnerability becoming resilience is perfectly portrayed in this portion here and in many other retellings where Rapunzel's tears are used to heal the prince.

    3. Once upon a time

      4 -- Rhetorical Structure

      The storytelling framework for Rapunzel narratives is often predictable, with a standard narrative structure comprising of an initial period of imprisonment followed by the appearance of either a prince or another character seeking liberation. The climax comes with overcoming obstacles to achieve ultimate victory. This model offers an overarching design for the genre and its characteristic rhetorical effects.

    4. locked her in a tower

      4 -- Analyze Rhetoric

      An indispensable aspect of fairy tale storytelling is the conspicuous tower in which Rapunzel is held captive. Its iconography and allegorical significance- evoking separation, desire, and an unwavering aspiration towards autonomy-remains specific to the story and genre of Rapunzel.

  2. Oct 2022
  3. Jul 2022
    1. Thanks for your making your first contribution to Cucumber, and welcome to the Cucumber committers team! You can now push directly to this repo and all other repos under the cucumber organization! In return for this generous offer we hope you will: Continue to use branches and pull requests. When someone on the core team approves a pull request (yours or someone else's), you're welcome to merge it yourself. Commit to setting a good example by following and upholding our code of conduct in your interactions with other collaborators and users. Join the community Slack channel to meet the rest of the team and make yourself at home. Don't feel obliged to help, just do what you can if you have the time and the energy. Ask if you need anything. We're looking for feedback about how to make the project more welcoming, so please tell us!
  4. 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
  5. 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.

  6. 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.
  7. Oct 2020
  8. Sep 2020
  9. Jul 2020
  10. Jun 2020
  11. May 2020
  12. 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?

  13. Mar 2020
  14. 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.
  15. 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.
  16. 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.
  17. Aug 2019
  18. Sep 2018