On 10/07/2010 07:22 PM, David wrote:
> On 10/06/2010 07:27 PM, Zach Gibbens wrote:
>> I know Tennessee had some opinions on it (at the time I thought it was
>> loco or irc council policy for some time, I was just a regional contact
>> back then) I'm going to add it to our teams agenda for our mee
On 10/08/2010 08:26 AM, David wrote:
> On 10/07/2010 07:22 PM, David wrote:
>> On 10/06/2010 07:27 PM, Zach Gibbens wrote:
>>> I know Tennessee had some opinions on it (at the time I thought it was
>>> loco or irc council policy for some time, I was just a regional contact
>>> back then) I'm going
dear sir
I want to appreciate ubuntu here in my area or state what cani do for this
--
Thanks & Regards
Arihant Jain
--
loco-contacts mailing list
loco-contacts@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/loco-contacts
On Mon, Oct 4, 2010 at 3:01 PM, Ubuntu LoCo Council
wrote:
> When new contributors are checking out teams they will have an opportunity
> to read past logs in effort to better learn more about the team, this will
> help them to see what they can expect from the team, and even potentially
> find wh
A suggestion:
Perhaps it would be helpful if the LoCo Council publishes a concise
problem statement, and then presents it's rationale on why/how logging
IRC channels will solve the problem(s).
Often decisions like these are quite unpopular until the reason(s)
behind them are well understood. We
On 10/08/2010 07:26 AM, David wrote:
> On 10/07/2010 07:22 PM, David wrote:
>> On 10/06/2010 07:27 PM, Zach Gibbens wrote:
>>> I know Tennessee had some opinions on it (at the time I thought it was
>>> loco or irc council policy for some time, I was just a regional contact
>>> back then) I'm goin
I agree with this. After careful consideration I would rather this be by
request and on a loco by loco basis.
~ cprofitt
On Fri, 2010-10-08 at 12:55 -0400, Daniel Chen wrote:
> Mandating logging as a requirement seems rather extreme. I'd rather
> see it implemented by request - per-LoCo team - t
