Skip to content
This repository has been archived by the owner on Feb 8, 2023. It is now read-only.

Moving from editing top comment to commenting individual sprints #65

Closed
2 tasks done
RichardLitt opened this issue Dec 1, 2015 · 6 comments
Closed
2 tasks done

Comments

@RichardLitt
Copy link
Member

We used to edit the top comment of a sprint to include our todos. I don't think we should keep doing this.

Why

  • Not everyone does it
  • It discourages people who do not have write access to the top editors comment
  • Throwing in a comment is easier
  • Throwing a comment in provides better time stamping and provenance
  • Editing leads to errors sometimes
  • It's confusing to use both.

Suggestion

  • Change the documentation to make it clear that you just need to add a comment with your sprint to dos each sprint.
  • Remove the ### [@Githubusername](dsdfs) link, as it isn't useful for anyone and takes time.
@whyrusleeping
Copy link
Member

👍

3 similar comments
@dignifiedquire
Copy link
Member

👍

@harlantwood
Copy link
Contributor

+1

@jbenet
Copy link
Member

jbenet commented Dec 2, 2015

👍

@jbenet
Copy link
Member

jbenet commented Dec 2, 2015

(this was a holdover from adding our todos in an etherpad. am totally fine moving to just messages on the sprint)

@daviddias
Copy link
Member

I'm good both ways :)

@RichardLitt RichardLitt mentioned this issue Dec 7, 2015
14 tasks
lidel pushed a commit that referenced this issue Nov 15, 2018
* Create 2017-12-29--q1-planning-brainstorming

* Enable markdown for 2017-12-29--q1-planning-brainstorming

* 2017-12-29--q1-planning-brainstorming: minor clarifications

* Q1 Brainstorming: Action Item related to OKR Proposals

Points everyone at the right "starting point" to PR agains.
daviddias pushed a commit that referenced this issue Nov 16, 2018
* Create 2017-03-29-standup.md

* Notes from Lab Week 2017: Roadblocks for IPFS in Browser Extension

* clean up / reorg

* Create 2017-12-29--q1-planning-brainstorming (#65)

* Create 2017-12-29--q1-planning-brainstorming

* Enable markdown for 2017-12-29--q1-planning-brainstorming

* 2017-12-29--q1-planning-brainstorming: minor clarifications

* Q1 Brainstorming: Action Item related to OKR Proposals

Points everyone at the right "starting point" to PR agains.

* Meeting notes for 2018-01-09

* Update 2018-01-09--q1-planning-brainstorming.md

* Add meeting notes for irc sync 2018-04-03

* Add meeting notes for irc sync 2018-04-09

* Add meeting notes for irc sync 2018-04-16

* Rename 2018-04-17--weekly-wg-sync.md to 2018-04-16--weekly-wg-sync.md

* Fix a typo

* Create 2018-04-23--weekly-wg-sync.md

* Add meeting notes for irc sync 2018-04-30

* Add meeting notes for irc sync 2018-05-08

* Add meeting notes for irc sync 2018-05-21

* Add meeting notes for irc sync 2018-06-04

* Add meeting notes for irc sync 2018-05-29

* Add meeting notes for irc sync 2018-05-14

* Add meeting notes for irc sync 2018-06-11

* Add meeting notes for irc sync 2018-06-18

* Add meeting notes for irc sync 2018-06-25

* Add meeting notes for irc sync 2018-07-02

* Add meeting notes for irc sync 2018-07-16

* Add meeting notes for irc sync 2018-07-23

* Add meeting notes for irc sync 2018-07-30

* Add IRC Sync 2018-08-06

* Create 2018-08-20--weekly-wg-sync.md

* Add meeting notes for irc sync 2018-08-28

* Create 2018-09-04--weekly-wg-sync.md

* Create 2018-09-10--weekly-wg-sync.md

* Create 2018-09-17--weekly-wg-sync.md

* Add meeting notes for 2018-09-24

* fix: forgot to add my name :)

* Create 2018-10-01--weekly-wg-sync.md

* Create 2018-10-15--weekly-wg-sync.md

* fix: remove duplicate name

* Create 2018-10-22--weekly-wg-sync.md

* Add Meeting Notes for 2018-10-29
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants