[Bf-interface] A branch for experimental UI dev

[Julian Eisel]

Alright, I set up the basic wiki page
(http://wiki.blender.org/index.php/Dev:Doc/Projects/UI/UI_experiments_branch)
and linked to it from the UI Projects page.

I'd propose that UI-team owners and devs are allowed to invite people
to use the branch. Of course designers can do that as well after
checking with a dev/owner (I added an invitation template to the
branch's wiki page - not mandatory, just for laziness ;) ). I think
this way we can keep things organized.

@Pawel, sounds good, feel free to send the first invitation :)

The branch is currently equal to latest master, so everything should
be ready now. Let's start playing!

Cheers,
- Julian -

On Fri, Apr 17, 2015 at 9:41 PM, Jonathan Williamson
<jonathan at cgcookie.com> wrote:
> This is good. Thanks for setting it up Julian!
>
> Jonathan Williamson
> http://cgcookie.com
>
> On Wed, Apr 15, 2015 at 10:37 AM, Diego Gangl <dnicolas at gmail.com> wrote:
>>
>> Hey \o
>>
>> What would be the workflow for this? do we post patches and the team
>> votes on them (and then you commit them)?
>>
>> also, +1 for addon icons
>>
>> Cheers,
>>
>> 2015-04-14 16:27 GMT-03:00 Paweł Łyczkowski <pawellyczkowski at gmail.com>:
>> > Awesome.
>> >
>> > Could be a good opportunity to revive "Icons for Add-ons" development.
>> > Here
>> > it is: https://developer.blender.org/D645
>> >
>> > Julian Eisel wrote:
>> >
>> >
>> > Hey guys!
>> >
>> > Today I set up a new branch 'UI-experiments'
>> > (https://developer.blender.org/diffusion/B/browse/UI-experiments/) so
>> > we finally have a place where we can test and develop features without
>> > having to worry about anything (well almost), it's our personal
>> > playground. I talked about it with Pablo last week and we decided to
>> > give it a go.
>> >
>> > The only three rules I propose:
>> > - No features from which we know they won't end up in master (rather
>> > soonish). The purpose of this branch is to develop features towards
>> > master (this also includes testing). If we don't see someone working
>> > on a feature for a some months, and we can't see the will to do s o, we
>> > simply kick the feature out
>> > - Features that go in must have an own up-to-date branch (local or
>> > remote) to make the final merge with master easier. This is in the
>> > hands of the developer of the feature - he has to prepare the feature
>> > for final merge, which can be difficult and annoying if you need to do
>> > it from a branch that is really diverged from master
>> > - All added features and the people involved must be listed somewhere
>> > so we can keep track of them easily (wiki page?)
>> >
>> > I can take care of the branch by making sure it stays up-to-date with
>> > master and builds fine (and maybe we can create testbuilds on and
>> > off).
>> >
>> > Curious to hear feedback and to get this running. If we got everything
>> > organized we can start bombing the branch with features :)
>> >
>> > Cheers,
>> > - Julian -
>> > _______________________________________________
>> > Bf-interface mailing list
>> > Bf-interface at blender.org
>> > http://lists.blender.org/mai lman/listinfo/bf-interface
>> >
>> >
>> > _______________________________________________
>> > Bf-interface mailing list
>> > Bf-interface at blender.org
>> > http://lists.blender.org/mailman/listinfo/bf-interface
>> >
>> _______________________________________________
>> Bf-interface mailing list
>> Bf-interface at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-interface
>
>
>
> _______________________________________________
> Bf-interface mailing list
> Bf-interface at blender.org
> http://lists.blender.org/mailman/listinfo/bf-interface
>