On Mon, Dec 21, 2009 at 06:28:32PM -0800, Toshio Kuratomi wrote:
On Fri, Dec 18, 2009 at 08:11:28AM -0500, Paul W. Frields wrote:
On Thu, Dec 17, 2009 at 06:41:47PM -0500, Mel Chua wrote:
Rodrigo and I talked a bit about FUDCon LATAM today, and how the upcoming Events FAD might be able to help it out.
For transparency-ness, here are meeting notes/logs - this was entirely spontaneous/unplanned, but when we realized we were talking about things that should be logged, we move to channel and logged it.
http://meetbot.fedoraproject.org/fudcon-planning/2009-12-17/fudcon-planning....
This also raises two interesting questions:
(1) Local FUDCons will be planned - and run - in local languages. How can we keep FUDCon planning in sync, given this? How much do we want to worry (at the moment) about translating FUDCons, bringing people from other regions in as guests to a region's FUDCon, etc?
There are really two separate aspects to translation in the context of FUDCon as a global event -- what happens during planning, and what happens during execution. During planning, we need to be able to communicate effectively in English between all planners, as the lingua franca of the Fedora Project. This seems pretty reasonable and, I think, expected by people who work in the project anyway. There's no other way for us to keep in sync other than to speak one language while doing so.
I think this greatly depends on who is doing the majority of the planning. Will FUDCon LatAm, for instance be planned 50-50 by people in Latin America and people in North America? If so, English may be the lingua franca between the participants. OTOH, if 90% of the planners are from LatAm then it may be that Spanish is a better choice for the language.
In Europe, where there's a multitude of local languages, English may be a good language to standardise on but that's not necessarily the same for all of the regions that will host FUDCons.
If we want this list to serve as a place where we can grow the number of people who can learn from the process of planning a FUDCon, we need to be able to communicate in a singular language. That process isn't as likely to change drastically from region to region, as opposed to the content, which does. The establishment of this list and the opening of the process was a brilliant stroke by Mel Chua to increase the Project's capacity handling in the area of FUDCons. Right now we're in an excellent position to grow the number of people who can take shared responsibility for FUDCon planning, and while the amount of oversight required is still significant, I see it dropping over time, which is just as it should be.
However, that need could decrease quite a bit if a group was able to plan and fund a FUDCon completely without assistance from the Community Architecture team. That is always a possibility of course! So your point is well taken.