[Bigbang-dev] Assigning tickets for 0.2 milestone

[Niels ten Oever]

This also depends on the capacity and resources for a sprint on which I
hope to hear back soon. Stay tuned.

Niels ten Oever
Head of Digital

Article 19
www.article19.org

PGP fingerprint    8D9F C567 BEE4 A431 56C4
                   678B 08B5 A0F2 636D 68E9

On 10/24/2016 10:09 PM, Sebastian Benthall wrote:
> 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
> <mailto: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 <mailto: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
>>     <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
>>     <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
>>     <http://producingoss.com/en/managing-participants.html#delegation>
>>
>>     All best,
>>     Seb
>>     _______________________________________________
>>     Bigbang-dev mailing list
>>     Bigbang-dev at data-activism.net <mailto:Bigbang-dev at data-activism.net>
>>     https://lists.ghserv.net/mailman/listinfo/bigbang-dev
>>     <https://lists.ghserv.net/mailman/listinfo/bigbang-dev>
> 
> 
> 
> 
> _______________________________________________
> Bigbang-dev mailing list
> Bigbang-dev at data-activism.net
> https://lists.ghserv.net/mailman/listinfo/bigbang-dev
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.ghserv.net/pipermail/bigbang-dev/attachments/20161025/3efc0f52/attachment.sig>