Re: How to continue to use our social media channels

On Mon, Jun 12, 2017 at 9:16 PM, Andreas Nauerz wrote: > ...Checklist... I like your checklist, I'd just add [] Does the content clearly come from an individual who's actively involved in Apache OpenWhisk? As opposed to coming from a vendor or organization. (based on

Re: How to continue to use our social media channels

Hi, On Mon, Jun 12, 2017 at 9:16 PM, Andreas Nauerz wrote: > ...Imho anyone part of the community (any developer, any vendor, ...) > working with OpenWhisk should be allowed to use the > above mentioned channels I'd say "part of the community" yes, as in "being

[DRAFT] What the new Status Pages potentially look like

All, We're piloting a new format for the podling status pages. Specifically, the current status page leaves a lot to be desired - it's basically crafted html, there's no structure and its hard to find missing items. The end goal is to have a web form editable in Whimsy, but until we get more

How to continue to use our social media channels

Hey all, I am currently managing most of our social media channels, which, for instance, include... a) Twitter: https://twitter.com/openwhisk b) Medium: https://medium.com/openwhisk c) Slideshare: http://slideshare.net/OpenWhisk d) Youtube:

Re: Requested new "low hanging fruit" (i.e., "lhf") label for Issues

Hi Carlos, I can volunteer to align all the labels (and colors for your benefit), but I am sure that you were and advocate of the "low hanging fruit" concept at ApacheCon, in fact that term probably was spoken by you first and I grabbed on it as this is what we did in the past to clearly

Loadbalancer Improvements

Hey folks, it's me again with the latest news on performance :). As some of you probably now: Our current loadbalancer strategy is quite "simple" and doesn't take load in the system into account at all. It hops to the next available invoker after you've invoked an action X times (where X is a

Re: Requested new "low hanging fruit" (i.e., "lhf") label for Issues

All repos have the label "help wanted" Let's use it for the purpose of identifying issues that are easy entry point for a contributor to get started. The issue should also have an additional labels lile "docs", "go", "javaScript", "Swift", etc.. So if someone with Swift skills wants to help out

Re: Looking at getting JIRA package working again...

I think all repos should be enable for Travis with the setting "Build only if .travis.yml is present" ON On Mon, Jun 12, 2017 at 12:17 PM Matt Rutkowski wrote: > Went Friday to the JIRA package repo. (which I knew was not Travis enabled > and needed "work"), but found

Re: Development documents

+1 Javadoc/Scaladoc/xxxDoc There are also expectations in Python (PEP8) that can confirm basic docstrings exist at various places in source modules (which now may be enabled via a PR a couple months ago). We also have Godoc... but strings can be "empty" to pass basic linting tests. anytime

Looking at getting JIRA package working again...

Went Friday to the JIRA package repo. (which I knew was not Travis enabled and needed "work"), but found more work to do here than planned. Will try to sort it out, but if anyone wants to help... BTW Thanks to INFRA for turning Travis on: https://issues.apache.org/jira/browse/INFRA-14314 and I

Re: Propose weekly "Technical Exchange" video meeting for OpenWhisk

On Mon, Jun 12, 2017 at 4:02 PM, Matt Rutkowski wrote: > ...We do have an existing YouTube channel... > https://www.youtube.com/channel/UCbzgShnQk8F43NKsvEYA1SA ... I think that's fine, the ASF does not currently have the capacity to store and distribute videos, and those

Re: Requested new "low hanging fruit" (i.e., "lhf") label for Issues

Ah! That's what we called it "help wanted" but it looks like we haven't been very good at labeling issues. https://github.com/apache/incubator-openwhisk/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22 -r

Re: Requested new "low hanging fruit" (i.e., "lhf") label for Issues

This is great idea. I agree with Rodric that I haven't seen "lhf" used in other open-source projects, they often choose "help-wanted" for tickets along with "easy/medium/hard" to allow easy searching. Serverless FW does a good job at this: https://github.com/serverless/serverless/labels On 12

Requested new "low hanging fruit" (i.e., "lhf") label for Issues

At ApacheCon many developers approached as us asking "where/how do we get started Contributing to OW?"; we discussed introucing a new Issue label for "low hanging fruit" that we could point new developers to which would include lower-priority/learning Issues for them to start with. To add this