search

nguyenducnhaty / opengse

Automatically exported from code.google.com/p/opengse
Apache License 2.0
0 stars 0 forks source link

Documentation and Sample Code #7

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
As per
http://wiki/Main/HowToOpenSourceGoogleCode#Documentation_and_Sample_Code:

"Documentation and Sample Code

The goal when releasing code as open source is usually to encourage others
to use it, and that will be a lot easier for people if they know how! You
should include some sort of documentation, even if it is just some notes in
the README file to help people get started.

If you are releasing a library or something else that exposes APIs, be sure
to include sample code. If possible, sample code should be licensed so that
people can cut-and-paste it into their own programs."

Who is taking responsible for writing sample code?  Who is taking
responsibility for writing documentation?  Where does this go in the heirarchy?

Marking this as Priority-High, but perhaps we want it to be
Priority-Critical?  A servlet engine with no examples and no documentation
probably isn't particularly useful.

Original issue reported on code.google.com by Mickey.K...@gmail.com on 28 Jul 2008 at 9:05

GoogleCodeExporter commented 8 years ago

Original comment by Mickey.K...@gmail.com on 29 Jul 2008 at 9:32

GoogleCodeExporter commented 8 years ago 
Programmatic configuration of the reference servlet engine is a secondary
consideration of this project.

The point of this project is to have open-source servlet spec tests. There 
happens to
be a reference servlet engine bundled which passes these tests, but it is no
replacement for Jetty, Tomcat et al.

Original comment by mike.c.j...@gmail.com on 9 Oct 2008 at 3:44