Quality Assurance rules for Command Line applications (CLI)
 

HI,

after some discussion we finally have defined quality assurance(QA) rules for command line applications, these apps should address two extras checks in order to be promoted to Extras:

* The application uses the CLI icon[1] in the application manager.
* The application description clearly says that the application only runs from the command line.

Big thanks to Tim Samoff for his work in the CLI icon.

[1] - http://wiki.maemo.org/Extras-testing...e_applications

Re: Q&A Rules for Command Line applications(CLI)
 

Maybe you should write out what Q&A stands for. I read it as quality assurane, but inexperienced developers (part of the target audience) might not know about the abbreviation. Also it should be QA, since Q&A usually means questions & answers.

peace!

Re: Q&A Rules for Command Line applications(CLI)
 

Err, your are right I've a bad habit of using Q&A instead of QA, thanks for pointing.

Re: Quality Assurance rules for Command Line applications (CLI)
 

Thread title updated at VDVsx's request.

Re: Quality Assurance rules for Command Line applications (CLI)
 

Thanks for setting these rules. I guess it's a bit late to make suggestions, but I wonder if using the word "terminal" would have been better than "command line" as the mandatory text in the description, to more helpfully guide users as to how to find the program.

Re: Quality Assurance rules for Command Line applications (CLI)
 

There's no mandatory words, the description only have to say that the application only runs from the command line/terminal/x-terminal, but please something less geeky as possible :) .

Re: Quality Assurance rules for Command Line applications (CLI)
 

"Terminal command line" covers it nicely. ;)

Re: Quality Assurance rules for Command Line applications (CLI)
 

http://wiki.maemo.org/images/0/09/Cli_icon_64p.png

So there's an icon to indicate which apps are paid apps?

That's not confusing. :/

Re: Quality Assurance rules for Command Line applications (CLI)
 

Sounds good to me. To avoid confusion, do these rules also apply to things like daemons or just interactive apps?

Re: Quality Assurance rules for Command Line applications (CLI)
 

Does this is final this time ? As all QA rules changing everytimes is really annoying ...

This are slowly forcing dev to create there own repository.

Re: Quality Assurance rules for Command Line applications (CLI)
 

The community drives the changes, if the community wants and have good reasons to change something, why not ?

I don't understand the whining since these are very simple rules, and very easy to deploy in your apps.

Re: Quality Assurance rules for Command Line applications (CLI)
 

Everything that is only reachable from the command line. I.e doesn't have a GUI. For example openSSH is one of these cases.

Re: Quality Assurance rules for Command Line applications (CLI)
 

We (devs) can also ignore that and stay in extras-devel/testing.

Re: Quality Assurance rules for Command Line applications (CLI)
 

Does this also apply to apps with a curses GUI and a menu icon, like htop?

Re: Quality Assurance rules for Command Line applications (CLI)
 

IMInterpretation not, if it has menu icon and some sort of UI (curses, gtk, qt, who cares...) then it's not CLI-only.

Re: Quality Assurance rules for Command Line applications (CLI)
 

No, apps that have a menu icon that opens a curses GUI are out of scope here, but a good description is recommend.

I'll setup a FAQ to clarify that.

Re: Quality Assurance rules for Command Line applications (CLI)
 

FAQ: http://wiki.maemo.org/Extras-testing...plications#FAQ

Feel free to improve it or add more info.