[Bf-committers] Blender developers meeting notes - 2018-12-03

Tue Dec 11 20:38:28 CET 2018

> We could do a call for documentation contributors at some point? Though
> that will also be some work to manage.

Yes but not sure exactly how well this will turn out based
on past contribution attempts. My biggest concern right now is the Grease
Pencil
which will be nice to get help from the developers who worked on this.

> Are you referring to documentation specific ones? You can close any that
> you think are no longer relevant or will be acted upon.

> For Blender development tasks we follow the same rule, not sure when it
> will all be updated. I close ones that I encounter, but some time needs to
> be made to go through them all.

I was referring mostly Blender bug reports/patches manly talking about BGE
and BI render.
These can be easily closed unless we want to provide support for these
features still.
Phab has a feature to edit many tasks at once in a project.

> It appears that close to every page that has a UI component to it will
need
> changes for 2.8, because of changes in shortcuts, menu paths, and shelves
> where things live. This is a massive amount of work and mostly pretty
> mechanical (though not particularly easy to automate). Is someone working
> on all of those changes, or do we need a big infusion of volunteers to do
> that?

These as been work to update the UI docs in general see these patches:
https://developer.blender.org/differential/query/.xO9ozEeacW8/#R

For specific tools these will have to be updated manually yes but
I don't think that we need a large number of people to work on this.
Someone will just have to search for terms: ":kbd:" and ":menuselection:"
This will take a couple hours to check, it is not hard but it will just be
tedious.

On Tue, Dec 11, 2018 at 12:23 PM Howard Trickey <howard.trickey at gmail.com>
wrote:

