31 Matching Annotations
  1. Jul 2021
    1. Do you prefer a different email validation gem? If so, open an issue with a brief explanation of how it differs from this gem. I'll add a link to it in this README.
  2. Jun 2021
  3. Apr 2021
    1. Terry is concerned by those commonly cited statistics revealing how little time museumgoers spend looking at art, but more upsetting is that most people don’t feel welcome in museums at all. “They’re looking for zero seconds,” he says.

      Being welcoming and inviting can be an important thing. If you're not, then your material is not even considered.

  4. Mar 2021
    1. jake2h@chrisaldrich that spreadsheet party is so brilliant! I would love to attend events in all kinds of mediums, tools, and games. @nastroika, do you think your cohort could automate a cyberparty together as a group project?

      @jake, your comment also reminds me of the atmosphere created by the game Candy Land which was designed for a particular setting which we often forget about today. There's an Atlantic article about it which helps to underline the idea of designing for particular contexts to make people feel welcomed and empowered: https://www.theatlantic.com/technology/archive/2019/07/how-polio-inspired-the-creation-of-candy-land/594424/

    1. Summary of moving from in person to online events a year ago.

      I like her admonition to consider welcoming new people to a community in an online only space.

      Try to avoid in-jokes. Make space for more phatic communication. Make considerations for parents, particularly around mealtimes and bedtimes.

  5. Feb 2021
    1. No contribution is too small Even if you find a single-character typo, we're happy to take the change! Although the codebase can feel daunting for beginners, we and other contributors are happy to help you along.
  6. Jan 2021
    1. 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.
    2. Contributions are welcome, like always. I love contributions and seeing other people getting value from this project. Keep doing it!
  7. Nov 2020
    1. If you have further thoughts here, please participate in the discussion on the issue tracker: #256.
    1. I'd like to go with an RFC-based governance model (similar to Rust, Ember or Swift) that looks something like this: new features go through a public RFC that describes the motivation for the change, a detailed implementation description, a description on how to document or teach the change (for kpm, that would roughly be focused around how it affected the usual workflows), any drawbacks or alternatives, and any open questions that should be addressed before merging. the change is discussed until all of the relevant arguments have been debated and the arguments are starting to become repetitive (they "reach a steady state") the RFC goes into "final comment period", allowing people who weren't paying close attention to every proposal to have a chance to weigh in with new arguments. assuming no new arguments are presented, the RFC is merged by consensus of the core team and the feature is implemented. All changes, regardless of their source, go through this process, giving active community members who aren't on the core team an opportunity to participate directly in the future direction of the project. (both because of proposals they submit and ones from the core team that they contribute to)
  8. Oct 2020
  9. Jul 2020
  10. Jun 2020
    1. That said, the distinction generally just affects which release your patch will get in to; we love feature submissions! They just won't get backported to maintenance branches.
  11. May 2020
    1. Future keyword improvements are being discussed in our epic for improving rules, where anyone can add suggestions or requests.
  12. Apr 2020
    1. There are many other factors that also aren't obvious so as much as suggestions for improvements are very welcomed, please keep in mind that they may not work in the broader sense of what's required to run this project.
  13. Mar 2020
    1. I enjoy dissent and debate among commenters, and criticism of my views is also always welcome; you are even free to call me an assclown, a dupe, a partisan ignoramus — whatever you like, as long as you don't insult other commenters.
    1. As part of the beta program, if you or someone on your team can give us quick feedback every 1-2 weeks, we'll keep extending your free trial (normally 2 weeks) indefinitely!
  14. Feb 2020
    1. We should counteract that by having short toes and feel comfortable letting others contribute to our domain.
    1. Wouldn't let me annotate a selection on this page:

      Reinforce your feedback loop

      The Timeline centralizes all your changes. It allows customers to browse updates, share and send feedback. Collected reactions provide the right information for improving your product and reducing churn.

  15. Dec 2019
    1. If none of this worked, please comment in this issue and we’ll try to help. Try to create a small reproducing example — you might discover the problem as you’re doing it.
  16. Nov 2019
    1. this is not intended to become a big, public thing. You're welcome to use anything and steal any code. Please do not count on us adressing feature requests or issues though.
    1. We have ideas about what we will build next for Cycle Analytics but we'd love to hear your thoughts. You can follow and contribute to the discussion on this issue.