Using Mepis to get the job done

This the kind of thing I was thinking (but not elaborating on) with reagrds to the e-zine idea. In fact the mandrakeuser.org site is EXACTLY the kind I was thinking of.

What kind of skill-sets do the volunteers have?
I would love to contibute in the development of a website for this. I do a lot of php coding and deal with mysql a great deal. I also try to work with STRICT html to keep things looking good OS/browser-wide (:

What kinds of things would the SOHO user need to be able to do?
This would certainly be a wide, wide range of things from setting up a complete and secure home network using wired or wireless, to setting up printer sharing for a multiple OS network. A person could think up about a millions needs for SOHO users.

What should the minimal expected skill level be of the target audience?
I think with how MEPIS is designed the expected skill level should pretty much be a computer literate person. Brinning linux to the desktop is a very demanding task, and from what I've read/discussed with people around these forums it appears that MEPIS would be a great step-forward in this process. So I'd the say target audience would be pretty much anyone who had a basic idea about the computing world.

Dema;
Do you have any experience with or know anything at all about Drupal? There is most definitely going to be a need for that sort of thing on the technical side of this project in that Drupal is what runs Mepis.org. Unfortunately my HTML skills died at about HTML 3.2 so this is really good news.

On the topic of topics I have two points:
1. It would be great to get some business-savvy but not necessarily technical people involved with this. The goal of documentation of any kind is to basically "answer the question" and the types of questions the business folks need answering are not necessarily the ones that come to the minds of technical folks such as us. There will be room for that too but to get Linux in general and Mepis in particular in a place where things like the City of Munich and Burlington Coat factory happen, we need to assess the needs of the business community.
That said,,
2. As a start perhaps we can build an outline of the topics we should shoot for. To start:

Admin
Setting up a mail server
Setting up a website (Apache)
Setting up a firewall
Installing/configuring a database (Oracle, MySQL, etc)
` Installing and configuring Backup solutions

Business
(and this is where I get stuck so if these ideas are dumb, I apoplogise)
Setting up a CRM (Customer Relation Management) tool
Project management (not just software)
Document storage and retrieval
Doing things in OpenOffice (now I am reaching)

Anyways, this is just a starter list...

Jeff

STIBS mentioned that drupal was what is used here, so I went and checked the site out and downloaded the code. I hafta say the design and ability to customize is pretty impressive, but outside of that the code doesn't really appeal to me that much. There are some bugs and sort of "wrong-way" solutions to things, to me anyway. Personally i'm not a fan of any "pre-built" things like that. It would certainly be a big project to undertake, but I would prefer to build a website from scratch. I guess my biggest quarrel with drupal is that it requires some strange php.ini file settings. It is sort of non-standard and I don't believe this server is even using the correct ones, as I am unable to "stay logged in" when I select it from the login page. But along the lines of pre-built systems, I have mentioned before and will again that slashcode is pretty nice. The only downside I see to it that it uses really outdated HTML, but it is very cross OS/browser friendlt none the less.

Along the lines of topics, I think it's a great idea to build a list, but instead of trying to hard to think things up, I suggest brainstorming for now (ie: just type out whatever comes to mind in regards to topics.)

Wired/Wireless networks home and business
Network security
Database management in additonial to installation
The use of powerful tools like Gimp, OpenOffice, etc
Resources for further learning (ie: places to find packages, etc)
Solving problems and finding help
Basic hardware setups
Command line usage
KDE, GNOME, etc general usage
Different variations of editors
Powerful encryption
User management
Debugging
Faxing
Multimedia usage and creation
Basic system preferences
Setting up a DNS
Setting up a Router
Interacting with PDA
Bluetooth

I'm running low here. Anyway, everyone get in this thread and just start thinking and typing, that's the first step

Two years ago I wouldn't have come up with a better list of topics ... hehe!

You mention important topics but let's don't forget these pretty simple things to earn money in a SOHO:

How do I get my bookkeeping done in Mepis?
How can I write an invoice to the right client?
How do I make my tax declaration with Mepis?
How can I send a serial fax or print a serial letter?
How can I make a flyer for advertising?

Oh ... and how do I get this kewl product picture, I shot yesterday with my digicam, into my online shop (that dema programmed for me) in a 320x200 resolution from the 1024x768 size it got right now?

chuckle...
STIBS

hehe, I know I am

Those are great ideas, keep um flowin people!

Jeff and all,

I realy like the idea of "cut to the chase" type How-to docs. So lets try to concentrate on that.

I also purpose that with the idea of Stibs concerning docs that can directly effect the SOHO type user we simply catergoize them as such. i.e. For the Business Mepis user etc.

My employeer is a very large food service company that is just begining to look at Linux for some server duty and desktop deployment. The big question that comes up is "can Linux desktops do what our Windows and Mac desktops do now?". For instance, will the copious M$ macros that we use in Excel work with Open Office, can we connect to our SAP apps, can we access our Unix servers with an emulation package, what type of email clients do we use, can we access the Exchange server...blah blah blah." These are more enterprise questions but can be applied to SOHO/Mid sized business then ultimatly Enterpise wide usage.

So we know that GnuLinux has reached the "good enough" mark no we are here to translate to the entrenched Windows user and new users what and how to accomplish their tasks, needs and wants using MEPIS Linux as the tool of choice.

My skill sets range from hardcore tinkerer of hardware, been using GnuLinux for 6 years, am not and will never be a guru( too much to learn), am comfortable with LAMP based software use, install and config, work very hard at learning what is available in the Open Source Software (OSS) world as alternatives to Closed Source products, am an evangelist of GnuLinux and OSS. I have attended college but did not finish. Have a wide range of work history from Fine dining cook to currently working in IS on a very busy help-desk, operated my own small biz selling GnuLinux based small biz servers based on Red Hat based e-smith server/gateway. I dont code but want to learn, have so far found what I need in the OSS apps. Most of all I am very resourceful and a visionary/dreamer, an idea-man who is passionate aboug GnuLinux and IT.

So I vonlunteer my time which is limited but will do my best.

Steve
"The secret to creativity is knowing how to hide your sources." Albert Einstein

> Oh ... and how do I get this kewl product picture, I shot yesterday with my digicam, into my online shop (that dema programmed for me) in a 320x200 resolution from the 1024x768 size it got right now?

--Uhhh, try ImageMagick.

http://wolfrdr.tripod.com/linuxtips.html

Your skills and enthusiasm are greatly appreaciated!

Here are some thoughts for the group; I am basically throwing a few ideas against the wall to see what sticks.

1. Format: I have always gotten a lot more use out of books and other tutorials that are laid out in a cook-book style format (I am thinking of things like The Linux Problem Solver, the Python cook book, etc). In other words, I know What the general task is that I am trying to do; it is then good to go to the book, find the "recipe" and execute it. How about everyone else?

2. Possible first steps:

2.1 Getting group together (in progress).

2.2 Determine what we want/need to accomplish with our first major push to get this going. I know that this will in essence be an on-going process with no predefined "conclusion" but the project manager in me likes milestones so that we can tell if our process is working; in other words, are we accomplishing what we set out to do? So I think that once we have all of the topics in the "pot" we can pick, say the six (+/-) best or most-likely to be needed tasks and concentrate on getting them done. This will help us shake bugs out of our system.

2.2.1 Query: There is also a Promotions group brewing here on Mepis; we should solicite some of their input as well in an attempt to perhaps have at least one or two of our initial tutorials (or whatever we end up calling them; MKMs (Mepis Knowledge Modules)? Bleh.) be "killer" solutions for Mepis. For the same reason we should try to gather some feedback from someone more on the purely business side of things. Antwerx sounds like he is (I am assuming Antwerx is a he ) the closest thing we have.

2.2.1.1: We could also kind of leverage the R & D that other major Linux vendors have done to find "hot" topics such as exchange server replacement. This is operating under the theory that some of these higher-end features are still open source; what brings the value is the expertise used in preconfiguration of these kinds of features. If this is true then Linux + Expertise might be able to get us in a spot where we have the high-end enterprise features that the big boys have but at a fraction of the price. Just an idea. I am talking about clean room re-engineering here.

2.3 Finally get some initial assignments laid out. I know that as techies not everyone likes writing docs of any type so what may also work here is if we have some hard-core techies that simply want to jot down the steps needed to accomplish whatever it is they are trying to document in a text editor, that could then be handed to to a tech writer to be polished up for publication.

Just some thoughts to get things going...

Cheers,
Jeff

In other words, I know What the general task is that I am trying to do; it is then good to go to the book, find the "recipe" and execute it. How about everyone else?
I would certainly agree with this idea. It is a great way to organize info and get points across.

Determine what we want/need to accomplish with our first major push to get this going.
Some ideas: Get a website beta protocol/layout up, pull together a general format for tutorials, get some real organization on ideas for said tutorials (ie: oragnize the ideas posted in this thread), and of course, build on those topics.

...(or whatever we end up calling them; MKMs (Mepis Knowledge Modules)? Bleh.)
Hehe, I like MKMs (:

I know that as techies not everyone likes writing docs of any type...
As I am not very familiar was linux yet ( trying not to say newb since ya dont like it (; ), I would be willing to test out/touch up some of the tutorials. Being mainly a Linux home user I wouldn't be able to get into heavy things (ie: exchange server replacement mentioned above) but would be more than willing to test some of the resulting docs and provide input.

I like the idea of a "cook book format" for how-to docs. Other docs it may be useful to have a basic format that lays out the minimum or must have data concerning the particular doc in question. Maybe a web form or downloadable Open Office templates.

Steve
"The secret to creativity is knowing how to hide your sources." Albert Einstein

To all who read this: As a pilot or proof of concept I am thinking that we could start out small given the size of our group with say six "recipes" to start with, three on the techie-admin side and three on the SOHO side. Mostly this is just to get a place to start. Questions/nominations from the group are being solicited here. What are (in your opinions) the best of breed open source applications for:

SOHO:
Book-keeping software
Groupware (there is a better name for this) for things like meeting mgmt, perhaps intranet email, calendaring, resource mgmt, etc. For an example of this, see projects like Tutos at freshmeat/source-forge. I think something that works well in a basic LAMP situation would be good. Alternatives are appreciated.
CRM software
DTP software
Project mgmt software (can be software-related but ideally should be applicable to any kind of project that deals with resources, schedules, milestones, etc.

Anything else the group can think of...

On the techie side:
Since Mepis seems to feature MySQL, should this tbe our "adopted" database? Postgres?
How about a mail server? What is considered best of breed right now?
Is GuardDog a strong enough firewall for the SOHO admin? I am not talking about protecting IBM.com or anything, just a typical SOHO arrangement...
Intranet IM software

This is more of a strategy than a product but what about applying security patches in Mepis: what is the best way for a part-time admin to keep his or her network machines patched with latest stuff (without breaking everything else)?

Thoughts or additional suggestions are appreciated...

Cheers,
Jeff

I would vote for MySQL as the "database of choice" for MEPIS. But I'm only basing that on it being the primary database I have worked with. I have heard, although few and far between, that some other database distros are a bit more "powerful."

As for a mail server, this is something I just recently did a lot of work on when setting up my most recent server. I've found Exim to be a GREAT mail server that is easy to install, fairly simple to configure, VERY versatile, and takes up a very small amount of memory.

I have always been rather fond of RedHat patching system. One is allowed to signup as a members and recieves email updates on patches that pertain to packages installed on their system. In most cases you can visit a website to learn about the patch or install it using up2date. I'm not sure how easy/hard software like that is to write, but it was certainly convenient.

I'm fairly new to Linux, but I can use a computer just as good, if not better than that next guy. I know how to code in Visual Basic, which doesn't help much in Linux, and I know some C++, also. I'm not very familiar with the term "SOHO", could anybody help me out with that? It sounds like you have a lot of things figured out already, although I did read something about an OpenOffice template? I think it should all be on the website, because it would make the site more independent. When I'm surfing the internet and I click on a link that opens up another program, in my eyes, it kind of degrades the website; makes it look like it can't do things on its own.

That's really just my two cents..
-Rex

The way I interpret it, it means a standalone or small system intended for a small office or home office. Which brings up a point in documentation when abbreviations such as this are used in documentation the complete term should be used at least once the first time it is presented. For example: a small home office (SOHO) . . . . .

Greetings all and thanks for such a great discussion. This is the type of discussion I've been hoping to see around other distros, but couldn't find it. To hear people talking about "How to" accomplish end user tasks is much more beneficial to me as an IT/Network administrator, than some of the more detailed, technical discussions that usually emerge when talking about Linux. Even though when I lapse over into geekdom, I do need to feed on such topics as how to compile the Kernel and such :+)

I hope my comments here are not off topic.

As the admin of a small business network (35--40 PCs in a Win2k environment) my concerns as I consider migrating my organization to Linux are:

1) End-User learning curve. If my workers can't familiarize themselves quickly with their new desktop and associated apps, I'm in trouble. Contrary to what some may think, most end-users can get up to speed fairly quickly, if the change in appearance and functionality isn't too drastic. I believe that Linux apps have come a long way in making this possible. If you can use Outlook, you can use Evolution. If you can use MS Word, you can use OpenOffice, etc.

2) Easy installation into the network environment during deployment is very imortant. I spent all day yesterday trying to get Mepis to print to a workgroup printer that was attached a PC. The day before I spent most of the day trying to connect to network shares--one on a Win2k server and one on a Linux based Netmax server. There needs to be a better way than having to manually edit multiple config files. I've posted a suggestion in the MEPIS IN THE NEWS Forum how this might be better handled.

3) I need the ability to select what software applications are needed, based on end-user tasks and workflow. For example, all of my staff need Word Processing, Email, a Web Browser and Anti-Virus. A select few need a spreadsheet app, while fewer need desktop publishing and Gimp. Only two need an HTML editor. So, to make my deployment more efficient, I need a way to select what apps I need, and only those I need at each unique install. In the same way, I don't need multiple applications of the same type. Let me choose either OpenOffice or KOFFICE, Evolution or KMAIL.

4) As much as I love cutting edge technology, it really has very little place in the current work environment. My concerns are also those of businesses with which I do IT consulting.We?? are looking for ways to utilize?? existing hardware. In these times of IT spending freezes, a distro that will work on legacy machines such as those with AMD K6-2s or PII chips with 4 gig HDs, Intel chipsets, etc. is still in great demand.

5) Finally, security issues are of great concern. Rather than carry on about about how insecure WIN98 and IExplorer are, I need desktop systems that have strong user level, file level?? and network security along with reliable anti-virus/worm software.

For many reasons, I want to move my organzation away from MS products.With the comments above, you can see that my "How-To" concerns focus primarily on ease of integration into my existing environment, with minimal disruption to work processes and productivity. My IT staff is small and our time is of a premium.

BTW, I think MEPIS is moving in the right direction and of all the distros that I've tried over the past year, it is farther down the road in meeting my goals as an IT Administrator than any others I've tried.. I hope that I can be a part of the MEPIS movement in the future and thanks for allowing me the time to comment in this forum.

Jim Adams
Maysville KY USA

I am definitely on the business side. I am considered a "power user" among my working peers but I am really clueless when it comes to any programming. I have spent the last few months getting to know Linux and have really been impressed with Mepis. While the application is great, the forum groups are top notch! I would like to use a Linux distro for my not for profit org but the thing that holds me back is learning how to configure everything. I would say that the biggest "how to" I would like to see is a detailed description on how to acquire, compile, install drivers for things like sound cards and modems. I just may be looking in the wrong areas, but I haven't found any real good detailed tutorials on this subject from a user perspective. That is the one thing that is really holding me back from shouting about Linux from the mountaintops!

I would be more than happy to participate as a tester for the how to's.

Chris

As far as security in a business environment, there are a few things that should be covered that are in the realm of your IT personnel. These would include things such as:

1) Setting up intrusion detection systems such as Snort and Tripwire.

2) Deciding on and setting up a firewall. Guarddog just doesn't do it for me. On a personal note I've found that APF works well on my webserver at ev1servers.com

3) Setting up email servers with all the different features configured for a secure system. Exim or Postfix would be my choice of actual server. But there are things that go hand in hand with this such as Spamassasin, ClamAV, Mailman, CyrusIMAP, etc...

4) Configuring Samba properly to work well in a mixed win2k active directory environment as that's what most people will either be working with or migrating from.

5) Slightly off-topic but along the lines of changing the installer to customize the package installs. Does linux have anything along the lines of the 'policies' of win2k where you can have a roaming profile which can be locked down for a user? I'm guessing that there is since linux has been used effectively in net cafes and such but have not seen it.

Hello all,

after reading through all the above posts, just a comment, I would think that Mepis is aimed at "Desktop" users, whether a SoHo or just end user at home.

1.A good run down on the "basics", such as Mepis apps - MS apps; Word - Kwrite etc with screenshots for the various icons etc would be a good start.

2.How to install software

3. How to add users

4. How to install a basic firewall

5. How to setup an email account / internet browsing

etc..............a lot of "new users" will need clear / concise docs on the above to "stick" with a distro

The databases / exchange servers etc.etc.......are all good as well, but perhaps an "intermediate / expert??section" when the learning curve gets steeper.

Without the basic users and basic howtos mant users will not stay. If the "details" are well covered, then the end product is polished and easy to use.

I have used at least a dozen distros and one of the things that turned me off Linux in the past has been the lack of / and/or deluge of howto docs, and the installation of software, something like this would have to be done right / indexed so users could easily find what they are looking for, I think if everyone jumps on the SoHo wagon the "everyday" user will get pushed to the rear, a lot of home users do not use a database or setup a mail server........??etc...........

Anything I can contribute I will be glad to.

Regards

Will

Hello Jim and the rest,
I assume this thread and project are still active?

There have been some very good points made in this thread thus far, some see it from a "workstation end user" perspective and others focus on the behind the scenes fucntionality (and justification) that Sys Admins *must* have before they can implement linux solutions into thier networks.

I saw many questions in this thread that I could provide useful answers to: a brief sample of these are:

Q: How to set up an IDS system with Linux (Mepis?)
A: I wouldnt, there are specialty distro's (sentinix linux) that are designed specifically for that task. I would however include a strong IP Tables FW and a GUI front end with Mepis designed documentation on configuring it and an anti-rootkit tool like "chkrootkit", anti-virus software etc.

Q: My users dont need "all" of the App's that are loaded with KDE, how can I limit what they have access to without major configuration.
A: (Just an Idea here I havent seen done before) Have a "default" profile available with the apps menu and the catagories therein like "system settings", "office", "Graphics" etc. but have no app links in them. You could use the KDE menu editor to populate the menu catagories with the apps you want. This could be done when you set the workstation up for deployment. a dozen or two apps per user should be plenty.

Q: I saw someone ask if linux would authenticate users to a windows network at login.
A: I would assume so, even if the Primary Domain Controller is a Winx machine is should authenticate the username and password combination to the domain (although a PDC will prompt you for admin rights the first time). But i havent verified this.

Those were just some quick bits I wanted to throw out.

My own question is this, is this requested "group" of volunteers going to be a documentation only sort of group or a "brainstorming, tutorials, docs, input for future developent" sort of group?

And will there be a location in addition to the forum like a "group site" or repository for serious technical discussion, file/document up/downloads etc? What is the plan if any?

I am a Net/Infosec admin in a Win/Nix enviroment, I'm also a father-to-be and a continuing student in fields relating to my industry (read: I have very little spare time). The limits of my contribution would be mostly commentary on the industry, it's needs and how it's developing. I would hope that I could provide some usefull information and insight in this regard. I'm a serious Linux geek and love a good IT conversation.

I deal with the same questions regarding Linux implementations that everyone else goes through, my shop was a Win-only shop before I arrived.

I'll leave it on that note.

thanks,
bf

Yes I aggree with Warren . Being a new linux user myself ( 4 months old ) and coming from a windows and macintosh background , I have found the forums here invaluable . I work as a tech in a windows shop , spending my days cleaning bugs out of missmanaged machines. This is why I have choosen to give Linux a shot . I have not regretted it even though it has and continues to be a learning curve . I have had to format and re-install 4 times after irresponsibly using apt-get and breaking the system . I would like to see more documentation on upgrading and package selection on line ( particual to Mepis as I am sure there are issues around package choices being a mix from testing and unstable ) .

I have read just every posting I could find on this subject in the Mepis forums and have come to the conclusion that I should stick to using the two cd set and play with installing and removing until I get a better understanding of the system.

I spend my recreational time with digital photography and restoration ( my hobby ) . I have used Photoshop for years and I am impresses with GIMP . Also it took a while to figure out because its visual layout ( GUI) was different . I would be more that happy to assist with manuals / tips in this area.

I am still trying to get a grasp on managing security issues ie viruses , spyware , trojens etc . There does not seem to be too much out there unless you are deploying a server . Even the forums have not mentioned too much on this issue .

Well those are my thoughts ....

Indeed, they're.
Bravo for your decision to try MEPIS.Please, keep on using it & also tell your friends about it.

To err is human, but to really foul things up requires a computer.
Farmers' Almanac, 1978

I must say I utterly and totally agree with Will. I really honor the fact that there should be comprehensive How To get The Job Done articles for the somehwat experienced user / SOHO admin. However: desktop acceptance largely relies on the end user's perception. On a very basic and low level people want to be able to send and receive mail, create and manipulate documents, surf the web etc. Many, many people don't have a clue about how to install neither Windows nor Linux, nor applications for either of them. Those people may derogatively be called newbies, but in the end they are just USERS. IMHO the 2004 RC4 version if Mepis is a giant step towards convincing those users of he fact that they can USE a linux based PC. First time users ought to be pampered, and get the feeling that they're not out on a limb once they get stuck with something simple. I like this forum, being technically a newbie when it comes to Linux, but I consider myself to be a little more advanced when it comes to computer management than the average user. What I would propose is a basic user forum / howto website, directly acessible via a shortcut / favorite on the Mepis desktop, where people can find answers to trivial things such as: how do I connect my printer (many of which will require turboprint, would be nice if it were included in the end user manual), how do I create interchangeable documents with MS office, how do I get KDE to behave and look like windows (you'd be amazed at how many people get lost if the windows behave differently) etc. This could partially be a library of sources in the user's PC (the doc files), related websites, but should be very accessible, with your typical forum function where people can drop all kinds of questions. Such a forum would maybe have to be moderated, to prevent flaming, which would deter users.

So I would actually propose a fork in the documentation project: one branch aimed at business related issues (creating systems to perform tasks), and one branch with your typical aunt in the country in mind. In the end, your aunt will probably work in somebody's office as well, and who knows, she might convince her boss that she ' likes the other Windows better??

Cheers
Carl

Newbie or not Newbie, there's always a question

Okay, here's my input.

I'm a small business owner looking to start another company. I am employed with a non-profit to pay the bills (technical writer, resource developer). I've developed a business plan to start a company that sells affordable, pre-installed linux desktops to a very defined target population. The comany name will be KROLODYNE SYSTEMS. I have the capital to make it happen this summer and I plan to offer systems in late July or early August.

Here's a little biographical information. I graduated from the University of Texas with a BA in 2000. I've used various linux distributions (SUSE, Mandrake, Gentoo, MEPIS) for several basic small business needs for about a year. I've also tinkered with all those distributions to see what linux could do. I am an 'intermediate' programmer and local 'power user'. I write simple programs in C++, C, Java and use GNU programming utilities (gcc, g++, gcc-java, etc) within the linux environment. I also program gui applications with Qt3. I can do alot more programming with MS products. I program Visual C++ and Java with Visual Studio, and make backend database applications with Visual Basic (6 and .Net). I have given up on MS and am trying to do EVERYTHING with linux.

I am willing to develop professional documentation for MEPIS on a voluntary basis.

After reading the previous posts, it looks like a lot of the basics have been covered. However, there is one distinction I would like to make with regards to the proposed documenation project: there needs to be a separation between (1) enhancing a company's capabilities and (2) providing user applications that give companies the ability to conduct daily operations with streamlined processes.

All the posts above that mention setting up networks, installing applications, setting up security, etc would be included in the 'capabilities' category. That category would show businesses how MEPIS could be used to create a viable business IT infrastructure that would satisfy its data/information needs. This section would give business owners and managers the bigger picture, so to speak.

Once these 'global' infrastructure capbilities offered by MEPIS are identified, then I think the technical information to setup this infrastructure should be presented in a *goal/objective/hardware* format. When I suggested Linux to other small business people, it was hard for them to navigate and grasp all the fragmented documentation out there. If you presented the material in a way that tells business owners what they will accomplish with a particular how-to (goal), the steps that will be taken to accomplish it (objectives), and the hardware they need to make it happen (hardware), I think it will simplify things for them and make sense. Then all the technical X's and O'x could follow this in SPECIFIC step by step paragraphs.

Business owners, managers and company employees then need to know which applications are bundled with MEPIS, what these apps can do, and how to get things done with them. This information needs to describe how company personnel can get things done from a day-to-day user perspective. The information should answer questions like: "How do I create a reliable customer database?", "If I want to develop a new simple website, what applications do I have with MEPIS to do this?", "How can I keep track of sales?", "How can I use MEPIS to keep track of inventory?", "What tools do I have to modify my company logo?", "What do I use to make professional presentations embedded with sound and photos?","Is it possible to develop simple programs customized for my company's needs?" etc.

I think the information should be broken down along the lines of process units. For example, my small company has the following process units: admin, promotions/marketing, sales/member recruitment, production, and quality control. Each unit does not necessarily represent a 'department'. There is no 'admin department' in my company. Admin is a process point where several functions are performed using approved methods that support the overall operation of my business. So if I were writing the documentation, I would give a list of all software packages that could be used to help with a company's administration needs and give step by step examlples that show how these packages could be utilized in real-life business situations. I think all the technical information will flow easier and make sense if presented in this format.

I really have too many ideas to list them all here. I've thought about this documentation need for quite some time and have other suggestions. If MEPIS needs help, I will volunteer to move things along.

Chris Villanueva

Jim Adams said it all. A SOHO distro is all about getting people working quickly. They're not daft, they just need a little help. MEPIS is almost there, but not quite. As a user, rather than an IT expert, pleased to help but not sure I can add much to the above.
(Can anybody tell me how to edit HTML. I see Jim only has 2 users who require this. I've tried the OOffice guides but OOfice Writer/web falls woefully short of something like Netscape composer IMO, and I don't want to go back to a simple text editor.) Greg

I've used mepis for over a year now, but would love to introduce it into the working enviroment. I'm a sys admin by trade and have done a few little things here and there for the cause.

I've helped on a project called karoshi (www.karoshi.org.uk) this project is geared towards making a scripted based server setup for education. i helped start off making the project run on multiple distributions by building the framework and making it run on Mepis, which ulitmatly meant supporting debian based distros.

Business based guides/solutions
PDC (ldap based) samba server configuration
Web based management tools configuration
CMS/intranet tool for company information
Sharepoint alternative for collaboration, including online document store
as mentioned a CRM
marketing/campaign management - maybe linking or same as collaboration tool.
asterisk telephone system

postgres configuration (best opensource database to compete with MS-SQL, my-sql just doesn't cut it for enterprise databases)

guides for central desktop configuration, for those companies that must have a "standard" desktop, in effect the MS group policy alternative. kiosk comes to mind.

workstation deployment guides

What should the minimal expected skill level be of the target audience?
Perhaps a rating system for each article to outline the skillset required?

i would gladly help anyway i can for this. on karoshi, it was simple scripts, but i do know a little basic, so i could write apps in realbasic and realase under any license agreement the project sees fit.

i think a guide to strip multimedia and desktop based configs from mepis to make it more server grade would also be cool.

Alan

Using Mepis...and proud of it.