Final common discussion
From My Wiki
From the report-backs
- Portal with information of tools, use cases, etc.
- Use guide for tools, not a good description to know if they're useful for their purposes.
- Project commitments, integrations.
- Using common standards is the way to get interoperability.
- Plugins developed for CMSs to generate po files. Developers band together to create them.
Cross-collaboration between developers and content people
- Developers tend to work in a walled garden. Push power to the edge, minimize ownership. Democratize access to production.
- Find a way to draft the conclusions to got in this event. Go drawn to draw the lines of the tools we need, the tools that exist and what doesn't. What we have now is not the final product, they're not the next steps of what is needed or what we want. It should get drafted.
- Lots of tool makers showing their tools, content people thinking how to integrate tools. There should be content people showing their content to developers so developers could think on how to deal with that content.
- Need to collaborate about making really good, detailed documentation. Keep in mind all levels, internationalization, code, culture etc. Present cases, collect in one place. Many great tools are not being used enough. Both sides need to be part of the process.
- Good APIs, make the tools secondary.
- We've come up with a lot of info on tools and cases. We should plan in the future how to document in a structured way, so other people can access to that info.
- Tool mapping in SSC, two papers.
- One thing that came out is that we bring translators together, especially for small languages. There's not much communication between the people who translate the same languages for different tools. Sharing resources, TMs etc.
- Consider more communication with the poeple who make your translation, so they understand your projects and you get to know each other better.
- The collection of case studies of folks using particular tools or sets or tools would be helpful to feed developers on what's missing, what's difficult, what's easy, etc. Also out to other users in a different format.
Michelle: we talked about the need for a portal or aggregator, and the wiki could be a good starting point, and thinking about what the portal would really look like and what other organisatoins we could link with.
Tomas: we have great toools but they arent used widely; the descriptions of what tools to use in what situations arent there, and the content people who want to make finding the right tool for the right job sounds just like this. a best practice guide so people who start a new project know what to keep in mind from the start would be great. we have projects doing translation and we're hoping they'll merge thanks to this weekend. And we have a big focus on common standards, PO files or at least import-export files. RSS is a standard for moving blocks of content between systems, there isnt a richer web API yet. but import/export of PO files does a great job. And theres potential for collaoration on a PO converter so that peoples strange other formats can go into PO and then out to anything else. So in the next fe wmomths, if we got the top 30 CMS to include some kind of translation tools infrastrucure, that would be great.
Stan: "I'm starting a project, where do I start with translation?" "Here's these tools, heres these cases who did use them already, and heres what we recommend dong." is what the portal should be like
Adam: We have a lot of information here, and in a similar gathering in a similar time span would be good to work out how to best capture the energy and information thats been shared within this room. You could come up with some powerful documents in this way.
Gunner: we'll get the tools mapping up, and I've love to do the annoying part of trying to get someone to fund it. Assuming you're willing to publish under a free culture license ;-)
Ed: There needs to be more communication between all the translators, so they understand each other better and then there will be better translation.
Michelle: If you have a certain workflow, and you think somethings missing, telling developers about that is very important, adna also telling other users as they might not be away of that problem.
Gunner: This is aspiration event #60, and we always have some variation on how to keep the momentum going after the event. Its often an awkward time, people are busy when they get back. We hope to plant some seeds, and for you to have "aha!" moment in the shower in two weeks time, and we hope you now think in more of a collaborative way. Everyone here would like to do this again, and many funders don't see the "ROI" of events like this, so the Open Society Institute has done an amazing job funding this, and Aspiration Tech has time to set up similar events, so please tap us if you want to do something like this for your NGO or Open Content Community.
