On Fri, May 11, 2012 at 12:21 AM, Ricardo Salveti <ricardo.salv...@linaro.org> wrote: > On Thu, May 10, 2012 at 1:20 PM, Christian Robottom Reis > <k...@linaro.org> wrote: >> On Thu, May 10, 2012 at 12:55:26PM -0700, Ricardo Salveti wrote: >>> Sorry to say that, but I hate these kind of emails at Linaro Dev, as I >>> believe we have other places (and better ones) to report such issues. >>> Twitter would probably be the way to go. >> >> Well, to be honest I don't really see the problem with letting the list >> know that there are issues, and I interpret Zach's brevity as "we're >> totally focused on getting the problem solved". I expect he's going to >> come back and explain what's broken when the issue is resolved. > > Well, just saying it's broken doesn't help much either. If you really > want a better and more up-to-date place to show this info even IRC > would be better. > >> Is Twitter really that much better to inform us it's broken? I would >> have missed the news entirely, for one random data point. > > Better than email at least :-) While it it's useful, did it actually > help you in any front? > > Twitter is the general place used by most of projects for status > update, that's why I thought that it'd be the best way to go. >
I would have preferred to get a bit more context as well, but as kiko said, getting an notification is definitely better than nothing. Especially if you are in the mids of a firedrill you might not have the time to explain the context, nor might you understand whats going on at all etc. -- Alexander Sack Technical Director, Linaro Platform Teams http://www.linaro.org | Open source software for ARM SoCs http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
