Bug#361418: [Proposal] new Debian menu structure

[Bill Allombert]

On Sat, Jun 23, 2007 at 01:23:49PM +0200, Bill Allombert wrote:
> On Sat, Jun 23, 2007 at 03:10:38AM -0700, Russ Allbery wrote:
> > Bill Allombert <[EMAIL PROTECTED]> writes:
> > 
> > > Please find the final version for approval.  Of course minor changes
> > > will be allowed in the course of the migration if they only affect a
> > > small number of package.
> > 
> > Could you prepare this as a patch against menu-policy.sgml?

Here it is. Please check it matches the proposed new menu structure.

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 
--- menu-policy-old.sgml	2007-06-23 18:35:20.0 +0200
+++ menu-policy.sgml	2007-06-23 19:46:59.0 +0200
@@ -110,173 +110,367 @@
 	Preferred menu structure
 	
 	  Here is the authoritative list of Debian's menu
-	  structure. Please do not put your packages into any other
-	  sections without asking for permission first!
-	
+	  structure. Packages must be placed in leaf sections.
+ 	
 	
-	Apps
+	Applications
 	
-	  normal applications
+	  Normal applications
 	  
-		  Databases
-		  
-		interactive database programs
-		  
+		  Accessibility
+   
+Tools to aid people with disabilities or for machines
+   lacking usual input devices.
+Examples: gok, yasr, dasher.
+  
+  Amateur Radio
+  
+Anything relating to HAM radio.
+Examples: baken, hamsoft, twlog
+   
+  Data Management
+  
+Interactive database programs, collection managers,
+   address books, bibliography tools, etc.
+gaby, alexandria, mdbtools
+  
 		  Editors
 		  
-		text editors, word processors
+Editors, other than office word processors, for 
+   text-based information.
+Examples: ksubtile, nano, hexedit
 		  
 		  Education
 		  
-		educational and training programs
+		Educational and training softwares.
+Examples: gtypist, gcompris, quiz
 		  
 		  Emulators
 		  
-		wine, dosemu, etc.
-		  
+Software that allows you to run non-native
+software or more than one OS at a time.
+Examples: wine, dosemu, qemu
+		  
+  File Management
+  
+Tools for file management, archiving,
+searching, CD/DVD burning, backup, etc.
+Examples: file-roller, mc, baobab
+  
 		  Graphics
 		  
-		image manipulation
-		  
-		  Hamradio
-		  
-		anything relating to ham radio
-		  
-		  Math
-		  
-		math related programs
-		  
-		  Net
-		  
-		network programs that don't fit elsewhere
+2D and 3D graphics manipulation software.
+Examples: gimp, inkscape, imagemagick
 		  
+  Mobile Devices
+  
+Software that allows you to interface with mobile
+   devices (phones, PDAs, etc.).
+Examples: kandy, gnokii, gnome-pilot
+  
+  Network
+  
+Network related software. This is a three-level
+section, do not put entries directly here.
+
+Communication
+
+  Mail, USENET news, chat, instant messaging,
+ IP telephony, video conferencing software, etc.
+  Examples: xchat, gaim, mutt
+
+File Transfer
+
+   File transfer software such as download
+  managers, FTP clients, P2P clients, etc.
+   Examples: amule, gftp, d4x
+
+Monitoring
+
+   Network monitoring software
+   Examples: gip, ettercap, iptstate
+
+Web Browsing
+
+   Web browsers, tools for offline browsing, etc.
+   Examples: elinks, epiphany-browser, webhttrack
+
+Web News
+
+  Web feed (RSS, Atom, etc.) and podcast aggregators.
+  
+  Examples: akregator, kitty, liferea
+
+
+  
+  Office
+  
+  Office suites, word processors, spreadsheets,
+ CRM, ERP, financial sofware, etc.
+  Examples: openoffice.org, tinyerp-client, gnucash
+  
 		  Pr

New policy

[Giacomo Catenazzi]

Hello list!

I followed Manoj talk at DebConf7, and I would like to help.

I'm trying to find and write down some idea, but they
inevitably give me some questions:

1- Is available already a starting document?

2- some guidelines about docbook?

3- what is the scope?
   It should be like actual document, a technical
   description of debian packages, or it should include
   also the social contract, the DD behaviour about bugs, ...

   I think it is difficult to split the two part
   (DD GPG-keys in packages; severity of bugs affect the priority
   of packages; changelog, ...)
   But OTOH, it will be a more difficult and long project.

4- It should be Debian specific or split into neutral and
   debian part?

   IMHO we are debian, so we should document debian,
   but it will pitty if Ubuntu and other organization will
   use a different (and probably not updated) version of
   .deb

   I like that RPM is pretty distribution neutral.

   OTHO if it can be used externally will complicate the
   policy process, it should be open to third parties, and
   it will complicate the live of DD (informations are split
   into two part)

ciao
cate


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#361418: [Proposal] new Debian menu structure

[Bill Allombert]

On Sat, Jun 23, 2007 at 03:10:38AM -0700, Russ Allbery wrote:
> Bill Allombert <[EMAIL PROTECTED]> writes:
> 
> > Please find the final version for approval.  Of course minor changes
> > will be allowed in the course of the migration if they only affect a
> > small number of package.
> 
> Could you prepare this as a patch against menu-policy.sgml?

I will prepare it.  

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#361418: [Proposal] new Debian menu structure

[Russ Allbery]

Bill Allombert <[EMAIL PROTECTED]> writes:

> Please find the final version for approval.  Of course minor changes
> will be allowed in the course of the migration if they only affect a
> small number of package.

Could you prepare this as a patch against menu-policy.sgml?

-- 
Russ Allbery ([EMAIL PROTECTED])   


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#361418: [Proposal] new Debian menu structure

[Russ Allbery]

Bill Allombert <[EMAIL PROTECTED]> writes:

> Well It is two week now, and I did not get a single answer. Should I
> consider that as a nihil obstat ?

Sorry about this.  Figuring out how to move forward with Policy was the
topic of much discussion at DebConf, but also since both Manoj and I are
here and pretty busy with talks, I hadn't had a chance to look at the
mailing list much.

I think this proposal has definitely had sufficient discussion, and the
impression that I had was that it had reached consensus.  Given that, I
see no reason for it to not go into the next version of Policy.

We're going to start using a new Policy process (Manoj is going to send
out a writeup), and I'm not sure if we want to start that for the next
release or do one final cleanup release with some obvious pending stuff
and then start.  I personally think I'd prefer the latter, including this,
probably the parallel build language, and a few other things that had
already been discussed and which are basically done.

Manoj, what's your feeling on this?

-- 
Russ Allbery ([EMAIL PROTECTED])   


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#361418: [Proposal] new Debian menu structure

[Bill Allombert]

On Sat, Jun 09, 2007 at 07:10:12PM +0200, Bill Allombert wrote:
> Dear developers,
> 
> I would like to go forward soon with the proposed menu structure change.
> Actually I should have done that two months ago, so I would like to
> catch up a bit.
> 
> Please find the final version for approval.  Of course minor changes
> will be allowed in the course of the migration if they only affect a
> small number of package.
> 
> I would like to start the translation soon.

Well It is two week now, and I did not get a single answer. Should I
consider that as a nihil obstat ?

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]