In System Monitor, there is a list of processes with various information. The idea is that in this process list, when an item is clicked, a panel on the right would give a description of that process. (What package it is part of, link to the man page, link to documentation, typical behavior)
This would be useful, because usually if you are attempting to identify what processes are running, and why - you will find the process name and start googling it to find out what package it is part of.
When I do this, I can usually see that others have googled to find out the same information. (One example is seeing two gdm instances..the info could show that it's typical to see two instances of this)
The info pages could also be set up via 'wiki'
This would also be very educational for getting newbies more comfortable with system processes and familiar with linux architecture.
This is kind of a good idea, but not every process has a man page that this feature could pull the info from. Programattically, other than doing it that way, via the man page, this task could prove to be rather difficult as addition information about a process would have to be stored "somewhere" and if that information wasn't filed in by "someone" then the feature is useless. The idea regarding the wiki linking is neat and all but I wouldn't find it useful other than saving me a few clicks, not really worth the effort to code it.
"This would also be very educational for getting newbies more familiar with system processes and comfortable with linux architecture." - This is an extremely important aspect of the Linux world, since unlike Windows, Linux is a LOT of seperate programs working together to create the user experience. It's important to understand the parts of the sum.
If it would save you a few clicks, imagine what it would do for a newbie.
> This is kind of a good idea, but not every process has a man page that this feature could pull the info from.
This makes something like this more important; if I am attempting to learn about what a process is, and there isn't a man page (which is already a bit of tech investigation beyond the average user,) understanding why this process is running is going to be even more of a hurdle.
> The idea regarding the wiki linking is neat and all but I wouldn't find it useful other than saving me a few clicks, not really worth the effort to code it.
It sounds as if you're a savvy user, and know how to do the research. A few clicks isn't a biggie. For newbie though, those clicks are the difference between remaining in the dark vs. learning a little bit.
Tying the various processes/applications to a wiki would be the tricky part. It also would make sense if the wiki could compile the info into a doc package that could be downloaded in updates, rather than being a 'live' page that you see when you go into sysinfo.
Initially, only the infrastructure would have to be in place, with a 'update wiki info for this process' available. Seems like the most common processes would be filled out by someone..
Maybe also display an icon for the program (if it has one), and another icon that signifies what type of process it is (e.g. system, program, network, etc).