[Trac] Missing library/component information. (attn: library authors)
It would be tremendously helpful to everyone if all the libraries had corresponding components and maintainers in Trac. So here's a short list of how you can help: * Read over the maintainers list in trac <http://svn.boost.org/trac/boost/report/15> * If you see a library, tool, or other component missing please respond with: the component name, the maintainer trac login name, and optionally a description of the component. * You might notice that some names are missing, even though the component has an assigned maintainer. So, also go to the list of users in Trac <http://svn.boost.org/trac/boost/report/16>. If you see the entry for yourself without a "Name" please go to the Trac settings <http://svn.boost.org/trac/boost/settings> and fill in a name. With luck, and effort, this maintainer list will be complete and we might no longer need the one in source (root/libs/maintainers.txt). -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
Hi Rene "Rene Rivera" <grafikrobot@gmail.com> wrote in message news:47001420.6090803@gmail.com...
It would be tremendously helpful to everyone if all the libraries had corresponding components and maintainers in Trac. So here's a short list of how you can help:
* Read over the maintainers list in trac <http://svn.boost.org/trac/boost/report/15>
* If you see a library, tool, or other component missing please respond with: the component name
statechart
, the maintainer trac login name
andreas_huber69
, and optionally a description of the component.
Boost.Statechart - Arbitrarily complex finite state machines can be implemented in easily readable and maintainable C++ code. Thanks! -- Andreas Huber When replying by private email, please remove the words spam and trap from the address shown in the header.
Rene Rivera wrote:
* If you see a library, tool, or other component missing please respond with: the component name, the maintainer trac login name, and optionally a description of the component.
uBLAS -> guwi17 description: uBLAS provides matrix and vector classes as well as basic linear algebra routines. Several dense, packed and sparse storage schemes are supported. mfg Gunter
Rene,
It would be tremendously helpful to everyone if all the libraries had corresponding components and maintainers in Trac. So here's a short list of how you can help:
* Read over the maintainers list in trac <http://svn.boost.org/trac/boost/report/15>
* If you see a library, tool, or other component missing please respond with: the component name, the maintainer trac login name, and optionally a description of the component.
* You might notice that some names are missing, even though the component has an assigned maintainer. So, also go to the list of users in Trac <http://svn.boost.org/trac/boost/report/16>. If you see the entry for yourself without a "Name" please go to the Trac settings <http://svn.boost.org/trac/boost/settings> and fill in a name.
Would it be possible to add a description to the Wave library? What about: 'The [http://www.boost.org/libs/wave/index.html Boost.Wave] library is a Standards conformant, and highly configurable implementation of the mandated C99/C++ preprocessor functionality packed behind an easy to use iterator interface.' Should we add the wave tool separately? Regards Hartmut
Hartmut Kaiser wrote:
Would it be possible to add a description to the Wave library?
Of course... It's done now.
Should we add the wave tool separately?
That's up to you. If you want it that way. The only reason to do I can think of is if you want bugs from the library and tool to be separate. But perhaps users will be confused as to which one to choose. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
Rene,
Would it be possible to add a description to the Wave library?
Of course... It's done now.
Thanks.
Should we add the wave tool separately?
That's up to you. If you want it that way. The only reason to do I can think of is if you want bugs from the library and tool to be separate. But perhaps users will be confused as to which one to choose.
You're right. Let's keep everything together. Regards Hartmut
participants (4)
-
Andreas Huber -
Gunter Winkler -
Hartmut Kaiser -
Rene Rivera