Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[pm] Sprint 15 February - 28 February #405

Closed
danfowler opened this issue Jan 18, 2016 · 18 comments
Closed

[pm] Sprint 15 February - 28 February #405

danfowler opened this issue Jan 18, 2016 · 18 comments
Assignees
Labels
Milestone

Comments

@danfowler
Copy link
Contributor

The purpose of this meta-issue is to define an initial two week sprint to take on and complete some Labs tasks within that sprint. In this initial sprint, I will probably take on the majority of tasks, but hopefully, in the next sprint, we can have others take on some commitments. This is loosely inspired by IPFS's project management strategy. As we go along, this workflow will certainly change 😅.

Task Lead Estimate (days) Issue Done
Sync with Labs leads 0.25
Schedule February Hangout @danfowler 0.25 #386 ✔️
Finalize a vision/manifesto document @rgrp 0.5 #409
Recategorize projects as per plan into active, retired @davbre + @rgrp 0.5 #274 ✔️
Establish "priority" projects @rgrp 0.5 #402 ✔️
Solicit submissions for & create Q12016 Newsletter @jwieder #398

What do you think of this methodology Labs team? Are any of you interested in taking on any tasks?

@davbre
@davidmiller
@jgkim
@loleg
@mattfullerton
@pdehaye
@jwieder
@todrobbins

@danfowler danfowler self-assigned this Jan 18, 2016
@danfowler danfowler added this to the Q1-2016 milestone Jan 18, 2016
@rufuspollock rufuspollock mentioned this issue Jan 18, 2016
15 tasks
@davbre
Copy link
Contributor

davbre commented Jan 19, 2016

@danfowler - this approach looks fine to me. I could give a hand with issue
#274.

On 18 January 2016 at 09:52, Daniel Fowler [email protected] wrote:

The purpose of this meta-issue is to define an initial two week sprint to
take on and complete some Labs tasks within that sprint. In this initial
sprint, I will probably take on the majority of tasks, but hopefully, in
the next sprint, we can have others take on some commitments. This is
loosely inspired by IPFS's project management https://github.com/ipfs/pm
strategy. As we go along, this workflow will certainly change [image:
😅].
Task Lead Estimate (days) Issue Done
Sync with Labs leads @danfowler https://github.com/danfowler 0.25
Schedule January Hangout @danfowler https://github.com/danfowler 0.25
#386 #386
Finalize a vision/manifesto document @danfowler
https://github.com/danfowler 0.5 #401
#401
Recategorize projects as per plan into active, retired @danfowler
https://github.com/danfowler 0.5 #274
#274
Establish "priority" projects @danfowler https://github.com/danfowler
0.5 #402 #402

What do you think of this methodology Labs team? Are any of you interested
in taking on any tasks?

@davbre https://github.com/davbre
@davidmiller https://github.com/davidmiller
@jgkim https://github.com/jgkim
@loleg https://github.com/loleg
@mattfullerton https://github.com/mattfullerton
@pdehaye https://github.com/pdehaye
@jwieder https://github.com/jwieder
@todrobbins https://github.com/todrobbins


Reply to this email directly or view it on GitHub
#405.

@todrobbins
Copy link
Member

Looks great @danfowler! What a helpful table = Markdown FTW!

Do you want us to edit your comment to add table rows?

@davidmiller
Copy link
Contributor

@danfowler Is there a draft of the vision/manifesto doc? Happy to take a look when there is.

Semi-related: #401 links to a mailing list discussion about a chat space - did that ever get decided on/actioned?

@puppycidedb
Copy link

@danfowler I also think this approach is good. I would be willing to
take on a task - I don't have a preference, so if something is left over
I can tackle it.

On 1/18/2016 3:52 AM, Daniel Fowler wrote:

The purpose of this meta-issue is to define an initial two week sprint
to take on and complete some Labs tasks within that sprint. In this
initial sprint, I will probably take on the majority of tasks, but
hopefully, in the next sprint, we can have others take on some
commitments. This is loosely inspired by IPFS's project management
https://github.com/ipfs/pm strategy. As we go along, this workflow
will certainly change 😅.

