|
1 | 1 | <?xml version="1.0" encoding="utf-8"?> |
2 | | -<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>FreeCAD Development Blog (Posts by FreeCAD Community)</title><link>https://freecad.github.io/</link><description></description><atom:link href="https://freecad.github.io/authors/freecad-community.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><copyright>Contents © 2018 <a href="mailto: [email protected]">FreeCAD Community</a> </copyright><lastBuildDate>Sun, 23 Sep 2018 11:29:22 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Summary of FreeCAD Development so far</title><link>https://freecad.github.io/posts/09-07-2018-Summary/</link><dc:creator>FreeCAD Community</dc:creator><description><div><p>Greetings to all FreeCADers, this post is created by a FreeCAD volunteer to keep the community up to date about how 0.18 development is progressing. Since FreeCAD has a pretty long release cycle (the team has decided on a yearly cycle) |
| 2 | +<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>FreeCAD Development Blog (Posts by FreeCAD Community)</title><link>https://freecad.github.io/</link><description></description><atom:link href="https://freecad.github.io/authors/freecad-community.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><copyright>Contents © 2019 <a href="mailto: [email protected]">FreeCAD Community</a> </copyright><lastBuildDate>Mon, 11 Mar 2019 19:50:48 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Introduction to FreeCAD development</title><link>https://freecad.github.io/posts/introduction-to-freecad-development/</link><dc:creator>FreeCAD Community</dc:creator><description><div><p>Have you ever wanted to contribute back to the project? Let us help you getting started!</p> |
| 3 | +<p>If you want to contribute, write a thread about what you want to do in the developers corner and we will do our best to get you going. This post provides a brief overview of our workflow.</p> |
| 4 | +<div class="section" id="forum"> |
| 5 | +<h2>Forum</h2> |
| 6 | +<p>The FreeCAD forum: <a class="reference external" href="https://forum.freecadweb.org/">https://forum.freecadweb.org/</a> is the primary place for communication between FreeCAD users as well as developers. |
| 7 | +This should be the first place to search for answers if you have any questions.</p> |
| 8 | +<p><strong>Note:</strong> When you create a forum account, it might take a while before it's activated as the process is currently manual. This is done to limit spamming.</p> |
| 9 | +</div> |
| 10 | +<div class="section" id="issues-tickets"> |
| 11 | +<h2>Issues/Tickets</h2> |
| 12 | +<div class="line-block"> |
| 13 | +<div class="line">FreeCAD uses <a class="reference external" href="https://mantisbt.org/">MantisBT</a> as its tracker for bug reporting and feature requests.</div> |
| 14 | +<div class="line">The FreeCAD tracker address is <a class="reference external" href="https://freecadweb.org/tracker/">https://freecadweb.org/tracker/</a></div> |
| 15 | +<div class="line"><strong>Note:</strong> In order to create issues you will have to create an separate MantisBT account.</div> |
| 16 | +</div> |
| 17 | +<p>As we are getting a lot of reports please follow the rules before creating a new issue</p> |
| 18 | +<ol class="arabic simple"> |
| 19 | +<li>Make sure you're using the most updated stable or development versions of FreeCAD.</li> |
| 20 | +<li><strong>PLEASE PLEASE PLEASE</strong> post to FreeCAD forum to verify the issue.</li> |
| 21 | +<li>Only after community vetting, open a ticket and link said thread to ticket and vice-a-versa.</li> |
| 22 | +<li>Post your <strong>Help&gt;About FreeCAD&gt;Copy to clipboard</strong> version info in to forum thread and ticket.</li> |
| 23 | +<li>Post a Step-By-Step explanation on how to recreate the issue.</li> |
| 24 | +<li>If possible, upload an example file to demonstrate problem.</li> |
| 25 | +<li>If there is a crash involved, please consider <a class="reference external" href="https://freecadweb.org/wiki/Debugging">Debugging</a> and attaching the traceback to the ticket.</li> |
| 26 | +</ol> |
| 27 | +</div> |
| 28 | +<div class="section" id="documentation"> |
| 29 | +<h2>Documentation</h2> |
| 30 | +<div class="line-block"> |
| 31 | +<div class="line">FreeCAD uses <a class="reference external" href="https://mediawiki.org">MediaWiki</a> for its documentation. To be able to modify the wiki, you must <a class="reference external" href="https://forum.freecadweb.org/viewtopic.php?f=21&amp;t=6830">request access from the FreeCAD wiki admins</a>.</div> |
| 32 | +<div class="line"><strong>Note:</strong> To get an Wiki account we require you to have a forum account with at least 1 post.</div> |
| 33 | +<div class="line">Before you start changing things in the wiki please read the <a class="reference external" href="https://www.freecadweb.org/wiki/WikiPages">WikiPages</a> guidelines,</div> |
| 34 | +<div class="line">There are several rules on how to write on the wiki to keep it organized, high quality, translated and up to date. It's our practice to discuss the additions/changes one wants to make in the <a class="reference external" href="https://forum.freecadweb.org/viewforum.php?f=21">FC wiki subforum</a> prior to posting.</div> |
| 35 | +</div> |
| 36 | +</div> |
| 37 | +<div class="section" id="code"> |
| 38 | +<h2>Code</h2> |
| 39 | +<p>The FreeCAD codebase is mostly C++ and Python, we are currently migrating to Python3, new contributions based on Python2.X are frowned upon. |
| 40 | +The git repo is hosted at <a class="reference external" href="https://github.com/FreeCAD/FreeCAD">https://github.com/FreeCAD/FreeCAD</a></p> |
| 41 | +</div> |
| 42 | +<div class="section" id="development"> |
| 43 | +<h2>Development</h2> |
| 44 | +<p>If you're interested developing for FreeCAD please look into</p> |
| 45 | +<ol class="arabic simple"> |
| 46 | +<li>Read the <a class="reference external" href="https://www.freecadweb.org/wiki/index.php?title=The_FreeCAD_source_code">Source code wiki page</a> and check the <a class="reference external" href="https://www.freecadweb.org/api/annotated.html">API reference</a> .</li> |
| 47 | +<li>Creating your own workbench (See <a class="reference external" href="https://www.freecadweb.org/wiki/Workbench_creation">Workbench Creation</a> , <a class="reference external" href="https://www.freecadweb.org/wiki/Module_Creation">Module Creation</a> , <a class="reference external" href="https://github.com/FreeCAD/Workbench-Starterkit">Workbench Starterkit</a> )</li> |
| 48 | +<li>Modifying an existing workbench (View source code of any external workbench at <a class="reference external" href="https://github.com/FreeCAD/FreeCAD-addons">FreeCAD-Addons Repo</a> )</li> |
| 49 | +<li>Creating your own macro (Read more about <a class="reference external" href="https://www.freecadweb.org/wiki/Macros">FreeCAD Macros</a> and the <a class="reference external" href="https://github.com/FreeCAD/FreeCAD-macros">FreeCAD Macros Repo</a> )</li> |
| 50 | +<li>Building FreeCAD and writing C++ code (See <a class="reference external" href="https://github.com/FreeCAD/FreeCAD#compiling">Compiling instructions</a> )</li> |
| 51 | +</ol> |
| 52 | +</div></div></description><guid>https://freecad.github.io/posts/introduction-to-freecad-development/</guid><pubDate>Sat, 10 Nov 2018 21:11:10 GMT</pubDate></item><item><title>Summary of FreeCAD Development so far</title><link>https://freecad.github.io/posts/09-07-2018-Summary/</link><dc:creator>FreeCAD Community</dc:creator><description><div><p>Greetings to all FreeCADers, this post is created by a FreeCAD volunteer to keep the community up to date about how 0.18 development is progressing. Since FreeCAD has a pretty long release cycle (the team has decided on a yearly cycle) |
3 | 53 | this blog then will come in handy for folks that are really wanting to use the vibrant and prolific bleeding-edge of FreeCAD (AKA 'HEAD' or the master branch) where many bugs are being removed (Hopefully! :wink:) and new features being woven in for testing and refinement.</p> |
4 | 54 | <p>It is the intention that there will be a post at the end of each month of FreeCAD development updates. Though that may seem a little ambitious, it may not be far from reality. For example, one of the core developers, Yorik Van Havre, creates a blog post on his <a class="reference external" href="http://yorik.uncreated.net/guestblog.php?tag=freecad">website</a> for his supporters every month with an update regarding his monthly FreeCAD hacking activities. So at the very least we'll figure out a way to link to his blog posts.</p> |
5 | 55 | <p>The main goal of the 0.18dev cycle is to iron out all Python3 and Qt5 incompatibilities.</p> |
|
0 commit comments