Make regular todos visible

[skade]

#76 needs to be planned regularly. We need to find a way to make this happen and to communicate to everyone that a task was done/being worked on.

[carols10cents]

Questions:

• Who is "everyone"? Everyone on the community team or everyone on the internet who might be interested in what we're up to?
• What do we need out of a solution to this? (that is, how will we know that we have made regular todos visible?)
• Once we know what we need, what tools are possibilities?

[edunham]

Here are my opinions on some answers:

• "Everyone" means "everyone on the community team, and optionally interested community members for some tasks"
• I think the MVP is a tool in which:
  • Anyone on the community team can add a recurring task, recurring either by # of days or by day of the month
  • Anyone on the community team can mark a task as completed, with optional comments
  • The tool nags the community team or assigned team member if a task remains incomplete for a certain amount of time

Nice-to-haves:

• No new account needed (we all have too many accounts already)
• TODOs and status are visible to the public as well as to the community team
• Possible options:
  • Google Calendar could get us part of the way there
  • Trello or an open-source clone thereof is good for non-recurring task conversation and management (one can host a trello-flavored thing in oasis.sandstorm.io for free, and use GitHub login iirc)
  • Plain ol' GitHub Issues, with a bot (maybe a new Highfive feature?) to submit the issue and label it as a recurring task, would be great for visibility and conversation
  • And more tools that I'm not aware of -- I'm not particularly involved with tasks that require collaborative, public, recurring TODO items.

After thinking through it this way, having a bot throw GitHub issues at is for monthly-or-less-frequent team TODO items sounds like it'd be a valid solution for now.

[erickt]

Also needs to be checked weekly:

• TWiR's Friends of the Forest
• TWiR's Quote of the Week

[edunham]

Another regular TODO is that every Tuesday, one person should check in with each team member to see if they have anything to add to the agenda.

[skade]

I came across a tool called taskwarrior that handles recurrence and wondered about how well it is suited for team collaboration. Also, about the availability of a web interface suitable for people not familiar with taskwarrior.

Also, I found a certain @erickt listed as a plugin author and hope they could give some feedback.

[skade]

Another option would be a zapier zap that creates a github issue.

Alternatively, meetingbot could develop a case of scope creep :).

[ashleygwilliams]

i think it would be useful to revisit this soon as we institute more structure to the rust comm team. i'm adding this as an agenda item for next meeting.