Difference between revisions of "MapServer Project Update - 2007 Q1"

From OSGeo
Jump to navigation Jump to search
 
Line 31: Line 31:
 
* Mailing list members, ... nbr of developers, etc.
 
* Mailing list members, ... nbr of developers, etc.
  
Take a look at Mapbender statistics at [http://www.ohloh.net/projects/3692 Ohloh]. Here are some excerpts:
+
Take a look at MapServer statistics at [http://www.ohloh.net/projects/3692 Ohloh]. Here are some excerpts:
  
 
* '''27 developers''': " Over the past twelve months, 12 developers contributed new code to MapServer. This is a relatively large team, putting this project among the top 5% of all project teams on Ohloh. For this measurement, Ohloh considered only recent changes to the code. Over the entire history of the project, 27 developers have contributed."
 
* '''27 developers''': " Over the past twelve months, 12 developers contributed new code to MapServer. This is a relatively large team, putting this project among the top 5% of all project teams on Ohloh. For this measurement, Ohloh considered only recent changes to the code. Over the entire history of the project, 27 developers have contributed."
  
 
* '''Mature, well-established codebase''': "The first lines of source code were added to MapServer in 2000. This is a relatively long time for an open source project to stay active, and can be a very good sign.<br> A long source control history like this one shows that the project has enough merit to hold contributors's interest for a long time. It might indicate a mature and relatively bug-free code base, and can be a sign of an organized, dedicated development team.<br> '''Note:''' The source code for MapServer might actually be older than the source control history can reveal. Many projects begin by duplicating a large amount of source code from an existing, older project. You can usually tell whether this is the case by looking for a rapid rise in the amount of code early in the project's history."
 
* '''Mature, well-established codebase''': "The first lines of source code were added to MapServer in 2000. This is a relatively long time for an open source project to stay active, and can be a very good sign.<br> A long source control history like this one shows that the project has enough merit to hold contributors's interest for a long time. It might indicate a mature and relatively bug-free code base, and can be a sign of an organized, dedicated development team.<br> '''Note:''' The source code for MapServer might actually be older than the source control history can reveal. Many projects begin by duplicating a large amount of source code from an existing, older project. You can usually tell whether this is the case by looking for a rapid rise in the amount of code early in the project's history."

Revision as of 14:04, 2 April 2007

Work in progress...

About MapServer

MapServer is ...

Recent Events

January 2007

  • ...

February 2007

  • ...

March 2007

  • ...

New MapServer features

  • ...

Future development

  • ...

Statistics

  • Mailing list members, ... nbr of developers, etc.

Take a look at MapServer statistics at Ohloh. Here are some excerpts:

  • 27 developers: " Over the past twelve months, 12 developers contributed new code to MapServer. This is a relatively large team, putting this project among the top 5% of all project teams on Ohloh. For this measurement, Ohloh considered only recent changes to the code. Over the entire history of the project, 27 developers have contributed."
  • Mature, well-established codebase: "The first lines of source code were added to MapServer in 2000. This is a relatively long time for an open source project to stay active, and can be a very good sign.
    A long source control history like this one shows that the project has enough merit to hold contributors's interest for a long time. It might indicate a mature and relatively bug-free code base, and can be a sign of an organized, dedicated development team.
    Note: The source code for MapServer might actually be older than the source control history can reveal. Many projects begin by duplicating a large amount of source code from an existing, older project. You can usually tell whether this is the case by looking for a rapid rise in the amount of code early in the project's history."