[Vxl-maintainers] RE: [Vxl-users] VXL contribution

[Ian S. <ian...@st...>]

Hi Jocelyn,
We are always happy to get new code.

The normal way to contribute whole libraries is to set up a directory in =
contrib. Get yourself an account on SourceForge, and we'll give you =
commit rights.

As for coding standards, I think the maintainers would agree with the =
following:
1. See the VXL book, especially Ch.1.4 =
http://paine.wiau.man.ac.uk/pub/doc_vxl/books/core/book.html#SEC17, and =
Chapter 3.
2. There are also some agreed style standards in
\core\doc\meetings\Zurich-meeting-notes.txt
3. The code should be self-documented according to=20
\core\doc\meetings\vxl_doc_rules.*, with a class description at the very =
least.
4. The code should build, preferably warning-free, on the platforms on =
our dashboard. You will get feedback, especially about building problems =
on vxl-maintainers.
5. The code should have good coverage with regression testing.
6. I guess the most important, if least explicit, is that it should fit =
neatly into the VXL framework, and the VXL philosophy, e.g. use existing =
classes for its API, not depend on too many other libraries, etc.

It isn't necessary that the first draft of your code in the repository =
meets the requirements, but I think it is expected that your code will =
evolve into that.

In order to get your code into vxl/core, there are some additional =
hurdles, that were agreed at one of the VXL meetings.

1. All the above 'shoulds' become 'musts' unless there is a good reason.

2. A 2nd site must be happily using your library. (It is unclear whether =
that second site needs to be a well known member of the VXL community)

3. There must be a texinfo chapter for the VXL book, that provides a =
beginners introduction and tutorial to your library.

Ian.



> -----Original Message-----
> From: vxl...@li...
> [mailto:vxl...@li...]On Behalf Of Marchadier
> Jocelyn
> Sent: Friday, April 30, 2004 2:08 PM
> To: vxl...@li...
> Cc: kr...@pr...
> Subject: [Vxl-users] VXL contribution
>=20
>=20
> Hello,
>=20
> I am currently working in the PRIP group in Vienna University=20
> of Technology=20
> (www.prip.tuwien.ac.at). We are mainly studying graph-based=20
> representations=20
> and digital topology for computer vision and pattern recognition.=20
>=20
> I have developed a software library for efficiently handling=20
> topological=20
> partitions (with combinatorial maps) and pyramids of partitions=20
> (combinatorial pyramids) of surfaces and 2d images (a bit=20
> like vtol). The=20
> partitions can be defined with an arbitrary embedding=20
> (digital planes,=20
> euclidean plane). This small library has been used in image=20
> segmentation=20
> applications, helped to extract primitves (line segments...),=20
> to represent=20
> geographic contents and to render polyhedrons.=20
>=20
> We think that it could be a nice contribution to the VXL=20
> library and we would=20
> like to add it to the VXL repository. Can we do this ? How=20
> can we do this ?=20
> What are the requirements (coding standards ...) ?
>=20
> Sincerely,=20
> --=20
> Jocelyn Marchadier
> Pattern Recognition and Image Processing Group (PRIP)
> Institute for Computer Aided Automation
> Vienna University of Technology
> Favoritenstra=DFe 9/1832
> A-1040 Wien, AUSTRIA
> tel. : (+43-1) 58801-18358
> e-mail : jm...@pr...
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by: Oracle 10g
> Get certified on the hottest thing ever to hit the market...=20
> Oracle 10g.=20
> Take an Oracle 10g class now, and we'll give you the exam FREE.
> http://ads.osdn.com/?ad_id149&alloc_id=8166&op=3Dick
> _______________________________________________
> Vxl-users mailing list
> Vxl...@li...
> https://lists.sourceforge.net/lists/listinfo/vxl-users
>=20