Taras,
On Wed, Mar 31, 2010 at 9:27 AM, Taras <naplan...@gmail.com> wrote:
> Andres,
>
>> > What I suggest is to start writting "W3AF Dev Guide" and follow it.
>> > It also will help new developers of w3af and w3af plugins to start
>> > quickly. I can prepare lite draft version.
>> >
>> > What do you think about it?
>>
>> Sure! Maybe we could start using Trac's wiki?
> Agree. Wiki will be nice place for such purpose.
> By the way, do we plan to totally migrate (bug tracking, wiki and so
> on) to the Trac?
Yes, the idea is to migrate everything. The problem is that
sourceforge's trac is "broken" [0] and migration might be somehow
difficult. I asked them if they had any way of automatically migrating
sourceforge bug tracker information to trac, they told me that they
don't.
I think I'll manually migrate the 75 open bugs we have on Thu or Fri.
[0] https://sourceforge.net/apps/trac/sourceforge/ticket/1416
> --
> Taras
> --
> "Software is like sex: it's better when it's free.", - Linus Torvalds.
>
--
Andrés Riancho
Founder, Bonsai - Information Security
http://www.bonsai-sec.com/
http://w3af.sf.net/
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
W3af-develop mailing list
W3af-develop@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/w3af-develop
