[Bf-committers] A more different reorganization of the development section

[D.J. Capelis]

See the difference between the two thought processes going on here is you've
got a layout for new developers and I'm trying to rig something that's also
useful for current developers as well.

I dunno about you, but in a development portal I don't want to have to go to
step 6 just so I can file a bug that I just noticed.  It's important that we
remember that development portals need to be useful for developers.  Recruiting
new developers can't be their sole purpose.

That's why I put what you had in mind _under_ the "Getting Involved" section. 
That way current developers can just get access to the tools that are critical
for work, people just coming to file a bug and leave can do that... and those
wanting to become developers can do that as well.

I think you're going to another right place, but we need to have both.

--- Shaul Kedem <shaul.kedem at gmail.com> wrote:

> DJCapelis, 
> 
>  I agree that we need the communication channels , trackers, links,
> etc. and that is part of the plan.
> 
>  As for the rest of the email, having a division between getting
> involved and current work is nice, but it's a different view on the
> same information, since if we won't have it in the "getting involved"
> part new coders will not have the benefit of knowing what is going on.
> 
>  I think that the current work should be represented in the getting
> involved part, making a whole. something like a "development portal"
> of sorts.
> 
> Shaul 

~D.J. Capelis~
Network Security and Cryptography Researcher.
Prepare for the launch of SGA, coming Quarter 4 2005.

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com