Differences between revisions 3 and 4
Revision 3 as of 2013-05-15 15:27:38
Size: 970
Editor: ?ChristianAnders
Comment:
Revision 4 as of 2013-05-15 15:30:15
Size: 980
Editor: ?ChristianAnders
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
and target users of Linux-desktops, newbies as well as experienced developers, with packages already configured to "just work". and target users of Linux-desktops - newbies and well experienced developers alike - with software configured to "just work".
Line 4: Line 4:
All changes in Tanglu should - if possible - flow into Debian. With patches being merged directly into the debian packages or a debian meta-package that contains configuration. All changes in Tanglu should - if possible - flow into Debian. With patches being merged directly into the debian packages or a debian meta-package that contains customized configurations.

We want to provide the latest upstream releases on a time-based release-cycle, and target users of Linux-desktops - newbies and well experienced developers alike - with software configured to "just work".

All changes in Tanglu should - if possible - flow into Debian. With patches being merged directly into the debian packages or a debian meta-package that contains customized configurations.

While Debian is in a freeze, Debian Developers are invited to test their packaging of the latest upstream software on Tanglu. By doing that, Tanglu users get recent software, while Debian gets better-tested packages when the new release cycle starts.

Decisions are made by writing spec pages in the wiki about a new feature and assigning people responsible for implementing the spec. (Obviously, people who volunteer for that) If a proposal is accepted or not is decided at the beginning of a cycle on a public IRC meeting, if no consensus is reached, we will do a vote.