From 958c1c0ebc2c1621797d71b640c7c4e3280dbd7b Mon Sep 17 00:00:00 2001 From: Aleksandar Fabijanic Date: Tue, 4 Jun 2013 23:16:05 -0500 Subject: [PATCH] Update README.md --- README.md | 27 +++++++++++++++++++++++---- 1 file changed, 23 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index f21e10374..5a6ddf30c 100644 --- a/README.md +++ b/README.md @@ -1,11 +1,30 @@ POCO C++ Libraries ================== -When contributing to POCO, please adhere to our coding styleguide: -http://www.appinf.com/download/CppCodingStyleGuide.pdf +POrtable COmponents C++ Libraries are: +-------------------------------------- +- A collection of C++ class libraries, conceptually similar to the Java Class Library, the .NET Framework or Apple’s Cocoa. +- Focused on solutions to frequently-encountered practical problems. +- Focused on ‘internet-age’ network-centric applications. +- Written in efficient, modern, 100% ANSI/ISO Standard C++. +- Based on and complementing the C++ Standard Library/STL. +- Highly portable and available on many different platforms. +- Open Source, licensed under the Boost Software License. -We use the branching model described in this article: -http://nvie.com/posts/a-successful-git-branching-model/ +In regards to Boost, in spite of some functional overlapping, +POCO is best thought of as a Boost complement (rather than replacement). +Side-by-side use of Boost and POCO is a very common occurence. + +---- + +POCO has an active user and contributing community, please visit our [web site](http://pocoproject.org), [forum](http://pocoproject.org/forum) and [blog](http://pocoproject.org/blog). +Answers to POCO-related questions can also be found on [Stack Overflow](http://stackoverflow.com/questions/tagged/poco-libraries). + +---- + +When contributing to POCO, please adhere to our [coding styleguide](http://www.appinf.com/download/CppCodingStyleGuide.pdf). + +We use the branching model described [here](http://nvie.com/posts/a-successful-git-branching-model/). All text file line endings in the repository must be Unix-style (LF). This includes Visual Studio project and solution files (.sln, .vcproj, .vcxproj, .vcxproj.filters).