<div dir="ltr">Thanks Julien! I attempted to build the UI branch the other day and it failed. I will try again shortly and let you know. I'm eager to test the User Preferences tabs.</div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr">Jonathan Williamson<div><a href="http://cgcookie.com" target="_blank">http://cgcookie.com</a></div></div></div></div>
<br><div class="gmail_quote">On Sat, Apr 25, 2015 at 9:47 AM, Julian Eisel <span dir="ltr"><<a href="mailto:eiseljulian@gmail.com" target="_blank">eiseljulian@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Alright, I set up the basic wiki page<br>
(<a href="http://wiki.blender.org/index.php/Dev:Doc/Projects/UI/UI_experiments_branch" target="_blank">http://wiki.blender.org/index.php/Dev:Doc/Projects/UI/UI_experiments_branch</a>)<br>
and linked to it from the UI Projects page.<br>
<br>
I'd propose that UI-team owners and devs are allowed to invite people<br>
to use the branch. Of course designers can do that as well after<br>
checking with a dev/owner (I added an invitation template to the<br>
branch's wiki page - not mandatory, just for laziness ;) ). I think<br>
this way we can keep things organized.<br>
<br>
@Pawel, sounds good, feel free to send the first invitation :)<br>
<br>
The branch is currently equal to latest master, so everything should<br>
be ready now. Let's start playing!<br>
<br>
Cheers,<br>
- Julian -<br>
<div class="HOEnZb"><div class="h5"><br>
On Fri, Apr 17, 2015 at 9:41 PM, Jonathan Williamson<br>
<<a href="mailto:jonathan@cgcookie.com">jonathan@cgcookie.com</a>> wrote:<br>
> This is good. Thanks for setting it up Julian!<br>
><br>
> Jonathan Williamson<br>
> <a href="http://cgcookie.com" target="_blank">http://cgcookie.com</a><br>
><br>
> On Wed, Apr 15, 2015 at 10:37 AM, Diego Gangl <<a href="mailto:dnicolas@gmail.com">dnicolas@gmail.com</a>> wrote:<br>
>><br>
>> Hey \o<br>
>><br>
>> What would be the workflow for this? do we post patches and the team<br>
>> votes on them (and then you commit them)?<br>
>><br>
>> also, +1 for addon icons<br>
>><br>
>> Cheers,<br>
>><br>
>> 2015-04-14 16:27 GMT-03:00 Paweł Łyczkowski <<a href="mailto:pawellyczkowski@gmail.com">pawellyczkowski@gmail.com</a>>:<br>
>> > Awesome.<br>
>> ><br>
>> > Could be a good opportunity to revive "Icons for Add-ons" development.<br>
>> > Here<br>
>> > it is: <a href="https://developer.blender.org/D645" target="_blank">https://developer.blender.org/D645</a><br>
>> ><br>
>> > Julian Eisel wrote:<br>
>> ><br>
>> ><br>
>> > Hey guys!<br>
>> ><br>
>> > Today I set up a new branch 'UI-experiments'<br>
>> > (<a href="https://developer.blender.org/diffusion/B/browse/UI-experiments/" target="_blank">https://developer.blender.org/diffusion/B/browse/UI-experiments/</a>) so<br>
>> > we finally have a place where we can test and develop features without<br>
>> > having to worry about anything (well almost), it's our personal<br>
>> > playground. I talked about it with Pablo last week and we decided to<br>
>> > give it a go.<br>
>> ><br>
>> > The only three rules I propose:<br>
>> > - No features from which we know they won't end up in master (rather<br>
>> > soonish). The purpose of this branch is to develop features towards<br>
>> > master (this also includes testing). If we don't see someone working<br>
>> > on a feature for a some months, and we can't see the will to do s o, we<br>
>> > simply kick the feature out<br>
>> > - Features that go in must have an own up-to-date branch (local or<br>
>> > remote) to make the final merge with master easier. This is in the<br>
>> > hands of the developer of the feature - he has to prepare the feature<br>
>> > for final merge, which can be difficult and annoying if you need to do<br>
>> > it from a branch that is really diverged from master<br>
>> > - All added features and the people involved must be listed somewhere<br>
>> > so we can keep track of them easily (wiki page?)<br>
>> ><br>
>> > I can take care of the branch by making sure it stays up-to-date with<br>
>> > master and builds fine (and maybe we can create testbuilds on and<br>
>> > off).<br>
>> ><br>
>> > Curious to hear feedback and to get this running. If we got everything<br>
>> > organized we can start bombing the branch with features :)<br>
>> ><br>
>> > Cheers,<br>
>> > - Julian -<br>
>> > _______________________________________________<br>
>> > Bf-interface mailing list<br>
>> > <a href="mailto:Bf-interface@blender.org">Bf-interface@blender.org</a><br>
>> > <a href="http://lists.blender.org/mai" target="_blank">http://lists.blender.org/mai</a> lman/listinfo/bf-interface<br>
>> ><br>
>> ><br>
>> > _______________________________________________<br>
>> > Bf-interface mailing list<br>
>> > <a href="mailto:Bf-interface@blender.org">Bf-interface@blender.org</a><br>
>> > <a href="http://lists.blender.org/mailman/listinfo/bf-interface" target="_blank">http://lists.blender.org/mailman/listinfo/bf-interface</a><br>
>> ><br>
>> _______________________________________________<br>
>> Bf-interface mailing list<br>
>> <a href="mailto:Bf-interface@blender.org">Bf-interface@blender.org</a><br>
>> <a href="http://lists.blender.org/mailman/listinfo/bf-interface" target="_blank">http://lists.blender.org/mailman/listinfo/bf-interface</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Bf-interface mailing list<br>
> <a href="mailto:Bf-interface@blender.org">Bf-interface@blender.org</a><br>
> <a href="http://lists.blender.org/mailman/listinfo/bf-interface" target="_blank">http://lists.blender.org/mailman/listinfo/bf-interface</a><br>
><br>
_______________________________________________<br>
Bf-interface mailing list<br>
<a href="mailto:Bf-interface@blender.org">Bf-interface@blender.org</a><br>
<a href="http://lists.blender.org/mailman/listinfo/bf-interface" target="_blank">http://lists.blender.org/mailman/listinfo/bf-interface</a><br>
</div></div></blockquote></div><br></div>