I just wish whatever we had were as easy to write documentation *with diagrams* in as, say, Google Docs. (I know, Google Docs doesn't have a linking structure that would make it suitable for what we are talking about here, but it does have reasonable diagramming and image insertion tools.) I found it quite tedious doing this: http://wiki.blender.org/index.php/Dev:Source/Modeling/Bevel . But wish more developers would spend time doing it about areas where we have to explore design tradeoffs and algorithms. And, I suppose relevant to this discussion, that Bevel documentation is a bit out of date now, partially because it is annoying to make new pictures in our current wiki system.
- Howard On Sat, Feb 27, 2016 at 7:14 AM Ton Roosendaal <[email protected]> wrote: > Hi, > > > - @Blendify proposes to migrate developer documentation to new system > > (and help with the migration), > > https://developer.blender.org/T47563 > > Seriously? I would rather discuss to move manual back to wiki one day. > The manual procedure we have now scares away nearly everyone who would > consider to help. > > I'd don't see evidence that Sphinx will work to get more people contribute > to Blender docs. It's really great to see 1 or 2 people contribute there so > much, but you cannot call it a community project... > > -Ton- > > -------------------------------------------------------- > Ton Roosendaal - [email protected] - www.blender.org > Chairman Blender Foundation - Producer Blender Institute > Entrepotdok 57A - 1018AD Amsterdam - The Netherlands > > > > > On 27 Feb, 2016, at 2:26, Campbell Barton <[email protected]> wrote: > > > > Hi, here are the notes from today's meeting in irc.freenode.net > #blendercoders. > > > > 1) Upcoming release > > > > So far things go smooth with 2.77rc1, reminder that release notes need > > attention still. > > > > - Mike Erwin will do OpenGL release notes. > > > > > > 2) Current projects > > > > - Developers confirm that after 2.77 we should *stop* focusing > > on 2.7x and move attention to bigger 2.8x projects. > > However discussion shows we still need more concrete planning. > > > > - UI team will start having its own meetings, > > current plan is to hold after next developer meeting. > > Will be announced on the bf-committers mailing list. > > > > - UI project has _many_ open tasks with discussion and no conclusion, > > these tasks could use some decisions from UI design leads. > > (or archive if theirs no clear outcome and nobody has time for them). > > > > > > 3) Other Projects > > > > - Kevin Dietrich has begun work on the DwarfLabs Alembic patch, > > plans to move development to a branch and update to support > > import/export based on suggested changes in review. > > https://developer.blender.org/D1783 > > > > - @Blendify proposes to migrate developer documentation to new system > > (and help with the migration), > > https://developer.blender.org/T47563 > > > > However others in meeting prefer further discussion > > on mailing list before going ahead and making changes > > (evaluate Phabricator's Wiki for developer docs for eg). > > > > -- > > - Campbell > > _______________________________________________ > > Bf-committers mailing list > > [email protected] > > http://lists.blender.org/mailman/listinfo/bf-committers > > _______________________________________________ > Bf-committers mailing list > [email protected] > http://lists.blender.org/mailman/listinfo/bf-committers > _______________________________________________ Bf-committers mailing list [email protected] http://lists.blender.org/mailman/listinfo/bf-committers
