Date   

Re: OSL - branding

Zap Andersson
 

I agree completely with Larrys opinions (i.e. mostly liking 3, or enjoying saying "the S means hope" about 4), including the "poor me" part if we are gonna reproduce #3 in OSL code, LOL. :P

The beauty of my logo - if I may say so myself, LOL - is that it's a pretty short snippet of OSL, generating a "fairly nice" logo, with code that I at least hope some people look at and go "how does this even work". :)

Anything not strictly based in math will (as code goes) look a lot less... elegant, full of if-statements and hard-coded numbers for "which thing goes where". 
While that is fine, it spoils the magic a little bit.

But then again, maybe we shouldn't design a logo based on the elegance of the code. 
Or.... us being us ... should we? :)

I am, obviously, 20000% biased, and bow to the wisdom of the group.

/Z

On Thu, Mar 18, 2021 at 8:06 AM Larry Gritz <lg@...> wrote:
I'm also leaning hard against overlapping or unclear letters, it just doesn't work for me. And I think that after prior discussions, Mario had me convinced that we should go more abstract, not try to make the logo BE the words or the letters.

I think 3 and 4 are my favourites of this set.

Is 3 too "busy"? I know that the lines are alluding to the "connection" idea, but to me it reads more as "circuitry" rather than the "shading" that I got clearly from some of the earlier hatching or halftone styles like the middle and upper right examples in section 3 of your Feb 18 email, or Zap's shader. But I could definitely be convinced if people like this variant. (Poor Zap, though, getting those wires exactly right in the shader will be tricky.)

4 also has potential. I'm less bothered than Chris about the missing L, I definitely get the O and S, and I don't mind the superman bit. (And you all know how much we're looking forward to saying "It's not an S" whenever somebody asks us about it.)

5 All I can think of is that the gradients might be hard to reproduce in some media and that it might not be readable small.


On Mar 17, 2021, at 10:43 PM, Chris Kulla <ckulla@...> wrote:

I'm really liking #3 -- ties into the shaded sphere and nodegraph ideas at the same time (and even half-tone dots to some extent).

#1 reads a bit too much like CSL for me

#2 I like the leftmost one, though its getting a bit abstract and i'm not sure about how well it reads over a dark background

#3 Definitely my favorite so far (both color and black&white versions)

#4 Without the L it's hard to read the circle as an O - so it feels more like a superman type of S logo.

#5  The depth effect is cool, though I'd worry that it would look too different to other industry logos and the "cut out hole" effect might not work in all contexts. The O and L also feel a bit squeezed and off-balance.

Overall the designs using the letters never quite click for me. Like you said before, it's a hard combination of letters to make work. But I'm liking where #3 is going.

Thanks for these - really nice work!





On Wed, Mar 17, 2021 at 10:06 PM mariovario via lists.aswf.io <mariovario=pm.me@...> wrote:
Hey,
Since I can't write OSL code and even if I could I think that we should design the logo then transfer it to OSL. I find vector graphics software way faster and nimble with graphics than code... Anyhow... Here is my next iteration of the brand experiments. This time it is all about shading... This is the main idea I was trying to express here. Have look and comment.
PDF attached.

m



--
Larry Gritz






--
--
Håkan "Zap" Andersson - http://twitter.com/MasterZap - the man, the myth, the concept.
--


Re: OSL - branding

Zap Andersson
 

Ok, willdo.

/Z

On Thu, Mar 18, 2021 at 6:43 AM Larry Gritz <lg@...> wrote:
OK, let's talk about this for the first 20 minutes at tomorrow's meeting.

Zap, can you let Jonathan (and anybody else coming *only* for the BSDF discussion) know that it's fine for them to arrive 15-20 minutes after the meeting start if they aren't interested in sitting through the logo discussion? Thanks.



On Mar 17, 2021, at 10:06 PM, mariovario via lists.aswf.io <mariovario=pm.me@...> wrote:

Hey,
Since I can't write OSL code and even if I could I think that we should design the logo then transfer it to OSL. I find vector graphics software way faster and nimble with graphics than code... Anyhow... Here is my next iteration of the brand experiments. This time it is all about shading... This is the main idea I was trying to express here. Have look and comment.
PDF attached.

m

--
Larry Gritz






--
--
Håkan "Zap" Andersson - http://twitter.com/MasterZap - the man, the myth, the concept.
--


Re: OSL - branding

Larry Gritz
 

I'm also leaning hard against overlapping or unclear letters, it just doesn't work for me. And I think that after prior discussions, Mario had me convinced that we should go more abstract, not try to make the logo BE the words or the letters.

I think 3 and 4 are my favourites of this set.

Is 3 too "busy"? I know that the lines are alluding to the "connection" idea, but to me it reads more as "circuitry" rather than the "shading" that I got clearly from some of the earlier hatching or halftone styles like the middle and upper right examples in section 3 of your Feb 18 email, or Zap's shader. But I could definitely be convinced if people like this variant. (Poor Zap, though, getting those wires exactly right in the shader will be tricky.)

4 also has potential. I'm less bothered than Chris about the missing L, I definitely get the O and S, and I don't mind the superman bit. (And you all know how much we're looking forward to saying "It's not an S" whenever somebody asks us about it.)

5 All I can think of is that the gradients might be hard to reproduce in some media and that it might not be readable small.


On Mar 17, 2021, at 10:43 PM, Chris Kulla <ckulla@...> wrote:

I'm really liking #3 -- ties into the shaded sphere and nodegraph ideas at the same time (and even half-tone dots to some extent).

#1 reads a bit too much like CSL for me

#2 I like the leftmost one, though its getting a bit abstract and i'm not sure about how well it reads over a dark background

#3 Definitely my favorite so far (both color and black&white versions)

#4 Without the L it's hard to read the circle as an O - so it feels more like a superman type of S logo.

#5  The depth effect is cool, though I'd worry that it would look too different to other industry logos and the "cut out hole" effect might not work in all contexts. The O and L also feel a bit squeezed and off-balance.

Overall the designs using the letters never quite click for me. Like you said before, it's a hard combination of letters to make work. But I'm liking where #3 is going.

Thanks for these - really nice work!





On Wed, Mar 17, 2021 at 10:06 PM mariovario via lists.aswf.io <mariovario=pm.me@...> wrote:
Hey,
Since I can't write OSL code and even if I could I think that we should design the logo then transfer it to OSL. I find vector graphics software way faster and nimble with graphics than code... Anyhow... Here is my next iteration of the brand experiments. This time it is all about shading... This is the main idea I was trying to express here. Have look and comment.
PDF attached.

m



--
Larry Gritz





Re: OSL - branding

Chris Kulla
 

I'm really liking #3 -- ties into the shaded sphere and nodegraph ideas at the same time (and even half-tone dots to some extent).

#1 reads a bit too much like CSL for me

#2 I like the leftmost one, though its getting a bit abstract and i'm not sure about how well it reads over a dark background

#3 Definitely my favorite so far (both color and black&white versions)

#4 Without the L it's hard to read the circle as an O - so it feels more like a superman type of S logo.

#5  The depth effect is cool, though I'd worry that it would look too different to other industry logos and the "cut out hole" effect might not work in all contexts. The O and L also feel a bit squeezed and off-balance.

Overall the designs using the letters never quite click for me. Like you said before, it's a hard combination of letters to make work. But I'm liking where #3 is going.

Thanks for these - really nice work!





On Wed, Mar 17, 2021 at 10:06 PM mariovario via lists.aswf.io <mariovario=pm.me@...> wrote:
Hey,
Since I can't write OSL code and even if I could I think that we should design the logo then transfer it to OSL. I find vector graphics software way faster and nimble with graphics than code... Anyhow... Here is my next iteration of the brand experiments. This time it is all about shading... This is the main idea I was trying to express here. Have look and comment.
PDF attached.

m


Re: OSL - branding

Larry Gritz
 

OK, let's talk about this for the first 20 minutes at tomorrow's meeting.

Zap, can you let Jonathan (and anybody else coming *only* for the BSDF discussion) know that it's fine for them to arrive 15-20 minutes after the meeting start if they aren't interested in sitting through the logo discussion? Thanks.



On Mar 17, 2021, at 10:06 PM, mariovario via lists.aswf.io <mariovario=pm.me@...> wrote:

Hey,
Since I can't write OSL code and even if I could I think that we should design the logo then transfer it to OSL. I find vector graphics software way faster and nimble with graphics than code... Anyhow... Here is my next iteration of the brand experiments. This time it is all about shading... This is the main idea I was trying to express here. Have look and comment.
PDF attached.

m

--
Larry Gritz





OSL - branding

mariovario@...
 

Hey,
Since I can't write OSL code and even if I could I think that we should design the logo then transfer it to OSL. I find vector graphics software way faster and nimble with graphics than code... Anyhow... Here is my next iteration of the brand experiments. This time it is all about shading... This is the main idea I was trying to express here. Have look and comment.
PDF attached.

m


OSL TSC meeting ( every other week ) - Thu, 03/18/2021 2:00pm-3:00pm #cal-reminder

osl-dev@lists.aswf.io Calendar <osl-dev@...>
 

Reminder: OSL TSC meeting ( every other week )

When: Thursday, 18 March 2021, 2:00pm to 3:00pm, (GMT-07:00) America/Los Angeles

Where:https://zoom.us/j/100511909

View Event

Organizer: Chris Kulla ckulla@...

Description:

Every other week meeting of the OSL TSC.

Meeting Agenda / Notes: https://docs.google.com/document/d/1yf0bG6eoE2EvKZBNZX3nskdTvu99ADTDTNOknCDJd1I/

Confirm this meeting invite is still valid by finding the meeting at https://lists.aswf.io/calendar.

Join Zoom Meeting https://zoom.us/j/100511909

Meeting ID: 100 511 909

One tap mobile +16465588656,,100511909# US (New York) +13126266799,,100511909# US (Chicago)

Dial by your location +1 646 558 8656 US (New York) +1 312 626 6799 US (Chicago) +1 669 900 6833 US (San Jose) +1 253 215 8782 US +1 301 715 8592 US +1 346 248 7799 US (Houston) 877 369 0926 US Toll-free 855 880 1246 US Toll-free +1 587 328 1099 Canada +1 647 374 4685 Canada +1 647 558 0588 Canada +1 778 907 2071 Canada +1 438 809 7799 Canada 855 703 8985 Canada Toll-free Meeting ID: 100 511 909 Find your local number: https://zoom.us/u/acBVrM6HWR


Re: OSL getmessage/setmessage

elizabeth.bonnefoy@...
 

Hi Chris

Thank you for your answer!

To give you more context, we try to read volumetric files from OpenVDB via texture3D(), so we need to provide it some arguments like:

- The name of the VDB file, which can hold many grids

- The name of the grid we want to read: "Density", "Heat", "LevelSet", ...

- Some lookup options, like using multi-resolution or not, some multiplicative scale on the filter size, access to the min/max grid useful for the tracking algorithm...

- Eventually the name of some metadata we would like to retrieve from the file

 

Actually it's ok, because as you said it, there is always an argument of texture3D we can use to provide additional informations, even if this could lead to several call to texture3D() for the same file.
We just wanted to know if there was a better way to do it, but we can deal with that.

Thank you again for your time.

Kind regards,

Zab


Upcoming Events #cal-summary

osl-dev@lists.aswf.io Calendar <osl-dev@...>
 

Open Shading Language discussion list Upcoming Events

OSL TSC meeting ( every other week )

When:
Thursday, 18 March 2021, 2:00pm to 3:00pm
(GMT-07:00) America/Los Angeles

Where:
https://zoom.us/j/100511909

Organizer: Chris Kulla ckulla@...

Details:

Every other week meeting of the OSL TSC.

Meeting Agenda / Notes: https://docs.google.com/document/d/1yf0bG6eoE2EvKZBNZX3nskdTvu99ADTDTNOknCDJd1I/

Confirm this meeting invite is still valid by finding the meeting at https://lists.aswf.io/calendar.

Join Zoom Meeting https://zoom.us/j/100511909

Meeting ID: 100 511 909

One tap mobile +16465588656,,100511909# US (New York) +13126266799,,100511909# US (Chicago)

Dial by your location +1 646 558 8656 US (New York) +1 312 626 6799 US (Chicago) +1 669 900 6833 US (San Jose) +1 253 215 8782 US +1 301 715 8592 US +1 346 248 7799 US (Houston) 877 369 0926 US Toll-free 855 880 1246 US Toll-free +1 587 328 1099 Canada +1 647 374 4685 Canada +1 647 558 0588 Canada +1 778 907 2071 Canada +1 438 809 7799 Canada 855 703 8985 Canada Toll-free Meeting ID: 100 511 909 Find your local number: https://zoom.us/u/acBVrM6HWR

View Event


OSL TSC meeting ( every other week )

When:
Thursday, 1 April 2021, 2:00pm to 3:00pm
(GMT-07:00) America/Los Angeles

Where:
https://zoom.us/j/100511909

Organizer: Chris Kulla ckulla@...

Details:

Every other week meeting of the OSL TSC.

Meeting Agenda / Notes: https://docs.google.com/document/d/1yf0bG6eoE2EvKZBNZX3nskdTvu99ADTDTNOknCDJd1I/

Confirm this meeting invite is still valid by finding the meeting at https://lists.aswf.io/calendar.

Join Zoom Meeting https://zoom.us/j/100511909

Meeting ID: 100 511 909

One tap mobile +16465588656,,100511909# US (New York) +13126266799,,100511909# US (Chicago)

Dial by your location +1 646 558 8656 US (New York) +1 312 626 6799 US (Chicago) +1 669 900 6833 US (San Jose) +1 253 215 8782 US +1 301 715 8592 US +1 346 248 7799 US (Houston) 877 369 0926 US Toll-free 855 880 1246 US Toll-free +1 587 328 1099 Canada +1 647 374 4685 Canada +1 647 558 0588 Canada +1 778 907 2071 Canada +1 438 809 7799 Canada 855 703 8985 Canada Toll-free Meeting ID: 100 511 909 Find your local number: https://zoom.us/u/acBVrM6HWR

View Event


OSL TSC meeting ( every other week ) - Thu, 03/18/2021 2:00pm-3:00pm #cal-reminder

osl-dev@lists.aswf.io Calendar <osl-dev@...>
 

Reminder: OSL TSC meeting ( every other week )

When: Thursday, 18 March 2021, 2:00pm to 3:00pm, (GMT-07:00) America/Los Angeles

Where:https://zoom.us/j/100511909

View Event

Organizer: Chris Kulla ckulla@...

Description:

Every other week meeting of the OSL TSC.

Meeting Agenda / Notes: https://docs.google.com/document/d/1yf0bG6eoE2EvKZBNZX3nskdTvu99ADTDTNOknCDJd1I/

Confirm this meeting invite is still valid by finding the meeting at https://lists.aswf.io/calendar.

Join Zoom Meeting https://zoom.us/j/100511909

Meeting ID: 100 511 909

One tap mobile +16465588656,,100511909# US (New York) +13126266799,,100511909# US (Chicago)

Dial by your location +1 646 558 8656 US (New York) +1 312 626 6799 US (Chicago) +1 669 900 6833 US (San Jose) +1 253 215 8782 US +1 301 715 8592 US +1 346 248 7799 US (Houston) 877 369 0926 US Toll-free 855 880 1246 US Toll-free +1 587 328 1099 Canada +1 647 374 4685 Canada +1 647 558 0588 Canada +1 778 907 2071 Canada +1 438 809 7799 Canada 855 703 8985 Canada Toll-free Meeting ID: 100 511 909 Find your local number: https://zoom.us/u/acBVrM6HWR


Re: OCIO via OIIO in OSL (ACRONYM SOUP :) )

Larry Gritz
 

Um, the texture lookups themselves are not color managed. They are assuming that you have done your color management in the "maketx" process, so the textures themselves are in your canonical linear rendering color space.


On Mar 11, 2021, at 8:36 AM, zap.andersson@... wrote:

So if we compile OIIO with OCIO2 for OSL (normal people are gonna wanter WTH I'm talking about :) ) ... is there some way to pass along paramters to OIIO through the OSL texture() call?

I.e. if I say I want a raw lookup (non color managed), is there a parameter for this? To give the color space?  Do something?

/Z

--
Larry Gritz





OCIO via OIIO in OSL (ACRONYM SOUP :) )

Zap Andersson
 

So if we compile OIIO with OCIO2 for OSL (normal people are gonna wanter WTH I'm talking about :) ) ... is there some way to pass along paramters to OIIO through the OSL texture() call?

I.e. if I say I want a raw lookup (non color managed), is there a parameter for this? To give the color space?  Do something?

/Z


Standardizing OSL Closures - The Topic(tm)

Zap Andersson
 

So as mentioned on last weeks OSL TSC meeting, there is a desire to have a default set of closures in OSL that can be supported natively, and on the meeting we said that the set used by MaterialX is a good candidate set.

I've invited Jonatan Stone (Lucasfilm) and Niklas Harrysson (Autodesk) to next TSC meeting to discuss the topic a bit. Both are key contributor to the PBR stuff in MaterialX and are both excited at this idea.

There are some interesting implementation wrinkles to think about, which is why these gentlemen are ideal to help us solve this.

Some "light reading" while we await next meeting:

http://www.materialx.org/assets/MaterialX.v1.38.PBRSpec.pdf

Also this talk by Niklas & Jonathan from SIGGRAPH is relevant viewing

https://www.youtube.com/watch?v=6Lz2wq1tA20

 (Coming form this course https://blog.selfshadow.com/publications/s2020-shading-course/ )


/Z


Re: OSL getmessage/setmessage

Chris Kulla
 

Hi Elizabeth,

I think getmessage is probably not the easiest way forward here. Generally we try to avoid calls that require holding onto state as much as possible (the trace call and getmessage being notable exceptions). In fact you probably noticed already that only the "trace" related getmessage calls will make it to render services. There isn't currently a form of setmessage that will invoke anything on the renderer services side.

It's a bit hard to say without knowing all the details of your use case - but perhaps you could take advantage of the "firstchannel" or "subimage" arguments to the texture call? This would allow you to return different values for different calls to texture3d. Or is there something about your use case that requires you to perform all the work in a single call to texture3d?

Can you give us a few more details about what you would like to pass in and out of the texture3d call?

Cheers,
Chris





On Wed, Mar 3, 2021 at 8:30 AM <elizabeth.bonnefoy@...> wrote:

 

Hi everyone!

I'm a R&D engineer at Illumination MacGuff, and i'm currently trying to use the setmessage() / getmessage() feature from OSL.

To provide a bit of context: we are creating an OSL shader to read our volume files using an override of the RendererServices::texture3d() function for the lookup in the file.

From this OSL shader, we would like to provide some additional arguments to the texture3d() call, and get back some informations from this call which are not in the available values returned by texture3d().

Maybe it is a bad idea - feel free to give me your advice - but we are trying to use setmessage() and getmessage() to do it, and the second part actually works very well: thanks to an override of the RendererServices::getmessage(), we can use the "trace" source to communicate between functions in RendererServices and the OSL shader.
So we succeed to retrieve additional outputs from texture3d() with something like that:

result = texture3d(...);

getmessage("trace", "texture3d_out0", out0);

getmessage("trace", "texture3d_out1", out1);

 

But the first part is problematic, because the setmessage() feature seems to be private. There is no available definition of setmessage() in RendererServices, so we can't override it to use the "trace" source.
Ideally we would like to use it like that:

 

setmessage("trace", "texture3d_arg0", arg0);
setmessage("trace", "texture3d_arg1", arg1);
result = texture3d(...);


Maybe there is an other way to communicate from an OSL shader to a RendererServices functions?

Thank you for your help.
Kind regards,
Zab

 


Upcoming Events #cal-summary

osl-dev@lists.aswf.io Calendar <osl-dev@...>
 

Open Shading Language discussion list Upcoming Events

OSL TSC meeting ( every other week )

When:
Thursday, 18 March 2021, 2:00pm to 3:00pm
(GMT-07:00) America/Los Angeles

Where:
https://zoom.us/j/100511909

Organizer: Chris Kulla ckulla@...

Details:

Every other week meeting of the OSL TSC.

Meeting Agenda / Notes: https://docs.google.com/document/d/1yf0bG6eoE2EvKZBNZX3nskdTvu99ADTDTNOknCDJd1I/

Confirm this meeting invite is still valid by finding the meeting at https://lists.aswf.io/calendar.

Join Zoom Meeting https://zoom.us/j/100511909

Meeting ID: 100 511 909

One tap mobile +16465588656,,100511909# US (New York) +13126266799,,100511909# US (Chicago)

Dial by your location +1 646 558 8656 US (New York) +1 312 626 6799 US (Chicago) +1 669 900 6833 US (San Jose) +1 253 215 8782 US +1 301 715 8592 US +1 346 248 7799 US (Houston) 877 369 0926 US Toll-free 855 880 1246 US Toll-free +1 587 328 1099 Canada +1 647 374 4685 Canada +1 647 558 0588 Canada +1 778 907 2071 Canada +1 438 809 7799 Canada 855 703 8985 Canada Toll-free Meeting ID: 100 511 909 Find your local number: https://zoom.us/u/acBVrM6HWR

View Event


OSL TSC meeting ( every other week )

When:
Thursday, 1 April 2021, 2:00pm to 3:00pm
(GMT-07:00) America/Los Angeles

Where:
https://zoom.us/j/100511909

Organizer: Chris Kulla ckulla@...

Details:

Every other week meeting of the OSL TSC.

Meeting Agenda / Notes: https://docs.google.com/document/d/1yf0bG6eoE2EvKZBNZX3nskdTvu99ADTDTNOknCDJd1I/

Confirm this meeting invite is still valid by finding the meeting at https://lists.aswf.io/calendar.

Join Zoom Meeting https://zoom.us/j/100511909

Meeting ID: 100 511 909

One tap mobile +16465588656,,100511909# US (New York) +13126266799,,100511909# US (Chicago)

Dial by your location +1 646 558 8656 US (New York) +1 312 626 6799 US (Chicago) +1 669 900 6833 US (San Jose) +1 253 215 8782 US +1 301 715 8592 US +1 346 248 7799 US (Houston) 877 369 0926 US Toll-free 855 880 1246 US Toll-free +1 587 328 1099 Canada +1 647 374 4685 Canada +1 647 558 0588 Canada +1 778 907 2071 Canada +1 438 809 7799 Canada 855 703 8985 Canada Toll-free Meeting ID: 100 511 909 Find your local number: https://zoom.us/u/acBVrM6HWR

View Event


OSL TSC meeting ( every other week ) - Thu, 03/04/2021 #cal-notice

osl-dev@lists.aswf.io Calendar <noreply@...>
 

OSL TSC meeting ( every other week )

When:
Thursday, 4 March 2021
2:00pm to 3:00pm
(GMT-08:00) America/Los Angeles

Where:
https://zoom.us/j/100511909

Organizer:
ckulla@...

Description:

Every other week meeting of the OSL TSC.

Meeting Agenda / Notes: https://docs.google.com/document/d/1yf0bG6eoE2EvKZBNZX3nskdTvu99ADTDTNOknCDJd1I/

Confirm this meeting invite is still valid by finding the meeting at https://lists.aswf.io/calendar.

Join Zoom Meeting https://zoom.us/j/100511909

Meeting ID: 100 511 909

One tap mobile +16465588656,,100511909# US (New York) +13126266799,,100511909# US (Chicago)

Dial by your location +1 646 558 8656 US (New York) +1 312 626 6799 US (Chicago) +1 669 900 6833 US (San Jose) +1 253 215 8782 US +1 301 715 8592 US +1 346 248 7799 US (Houston) 877 369 0926 US Toll-free 855 880 1246 US Toll-free +1 587 328 1099 Canada +1 647 374 4685 Canada +1 647 558 0588 Canada +1 778 907 2071 Canada +1 438 809 7799 Canada 855 703 8985 Canada Toll-free Meeting ID: 100 511 909 Find your local number: https://zoom.us/u/acBVrM6HWR


OSL TSC meeting ( every other week ) - Thu, 03/04/2021 2:00pm-3:00pm #cal-reminder

osl-dev@lists.aswf.io Calendar <osl-dev@...>
 

Reminder: OSL TSC meeting ( every other week )

When: Thursday, 4 March 2021, 2:00pm to 3:00pm, (GMT-08:00) America/Los Angeles

Where:https://zoom.us/j/100511909

View Event

Organizer: Chris Kulla ckulla@...

Description:

Every other week meeting of the OSL TSC.

Meeting Agenda / Notes: https://docs.google.com/document/d/1yf0bG6eoE2EvKZBNZX3nskdTvu99ADTDTNOknCDJd1I/

Confirm this meeting invite is still valid by finding the meeting at https://lists.aswf.io/calendar.

Join Zoom Meeting https://zoom.us/j/100511909

Meeting ID: 100 511 909

One tap mobile +16465588656,,100511909# US (New York) +13126266799,,100511909# US (Chicago)

Dial by your location +1 646 558 8656 US (New York) +1 312 626 6799 US (Chicago) +1 669 900 6833 US (San Jose) +1 253 215 8782 US +1 301 715 8592 US +1 346 248 7799 US (Houston) 877 369 0926 US Toll-free 855 880 1246 US Toll-free +1 587 328 1099 Canada +1 647 374 4685 Canada +1 647 558 0588 Canada +1 778 907 2071 Canada +1 438 809 7799 Canada 855 703 8985 Canada Toll-free Meeting ID: 100 511 909 Find your local number: https://zoom.us/u/acBVrM6HWR


Re: OSL - branding

Eric Enderton
 

Very nice!  A possible tweak: Have the dark regions of the sphere form an “S” shape, such as, a crescent in both the lower-right and the upper-left, connecting in the middle somehow.  Then you have both an “O” and an “S”, as well as the concept of 3D shading.

 

From: <osl-dev@...> on behalf of "zap.andersson@..." <zap.andersson@...>
Date: Monday, March 1, 2021 at 7:35 AM
To: "osl-dev@..." <osl-dev@...>
Subject: Re: [OSL Discussion] OSL - branding

 

 

Of course, in the spirit of "eat your own dogfood" (or was it "you are what you eat"?), of course the OSL LOGO should be in OSL

Fully tweakable logo shader - enjoy :)


Enjoy :P

/Z


LFX EasyCLA v2 Release: What you need to know

John Mertic
 

I'm forwarding this note to the various communities for your visibility in case you aren't on the TAC email list.

Thank you,

John Mertic
Director of Program Management - Linux Foundation
ASWF, LF AI and Data, LF Energy and Open Mainframe Project
Schedule a meeting with me at https://meetings.hubspot.com/jmertic


---------- Forwarded message ---------
From: John Mertic <jmertic@...>
Date: Thu, Mar 4, 2021 at 3:01 PM
Subject: LFX EasyCLA v2 Release: What you need to know
To: tac@... Calendar <tac@...>, board <board@...>


ASWF Governing Board and Techincal Community members,


As previously discussed, the LFX Developer Team is making some significant improvements to EasyCLA that we want to make sure you’re aware of. 


As a participant in the ASWF project community, you’ll have first access to version 2 of EasyCLA. Your current CLAs, approved lists, and workflows shouldn’t be impacted by this release. However, you’ll notice new features and UI that will make signing and managing CLAs even easier.


How Will This Impact Me?

Contributors:

  • No change to the overall process for existing contributors’ workflows.

  • New contributors (those gated by EasyCLA) will follow the same process as before, with improved UI and contextualized help to ensure a smooth workflow.


CLA Managers & Project Managers:

  • No change to the overall process for your workflows.

  • Improved UI and functionality will make managing your CLAs easier.


What’s New in EasyCLA?

For all Users:

  • Improved user experience & streamlined workflows

  • Contextualized help including tooltips & links to support resources

  • Audit Logs record key activity related to CLA actions & authorizations

For Corporate CLA Workflows:

  • Streamlined UI for adding authorized contributors

  • Search, filter, or download authorized contributor lists for your company

  • Download signed CLAs as PDFs

For Project Manager Workflows:

  • Auto-enable new repositories under a GitHub Organization

  • Auto set-up Branch Protection for the default repository branch


How to Get Started?

You’ll automatically have access to EasyCLA v2 once the cut-over takes place.

  • Contributors: You’ll only need to access EasyCLA if gated (not previously authorized) by GitHub. If so, follow the links from the GitHub pull request status section.


  • CLA Managers & Project Managers: For ASWF projects, go to the EasyCLA Landing Page and select “Proceed” under your respective role, then “EasyCLA Version 2” when prompted. You should see all of your existing data, including CLAs and authorized lists here.

    >> Get Started: easycla.lfx.linuxfoundation.org


Please reach out if you have any questions.

Want to Learn more?

Have Questions or Feedback: lfx.dev/questions


Thank you,

John Mertic
Director of Program Management - Linux Foundation
ASWF, LF AI and Data, LF Energy and Open Mainframe Project
Schedule a meeting with me at https://meetings.hubspot.com/jmertic


OSL TSC meeting ( every other week ) - Thu, 03/04/2021 2:00pm-3:00pm #cal-reminder

osl-dev@lists.aswf.io Calendar <osl-dev@...>
 

Reminder: OSL TSC meeting ( every other week )

When: Thursday, 4 March 2021, 2:00pm to 3:00pm, (GMT-08:00) America/Los Angeles

Where:https://zoom.us/j/100511909

View Event

Organizer: Chris Kulla ckulla@...

Description:

Every other week meeting of the OSL TSC.

Meeting Agenda / Notes: https://docs.google.com/document/d/1yf0bG6eoE2EvKZBNZX3nskdTvu99ADTDTNOknCDJd1I/

Confirm this meeting invite is still valid by finding the meeting at https://lists.aswf.io/calendar.

Join Zoom Meeting https://zoom.us/j/100511909

Meeting ID: 100 511 909

One tap mobile +16465588656,,100511909# US (New York) +13126266799,,100511909# US (Chicago)

Dial by your location +1 646 558 8656 US (New York) +1 312 626 6799 US (Chicago) +1 669 900 6833 US (San Jose) +1 253 215 8782 US +1 301 715 8592 US +1 346 248 7799 US (Houston) 877 369 0926 US Toll-free 855 880 1246 US Toll-free +1 587 328 1099 Canada +1 647 374 4685 Canada +1 647 558 0588 Canada +1 778 907 2071 Canada +1 438 809 7799 Canada 855 703 8985 Canada Toll-free Meeting ID: 100 511 909 Find your local number: https://zoom.us/u/acBVrM6HWR