Closed RichardLitt closed 8 years ago
we should probably just deploy our own damn etherpad until we make one on ipfs.
we should probably just deploy our own damn etherpad until we make one on ipfs.
What exactly is the benefit in the current structure of the sessions for an etherpad, as far as I can tell everybody is just pasting his or her goals for the week and then it gets copied over to github. So why not just post it as a comment directly on github?
benefits
this is more vestigial from when i had more time to PM better.
we could move to:
Why don't we try posting individual comments in the sprint issue this week? I want to see if that works, I suspect it will work just as well. Combined with a list of attendants at the top, it'll streamline my efforts, anyway. I haven't seen anyone edit it async in the past few weeks.
I'm just the sprint master, not a PM, so I don't know if I can help completely, but I think that would be a smart thing to do.
@RichardLitt's update:
@chriscool's update:
ipfs commands
in t0010 and related cleanupipfs commands --flags
@ike's update:
I got laid off this week, so I made no progress on indie-comments. If anybody has any leads on front-end dev or bizdev gigs, I'd be super appreesh.
indie-comments:
New sprint! https://github.com/ipfs/pm/issues/40
Sprint 37
Date: October 12, 2015
Sprint Goals
Sprint Discussions
See https://github.com/ipfs/pm#sprint-discussion-schedule
Please take notes in a separate pad, if you can, and link it here.
Sprint Deliverables
Participants
At sync time
daviddias, lgierth, kyledrake, krl, RichardLitt, whyrusleeping, dignifiedquire
With deliverables this week
@dignifiedquire
electron-app
WebUI
@krl
@kyledrake
Recap from last sprint:
_ :palmtree: No tasks this week
@whyrusleeping
@RichardLitt
README Overhaul
API Documentation
@diasdavid || @daviddias
@amstocker
Python ipfs api:
Other:
@ike
indie-comments: