Free Publishing Software

Fish tank problems!!?

INGNORE TITLE LISTEN HERE!!!!!!!

i think we all know what my real question

what does all this mean?

‘I gasped. Nothing could be more thrilling than this. Figure of speech of coarse. I laughed. Nothing would be forever. I’ve been looking for my perfect content management system (CMS) for quite a while now. I’ve gone through about 6 or 7 and finally realized that a perfect solution doesn’t exist. Instead, I recently stumbled upon Drupal, which is an open source CMS. It was recently given a CNet “Webware 100” award in the Publishing category. The way Drupal works really is a paradigm shift from all other CMS software that I’ve used. Once I grasped the concept, its been pretty easy to learn

On a computerization project, does the testing, in particular the informal testing, resemble “lightweight?

software test automation” ?

<<Lightweight software test automation is the process of creating and using relatively short and simple computer programs, called lightweight test harnesses, designed to test a software system. Lightweight test automation harnesses are not tied to a particular programming language but are most often implemented with the Java, Perl, Visual Basic .NET, and C# programming languages. Lightweight test automation harnesses are generally four pages of source code or less, and are generally written in four hours or less. Lightweight test automation is often associated with Agile software development methodology.

The three major alternatives to the use of lightweight software test automation are commercial test automation frameworks, Open Source test automation frameworks, and heavyweight test automation. The primary disadvantage of lightweight test automation is manageability. Because lightweight automation is relatively quick and easy to implement, a test effort can be overwhelmed with harness programs, test case data files, test result files, and so on. However, lightweight test automation has significant advantages. Compared with commercial frameworks, lightweight automation is less expensive in initial cost and is more flexible. Compared with Open Source frameworks, lightweight automation is more stable because there are fewer updates and external dependencies. Compared with heavyweight test automation, lightweight automation is quicker to implement and modify. Lightweight test automation is generally used to complement, not replace these alternative approaches.

Lightweight test automation is most useful for regression testing, where the intention is to verify that new source code added to the system under test has not created any new software failures. Lightweight test automation may be used for other areas of software testing such as performance testing, stress testing, load testing, security testing, code coverage analysis, mutation testing, and so on. The most widely published proponent of the use of lightweight software test automation is Dr. James D. McCaffrey.>> (wikipedia)
To gi….

Thanks.

How does the GPL pertain to server based applications?

I am reading up on the GNU General Public License (GPL), one piece of software I would like to use is published under the GPL.

The GPL requires that any software that makes use of the GPL distributed package is its self open source under a compatible GPL.

But I am going to use the software in a server based application (part of a web backend architecture).

So I will not be distributing the software (as it is a server).

Does anyone know how to interpret the license in this case? Can I use the software legally since there is no “distribution”? Though I will charge for the web service being provided.

Thanks,
David