This page is a translated version of the page Help FreeCAD and the translation is 50% complete.

Si te gusta FreeCAD y quieres ayudar a su desarrollo, hay diversas cosas que puedes hacer, incluso si no eres programador. En realidad, hay cosas que hacer para todos: usuarios, usuarios avanzados y programadores:

Work on the documentation

Help us to build, correct and extend this documentation. Correct mistakes, extend or correct pages that are unclear, create new pages if a topic is missing, etc. Contributing to FreeCAD Wiki is easy, at WikiPages you can find the FreeCAD Wiki rules and the help needed to to get you started. To edit the wiki, you will need a FreeCAD Wiki account (the wiki is write-protected to avoid spamming). You can ask for an account on the forum or on the irc channel. Please note that the IRC channel may not be as responsive as the forum.

Algunas áreas en las que será bienvenido tu trabajo:

  • La página de la Lista de comandos y la documentación de todos los comandos de FreeCAD. La mayoría de ellos tiene poca o ninguna información. Por favor refiérete a WikiPages ara ver ejemplos de cómo las páginas de documentación deberían ser.
  • La sección de Tutoriales aún es muy pobre. Si creas algo interesante con FreeCAD, por qué no escribir cómo lo hiciste?

Comparte tus conocimientos de FreeCAD

La comunidad de usuarios que rodea a FreeCAD aún es pequeña, pero ya incluye varios usuarios avanzados que realizan un trabajo muy importante mostrando a los recién llegados como utilizar el software. Si te empiezas a sentir cómodo con FreeCAD, tus conocimientos podrían ser muy apreciados por otros, y podrías contribuir con asuntos importantes , como:

  • Mostrando el trabajo que haces con FreeCAD en este hilo del foro. Puedes publicar capturas de pantalla, e incluso mejor aún, adjuntar adjuntar tus archivos de FreeCAD así otras personas podrán examinarlos y comprender como los hiciste.
  • Grabar vídeos mostrando como hiciste algo interesante en FreeCAD. Estos vídeos normalmente hacen un gran trabajo mostrando el funcionamiento de las nuevas características.
  • Escribe tutoriales describiendo o enseñando algo interesante. Puedes escribir tutoriales en tu propio blog, directamente en nuestra wiki, o incluso en el foro.

Traduce FreeCAD

  • Traduce FreeCAD a tu idioma. Todos los textos de la interfaz de FreeCAD se pueden traducir fácilmente a otros idiomas. Todo lo que necesitamos es alguien que sepa ese otro idioma y quiera ayudar! Actualmente tenemos traducciones en inglés, alemán y francés. Todas las traducciones se realizan online en [crowdin].

For details on translation, see FreeCAD Wiki Translation Process under Localisation.

Translate the documentation

Translating is easy, the FreeCAD wiki supports a Translation plugin which allows to manage translations between pages.

For details on translation, see FreeCAD Wiki Translation Process under Localisation#Translating_the_wiki.

Please be sure to be familiar with the WikiPages style guide, which includes rules for good translations.

The Help Editing page provides some information on editing.

Ayuda a otros a conocer FreeCAD

  • Habla de FreeCAD a otras personas que puedan estar interesadas
  • Encuentra usos interesantes para FreeCAD, y documentalos, por ejemplo con capturas de pantalla. FreeCAD es muy joven, y no hay muchas personas que hayan visto lo que pueden hacer con él. Si ya eres un seguidor de FreeCAD, seguramente conozcas algunas cosas interesantes que puede hacer FreeCAD. Ayúdanos a mostrárselo a los demás!
  • Participa en los foros, y ayuda a los nuevos usuarios a resolver cuestiones básicas
  • Escribe tutoriales, graba vídeos, etc... mostrando lo que haces con FreeCAD
  • Contribuye con archivos, dibujos, etc... Aún nos faltan buenos archivos de ejemplo de lo que se puede hacer con FreeCAD

Report bugs and ask for interesting features

Although the place to report confirmed bugs and suggest new features is eventually the FreeCAD Tracker, please always post bug reports and feature requests to the Help forum first. In order to save developers time (triaging and handling hard to understand bugs can be very time consuming), and avoid frustrations because your issue was not handled the way you would like, please read the following:

  • Bugs and features requests are handled in the same tracker. Just mark your issue as "bug" (something that doesn't work as it should) or "feature" (something that is not there but you think it would be good to have)
  • Although originally you could submit issues anonymously, unfortunately this had to be cancelled due to spam. Now if you would like to create/edit tickets you will have to create an account. You will then by default be notified when someone adds notes to the issue. In many cases, the person who will handle the bug will need more information from you.
  • When reporting a bug, the most important point is to allow developers to reproduce it. Be sure to include the exact steps needed to make the bug happen, so another person can do the same and see the bug happen on his machine too. If the developer cannot see the bug, he cannot solve it either.
  • Also include information that can help developers to situate the problem, like the operating system you are running FreeCAD on, the exact version of FreeCAD and the relevant libraries. Please post all the data by using the "copy to clip board" button in the Help (menu) -> about FreeCAD dialogue, and do this from the Part or PartDesign workbench.
  • No matter how sure you are that you have found a bug, please always discuss bugs first in the Help forum.
  • Before submitting a feature request, always discuss it with other users first on the Open discussion forum, so you might end up with a more solid proposal, with more chances to interest a developer to implement it.
  • Remember that FreeCAD is developed by volunteers who use their free time to work on it. Although everyone tries his best to make the best possible application, your bug report might be treated with low priority, or cancelled if you cannot give sufficient information, and your feature request might be postponed or even refused if no developer has interest in implement it or if that would request unrealistic amount of work.

Diseña material gráfico

Mira la página del Material gráfico para ver las directrices sobre el diseño de iconos para FreeCAD.

Program!

Writing code for FreeCAD is not hard, and you don't need any permission, you can start right now to work on something you want, then submit a patch on the tracker or request a merge from a git branch. But to avoid some headache you should meet the following prerequisites first:

  • FreeCAD goes at its own pace, and has a very small team of developers. We have not as much time as we would like to dedicate to FreeCAD, and things are not planned ahead, they are done when some developer sees it fit and when he finds time to do it. So we don't maintain a list of tasks to be done. It is up to you to find something you would like to do, for example a defect you would like to correct, or a small feature you think is missing. The tracker also contains some items that are not yet assigned to anybody.
  • Before you start to code for FreeCAD, you must know well how FreeCAD works. This seems obvious, but if you don't know how it is supposed to work you won't know what to do internally or how to do it.
  • Almost everything can be done either in python or C++. The internals work almost the same in both languages. We suggest you read through the Power users hub pages, even if you're going to code in C++, since it will give you a good overview of the internals.
  • If you are going to work in C++, make sure you can compile FreeCAD without problems first.
  • Present yourself to other developers. FreeCAD is before anything a social project, we discuss a lot of things on the forum before implementing it, and it's always best to discuss your ideas and tell people what you are planning to do before actually doing it. We also have an IRC channel, but the forum is the one and only place where you can meet all the developers.
  • Since 2016, FreeCAD is also participating to the Google Summer of Code. Be sure to check our ideas there if you are interested in participating in a next edition.
Other languages:
čeština • ‎Deutsch • ‎English • ‎español • ‎français • ‎italiano • ‎polski • ‎português • ‎português do Brasil • ‎română • ‎русский • ‎svenska • ‎українська • ‎中文(台灣)‎