Task Lead Estimate (days) Issue Done
Sync with Labs leads @danfowler https://github.com/danfowler 0.25
Schedule January Hangout @danfowler https://github.com/danfowler
0.25 #386 #386
Finalize a vision/manifesto document @danfowler
https://github.com/danfowler 0.5 #401
#401
Recategorize projects as per plan into active, retired @danfowler
https://github.com/danfowler 0.5 #274
#274
Establish "priority" projects @danfowler
https://github.com/danfowler 0.5 #402
#402

What do you think of this methodology Labs team? Are any of you
interested in taking on any tasks?

@davbre https://github.com/davbre
@davidmiller https://github.com/davidmiller
@jgkim https://github.com/jgkim
@loleg https://github.com/loleg
@mattfullerton https://github.com/mattfullerton
@pdehaye https://github.com/pdehaye
@jwieder https://github.com/jwieder
@todrobbins https://github.com/todrobbins


Reply to this email directly or view it on GitHub
#405.

@danfowler danfowler changed the title [pm] Sprint 18 January - 29 January [pm] Sprint 15 February - 28 February Feb 4, 2016
@danfowler
Copy link
Contributor Author

OK, picking this up again and adjusting dates. I've scheduled the next hangout planned, and I really hope you all can join.

https://discuss.okfn.org/t/tech-hangout-february-2016/2019

@davbre can you take a look at #274 ?
@todrobbins feel free to edit the table :)
@davidmiller nothing was decided. Do you have a strong preference?
@puppycidedb can you help solicit suggestions for a new newsletter and add that task the list?

@puppycidedb
Copy link

puppycidedb commented Feb 18, 2016 via email

@davbre
Copy link
Contributor

davbre commented Feb 18, 2016

@danfowler - yes, that's fine - I'll take a look when I can.

On 18 February 2016 at 14:39, Puppycide Database Project <
[email protected]> wrote:

@danfowler - I will be available for the tech hangout next week & I will
get started on the newsletter tasks. - @jwieder / @puppycidedb


Reply to this email directly or view it on GitHub
#405 (comment)
.

jwieder added a commit to jwieder/okfn.github.com that referenced this issue Feb 18, 2016
@jwieder
Copy link
Contributor

jwieder commented Feb 18, 2016

@danfowler Updated the table above, created a blog post requesting submissions ( Pull request #406 ), sent out a tweet to okfnlab followers & added a discussion list topic

@danfowler
Copy link
Contributor Author

@jwieder 👍 👍

@davidmiller
Copy link
Contributor

@danfowler I have no strong opinions, just wondering what the status was. It's the kind of thing where making a decision is more important than the value of the decision.

I delegate any vote I might have had to you ;)

@rufuspollock
Copy link
Member

@danfowler - i missed this originally (do feel free to @ me in future!). Looks really good.

@davidmiller +1 on the value of the decision. As for that forum thread I have just commented this weekend with an update recommending (personally) gitter. I have created the public room here https://gitter.im/okfn/chat and invite folks to join and try it out.

@davidmiller The manifesto / vision doc is here. If you were up to taking at look at this this is something I'd love to work with you on.

@rufuspollock
Copy link
Member

@danfowler how are we doing here - do you have any updates on the (beautiful) tasks matrix :-)

@davidmiller let me know yay or nay on doing a session on the manifesto / vision doc.

@rufuspollock
Copy link
Member

@danfowler i've updated tasks matrix with two assignments on items. Do you know who is taking on updating labs leads? Could we get a separate issue for this as i have some suggestions to offer.

@danfowler
Copy link
Contributor Author

@rgrp thanks. I will take on updating team leads.
On Mar 5, 2016 20:21, "Rufus Pollock" [email protected] wrote:

@danfowler https://github.com/danfowler i've updated tasks matrix with
two assignments on items. Do you know who is taking on updating labs leads?
Could we get a separate issue for this as i have some suggestions to offer.


Reply to this email directly or view it on GitHub
#405 (comment)
.

@pwalsh
Copy link
Member

pwalsh commented Mar 6, 2016

@danfowler a lot going on here, great! Can you please also communicate this stuff internally at OKI, especially with the Tech Team.

@rufuspollock
Copy link
Member

@danfowler how are we doing here with the newsletter and the syncing with labs leads? Everything else is done 🎂

@rufuspollock
Copy link
Member

@danfowler can we close this out and move items to 2016 Q2 item.

@danfowler
Copy link
Contributor Author

Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

8 participants