[bisq-network/proposals] Start daily update calls for active developers (#137)
notifications at github.com
Tue Jan 21 05:11:10 UTC 2020
Update: I've posted the following request to all members of the Bisq keybase team. We only ever did video calls once or twice (as suggested in this proposal), and the practice that has emerged is to send textual updates at or around 8p CET in the #standup channel. This practice has been working pretty well, so I've asked every active contributor to begin doing it on days that they do work for Bisq.
> `@channel` this message is primarily intended for current and potential future contributors, but users and BSQ stakeholders may also be interested in its content. Please forgive the global `@mention`, but I actually do want to get everyone's attention here.
> As many of you know, we're in the process of putting together a budget, a prioritized list of goals for the project and other important organizational changes. These will be announced soon and will begin taking effect with DAO Cycle 10, which is just starting now. Stay tuned for full details, but in the meantime **I have a request for everyone that is currently contributing, including anyone who plans to issue a compensation request for Cycle 10:**
> You may have seen that a number of us have been submitting updates every weekday in the #standup channel for the last month or so. **I'm now asking everyone who plans to submit a compensation request in Cycle 10 to begin doing the same.**
> If you're not familiar with what a "standup" is, it's a name for a short meeting that many professional software teams hold every day. Team members get in the same room and literally stand up while giving updates on what they're doing. The discomfort of standing helps ensure that the meeting goes quickly. Obviously we can't actually get in the same physical room together and you don't actually have to stand up when you send your update, but you get the idea.
> Updates should typically be short and as clear as you can make them. A good guideline is the "three questions" common to many standup meetings (from https://en.wikipedia.org/wiki/Stand-up_meeting#Three_Questions):
> 1. What did I do yesterday that helped the team meet the sprint goal?
> 2. What will I do today to help the team meet the sprint goal?
> 3. Do I see any impediment that prevents me or the team from meeting the sprint goal?
> Nevermind the "sprint goal" for now. As we roll out the budget and priority list, it will become clear what the current goals are, and you'll easily be able to figure out whether what you're working on is toward those goals or not (and therefore whether what you're working on is eligible for compensation or not). **For the time being, please just send an update that says what you worked on today and what, if anything, is standing in your way of making progress.**
> If you don't work on Bisq every day, that's just fine and there is no need to send an update every day. Just send an update every day that you do work. In any case, if you don't send an update the assumption will be that you did not contribute anything on that day.
> If you're someone who typically works most or every day and you know you're going to be away for a while, send an update that says so.
> Those of us that have been doing this for a while try to send our updates around 8p Central European Time, but our contributor base is widely distributed, so **if 8p CET is not convenient for you, please send your update at the end of your workday,** whenever that may be.
> The goal of doing these standup updates is to help us focus together on accomplishing the most important things and to help control costs as we do so. They also have the wonderful effect of making it feel like you're _actually part of a team._ I and the others who have been doing these updates see them as the bare minimum amount of communication required for a distributed team like ours to stay in touch and succeed.
> If you have other questions about how to submit these updates, please ask them here or in the #standup channel. If you are unwilling to accept this request, please consider sending me a direct message to explain why; I will appreciate and take seriously any feedback. Please hold off for now on questions about the larger set of changes we're rolling out; it's my number one priority to deliver an announcement about that as soon as possible.
> Thanks for reading, and I look forward to seeing you in #standup!
> P.S.: Note that I plan to cross-post this message to the `bisq-contrib` mailing list, which I intend to use a bit more frequently for this sort of thing. If you're not already subscribed, please consider doing so at https://lists.bisq.network/listinfo/bisq-contrib. Everyone interested in BSQ, the Bisq DAO and our plans for Bisq in general is welcome to join.
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the bisq-github