[Bf-committers] Wiki reorganization proposal

[Campbell Barton]

Im not that fussed where exactly the scripts go. if bf-scripts is
renamed to bf-extras then the path could be..
bf-extensions/trunk/scripts/2_4x/
bf-extensions/trunk/scripts/2_4x/contrib
bf-extensions/trunk/scripts/2_5x/.... etc
or...
bf-extensions/trunk/2_5x/scripts/

Though Im not sure why we would want to have some scripts in
bf-scripts/bf-extensions and others in bf-blender,  The bf-scripts svn
has alredy failed to gain interest from script developers as a
'contrib' only repo. So if were going to use it at all, Id prefer put
all blenders scripts there and use an external svn repo thingy so
updating blender updates scripts too.

Btw, who wants to do this? :)

On Thu, Jan 15, 2009 at 10:09 AM, Willian Padovani Germano
<wpgermano at gmail.com> wrote:
> Hi,
>
> I agree with moving the scripts to bf-scripts.
>
> It'd be better to clearly label pre 2.5 scripts, by putting them in
> their own branch in bf-scripts or at least under a
> bf-scripts/trunk/2.4x/ folder.
>
> We may also use bf-scripts to store 2.5 scripts, then -- not necessarily
> all, but at least those not shipped with Blender, user contributed, ones
> that need more testing / better ui / docs, etc.
>
> New scripts written for Blender version >= 2.5 will be
> Campbell Barton wrote:
>> Notice hidden in this proposal is moving scripts over to the scripts
>> repo 'bf-scripts'
> (...)
>> Move  bf-blender/trunk/release/scripts/*  to  bf-scripts/trunk/
>>  (make bf-blender/trunk/release/scripts  point to  bf-scripts/trunk as
>> mentioned above)
>>
>> Add a directory in bf-scripts for unsupported, user contributed
>> scripts: bf-scripts/trunk/contrib/
>
> --
> Willian
> http://encanners.net
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>



-- 
- Campbell