Re: Decomposition of OpenWhisk components and repositories

2017-12-10 Thread Carlos Santana
Yeah I agree putting a short statement/disclaimer on the state on the repo’s README that way is clear that “use on your own risk or it might take time before someone responds to an issue” It also could have a link back to the wiki page. — Carlos On Sun, Dec 10, 2017 at 11:33 AM Michael Marth wro

Re: Decomposition of OpenWhisk components and repositories

2017-12-10 Thread Michael Marth
Hi Carlos, I am not sure if the people new to OpenWhisk would look at that table. I, for one, was not even aware it existed ( How about putting a badge/note at the top of the experimental repo’s READMEs? That would probably be seen. Additional benefit: the badge could be raised as a PR against t

Re: Decomposition of OpenWhisk components and repositories

2017-12-09 Thread Carlos Santana
Hi Michael I got the list by going over every repo recently and reviewing latest state. Which for the most part I follow all changes, PR, issues to every OpenWhisk repo :-) What do you think if we add a column to the Repo Status Wiki page? https://cwiki.apache.org/confluence/display/OPENWHISK/Gi

Re: Decomposition of OpenWhisk components and repositories

2017-12-08 Thread Michael Marth
Hi Carlos, Thanks for sharing that! Slide 4 made me wonder on the distinction between “maintained” repos and “experimental” repos. I totally agree that this distinction exists in practice, but I wondered how you got to the list. And I should add: I don’t dispute the repos you put on the “experi

Decomposition of OpenWhisk components and repositories

2017-12-06 Thread Carlos Santana
This week I gave a talk internal in IBM to illustrate the work recently done in braking openwhisk components into multiple repositories, and how we integrate them in our downstream deployment. Some slides I think are useful to share with the community it gives a map where are components located.