Differences between revisions 12 and 15 (spanning 3 versions)
Revision 12 as of 2018-02-17 17:19:42
Size: 2962
Comment: Add CategoryTeams
Revision 15 as of 2020-06-08 04:22:32
Size: 2791
Editor: PaulWise
Comment: cleanup
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was renamed from 3D-printer
Line 8: Line 9:
 * [[https://alioth.debian.org/projects/3dprinter/|Team page on Alioth]]  * [[https://salsa.debian.org/3dprinting-team|Team page]]
Line 10: Line 11:
 * [[https://alioth.debian.org/plugins/scmgit/cgi-bin/gitweb.cgi?a=project_list;pf=3dprinter|Team packages repository]]
 * [[http://qa.debian.org/developer.php?login=3dprinter-general@lists.alioth.debian.org|Team PTS page]]
 * [[irc://irc.debian.org/%23debian-3dprinting|#debian-3dprinting IRC channel]]
 * [[https://salsa.debian.org/3dprinting-team|Team packages repository]]
 * [[https://qa.debian.org/developer.php?login=3dprinter-general@lists.alioth.debian.org|Team PTS page]]
 * [[ircs://irc.oftc.net/debian-3dprinting|#debian-3dprinting IRC channel]]
Line 28: Line 29:
 * octoprint (ITP - #718591)  * octoprint (ITP DebianBug:718591)
Line 40: Line 41:
The team manages the packaging work with git-buildpackage, repos are stored on alioth.debian.org. The layout is as follow:
 * moszumanska:/git/3dprinter/packages/<package>.git: repo for the team-maintained packages (one repo per package).
 * moszumanska:/git/3dprinter/3dprinter.git: repo for the whole project, used for tools, webpages, etc.
The team manages the packaging work with git-buildpackage, repos are stored on salsa.debian.org. The layout is as follow:
 * 3dprinting-team/packages/<package>.git: repo for the team-maintained packages (one repo per package).
 * 3dprinting-team/3dprinter.git: repo for the whole project, used for tools, webpages, etc.
Line 44: Line 45:
The repos can be browsed at [[https://alioth.debian.org/plugins/scmgit/cgi-bin/gitweb.cgi?a=project_list;pf=3dprinter]] The repos can be browsed at [[https://salsa.debian.org/3dprinting-team]]
Line 46: Line 47:
To push your work to the team repo, create a directory on moszumanska and then add a remote: To push your work to the team repo, create a repository via the website add a remote suggested by the website.
Line 48: Line 49:
{{{git remote add origin ssh://<username>@git.debian.org/git/3dprinter/packages/<package>.git}}}

Please refer to [[3D-printer/gbp]] for more info about packaging with git-buildpackage.
Please refer to the [[/gbp|gbp]] page for more info about packaging with git-buildpackage.
Line 55: Line 54:
Line 65: Line 65:
 * CategoryTeams CategoryTeams

The 3D-Printer Packaging Team

3DPPT takes care of packages related to 3D-printing. It is an open team and everyone interested in its activities can join it. This wiki page sums up some information about team policy, the status of packages we work on and more. Useful links:

If you are looking for informations on *using* 3D printers in Debian, see 3DPrinting

Packages

Programs that are, or should be packaged by the team.

  • cura (including CuraEngine, python-power and libpolyclipping)

  • pronterface
  • RepetierHost

  • RepetierFirmware

  • RepetierServer

  • slic3r
  • repsnapper
  • arduino-mighty-1284p
  • octoprint (ITP 718591)

  • skeinforge

Related programs that are packaged by others, but may be handled by the team in the future, should its current maintainers want a break:

  • arduino
  • arduino-mk
  • avr-gcc
  • avrdude

Repository

The team manages the packaging work with git-buildpackage, repos are stored on salsa.debian.org. The layout is as follow:

  • 3dprinting-team/packages/<package>.git: repo for the team-maintained packages (one repo per package).

  • 3dprinting-team/3dprinter.git: repo for the whole project, used for tools, webpages, etc.

The repos can be browsed at https://salsa.debian.org/3dprinting-team

To push your work to the team repo, create a repository via the website add a remote suggested by the website.

Please refer to the gbp page for more info about packaging with git-buildpackage.

Packaging policy

We are using the following rules for our packages:

  1. We use debhelper.
  2. We use dh in debian/rules, to keep it short and clean.
  3. debian/rules clean removes or restores ALL generated files. (The only exception being debian/po/templates.pot, which has to be generated at the end of clean to make life easier for translators.)

  4. Everything should be built from source. (In particular, packages using autotools should use dh --with dh_autoreconf).

  5. We allow no lintian errors at all, and no lintian warnings where reasonably possible.
  6. Watch files are always present and up to date.
  7. We use DEP-5 copyright files on all packages.
  8. We write verbose changelogs which follow the "where, what, why" rule.


CategoryTeams