Active Topics

 


Reply
Thread Tools
Posts: 2,802 | Thanked: 4,491 times | Joined on Nov 2007
#11
FYI, there's a new package with a "CLI" icon in extras-testing now, so it'd be great if the squad tested that this week instead of thumbing down the old one :-)
 

The Following User Says Thank You to lma For This Useful Post:
Jaffa's Avatar
Posts: 2,535 | Thanked: 6,681 times | Joined on Mar 2008 @ UK
#12
CLI icons are not necessary for daemons which are autostarted (e.g. OpenSSH server). However they are necessary for applications (or servers) which can only be started by launching X Terminal.

So, if openntpd autostarts, is a daemon, and requires no user intervention to get its benefit then (AIUI):
  1. It does not need a CLI icon (or CLI icon badge)
  2. The description needs to be clear that the user doesn't have to do anything as it runs in the background.
__________________
Andrew Flegg -- mailto:andrew@bleb.org | http://www.bleb.org
 

The Following 4 Users Say Thank You to Jaffa For This Useful Post:
Posts: 2,802 | Thanked: 4,491 times | Joined on Nov 2007
#13
Originally Posted by Jaffa View Post
CLI icons are not necessary for daemons which are autostarted (e.g. OpenSSH server).
Furrfu, make up your mind people! I'm way past caring what the actual policy is, as long as we have one that's clear and unambiguous but apparently that's too hard (cf http://wiki.maemo.org/Extras-testing...pplication_.3F).
 
Jaffa's Avatar
Posts: 2,535 | Thanked: 6,681 times | Joined on Mar 2008 @ UK
#14
Originally Posted by lma View Post
Furrfu, make up your mind people! I'm way past caring what the actual policy is, as long as we have one that's clear and unambiguous but apparently that's too hard (cf http://wiki.maemo.org/Extras-testing...pplication_.3F).
And I've argued against it (and been ignored by whoever wrote that), not seen any consensus and it's just plain wrong by reductio ad absurdum. What is the difference between:
  1. OpenSSH server (starts at boot, is secure by asking for a root password on installation, has no other GUI)
  2. Additional multimedia decoders
  3. openntpd

