15 Matching Annotations
  1. 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)
  2. Oct 2020
  3. Jul 2020
  4. May 2020
    1. Future keyword improvements are being discussed in our epic for improving rules, where anyone can add suggestions or requests.
  5. 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.
  6. Mar 2020
    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!
  7. 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.

  8. Dec 2019
  9. Nov 2019
    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.