Re: Use an explicit property to define type of Whisk entity

Thanks Rodric for the background details. Continuing the discussion from Slack > You'll have to augment the serialize entity type to add this property (but > I would not add it to the actual types since it's redundant). Ack. So would add the types implicitly in serialization logic > The same

Re: Drafting our podling report in CWIKI, feel free to provide comment/content/updates

We should focus on reporting the keys aspects relevant for the board. Again, we are running late :-/ On Wed, Dec 6, 2017 at 7:16 AM, Carlos Santana wrote: > We should look into scripting something to gather issues and prs activities > across all the repos, and also report

Re: Use an explicit property to define type of Whisk entity

Adding an entity type can work - it would simplify the views. It's mostly a historical footnote why it doesn't exist and why it's inferred. You'll have to augment the serialize entity type to add this property (but I would not add it to the actual types since it's redundant). This could benefit

Re: list etiquette: job postings?

+1 On 7 Dec 2017 11:51 a.m., "Carlos Santana" wrote: > +1 > > Also add to the policy that posting should make it clear that is not the > ASF hiring :-) > On Thu, Dec 7, 2017 at 6:49 AM Michael Marth > wrote: > > > Hi, > > > > as you might (or

list etiquette: job postings?

Hi, as you might (or not) be aware there is a #jobs channel in the OW Slack. However, that channel only has 35 members which made me wonder how people feel about OpenWhisk job postings on this list? Obviously, the posting would need to be clearly relevant to OpenWhisk and should have a subject

Re: Use an explicit property to define type of Whisk entity

Would be helpful if some feedback can be provided here. If this looks ok I can work on PR around this topic Chetan Mehrotra On Mon, Dec 4, 2017 at 4:41 PM, Chetan Mehrotra wrote: > Hi everyone, > > Currently all whisk entities are stored in "whisks" collection in >