Or even things like Telepathy plugins, Flashlight or the Facebook uploading widget which have no obvious GUI (or icon after installation) and require you to go to some specific part of the platform to discover them. Descriptions are important for all of these, a CLI icon (when they're not accessed through the CLI) is just plain silly.
__________________
Andrew Flegg -- mailto:andrew@bleb.org | http://www.bleb.org
 

The Following 4 Users Say Thank You to Jaffa For This Useful Post:
Jaffa's Avatar
Posts: 2,535 | Thanked: 6,681 times | Joined on Mar 2008 @ UK
#15
If the Testing Squad agrees (and, as I say, there was no consensus beyond "CLI apps should have an icon"), I will modify the wiki.
__________________
Andrew Flegg -- mailto:andrew@bleb.org | http://www.bleb.org
 

The Following 2 Users Say Thank You to Jaffa For This Useful Post:
Posts: 278 | Thanked: 303 times | Joined on Feb 2010 @ Norwich, UK
#16
I'd agree with that. I see no reason for daemon applications to require a CLI icon, though IMO they should state that theyre daemons which don't require any user interaction once installed.
 
VDVsx's Avatar
Posts: 1,070 | Thanked: 1,604 times | Joined on Sep 2008 @ Helsinki
#17
Originally Posted by Jaffa View Post
If the Testing Squad agrees (and, as I say, there was no consensus beyond "CLI apps should have an icon"), I will modify the wiki.
IIRC this discussion was very brief and there was no consensus at that time, one of the arguments were that some daemons can be activated from the command line, or can receive commands, so in order to simplify and don't create more rules we reach this decision.
Feel free to reopen the discussion or write more clear rules that clearly separate daemon/enablers from pure CLI apps.
__________________
Valério Valério
www.valeriovalerio.org
 
Posts: 489 | Thanked: 404 times | Joined on Dec 2009
#18
Hi,
here is the list of apps under testing this week (excluding themes):
From week 14:

http://maemo.org/packages/package_in...eader/0.0.2-2/
http://maemo.org/packages/package_in...t-tor/0.0.4-2/
http://maemo.org/packages/package_in...-widget/0.1-6/
http://maemo.org/packages/package_in...cklet/0.0.1-4/
http://maemo.org/packages/package_in...support/1.0.4/
http://maemo.org/packages/package_in...ntral/1.1.8-0/
http://maemo.org/packages/package_in...ntral/1.1.8-0/

New:
http://maemo.org/packages/package_in...ecipe/0.5.1-3/
http://maemo.org/packages/package_in...s/2.6.6-1nix0/
http://maemo.org/packages/package_in...n/2.6.6-1nix0/
http://maemo.org/packages/package_in...sitrep/0.4-16/
http://maemo.org/packages/package_in...utter/1.0.0-2/
http://maemo.org/packages/package_in...-logger/0.3-1/
http://maemo.org/packages/package_in...dictl/0.0.1-2/
http://maemo.org/packages/package_in...pattern/1.0.0/
http://maemo.org/packages/package_in...sh-l10n/1.0.0/
http://maemo.org/packages/package_in...ziggy/0.1.8-2/
http://maemo.org/packages/package_in...eloper/1.6.12/
http://maemo.org/packages/package_in...btexter/0.7.8/
http://maemo.org/packages/package_in...pwsafe/1.6.3c/
http://maemo.org/packages/package_in...rreco/0.3.0-1/
http://maemo.org/packages/package_in...eller/1.0.1-3/

With clear faults/bugs (can be voted down):

http://maemo.org/packages/package_in...maemo/1.0.0.8/
http://maemo.org/packages/package_in...maemo/1.0.0.7/
http://maemo.org/packages/package_in...inparty/0.5-2/
http://maemo.org/packages/package_in...-5-fremantle5/
 
Jaffa's Avatar
Posts: 2,535 | Thanked: 6,681 times | Joined on Mar 2008 @ UK
#19
Originally Posted by VDVsx View Post
IIRC this discussion was very brief and there was no consensus at that time, one of the arguments were that some daemons can be activated from the command line, or can receive commands, so in order to simplify and don't create more rules we reach this decision.
Feel free to reopen the discussion or write more clear rules that clearly separate daemon/enablers from pure CLI apps.
Consider the discussion reopened ;-)

Clear rules:
  • An application MUST use the standard CLI icon, or the standard CLI badge over an alternative icon, if the user must use X Terminal to start the main purpose of the application.
  • Packages which auto-start in a secure manner, or enable alternative functionality in other applications, SHOULD NOT use the CLI icon, as interaction with them through the CLI is not required.
  • Any daemon which auto-starts MUST NOT provide a trivial attack vector, and so SHOULD (for example) prompt for a password during installation.
__________________
Andrew Flegg -- mailto:andrew@bleb.org | http://www.bleb.org
 

The Following 4 Users Say Thank You to Jaffa For This Useful Post:
GeneralAntilles's Avatar
Posts: 5,478 | Thanked: 5,222 times | Joined on Jan 2006 @ St. Petersburg, FL
#20
Originally Posted by Jaffa View Post
Clear rules:
  • An application MUST use the standard CLI icon, or the standard CLI badge over an alternative icon, if the user must use X Terminal to start the main purpose of the application.
  • Packages which auto-start in a secure manner, or enable alternative functionality in other applications, SHOULD NOT use the CLI icon, as interaction with them through the CLI is not required.
  • Any daemon which auto-starts MUST NOT provide a trivial attack vector, and so SHOULD (for example) prompt for a password during installation.
Just in case the Thanks! doesn't clue people in, I'm very much agreed with these changes.
__________________
Ryan Abel
 

The Following User Says Thank You to GeneralAntilles For This Useful Post:
Reply

Tags
extras, testing apps


 
Forum Jump


All times are GMT. The time now is 17:35.