> It appears that close to every page that has a UI component to it will need
> changes for 2.8, because of changes in shortcuts, menu paths, and shelves
> where things live. This is a massive amount of work and mostly pretty
> mechanical (though not particularly easy to automate). Is someone working
> on all of those changes, or do we need a big infusion of volunteers to do
> that?
>
> On Tue, Dec 11, 2018 at 12:19 PM Brecht Van Lommel <
> brechtvanlommel at gmail.com> wrote:
>
> > On Mon, Dec 10, 2018 at 7:45 PM Aaron Carlisle <carlisle.b3d at gmail.com>
> > wrote:
> >
> > > Some might have noticed some work has been started on documentation.
> > > The past couple of weeks have been busy but I am planning to spend
> > > a lot of time on this over my holiday break. I am just writing this so
> > that
> > > people know what is going on.
> > >
> >
> > Sounds great!
> >
> > We could do a call for documentation contributors at some point? Though
> > that will also be some work to manage.
> >
> >
> > > Also there are lots of bugs and patches opened for features
> > > that are now obsolete, when is the plan to close all these?
> > >
> >
> > Are you referring to documentation specific ones? You can close any that
> > you think are no longer relevant or will be acted upon.
> >
> > For Blender development tasks we follow the same rule, not sure when it
> > will all be updated. I close ones that I encounter, but some time needs
> to
> > be made to go through them all.
> >
> > Regards,
> > Brecht.
> >
> >
> >
> >
> > > Best,
> > >
> > > Aaron Carlisle
> > >
> > > On Mon, Dec 10, 2018 at 1:20 PM Brecht Van Lommel <
> > > brechtvanlommel at gmail.com>
> > > wrote:
> > >
> > > > Hi all,
> > > >
> > > > Here are the notes from today's developer meeting. Next meeting is
> > > Monday,
> > > > 17 December 10:00 CET / 9:00 UTC.
> > > >
> > > > 1) New Features and Changes
> > > >
> > > > This week was mostly about bug triaging and fixing. By my estimate
> > about
> > > > 120 bugs were fixed this week.
> > > >
> > > > * Cycles GPU rendering now has support for NVIDIA Turing cards (RTX
> > 20xx
> > > > and similar). Note this is using CUDA still, not the raytracing
> > hardware
> > > > units at this point.
> > > > * Cycles OpenCL rendering on macOS is no longer supported:
> > > >
> > >
> >
> https://lists.blender.org/pipermail/bf-committers/2018-December/049695.html
> > > > * Animated values that have been modified but not keyframed now get
> an
> > > > orange button color.
> > > > * Render metadata now has an option to include the hostname, useful
> for
> > > > render farms.
> > > > * Shader node editor now includes materials settings panels, so all
> > > > material work can be done in one editor.
> > > > * Wireframe drawing got many optimizations, both for faster drawing
> of
> > > > heavy scenes and when using low end hardware.
> > > > * Grease Pencil has a new arc primitive tool.
> > > >
> > > > 2) Merging Branches
> > > >
> > > > The proposal is to do the following:
> > > > * Rename master to blender2.7 branch, blender2.8 to master.
> > > > * All git history is kept, since it is valuable even if it makes
> bisect
> > > > harder.
> > > > * "BF Blender 2.8" bugs will be moved to "BF Blender", to have a
> single
> > > > tracker. These are already quite mixed up anyway.
> > > > * We keep supporting blender2.7 to more or less the same (minimum)
> > level
> > > as
> > > > we do master now, to ensure there is a production-ready Blender
> version
> > > > being maintained.
> > > > * The blender2.8 branch could be deleted and blocked from being
> > recreated
> > > > on the git server? To avoid users and developers using the wrong
> branch
> > > by
> > > > accident.
> > > >
> > > > If any developers disagree with this, let's discuss it. Otherwise,
> > we'll
> > > do
> > > > the merge in the coming week or two.
> > > >
> > > > 3) Other Projects
> > > >
> > > > The developer wiki has a new theme:
> > > > https://wiki.blender.org
> > > >
> > > > 4) Team
> > > >
> > > > Sebastian Parborg started this week, helping with bug triaging and
> > > fixing.
> > > > Welcome!
> > > >
> > > > 5) Weekly Reports
> > > >
> > > > * Bastien:
> > > >
> > > >
> > >
> >
> https://wiki.blender.org/wiki/User:Mont29/Foundation/2018#Week_273_-_12.2F01_to_12.2F07
> > > > * Brecht:
> > > >
> https://wiki.blender.org/wiki/User:Brecht/Reports/2018#December_3_-_7
> > > > * Campbell:
> > > >
> > > >
> > >
> >
> https://download.blender.org/ftp/ideasman42/donelist/2018.html#week-303-december-3
> > > > * Clément:
> > > >
> > > >
> > >
> >
> https://wiki.blender.org/wiki/User:Hypersomniac/Foundation/2018#Week_100_:_3rd_-_9th_Dec
> > > > * Dalai:
> > > >
> > https://wiki.blender.org/wiki/User:Dfelinto/Reports/2018#December_3_-_7
> > > > * Jacques:
> > > >
> > > >
> > >
> >
> https://wiki.blender.org/wiki/User:JacquesLucke/Reports/2018#Week_12:_December_3-7
> > > > * Philipp:
> > > >
> > > >
> > >
> >
> https://wiki.blender.org/wiki/User:PhilippOeser/Foundation/2018#Calendar_Week_49_.28Dec_3rd_-_Dec_7th.29
> > > > * Sergey:
> > > >
> > > >
> > >
> >
> https://wiki.blender.org/wiki/User:Sergey/Foundation/2018#Week_364:_3d_-_9th_December
> > > > _______________________________________________
> > > > Bf-committers mailing list
> > > > Bf-committers at blender.org
> > > > https://lists.blender.org/mailman/listinfo/bf-committers
> > > >
> > >
> > >
> > > --
> > > Aaron Carlisle
> > >
> > > Project administrator for the Blender 3D Documentation Project
> > > Email: carlisle.b3d at gmail.com
> > > Website: https://blendify.github.io
> > > _______________________________________________
> > > Bf-committers mailing list
> > > Bf-committers at blender.org
> > > https://lists.blender.org/mailman/listinfo/bf-committers
> > >
> > _______________________________________________
> > Bf-committers mailing list
> > Bf-committers at blender.org
> > https://lists.blender.org/mailman/listinfo/bf-committers
> >
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> https://lists.blender.org/mailman/listinfo/bf-committers
>

-- 
Aaron Carlisle

Project administrator for the Blender 3D Documentation Project
Email: carlisle.b3d at gmail.com
Website: https://blendify.github.io