Developers/Projects/lang-es

  For Developers

Please copy/paste "{{Translationlist | xx | origlang=en | translated={{{translated}}}}}" (where xx is ISO 639 language code for your translation) to Developers/Projects/lang-es/translations

HowTo [ID# 256845]  +/-

Previo Siguiente

Esta sección intenta ayudar a contestar tus preguntas "Donde debo empezar?". La OLPC es un proyecto enorme con miles de personas trabajando en el, ya sea directamente, o en un proyecto que se alimenta de este. Ya que estas leyendo este documento asumiremos que quieres trabajar directamente en el proyecto de la OLPC, en vez de que uno de los proyectos que dependen de este.

Muchos de los nuevos desarrolladores que probablemente quieran trabajar en una Actividad (una aplicación individual) para el desarrollo a usuarios finales (normalmente niños). Siempre estamos buscando ayuda para el sistema core (ejemplo Sugar, Journal, Bitfrost, School Server), particularmente para programadores avanzados de Python y gente interesada en la documentación y traducciones.

Proyectos existentes

Software projects describes the currently active projects that may need help. Note that the list there is maintained by the project owners, so while we say "active", some of the projects may be hanging in limbo. If you attempt to contact the owner and they do not respond or indicate they are no longer working on the project, speak up on the Devel list and we will attempt to figure out how to move the project forward.

If you are looking for a mature project to join, the various Activities already available on/for the XO may need help. While Software projects includes many projects that have barely started, Activities are the projects which already have public (child) facing releases. Bug fixing, testing, documentation, translations and the like are always highly sought-after contributions in these mature projects.

Nuevos Proyectos

Si estas viendo como comenzar tu propio proyecto, existen muchos requisitos que aun no se han cubierto. O quizas ya tienes una idea que quieras hacer. De cualquier forma, leer esta discusión de como integrar tu proyecto dentro del proyecto de OLPC.

Proyectos bases

Existen solo cierto espacio en una laptop OLPC-XO (o cualquier laptop similar), y la opción de que Actividades deben ser incluidas en la imagen base esta involucrada. Las metas para una actividad del cual forma parte de la base entregada a todos los hijos que de ser así:

1. Impacto epistemológico — a que grado esta actividad impacta positivamente el aprendizaje? (Esta desde luego el criterio mas importante.)
2. Divertido—esto es invertido? envolvente o adictivo?
3. Calidad—Es la actividad lo suficientemente robusta, o su implementación, no compromete la integridad y capacidades del sistema? Es la calidad global de la implementación la adecuada y que llegue a nuestros estándares? Puedes involucrar a la comunidad en el proceso de pruebas y "garantizar" el mantenimiento de la actividad?
4. Sugarizado—a que medida la actividad ha sido integrado dentro de Sugar, incluyendo UI, Diario, seguridad, internacionalización, etc? La actividad requiere la dependencia de sus librerías dentro librerías y recursos? (Este tiene impacto de robustes-positiva y negativo-soporte, inflado, y la usabilidad general, estética, y percepción de calidad en la maquina.)
5. FOSS—es la actividad y todas las dependencias abiertas y libres?
6. Extensibles—si la actividad algo que la comunidad pueda extender? Atiende a múltiples necesidades? (Y tiene-o el potencial de tener- el soporte de una comunidad con el tiempo?)
7. Singularidad—si la actividad agrega una mejora única a la base?
8. Expectativa—does the activity meet the expectations of (children, teachers, parents, G1G1 audience, etc.)?
9. Discoverable—is the core activity discoverable? (This is not to say that it shouldn't be hard work to fully exploit the power of an activity, but it should have a low barrier to entry.)

If you are interested in eventually making your activity a core component of the OLPC, you should keep these targets in mind throughout your development process.

Ver: Hilo original

Registrando una idea

Si tienes una buena idea para un nuevo proyecto, seria genial que la agregaras a la zona de ideas de Software o hardware, para que no se pierda. Considera la opción de añadir información de contacto para que la gente interesada pueda ponerse en contacto contigo y comparta ideas o haga preguntas.

Trata de mantener la idea en una linea o dos. Si se necesita más espacio, se puede publicar en una nueva pagina del wiki, en donde se puede describir mas detalles. If you intend to work on the project yourself, this can become the homepage for your project eventually.

Al registrar la idea antes de empezar el trabajo, podemos asegurar que no se pierde porque "la vida la puso en el camino"

Encontrando ideas

The obvious result of recording a great new project idea on the Software ideas page is that if you are looking for a new project idea, there are lots of them.

If you find an idea on the software ideas page, remember that lots of other people have probably read that page and may also be intending to work on that project. Be sure to advertise your intention to work on the project loudly so that you can flush anyone working on it silently out of the woodwork.

If the requirements are not clear, consider contacting the person who posted the request to get more information about what they were intending. Even if the requirements seem clear, consider contacting the person. Even if you wrote the requirements, consider discussing the requirements in public so that you can get input and feedback on what/how/whether the project should or could be done.

Escogiendo/Refinando tu Idea

OLPC is not just a fancy hardware platform for kids to use — it is also a rethinking about how to use a computer as an educational tool. To that end, there are several design principles to keep in mind as you think about your activity. In particular, activities should include:

• Discoverability — Is the activity intuitive to learn? Long instruction manuals are boring to read and hard to translate. The more intuitive you can make your activity's interface, the better. That means using an interaction model that encourages experimentation, using evocative images on buttons rather than text, etc.
• Extensibility — Can the activity be easily edited by teachers and kids to expand its use? For example, does your quiz activity give teachers the ability to change the questions, so that they can use it for any type of quiz question, not just the ones you thought of?
• Collaboration — Can your activity be used by more than one child at a time? Great activities should have both a single-user mode and a multi-user mode, if that makes sense with the activity. Is your game multiplayer? Does your word processor let two people write the same document?

These are core principles in the XO's Sugar user interface; it is worth looking at the OLPC human interface guidelines and the educational activity guidelines for more detailed discussions of what type of activity we are looking for.

Also, look at existing activities to find out what is already going on and what type of software is being developed.

Comenzando un proyecto

There are some basic steps you should take to start your new project and get it to the point where children are using it on their laptops:

• Announce your project before you even start work
  • So that people know what you are working on and can potentially help you out
  • In case someone else is already working on a similar project
• Add your project to Software projects
  • Add your contact information so that potential collaborators can reach you
  • Homepage (e.g. a page on the wiki with a full description of the project)
• Write a few lines of Code (say 10)
• Set up Source Code Control and Bug Tracker (See: #Project Hosting below)
  • Be sure you have a public bug tracker available somewhere, think millions of users, there will be bug reports!
• Code
  • Remember to use source control, lost work sucks
• Distribute under these licenses (where possible)
  • GPL, LGPL or the MIT license for software
  • CC-BY, CC-BY-SA, or the GFDL for text and media
  • A more comprehensive guide to Software licensing is available
• Test your application in an official image (preferably on a physical laptop) before publishing broadly
  • People will often test new code on their OLPC-XO if you don't have one
• When ready to face real users (children) add your activity to the Activities page to allow for easy download and installation

Hospedaje de proyecto

The OLPC Developers Program can provide Project hosting for OLPC-compatible projects, especially XO-specific projects. These services allow you to run your entire OLPC development project off of the OLPC servers.

For more general Sugar-based projects, see the resources at http://wiki.sugarlabs.org/Activity_Team and http://git.sugarlabs.org.

You are not required to use the OLPC's project hosting services, there are numerous other hosting services, such as:

• Sugar Labs
• SourceForge
• GNU Savannah
• Google Code

or you can host your code on your own or your project's servers. Please keep in mind, though, that having your source code and ticket tracking engines publicly available is very important.

Note the OLPC servers are public and anyone can see anything you put on them. Do not put anything into your project repository (or the wiki, or the ticket tracker) which is proprietary, security-sensitive, or for which you do not hold the rights required to release publicly!

Espacio de Wiki

The main OLPC Wiki can be used to set up your project's home page. This allows you to collaborate on the layout and setup of your project with both other members of your team and the wider OLPC community.

Control de código fuente

Source Code Control (SCC) is critically important for any software project. The Developer's Program can provide you with GIT-based SCC. While GIT is neither familiar nor particularly friendly, it is used heavily by the Linux kernel developers, and is correspondingly robust. It allows for a distributed repository (similar to the Linux Kernel) or a central tree (like traditional SCC systems).

Users familiar with more traditional SCC systems should read the Git-SVN crash course, do not expect to be able to "work it out" just by trying to do things, GIT does not try to be user-friendly and does a very good job of not being intuitive.

Siguiendo tickets

Ticket Tracking is similarly important in any software project. You need a way for users to report problems in a way that prevents issues from being lost or ignored. The Developer's Program provides a Trac-based ticket-tracking system which is reasonably straightforward to use.

See: Importing your project for a detailed description of how to use the Project hosting facilities

Previo Siguiente