89 lines
5.7 KiB
HTML
89 lines
5.7 KiB
HTML
<html><head><title>FreeCAD development model project</title><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><link type='text/css' href='wiki.css' rel='stylesheet'></head><body><h1>FreeCAD development model project</h1></div>
|
|
|
|
<div id="mw-content-text" lang="en" dir="ltr" class="mw-content-ltr"><div class="mw-parser-output"><p>This page is toward the transition of the FreeCAD code in a GIT repository and a more capable development model. It follows the rules of the <a rel="nofollow" class="external text" href="http://en.wikipedia.org/wiki/GTD#GTD_methodology%7C">Getting things done</a> process. The projects are collected in the <a href="Development_roadmap.html" title="Development roadmap">Development roadmap</a>.
|
|
</p>
|
|
<div id="toc" class="toc"><div class="toctitle"><h2>Contents</h2></div>
|
|
<ul>
|
|
<li class="toclevel-1 tocsection-1"><a href="#Purpose_and_principles"><span class="tocnumber">1</span> <span class="toctext">Purpose and principles</span></a></li>
|
|
<li class="toclevel-1 tocsection-2"><a href="#Outcome"><span class="tocnumber">2</span> <span class="toctext">Outcome</span></a></li>
|
|
<li class="toclevel-1 tocsection-3"><a href="#Brainstorming"><span class="tocnumber">3</span> <span class="toctext">Brainstorming</span></a>
|
|
<ul>
|
|
<li class="toclevel-2 tocsection-4"><a href="#Git"><span class="tocnumber">3.1</span> <span class="toctext">Git</span></a></li>
|
|
<li class="toclevel-2 tocsection-5"><a href="#Development_mailing_list"><span class="tocnumber">3.2</span> <span class="toctext">Development mailing list</span></a></li>
|
|
<li class="toclevel-2 tocsection-6"><a href="#Clarify_responsibilities"><span class="tocnumber">3.3</span> <span class="toctext">Clarify responsibilities</span></a>
|
|
<ul>
|
|
<li class="toclevel-3 tocsection-7"><a href="#Step_ups"><span class="tocnumber">3.3.1</span> <span class="toctext">Step ups</span></a></li>
|
|
</ul>
|
|
</li>
|
|
</ul>
|
|
</li>
|
|
<li class="toclevel-1 tocsection-8"><a href="#Organizing"><span class="tocnumber">4</span> <span class="toctext">Organizing</span></a></li>
|
|
<li class="toclevel-1 tocsection-9"><a href="#Next_actions"><span class="tocnumber">5</span> <span class="toctext">Next actions</span></a></li>
|
|
</ul>
|
|
</div>
|
|
|
|
<h2><span class="mw-headline" id="Purpose_and_principles">Purpose and principles</span></h2>
|
|
<p>This project aims to define a new development and governance model for FreeCAD.
|
|
We come to point where one SVN repository is hard to govern. Working with patches
|
|
is annoying and complicated for people willing to contribute code.
|
|
To give everyone write access to the SVN repo dangerous. People can
|
|
unintentional break something in the base system or force tasty decisions.
|
|
</p><p>So I look at the Linux development process, which is maybe at the moment
|
|
too big for our shoes, but never the less! Which means Git as distributed
|
|
version control system (DVCS), mailing lists and submaintainers (lieutenants).
|
|
</p>
|
|
<h2><span class="mw-headline" id="Outcome">Outcome</span></h2>
|
|
<h2><span class="mw-headline" id="Brainstorming">Brainstorming</span></h2>
|
|
<h3><span class="mw-headline" id="Git">Git</span></h3>
|
|
<ul><li> Using Git as new version control system</li>
|
|
<li> Keeping SVN (at least for while)
|
|
<ul><li> use it as some kind of release repository to keep the ppa work flows and the nice revision numbers</li>
|
|
<li> restrict SVN writes to Werner, Yorik and Jurgen (official tree)</li>
|
|
<li> all other things, like development, branches, experiments go into Git!</li>
|
|
<li> <b>Option:</b> switch completely to Git
|
|
<ul><li> would give some collaterals in version numbering and ppa builds.... </li></ul></li></ul></li>
|
|
<li> give write rights (push) to everyone interested in</li></ul>
|
|
<h3><span class="mw-headline" id="Development_mailing_list">Development mailing list</span></h3>
|
|
<p>The forum has its limitation, I would use the one or more mailing lists to
|
|
manage branches and pull requests. That has advantages:
|
|
</p>
|
|
<ul><li> can work off-line</li>
|
|
<li> use powerful search of the mail client</li>
|
|
<li> no restrictions in attachments and sizes </li></ul>
|
|
<h3><span class="mw-headline" id="Clarify_responsibilities">Clarify responsibilities</span></h3>
|
|
<p>We will soon become more and more developers and user will have conflicting feature requests.
|
|
We have to have structure and responsibilities to filter and decide such requests and incoming
|
|
code.
|
|
</p>
|
|
<h4><span class="mw-headline" id="Step_ups">Step ups</span></h4>
|
|
<pre>Adrian Przekwas:
|
|
Publicity - G+, Youtube,
|
|
Tutorials - <a rel="nofollow" class="external free" href="http://freecad-tutorial.blogspot.com">http://freecad-tutorial.blogspot.com</a>
|
|
Translation (unsure) - Polish (Wiki, Crowdin)
|
|
</pre>
|
|
<pre>Yorik van Havre:
|
|
Software: arch module, draft module, artwork
|
|
Documentation: general wiki organization and design
|
|
Translation: french, dutch, brazilian portuguese
|
|
Publicity: articles on <a rel="nofollow" class="external free" href="http://yorik.uncreated.net/guestblog.php">http://yorik.uncreated.net/guestblog.php</a>, G+, facebook
|
|
</pre>
|
|
<h2><span class="mw-headline" id="Organizing">Organizing</span></h2>
|
|
<p>Decided rules and information goes to the <a href="FreeCAD_development_model.html" title="FreeCAD development model">FreeCAD development model</a> document.
|
|
</p>
|
|
<h2><span class="mw-headline" id="Next_actions">Next actions</span></h2>
|
|
<div style="clear:both"></div>
|
|
</div>
|
|
|
|
|
|
|
|
</div>
|
|
|
|
</div><div class="printfooter">
|
|
Online version: "<a dir="ltr" href="https://www.freecadweb.org/wiki/index.php?title=FreeCAD_development_model_project&oldid=122797">http://www.freecadweb.org/wiki/index.php?title=FreeCAD_development_model_project&oldid=122797</a>"</div>
|
|
<div id="catlinks" class="catlinks" data-mw="interface"></div><div class="visualClear"></div>
|
|
</div>
|
|
</div>
|
|
<div id="mw-navigation">
|
|
<h2>Navigation menu</h2>
|
|
|
|
</body></html> |