Re: [Slashcode-development] I'd like to contribute

[shane <sh...@lo...>]

On May 3, 2007, at 3:51 AM, Faye Gibbins wrote:

>
> Hi,
>
>   I'm a Sys Admin at Edinburgh Uni, Scotland. I'm doing work on
> installing slash as a non root user in SSL enabled apache servers  
> which
> use external authentication (I'm also a PostgreSQL DBA, so I might  
> touch
> on that as well). My primary platforms are SL4, RHEL4 and FC6.
>
>   I'm fluent in Perl/SQL and would like to contribute patches to the
> slash code as and when I find bugs and possible enhancements.
>
>   Please let me know the etiquette/methodology for doing so.
>
> Yours
> Faye Gibbins

Welcome aboard :)

Here's my understanding of how OSTG wants things:

When you diff: diff -N -U3 -xCVS -r from the root of your CVS checkout.

When you find what you think is a bug, goto Slashcode's SF homepage  
and browse the bug list:

http://sourceforge.net/tracker/?group_id=4421&atid=104421

If you don't find anything relevant, then create a new bug report.

Keep in mind the version of Slashcode you are using, however. Because  
if you are using an older T_ or R_ tag, what you are reporting on may  
have already been fixed by someone, but there's no mention of it in  
Slash's SF.

That's about it. I try to, if I think I've found a bug, submit a diff  
with it to patch if I can. Same with feature requests. Like many  
opensource projects, the easier you can make it for those w/ commit  
access to make the change, the higher the odds are that what you want  
done will be included :)

You should hop on the IRC channel if you can, too.

  Shane




--
My slashcode stuff: http://slash.lottadot.com/
Slashcode faq: http://slash.lottadot.com/slash-faq
How to ask a question: http://www.catb.org/~esr/faqs/smart- 
questions.html#before