[Bf-committers] Blender developers meeting minutes - February 27, 2016
ton at blender.org
Sun Feb 28 12:16:43 CET 2016
Look at this beautiful WYSIWYG demo page on mediawiki:
Just click edit and it's available right away. It even supports D&D image upload (only with account).
Ton Roosendaal - ton at blender.org - www.blender.org
Chairman Blender Foundation - Producer Blender Institute
Entrepotdok 57A - 1018AD Amsterdam - The Netherlands
> On 28 Feb, 2016, at 2:33, Campbell Barton <ideasman42 at gmail.com> wrote:
> On Sun, Feb 28, 2016 at 11:48 AM, Sergey Sharybin <sergey.vfx at gmail.com> wrote:
>> Dan, i'm not talking about compilation on server, talking about compilation
>> on my laptop and desktop.
>> Campbell, I don't follow IRC that much, but happened few times there.
>> As for timing, while it's not exact 30min (at least not with latest sources
>> etc), it's an order of magnitude more on my core i7 desktop, took almost
>> 10min to do a rebuilt. After doing simple modifications it's in average
>> While content was based on existing wiki, remember how much effort was put
>> to fix missing pages and broken libraries.
>> In any case, we can compare who's machine is faster, it's all not gonna to
>> make things faster here and it's not what's the thread originally was about.
>> Let me summarize and stop wasting time and energy in this discussion.
>> - I am an opponent of increasing offline-factor of documentation, it just
>> adds extra complexity without solving any real issues, or will have the
>> same technical aspect issues if they're becoming any more popular for
>> - I am also an opponent of using dev.b.o's wiki: it is a limited wiki
>> engine, it would have more issues as any stand-alone wiki, it wouldn't
>> really be any more sustainable to abuse that the current wiki.b.o and i do
>> not want dev.b.o being abused in any way.
>> - I do agree with the fact that we should fresh install wiki and not have
>> any piss-poor hacks in it, and keep it maintainable, accessible by the
>> - I do believe with freshly installed and properly configured wiki we can
>> avoid splitting of any documentation further, and to keep documentation in
>> an actual non-broken state we'll need a strong editor team (we'll need it
>> with any underlying tool for docs/manual, it's not something new, it is
>> just something current wiki is lacking completely).
> +1 this has been the plane for some time anyway, closed T47563.
> In the future it would be good if we could discuss topics without knee
> jerk reactions and mixing up multiple topics.
> Bf-committers mailing list
> Bf-committers at blender.org
More information about the Bf-committers