Douglas Gregor wrote:

Hmmm. We could create a "dummy" maintainer for these libraries. Even once people log into the Trac, some library maintainers have been absent for a long time...

Sure. "jdoe" and "nobody", as users comes to mind. -- -- 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

Douglas Gregor wrote:

Rene Rivera wrote:

...

Daryle Walker wrote:

...

I was working the ticket list at <http://svn.boost.org/trac/boost/report/14>, trying to re-categorize the issues under the "None" component. I noticed that there isn't any components for the Pool and Optional libraries. How can I add them, or does an administrator have to add new components? (I just picked two at random; there may be other Boost libraries without a component list entry.)

There are others, we talked about some of them last week. Problem is that I need people to log into Trac at least once for me to have a maintainer to assign to new components. You can see the users that have logged in here <http://svn.boost.org/trac/boost/report/16> along with their name if they fill it out in the "Settings". You can also see the current set of components, and their maintainers at <http://svn.boost.org/trac/boost/report/15>.

Hmmm. We could create a "dummy" maintainer for these libraries. Even once people log into the Trac, some library maintainers have been absent for a long time...

Here are some more issues: * Spirit has many maintainers. The proper recipient would be the spirit-devel list (spirit-devel -at- lists.sourceforge.net). * I see that I can simply set up a thunderbird filter to forward to that address when I receive a Trac ticket email. Alas, there's no reliable way to detect a Trac ticket message. The title: [Boost C++ Libraries]... is non-descriptive enough. Rene is looking for way to add the library name to the email title. If all goes well, this trick should do it. But it's useful for other purposes as well (e.g. organizing your inbox). * Some libraries have multiple maintainers. For example, Fusion is maintained by Dan Marsden, Tobias and me. Can a certain set of maintainer have their own identity on the maintainer list and can Trac be setup to fire emails to all maintainers of a specific group? Regards, -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net