17 Matching Annotations
  1. Jan 2021
    1. The rationale for branches is simple. Each snap in the Snap Store has a default track called ‘latest’ in which there are four channels named ‘stable’, ‘beta’, ‘candidate’ and ‘edge’. These are all typical buckets in which snaps are published for an extended period, perhaps months or maybe even years. Branches on the other hand are short-lived silos for publishing snaps. 
  2. Jan 2020
    1. If we allow this, we then need a way to say ‘Let this person see everything on this Page’, at which point Pages become permission vehicles, complicating (in my mind) the permission structure we have.

      I think you will need to explain this to me.

    2. The external contributor can simply click ‘New Review’, self-assign themselves as the reviewer and make suggested changes. When done, they can forward it on to the author or other Pub manager.

      This would take a significant amount of education in order for folks to understand it. Suggest Edit, makes more sense.

    3. list all reviews

      This doesn't make any sense. Students will not understand it...

    4. a teacher can create a new review in all relevant chapters.

      Here, I think version makes more sense--I guess it depends on the perspective. Is it another copy of an existing publication? Even then, you'd need one for each of your classes. Would you have to go back to the original every time?

    5. Review

      Here, I think Group makes the most sense.

    6. new review

      I think version would make more sense here. Creating a new review doesn't mean anything to me...

    7. author wants to submit their work for peer review

      It's probably going to be an editor who submits for peer review. An author may want someone else to review it, but an author wouldn't submit for peer review.

    8. Depending on whether the author is viewing a release or the draft branch, two options will appear: ‘Publish New Release’ or ‘Edit Document’

      I don't think I understand the difference between New Review and Edit? What I really want to be able to see her is what permissions/rights do I have, I think. Is that meant to be conveyed by the tiny text in the leftmost button?

    9. Branch + Merge Request + Conversation space.

      Some branches may be intended to never merge with any others--like translations or classroom groups.

    10. a space

      Potentially many spaces, one per class section. New groups per term, etc.

    11. author

      Team of collaborators want to review portions of documents before sharing with the rest of the group/public.

    12. author

      or Editor

  3. Dec 2019
  4. Jan 2017
  5. Jun 2015
    1. The best way to find branches I've recently used is to use the following command: git for-each-ref --sort=-committerdate refs/heads/
  6. May 2015
    1. git for-each-ref --sort='-committerdate' --format='%(refname)%09%(committerdate)' refs/heads | sed -e 's-refs/heads/--'