Hi Chris, I was thinking on a mixed approach: while the basic guidelines to get started with the project would be translated, to ease the learning curve at the beginning, the more advanced and specific documentation would be the original in English, and the Spanish documents will point to them.
However, as I said, we think that the Spanish community (and I guess it happens the same to others) has specific issues and areas of interest that sometimes differ from the general community. We think that, rather than discuss those topics in a separate place, having a section in the project wiki will help adopters to understand that there's a full integration into the community and to get used to browse the official site. From our position in UVigo we will keep track of those discussions and bring interesting discussions, topics, etc. to the main list. As the community grows, I believe we will not be the only ones to do so. After all, the most active Spanish adopters are also subscribed to the general mail lists, but they still prefer to communicate through the "opencastES" list because, I assume, they feel more comfortable in their own language. We certainly do NOT want to create a parallel wiki. This is not a mere translation, but a starting point for newcomers, in their own language. Of course, the official language in the Community is English, and as their interest in being an active part of it grows, they'll have to accept that, too. As I tried to explain (though perhaps I failed to do so), we do not mean to "break" the community, but exactly the opposite. Best regards Rubén 2011/9/19 Christopher Brooks <[email protected]> > On Mon, 19 Sep 2011 18:21:20 +0200 > Rubén Pérez <[email protected]> wrote: > > > I look forward to hearing your responses, criticism and, if any, > > praise on this #proposal. > > Ruben, > > My only comment is that I worry that it will rapidly fall out of date. > This is my worry with all documentation that is not based on code > artifacts; that they will fails to represent the actual system, and > instead represent the system at some time in the past. We mitigate > this by tagging our release docs with the version number (a good thing > I think), but it's still an error prone process. > > Don't know how to mitigate this when it comes to a translation, but I > think that's the biggest hurdle you will face. > > (and, is it a translation of the wiki, or is it different from a > translation? if it's just a translation then sharing the space is > certainly the way to do it. if it's going to have original content > though, I'd prefer to separate the spaces) > > Chris > -- > Christopher Brooks, BSc, MSc > ARIES Laboratory, University of Saskatchewan > > Web: http://www.cs.usask.ca/~cab938 > Phone: 1.306.966.1442 > Mail: Advanced Research in Intelligent Educational Systems Laboratory > Department of Computer Science > University of Saskatchewan > 176 Thorvaldson Building > 110 Science Place > Saskatoon, SK > S7N 5C9 >
_______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
