> My post really only targets the Analytics Development team (see last email's greeting).
*face palm* Woops. Thanks for answering my questions anyway. :) On Mon, Feb 24, 2014 at 4:17 AM, Christian Aistleitner < [email protected]> wrote: > Hi Aaron, > > On Fri, Feb 21, 2014 at 01:31:58PM -0500, Aaron Halfaker wrote: > > I don't know what type of things you are referring to. Should we manage > > tasks on this list or can they stay in mingle/trello? > > Keep Trello! > Keep Mingle! well ... :-D > > But seriously, keep doing whatever you used to do, and using whatever > tools that you used to use. My post really only targets the Analytics > Development team (see last email's greeting). That's the place where > it seemed to me that we had general agreement about the policy. I am > not trying to mess with the Research & Data team. So feel free to > ignore :-) > > > [...], but there should be a > > definition of what is relevant and what is not. Could you help me > > understand with a few examples? > > I hope that common sense will lead us along the path :-) > Of course Apache's use of it, as requirement to bring technical > discussions/decisions to the list, serves as example. > > So assume we would have a Hangout meeting tomorrow, where we would > decide to ditch Hadoop and reimplement it because of NIH. That'd be > "ok" only if we bring the decision and discussion to the list. > > If Toby has new information about the level of privacy we have to > employ around Wikipedia Zero data, it is fine if he tells the > Development team in a Hangout. But it did not "happen" until he posted > it to a list. > > Thereby, it is assured that we have decisions and discussions around it > * visible, > * archived, and > * addressable via an URL. > > A different example is that the Development recently discussed doing a > spike around how to best consume the request stream's compressed json > in Hadoop through Pig. That's not a decision per se, but I'd hope > (others might disagree :-) ) that it will lead to a short post to this > list, so others can see the outcome and later revisit, refer to or use > it. > > On the other end, obviously my nice's next birthday, or me switching > from Emacs to Vi, or minor things like whether or not we use > constructor injection or setter injection for $RANDOM_CLASS_X would > not not require mails to the list under normal circumstances from my > point of view. > > As you directly asked about whether or not one should manage tasks on > this list; I hope we do not need to. From my point of view, that would > increase noise a lot. But in a condensed manner that would totally > make sense to me. Like Toby sent out a "Sprint Planning Update" some > days ago, just like Diederik used to do. That looked good to me. > > Have fun, > Christian > > > > -- > ---- quelltextlich e.U. ---- \\ ---- Christian Aistleitner ---- > Companies' registry: 360296y in Linz > Christian Aistleitner > Gruendbergstrasze 65a Email: [email protected] > 4040 Linz, Austria Phone: +43 732 / 26 95 63 > Fax: +43 732 / 26 95 63 > Homepage: http://quelltextlich.at/ > --------------------------------------------------------------- > OpenPGP key transition from 0xEF78CCDE to 0x13C1072F: > http://quelltextlich.at/openpgp-transition-0xEF78CCDE-to-0x13C1072F.txt > > _______________________________________________ > Analytics mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/analytics > >
_______________________________________________ Analytics mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/analytics
