Hi Sergio, council, and team contacts,

The response ended on this list (loco-contacts) by accident, an
unfortunate circumstance of my allowing Thunderbird to auto-complete an
address beginning with loco- and then pressing send without looking
carefully. The response was meant to go to the moderated
"loco-coun...@lists.ubuntu.com" (where the original request to add
Moscow to LTP was made) and not to a public list. Please accept my
apologies for that carelessness.

I was intending to write a general proposal to the loco-contacts list
and also to council that will solve the problem of country teams not
meeting the needs of the cities (and towns) within them. I still intend
to do that, and I welcome correspondence, either private or public from
leaders that are running active city-based teams. (Note: I am less
interested in feedback from leaders that are not operating/leading
locally, as the challenges are significantly different.)

So,

Chicago
Dallas
(Vancouver)
Omsk
Hong Kong
Singapore
Delhi
St. Petersburg
Bangalore
Moscow
Washington DC
and others

.. I'm specifically looking for your thoughts.

With regards to the IRC log below, from July 2012, I reviewed the log
and did not see any dialog with the Ubuntu Moscow team lead (Garfield).
I would have hoped/expected that s/he would have been solicited for
feedback as part of the process. I'll restate my thesis: if a city team
has formed, it is because it is serving a need not filled by existing
structure. In fact, if *any* team is formed, it's a result of a real
need. We should respect that need and offer to help them grow and be
successful as the first response.

I'm looking forward to the LoCo council clearing all obstacles for
"non-traditional" teams and helping us grow the Ubuntu community.

Cheers,
Randall.

--

On 13-04-03 02:24 PM, Sergio Meneses wrote:
> Hi everybody!
>
> I see a lot of opinions and different points of view, this is always a
> good thing! but as Pablo Rubianes said the LoCo Council must work on
> this, with the help of this commentaries and of course with Ubuntu-RU
> leaders
>
> We (LoCo Council) are working on this, in our last meeting with
> Ubuntu-RU team we talk about this, as you can see in our minute:
> https://wiki.ubuntu.com/LoCoCouncil/Minutes/20120717
>
> In order to finish this message, I don't know why this message ended
> in the lococontacts-mailinglist! and reading Laura's answer, I didn't
> see nothing like "condescending" or something. I think Laura's mail is
> totally valid!
>
> Remember, the LoCo Council is here to help! and if anyone has problems
> about locoteams, please let us know without intermediaries.
>
>
> Regards!
>
>
>
> Sergio Meneses
> Ubuntu LoCo Council
>
>
> On Wed, Apr 3, 2013 at 1:02 PM, Michael Hall <mhall...@ubuntu.com
> <mailto:mhall...@ubuntu.com>> wrote:
>
>     On 04/03/2013 01:41 AM, Jono Bacon wrote:
>     > Hi All,
>     > ...
>     > I think if we have a team in Moscow that is being active, we
>     > should let them post their blog posts to loco.ubuntu.com
>     <http://loco.ubuntu.com>
>     > <http://loco.ubuntu.com> - why would we not want to expose their
>     Ubuntu
>     > contributions to the wider LoCo community?
>     >
>
>     Adding blogs to the LTP homepage isn't the issue, we can add any blog
>     feed and assign it to any team.  If the Moscow team has a blog, we can
>     add it to LTP under the Russian team (or even no team if we wanted).
>
>     The bigger question is events and meetings, should the Moscow members
>     use the Russian team for events and meetings?  As long as they are
>     members of that Russian LP team they can do that in LTP.
>
>     Michael Hall
>     mhall...@ubuntu.com <mailto:mhall...@ubuntu.com>
>
>     --
>     loco-contacts mailing list
>     loco-contacts@lists.ubuntu.com <mailto:loco-contacts@lists.ubuntu.com>
>     https://lists.ubuntu.com/mailman/listinfo/loco-contacts
>
>
>
>


Attachment: signature.asc
Description: OpenPGP digital signature

-- 
loco-contacts mailing list
loco-contacts@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/loco-contacts

Reply via email to