Comment 16 for bug 392976

I'll think translating it into different anguages should be a good
work item too...

On Sun, Apr 4, 2010 at 6:39 AM, Chris Crisafulli <email address hidden> wrote:
> I agree that this holds great value for our community, It would help
> alleviate some questions and doubts on what's expected from Loco team
> leaders, and present and future leadership of our teams. As was
> mentioned earlier, I feel it would be good to include signing of the
> LCoC for All council positions. We should also encourage existing Team
> Leaders/Contacts/Administrators to read, understand, and sign the LCoC
> as well (at risk of not staying within boundaries of this current bugs
> scope).
>
> We can even go a step further in the near future and set it as a
> prerequisite for a LoCo's Leadership prior to applying for Team Approval
> (In cases where new teams are being formed), and potentially Re-
> Approvals.
>
> This should not be limited to just those few in my opinion, though. I
> feel it should extend to potential leaders and members that would like
> to demonstrate that they've made a choice to hold themselves to this
> higher standard. This could be really helpful when teams are spread out
> across many miles within a state, country or region, and teams look to
> identify leaders in those areas. LoCo leaders would have a much easier
> time growing their teams and running simultaneous events, if volunteers
> interested in leading could also sign.
>
> There should be a distinction though between this and the standard CoC.
> We need to impress the importance of the difference and ensure that
> people don't just sign it in a trivial manner, as just another task item
> to mark completed.
>
> --
> Leadership CoC not given to LoCo Leads
> https://bugs.launchpad.net/bugs/392976
> You received this bug notification because you are a member of Ubuntu
> LoCo Council, which is a bug assignee.
>