[Bigbang-dev] Assigning tickets for 0.2 milestone

[Sebastian Benthall]

That's a great question.

So far, we don't have a timeline set.

I propose we hold a meeting some time next week to discuss the scope of the
0.2 release.

On Mon, Oct 24, 2016 at 8:48 PM, Nick Doty <npdoty at ischool.berkeley.edu>
wrote:

> Is there a suggested schedule for 0.2 milestone or a set of guidelines for
> what has to be completed in that milestone vs. later? Some simple guidance
> there could help me in determining whether I can take on tickets, or
> whether I think tickets should be in this or a later milestone.
>
> Cheers,
> Nick
>
> On Oct 23, 2016, at 3:52 PM, Sebastian Benthall <sbenthall at gmail.com>
> wrote:
>
> Hi all,
>
> I've gone through the 0.2 tickets and tried to assign them based on my
> best guess as to who would be interested in and available to work on them.
>
> https://github.com/datactive/bigbang/milestone/6
>
> The one I wasn't able to assign was this one, because I'm not sure who has
> a mac computer. (Also, note its possible redundancy with ticket #248
>
> https://github.com/datactive/bigbang/issues/269
>
> For those not totally familiar with the idioms of open source development,
> I want to make it clear that assigning a ticket to somebody should be
> interpreted as a kind of question, "I think you are the right person to
> look at this issue next. What do you think?", not as a firm delegation of
> responsibility. As always, Fogel has some helpful commentary on this:
>
> http://producingoss.com/en/managing-participants.html#delegation
>
> All best,
> Seb
> _______________________________________________
> Bigbang-dev mailing list
> Bigbang-dev at data-activism.net
> https://lists.ghserv.net/mailman/listinfo/bigbang-dev
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ghserv.net/pipermail/bigbang-dev/attachments/20161024/b2b06dca/attachment.html>