55
I think we're addressing another, fundamental issue here, one that is not directly caused by the security issues but is in the heart of the way XOOPS works.
XOOPS has local support and development communities, where great things are happening. The issue here is how can we bring what happens there and what happens here at xoops.org together? If English is a barrier for these local communities, so is Japanese, Portugese, Spanish etc. for those that speak mainly English. So Giba's comment on 'watch what goes on here as language is a barrier for us' goes in two directions. And frankly, the Google/Babelfish translations suck most of the time (Giba's post being a good example of that, it still has essential portugese words mixed in).
Ok, what I'm trying to say here people, is that we share the problem. English still is the main langaueg of the XOOPS.org project, but if possible, I would like to address these issues in a practical manner. How can we communicate changes, additions, policy and so on when language is a barrier?
Any ideas on how to tackle this?
Herko