Re: [Slashcode-development] Chat for slash

[Brian A. <br...@ta...>]

On Tue, 2002-03-05 at 06:20, shane wrote:

> 2. When it's a plugin for slash, the module will actually be Slash::{name}.
>   Example: I'm working on the calendar plugin, and ran into naming problems 
> clashing with
>   Slash::Events.
> 
>   My module name is Slash::Calleria. Slash::Events has a script called 
> calendar.pl,
>   and so did mine. So mine is now called calleria.pl.
Should have mentioned that to me, I would have been happy to change it
:)

>   So you may want to consider picking unique names for your module and scripts,
>   because anything either a) included in the normal slash bundle/install or b)
>   (I assume) anything done by some of the slash guys is going to take priority
>   over what outsiders have done, if not only for the lack of time they'd have
>   to keep renaming their stuff because contributors keep using basic names
>   that conflict, and we want them to write as much functionality as possible :)
Register plugins in the repository on Slashcode. That way people can
look up names and see what has been taken. 

	-Brian
-- 
_______________________________________________________
Brian Aker, br...@ta... 
Slashdot Senior Developer
Seattle, Washington
http://tangent.org/~brian/
http://askbrian.org/
_______________________________________________________
You can't grep a dead tree.