Date: Mon, 25 Feb 2008 17:08:58 +0300 From: "(GalaxyMaster)" <galaxy@...nwall.com> To: oss-security@...ts.openwall.com Subject: Re: wiki page/namespace names, wiki feature requests, etc. On Mon, Feb 25, 2008 at 08:50:18AM -0500, Josh Bressers wrote: > could be useful to have a namespace called terms, or definitions, or > something similar, where we could provide some definitions of the various > security related terminology (things like buffer overflow, and double free > mean very little to most people). Moreover, I can make some tweaks and such a page could be automatically referenced from other pages. For instance, if we maintain a page with common abbreviations then any other page which mention a defined abbreviation would have an on-hover event with a description of the abbreviation. Just an idea. > The problem I see though, is keeping track of all these terms. Is there a > way I could create a page called "terms:buffer_overflow", that would then > be magically added to an index at "terms"? I can install the auto-index plugin that does this. Currently, we are running a bare installation of DokuWiki with the minimal set of plugins. One more topic to discuss is where all these Wiki enhancements should be discussed. I feel that oss-security is the wrong place since this mailing list's goal is to discuss security and not the Wiki itself. Perhaps, all Wiki-related discussions should go to to a namespace that is describing the Wiki itself, and once some functionality is discussed there - a short request for approval/disapproval should be posted here. My concern is that if we move the whole Wiki-enhancement topic off this list we might lose a connection between people on this list (who are populating the Wiki) and a team who is maintaining the Wiki (currently, it's me and Solar). -- (GM)
Powered by blists - more mailing lists
Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.