From manderse at redhat.com Wed Apr 22 20:17:33 2020 From: manderse at redhat.com (Max Rydahl Andersen) Date: Wed, 22 Apr 2020 22:17:33 +0200 Subject: [Devtools] Project generation now available on launcher without requiring credentials Message-ID: Heya, We (Naina and Max) are happy to announce that https://developers.redhat.com/launch/ no longer requires credentials upfront to use. Anyone can now go and generate example projects and download a zip using many of our middleware runtimes within seconds. They can also deploy it to OpenShift and at that moment they will be asked for credentials. This makes it at par with the experience you get in VSCode and Eclipse using the plugins we have. These plugins are utilizing the same backend launcher service. I want to thank everyone involved, Erik Jan De Wit, Tako Schotanus, George Gastaldi, Andy Damevin and Naina Singh to get this implemented and especially also Shoubhik Bose, Gorkem Ercan, Adi Sakala, Parag Dave, Steve Speicher, Tiffany-Emil Jacob and Andrew Rubinger in helping to move roadblocks out of the way to make life easier for our users! Thank you! Some context: Launcher as an independent project/product is in maintenance phase and will eventually retire. The work and ideas done in and around launcher are being merged/absorbed into the overall Red Hat Developer experience. The service at developers.redhat.com/launch/ is still alive and also used by VSCode and Eclipse plugins to provide Quickstarts/Examples. We are not adding new features to it, but it is still relevant to keep the examples up-to-date. Currently, that part is not covered by the OpenShift Developer experience work in the Developer group. As we work together across Red Hat to improve our Developer Experience we?ll ensure things get better and more aligned. If you are interested in this topic of Developer Experience from a middleware perspective please post and/or signup to [middleware-devexp](https://post-office.corp.redhat.com/mailman/listinfo/middleware-devexp). p.s. sorry for the wide net but thought this change was worth sharing. Thank you, Naina and Max -------------- next part -------------- An HTML attachment was scrubbed... URL: From probinso at redhat.com Thu Apr 23 09:50:16 2020 From: probinso at redhat.com (Paul Robinson) Date: Thu, 23 Apr 2020 10:50:16 +0100 Subject: [Devtools] [protean-dev] Project generation now available on launcher without requiring credentials In-Reply-To: References: Message-ID: Thanks Max, this is great news! I think this was the biggest hurdle to adoption of Launcher, so I'm really pleased to see that the team has been able to reach consensus on this. The long list of names you mention attests to how deceptively complex this change is. Paul. On Wed, Apr 22, 2020 at 9:18 PM Max Rydahl Andersen wrote: > Heya, > > We (Naina and Max) are happy to announce that > https://developers.redhat.com/launch/ no longer requires credentials > upfront to use. > > Anyone can now go and generate example projects and download a zip using > many of our middleware runtimes within seconds. > > They can also deploy it to OpenShift and at that moment they will be asked > for credentials. > > This makes it at par with the experience you get in VSCode and Eclipse > using the plugins we have. > These plugins are utilizing the same backend launcher service. > > I want to thank everyone involved, Erik Jan De Wit, Tako Schotanus, George > Gastaldi, Andy Damevin and Naina Singh to get this implemented > and especially also Shoubhik Bose, Gorkem Ercan, Adi Sakala, Parag Dave, > Steve Speicher, Tiffany-Emil Jacob and Andrew Rubinger in helping to move > roadblocks out of the way to make life easier for our users! > > Thank you! > > Some context: > > Launcher as an independent project/product is in maintenance phase and > will eventually retire. The work and ideas done in and around launcher are > being merged/absorbed into the overall Red Hat Developer experience. The > service at developers.redhat.com/launch/ is still alive and also used by > VSCode and Eclipse plugins to provide Quickstarts/Examples. > > We are not adding new features to it, but it is still relevant to keep the > examples up-to-date. Currently, that part is not covered by the OpenShift > Developer experience work in the Developer group. > > As we work together across Red Hat to improve our Developer Experience > we?ll ensure things get better and more aligned. > > If you are interested in this topic of Developer Experience from a > middleware perspective please post and/or signup to middleware-devexp > . > > p.s. sorry for the wide net but thought this change was worth sharing. > > Thank you, > Naina and Max > This mailing list is limited to Red Hat specific and product related > conversations about Quarkus. For technical discussions, use > https://groups.google.com/d/forum/quarkus-dev -- Paul Robinson ENGINEERING MANAGER He/Him/His Red Hat *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours. * -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmaury at redhat.com Thu Apr 23 11:31:44 2020 From: jmaury at redhat.com (Jean-Francois Maury) Date: Thu, 23 Apr 2020 13:31:44 +0200 Subject: [Devtools] [protean-dev] Project generation now available on launcher without requiring credentials In-Reply-To: References: Message-ID: On Thu, Apr 23, 2020 at 1:25 PM Christophe Laprun wrote: > I think (?) there used to be an api to Launcher. Is it still available? > Yes this is the one that's being used in Project Initializer and JBoss Tools Launcher wizard. But there is no Quarkus runtime there, any reason it's only through the Web UI ? > On Thu, Apr 23, 2020 at 11:51 AM Paul Robinson > wrote: > >> Thanks Max, this is great news! >> >> I think this was the biggest hurdle to adoption of Launcher, so I'm >> really pleased to see that the team has been able to reach consensus on >> this. The long list of names you mention attests to how >> deceptively complex this change is. >> >> Paul. >> >> On Wed, Apr 22, 2020 at 9:18 PM Max Rydahl Andersen >> wrote: >> >>> Heya, >>> >>> We (Naina and Max) are happy to announce that >>> https://developers.redhat.com/launch/ no longer requires credentials >>> upfront to use. >>> >>> Anyone can now go and generate example projects and download a zip using >>> many of our middleware runtimes within seconds. >>> >>> They can also deploy it to OpenShift and at that moment they will be >>> asked for credentials. >>> >>> This makes it at par with the experience you get in VSCode and Eclipse >>> using the plugins we have. >>> These plugins are utilizing the same backend launcher service. >>> >>> I want to thank everyone involved, Erik Jan De Wit, Tako Schotanus, >>> George Gastaldi, Andy Damevin and Naina Singh to get this implemented >>> and especially also Shoubhik Bose, Gorkem Ercan, Adi Sakala, Parag Dave, >>> Steve Speicher, Tiffany-Emil Jacob and Andrew Rubinger in helping to move >>> roadblocks out of the way to make life easier for our users! >>> >>> Thank you! >>> >>> Some context: >>> >>> Launcher as an independent project/product is in maintenance phase and >>> will eventually retire. The work and ideas done in and around launcher are >>> being merged/absorbed into the overall Red Hat Developer experience. The >>> service at developers.redhat.com/launch/ is still alive and also used >>> by VSCode and Eclipse plugins to provide Quickstarts/Examples. >>> >>> We are not adding new features to it, but it is still relevant to keep >>> the examples up-to-date. Currently, that part is not covered by the >>> OpenShift Developer experience work in the Developer group. >>> >>> As we work together across Red Hat to improve our Developer Experience >>> we?ll ensure things get better and more aligned. >>> >>> If you are interested in this topic of Developer Experience from a >>> middleware perspective please post and/or signup to middleware-devexp >>> >>> . >>> >>> p.s. sorry for the wide net but thought this change was worth sharing. >>> >>> Thank you, >>> Naina and Max >>> This mailing list is limited to Red Hat specific and product related >>> conversations about Quarkus. For technical discussions, use >>> https://groups.google.com/d/forum/quarkus-dev >> >> >> >> -- >> >> Paul Robinson >> >> ENGINEERING MANAGER >> >> He/Him/His >> >> >> Red Hat >> >> *Red Hat respects your work life balance. Therefore there is no need to >> answer this email out of your office hours. >> * >> > -- Jeff Maury Manager, DevTools Red Hat EMEA jmaury at redhat.com @RedHat Red Hat Red Hat -------------- next part -------------- An HTML attachment was scrubbed... URL: From manderse at redhat.com Thu Apr 23 12:25:00 2020 From: manderse at redhat.com (Max Rydahl Andersen) Date: Thu, 23 Apr 2020 14:25:00 +0200 Subject: [Devtools] [protean-dev] Project generation now available on launcher without requiring credentials In-Reply-To: References: Message-ID: <68DA88EC-EFBB-42FC-8BE3-BF268EAD4DCE@redhat.com> > I think that's because the author of that extension seems to have > hard-coded the list of available runtimes: > > https://github.com/redhat-developer/vscode-project-initializer/blob/master/src/extension.ts#L11-L16 That ain't good - if our primary tools accessing this assume everything is static makes maintenance harder :) Jean-Francois can you take care of open issue and get that worked out on the tooling side ? I'm sure Tako will help out if there are questions about what API's to use - but it sounds like the code here is implemented statically and ignores any additions available. Thank you! > > PS: That plugin was not made nor maintained by the Launcher team > > On Thu, Apr 23, 2020 at 1:32 PM Jean-Francois Maury > > wrote: > >> >> >> On Thu, Apr 23, 2020 at 1:25 PM Christophe Laprun >> >> wrote: >> >>> I think (?) there used to be an api to Launcher. Is it still >>> available? >>> >> Yes this is the one that's being used in Project Initializer and >> JBoss >> Tools Launcher wizard. But there is no Quarkus runtime there, any >> reason >> it's only through the Web UI ? >> >> >>> On Thu, Apr 23, 2020 at 11:51 AM Paul Robinson >>> wrote: >>> >>>> Thanks Max, this is great news! >>>> >>>> I think this was the biggest hurdle to adoption of Launcher, so I'm >>>> really pleased to see that the team has been able to reach >>>> consensus on >>>> this. The long list of names you mention attests to how >>>> deceptively complex this change is. >>>> >>>> Paul. >>>> >>>> On Wed, Apr 22, 2020 at 9:18 PM Max Rydahl Andersen >>>> >>>> wrote: >>>> >>>>> Heya, >>>>> >>>>> We (Naina and Max) are happy to announce that >>>>> https://developers.redhat.com/launch/ no longer requires >>>>> credentials >>>>> upfront to use. >>>>> >>>>> Anyone can now go and generate example projects and download a zip >>>>> using many of our middleware runtimes within seconds. >>>>> >>>>> They can also deploy it to OpenShift and at that moment they will >>>>> be >>>>> asked for credentials. >>>>> >>>>> This makes it at par with the experience you get in VSCode and >>>>> Eclipse >>>>> using the plugins we have. >>>>> These plugins are utilizing the same backend launcher service. >>>>> >>>>> I want to thank everyone involved, Erik Jan De Wit, Tako >>>>> Schotanus, >>>>> George Gastaldi, Andy Damevin and Naina Singh to get this >>>>> implemented >>>>> and especially also Shoubhik Bose, Gorkem Ercan, Adi Sakala, Parag >>>>> Dave, Steve Speicher, Tiffany-Emil Jacob and Andrew Rubinger in >>>>> helping to >>>>> move roadblocks out of the way to make life easier for our users! >>>>> >>>>> Thank you! >>>>> >>>>> Some context: >>>>> >>>>> Launcher as an independent project/product is in maintenance phase >>>>> and >>>>> will eventually retire. The work and ideas done in and around >>>>> launcher are >>>>> being merged/absorbed into the overall Red Hat Developer >>>>> experience. The >>>>> service at developers.redhat.com/launch/ is still alive and also >>>>> used >>>>> by VSCode and Eclipse plugins to provide Quickstarts/Examples. >>>>> >>>>> We are not adding new features to it, but it is still relevant to >>>>> keep >>>>> the examples up-to-date. Currently, that part is not covered by >>>>> the >>>>> OpenShift Developer experience work in the Developer group. >>>>> >>>>> As we work together across Red Hat to improve our Developer >>>>> Experience >>>>> we?ll ensure things get better and more aligned. >>>>> >>>>> If you are interested in this topic of Developer Experience from a >>>>> middleware perspective please post and/or signup to >>>>> middleware-devexp >>>>> >>>>> . >>>>> >>>>> p.s. sorry for the wide net but thought this change was worth >>>>> sharing. >>>>> >>>>> Thank you, >>>>> Naina and Max >>>>> This mailing list is limited to Red Hat specific and product >>>>> related >>>>> conversations about Quarkus. For technical discussions, use >>>>> https://groups.google.com/d/forum/quarkus-dev >>>> >>>> >>>> >>>> -- >>>> >>>> Paul Robinson >>>> >>>> ENGINEERING MANAGER >>>> >>>> He/Him/His >>>> >>>> >>>> Red Hat >>>> >>>> *Red Hat respects your work life balance. Therefore there is no >>>> need to >>>> answer this email out of your office hours. >>>> * >>>> >>> >> >> -- >> >> Jeff Maury >> >> Manager, DevTools >> >> Red Hat EMEA >> >> jmaury at redhat.com >> @RedHat Red Hat >> Red Hat >> >> >> >> > > > -- > *TAKO SCHOTANUS* > SENIOR SOFTWARE ENGINEER > Red Hat > > > > From jmaury at redhat.com Thu Apr 23 12:32:03 2020 From: jmaury at redhat.com (Jean-Francois Maury) Date: Thu, 23 Apr 2020 14:32:03 +0200 Subject: [Devtools] [protean-dev] Project generation now available on launcher without requiring credentials In-Reply-To: <68DA88EC-EFBB-42FC-8BE3-BF268EAD4DCE@redhat.com> References: <68DA88EC-EFBB-42FC-8BE3-BF268EAD4DCE@redhat.com> Message-ID: No, you're misreading the code. The plugin has several commands: one generic that should list all runtimes plus additional ones limited to certain runtuimes (requested by the Camel team). Look at the retrieved catalog ( https://forge.api.openshift.io/api/booster-catalog), Quarkus is not there Jeff On Thu, Apr 23, 2020 at 2:25 PM Max Rydahl Andersen wrote: > > > I think that's because the author of that extension seems to have > > hard-coded the list of available runtimes: > > > > > https://github.com/redhat-developer/vscode-project-initializer/blob/master/src/extension.ts#L11-L16 > > That ain't good - if our primary tools accessing this assume everything > is static makes maintenance harder :) > > Jean-Francois can you take care of open issue and get that worked out on > the tooling side ? > I'm sure Tako will help out if there are questions about what API's to > use - but it sounds like > the code here is implemented statically and ignores any additions > available. > > Thank you! > > > > > PS: That plugin was not made nor maintained by the Launcher team > > > > On Thu, Apr 23, 2020 at 1:32 PM Jean-Francois Maury > > > > wrote: > > > >> > >> > >> On Thu, Apr 23, 2020 at 1:25 PM Christophe Laprun > >> > >> wrote: > >> > >>> I think (?) there used to be an api to Launcher. Is it still > >>> available? > >>> > >> Yes this is the one that's being used in Project Initializer and > >> JBoss > >> Tools Launcher wizard. But there is no Quarkus runtime there, any > >> reason > >> it's only through the Web UI ? > >> > >> > >>> On Thu, Apr 23, 2020 at 11:51 AM Paul Robinson > >>> wrote: > >>> > >>>> Thanks Max, this is great news! > >>>> > >>>> I think this was the biggest hurdle to adoption of Launcher, so I'm > >>>> really pleased to see that the team has been able to reach > >>>> consensus on > >>>> this. The long list of names you mention attests to how > >>>> deceptively complex this change is. > >>>> > >>>> Paul. > >>>> > >>>> On Wed, Apr 22, 2020 at 9:18 PM Max Rydahl Andersen > >>>> > >>>> wrote: > >>>> > >>>>> Heya, > >>>>> > >>>>> We (Naina and Max) are happy to announce that > >>>>> https://developers.redhat.com/launch/ no longer requires > >>>>> credentials > >>>>> upfront to use. > >>>>> > >>>>> Anyone can now go and generate example projects and download a zip > >>>>> using many of our middleware runtimes within seconds. > >>>>> > >>>>> They can also deploy it to OpenShift and at that moment they will > >>>>> be > >>>>> asked for credentials. > >>>>> > >>>>> This makes it at par with the experience you get in VSCode and > >>>>> Eclipse > >>>>> using the plugins we have. > >>>>> These plugins are utilizing the same backend launcher service. > >>>>> > >>>>> I want to thank everyone involved, Erik Jan De Wit, Tako > >>>>> Schotanus, > >>>>> George Gastaldi, Andy Damevin and Naina Singh to get this > >>>>> implemented > >>>>> and especially also Shoubhik Bose, Gorkem Ercan, Adi Sakala, Parag > >>>>> Dave, Steve Speicher, Tiffany-Emil Jacob and Andrew Rubinger in > >>>>> helping to > >>>>> move roadblocks out of the way to make life easier for our users! > >>>>> > >>>>> Thank you! > >>>>> > >>>>> Some context: > >>>>> > >>>>> Launcher as an independent project/product is in maintenance phase > >>>>> and > >>>>> will eventually retire. The work and ideas done in and around > >>>>> launcher are > >>>>> being merged/absorbed into the overall Red Hat Developer > >>>>> experience. The > >>>>> service at developers.redhat.com/launch/ is still alive and also > >>>>> used > >>>>> by VSCode and Eclipse plugins to provide Quickstarts/Examples. > >>>>> > >>>>> We are not adding new features to it, but it is still relevant to > >>>>> keep > >>>>> the examples up-to-date. Currently, that part is not covered by > >>>>> the > >>>>> OpenShift Developer experience work in the Developer group. > >>>>> > >>>>> As we work together across Red Hat to improve our Developer > >>>>> Experience > >>>>> we?ll ensure things get better and more aligned. > >>>>> > >>>>> If you are interested in this topic of Developer Experience from a > >>>>> middleware perspective please post and/or signup to > >>>>> middleware-devexp > >>>>> < > https://post-office.corp.redhat.com/mailman/listinfo/middleware-devexp> > >>>>> . > >>>>> > >>>>> p.s. sorry for the wide net but thought this change was worth > >>>>> sharing. > >>>>> > >>>>> Thank you, > >>>>> Naina and Max > >>>>> This mailing list is limited to Red Hat specific and product > >>>>> related > >>>>> conversations about Quarkus. For technical discussions, use > >>>>> https://groups.google.com/d/forum/quarkus-dev > >>>> > >>>> > >>>> > >>>> -- > >>>> > >>>> Paul Robinson > >>>> > >>>> ENGINEERING MANAGER > >>>> > >>>> He/Him/His > >>>> < > https://medium.com/gender-inclusivit/why-i-put-pronouns-on-my-email-signature-and-linkedin-profile-and-you-should-too-d3dc942c8743 > > > >>>> > >>>> Red Hat > >>>> > >>>> *Red Hat respects your work life balance. Therefore there is no > >>>> need to > >>>> answer this email out of your office hours. > >>>> * > >>>> > >>> > >> > >> -- > >> > >> Jeff Maury > >> > >> Manager, DevTools > >> > >> Red Hat EMEA > >> > >> jmaury at redhat.com > >> @RedHat Red Hat > >> Red Hat > >> > >> > >> > >> > > > > > > -- > > *TAKO SCHOTANUS* > > SENIOR SOFTWARE ENGINEER > > Red Hat > > > > > > > > > > > -- Jeff Maury Manager, DevTools Red Hat EMEA jmaury at redhat.com @RedHat Red Hat Red Hat -------------- next part -------------- An HTML attachment was scrubbed... URL: From manderse at redhat.com Fri Apr 24 15:35:24 2020 From: manderse at redhat.com (Max Andersen) Date: Fri, 24 Apr 2020 17:35:24 +0200 Subject: [Devtools] [protean-dev] Project generation now available on launcher without requiring credentials In-Reply-To: References: <68DA88EC-EFBB-42FC-8BE3-BF268EAD4DCE@redhat.com> Message-ID: On Fri, 24 Apr 2020 at 16:30, Thomas Qvarnstrom wrote: > Quarkus has it's own VSCode plugin. > It also has its own node, EAP and vertx features. This is about making the behaviors consistent. Ie. Vscode quarkus plug-in aren?t going to have multiple example generation like done for other runtimes. Thus it should not be about wether there are tools similar available in just one Ide - but wether it make sense to have quarkus examples for the use cases covered by the other runtimes and have that available in web, eclipse, vscode and direct api usage. > /max > > ---- > Thomas Qvarnstr?m > Sr. Pr. Product Manager > Red Hat, Inc. > > > On Fri, Apr 24, 2020 at 3:47 PM Naina Singh wrote: > >> Does this mean that there are no example apps in Launcher for Quarkus. >> I believe there is.a separate plugin for Quarkus in VSCode and probably >> that is why this got overlooked. >> >> @Thomas Qvarnstrom I think we should have >> Quarkus as part of the Project Initializer plugin as well. What do you >> think? >> >> On Thu, Apr 23, 2020 at 8:37 AM George Gastaldi >> wrote: >> >>> That's because the plugin does the same as the "Deploy an Example >>> Application" in Launcher (which also does not feature Quarkus). See >>> https://developers.redhat.com/launch/flow/deploy-example-app >>> Quarkus is only featured in >>> https://developers.redhat.com/launch/flow/new-app and is a bit outdated. >>> >>> Best Regards, >>> >>> >>> George Gastaldi >>> >>> Principal Software Engineer >>> >>> Red Hat >>> >>> >>> >>> >>> On Thu, Apr 23, 2020 at 9:32 AM Jean-Francois Maury >>> wrote: >>> >>>> No, you're misreading the code. >>>> The plugin has several commands: one generic that should list all >>>> runtimes plus additional ones limited to certain runtuimes (requested by >>>> the Camel team). >>>> Look at the retrieved catalog ( >>>> https://forge.api.openshift.io/api/booster-catalog), Quarkus is not >>>> there >>>> >>>> Jeff >>>> >>>> >>>> On Thu, Apr 23, 2020 at 2:25 PM Max Rydahl Andersen < >>>> manderse at redhat.com> wrote: >>>> >>>>> >>>>> > I think that's because the author of that extension seems to have >>>>> > hard-coded the list of available runtimes: >>>>> > >>>>> > >>>>> https://github.com/redhat-developer/vscode-project-initializer/blob/master/src/extension.ts#L11-L16 >>>>> >>>>> That ain't good - if our primary tools accessing this assume >>>>> everything >>>>> is static makes maintenance harder :) >>>>> >>>>> Jean-Francois can you take care of open issue and get that worked out >>>>> on >>>>> the tooling side ? >>>>> I'm sure Tako will help out if there are questions about what API's to >>>>> use - but it sounds like >>>>> the code here is implemented statically and ignores any additions >>>>> available. >>>>> >>>>> Thank you! >>>>> >>>>> > >>>>> > PS: That plugin was not made nor maintained by the Launcher team >>>>> > >>>>> > On Thu, Apr 23, 2020 at 1:32 PM Jean-Francois Maury >>>>> > >>>>> > wrote: >>>>> > >>>>> >> >>>>> >> >>>>> >> On Thu, Apr 23, 2020 at 1:25 PM Christophe Laprun >>>>> >> >>>>> >> wrote: >>>>> >> >>>>> >>> I think (?) there used to be an api to Launcher. Is it still >>>>> >>> available? >>>>> >>> >>>>> >> Yes this is the one that's being used in Project Initializer and >>>>> >> JBoss >>>>> >> Tools Launcher wizard. But there is no Quarkus runtime there, any >>>>> >> reason >>>>> >> it's only through the Web UI ? >>>>> >> >>>>> >> >>>>> >>> On Thu, Apr 23, 2020 at 11:51 AM Paul Robinson < >>>>> probinso at redhat.com> >>>>> >>> wrote: >>>>> >>> >>>>> >>>> Thanks Max, this is great news! >>>>> >>>> >>>>> >>>> I think this was the biggest hurdle to adoption of Launcher, so >>>>> I'm >>>>> >>>> really pleased to see that the team has been able to reach >>>>> >>>> consensus on >>>>> >>>> this. The long list of names you mention attests to how >>>>> >>>> deceptively complex this change is. >>>>> >>>> >>>>> >>>> Paul. >>>>> >>>> >>>>> >>>> On Wed, Apr 22, 2020 at 9:18 PM Max Rydahl Andersen >>>>> >>>> >>>>> >>>> wrote: >>>>> >>>> >>>>> >>>>> Heya, >>>>> >>>>> >>>>> >>>>> We (Naina and Max) are happy to announce that >>>>> >>>>> https://developers.redhat.com/launch/ no longer requires >>>>> >>>>> credentials >>>>> >>>>> upfront to use. >>>>> >>>>> >>>>> >>>>> Anyone can now go and generate example projects and download a >>>>> zip >>>>> >>>>> using many of our middleware runtimes within seconds. >>>>> >>>>> >>>>> >>>>> They can also deploy it to OpenShift and at that moment they >>>>> will >>>>> >>>>> be >>>>> >>>>> asked for credentials. >>>>> >>>>> >>>>> >>>>> This makes it at par with the experience you get in VSCode and >>>>> >>>>> Eclipse >>>>> >>>>> using the plugins we have. >>>>> >>>>> These plugins are utilizing the same backend launcher service. >>>>> >>>>> >>>>> >>>>> I want to thank everyone involved, Erik Jan De Wit, Tako >>>>> >>>>> Schotanus, >>>>> >>>>> George Gastaldi, Andy Damevin and Naina Singh to get this >>>>> >>>>> implemented >>>>> >>>>> and especially also Shoubhik Bose, Gorkem Ercan, Adi Sakala, >>>>> Parag >>>>> >>>>> Dave, Steve Speicher, Tiffany-Emil Jacob and Andrew Rubinger in >>>>> >>>>> helping to >>>>> >>>>> move roadblocks out of the way to make life easier for our users! >>>>> >>>>> >>>>> >>>>> Thank you! >>>>> >>>>> >>>>> >>>>> Some context: >>>>> >>>>> >>>>> >>>>> Launcher as an independent project/product is in maintenance >>>>> phase >>>>> >>>>> and >>>>> >>>>> will eventually retire. The work and ideas done in and around >>>>> >>>>> launcher are >>>>> >>>>> being merged/absorbed into the overall Red Hat Developer >>>>> >>>>> experience. The >>>>> >>>>> service at developers.redhat.com/launch/ is still alive and >>>>> also >>>>> >>>>> used >>>>> >>>>> by VSCode and Eclipse plugins to provide Quickstarts/Examples. >>>>> >>>>> >>>>> >>>>> We are not adding new features to it, but it is still relevant >>>>> to >>>>> >>>>> keep >>>>> >>>>> the examples up-to-date. Currently, that part is not covered by >>>>> >>>>> the >>>>> >>>>> OpenShift Developer experience work in the Developer group. >>>>> >>>>> >>>>> >>>>> As we work together across Red Hat to improve our Developer >>>>> >>>>> Experience >>>>> >>>>> we?ll ensure things get better and more aligned. >>>>> >>>>> >>>>> >>>>> If you are interested in this topic of Developer Experience from >>>>> a >>>>> >>>>> middleware perspective please post and/or signup to >>>>> >>>>> middleware-devexp >>>>> >>>>> < >>>>> https://post-office.corp.redhat.com/mailman/listinfo/middleware-devexp >>>>> > >>>>> >>>>> . >>>>> >>>>> >>>>> >>>>> p.s. sorry for the wide net but thought this change was worth >>>>> >>>>> sharing. >>>>> >>>>> >>>>> >>>>> Thank you, >>>>> >>>>> Naina and Max >>>>> >>>>> This mailing list is limited to Red Hat specific and product >>>>> >>>>> related >>>>> >>>>> conversations about Quarkus. For technical discussions, use >>>>> >>>>> https://groups.google.com/d/forum/quarkus-dev >>>>> >>>> >>>>> >>>> >>>>> >>>> >>>>> >>>> -- >>>>> >>>> >>>>> >>>> Paul Robinson >>>>> >>>> >>>>> >>>> ENGINEERING MANAGER >>>>> >>>> >>>>> >>>> He/Him/His >>>>> >>>> < >>>>> https://medium.com/gender-inclusivit/why-i-put-pronouns-on-my-email-signature-and-linkedin-profile-and-you-should-too-d3dc942c8743 >>>>> > >>>>> >>>> >>>>> >>>> Red Hat >>>>> >>>> >>>>> >>>> *Red Hat respects your work life balance. Therefore there is no >>>>> >>>> need to >>>>> >>>> answer this email out of your office hours. >>>>> >>>> * >>>>> >>>> >>>>> >>> >>>>> >> >>>>> >> -- >>>>> >> >>>>> >> Jeff Maury >>>>> >> >>>>> >> Manager, DevTools >>>>> >> >>>>> >> Red Hat EMEA >>>>> >> >>>>> >> jmaury at redhat.com >>>>> >> @RedHat Red Hat >>>>> >> Red Hat >>>>> >> >>>>> >> >>>>> >> >>>>> >> >>>>> > >>>>> > >>>>> > -- >>>>> > *TAKO SCHOTANUS* >>>>> > SENIOR SOFTWARE ENGINEER >>>>> > Red Hat >>>>> > >>>>> > >>>>> > >>>>> > >>>>> >>>>> >>>>> >>>> >>>> -- >>>> >>>> Jeff Maury >>>> >>>> Manager, DevTools >>>> >>>> Red Hat EMEA >>>> >>>> jmaury at redhat.com >>>> @RedHat Red Hat >>>> Red Hat >>>> >>>> >>>> >>>> >>> >> >> -- >> >> *Best,* >> >> Naina Singh >> >> Senior Product Manager >> >> naina.s at redhat.com +19194506323 >> >> @madhatter_ns >> NOTE:THE PRODUCT FEATURES AND SCHEDULES >> MENTIONED IN THIS EMAIL DON'T CONSTITUTE COMMITMENTS. >> >> -- /max https://about.me/maxandersen -------------- next part -------------- An HTML attachment was scrubbed... URL: From manderse at redhat.com Fri Apr 24 16:14:24 2020 From: manderse at redhat.com (Max Andersen) Date: Fri, 24 Apr 2020 18:14:24 +0200 Subject: [Devtools] [protean-dev] Project generation now available on launcher without requiring credentials In-Reply-To: References: <68DA88EC-EFBB-42FC-8BE3-BF268EAD4DCE@redhat.com> Message-ID: Btw. These examples would be what you (Thomas) suggested as our definition of what is supported Api. Part of QuickStart Repo and just following same pattern so they can be made to use in the various tools. Thus it?s not like we couldn?t use these or maybe already have them :) On Fri, 24 Apr 2020 at 17:54, Naina Singh wrote: > > > On Fri, Apr 24, 2020 at 11:35 AM Max Andersen wrote: > >> >> >> On Fri, 24 Apr 2020 at 16:30, Thomas Qvarnstrom >> wrote: >> >>> Quarkus has it's own VSCode plugin. >>> >> >> It also has its own node, EAP and vertx features. >> >> This is about making the behaviors consistent. >> > +1. This is important as this would bring the web experience as par with > the VSCode. > >> >> Ie. Vscode quarkus plug-in aren?t going to have multiple example >> generation like done for other runtimes. >> >> Thus it should not be about wether there are tools similar available in >> just one Ide - but wether it make sense to have quarkus examples for the >> use cases covered by the other runtimes and have that available in web, >> eclipse, vscode and direct api usage. >> > I agree with Max here. Since Quarkus is part of the offered Runtimes now. > It would make sense to add it to the existing plugin for Launcher. > >> >> >> /max >> >> >>> >>> ---- >>> Thomas Qvarnstr?m >>> Sr. Pr. Product Manager >>> Red Hat, Inc. >>> >>> >>> On Fri, Apr 24, 2020 at 3:47 PM Naina Singh wrote: >>> >>>> Does this mean that there are no example apps in Launcher for Quarkus. >>>> I believe there is.a separate plugin for Quarkus in VSCode and probably >>>> that is why this got overlooked. >>>> >>>> @Thomas Qvarnstrom I think we should have >>>> Quarkus as part of the Project Initializer plugin as well. What do you >>>> think? >>>> >>>> On Thu, Apr 23, 2020 at 8:37 AM George Gastaldi >>>> wrote: >>>> >>>>> That's because the plugin does the same as the "Deploy an Example >>>>> Application" in Launcher (which also does not feature Quarkus). See >>>>> https://developers.redhat.com/launch/flow/deploy-example-app >>>>> Quarkus is only featured in >>>>> https://developers.redhat.com/launch/flow/new-app and is a bit >>>>> outdated. >>>>> >>>>> Best Regards, >>>>> >>>>> >>>>> George Gastaldi >>>>> >>>>> Principal Software Engineer >>>>> >>>>> Red Hat >>>>> >>>>> >>>>> >>>>> >>>>> On Thu, Apr 23, 2020 at 9:32 AM Jean-Francois Maury >>>>> wrote: >>>>> >>>>>> No, you're misreading the code. >>>>>> The plugin has several commands: one generic that should list all >>>>>> runtimes plus additional ones limited to certain runtuimes (requested by >>>>>> the Camel team). >>>>>> Look at the retrieved catalog ( >>>>>> https://forge.api.openshift.io/api/booster-catalog), Quarkus is not >>>>>> there >>>>>> >>>>>> Jeff >>>>>> >>>>>> >>>>>> On Thu, Apr 23, 2020 at 2:25 PM Max Rydahl Andersen < >>>>>> manderse at redhat.com> wrote: >>>>>> >>>>>>> >>>>>>> > I think that's because the author of that extension seems to have >>>>>>> > hard-coded the list of available runtimes: >>>>>>> > >>>>>>> > >>>>>>> https://github.com/redhat-developer/vscode-project-initializer/blob/master/src/extension.ts#L11-L16 >>>>>>> >>>>>>> That ain't good - if our primary tools accessing this assume >>>>>>> everything >>>>>>> is static makes maintenance harder :) >>>>>>> >>>>>>> Jean-Francois can you take care of open issue and get that worked >>>>>>> out on >>>>>>> the tooling side ? >>>>>>> I'm sure Tako will help out if there are questions about what API's >>>>>>> to >>>>>>> use - but it sounds like >>>>>>> the code here is implemented statically and ignores any additions >>>>>>> available. >>>>>>> >>>>>>> Thank you! >>>>>>> >>>>>>> > >>>>>>> > PS: That plugin was not made nor maintained by the Launcher team >>>>>>> > >>>>>>> > On Thu, Apr 23, 2020 at 1:32 PM Jean-Francois Maury >>>>>>> > >>>>>>> > wrote: >>>>>>> > >>>>>>> >> >>>>>>> >> >>>>>>> >> On Thu, Apr 23, 2020 at 1:25 PM Christophe Laprun >>>>>>> >> >>>>>>> >> wrote: >>>>>>> >> >>>>>>> >>> I think (?) there used to be an api to Launcher. Is it still >>>>>>> >>> available? >>>>>>> >>> >>>>>>> >> Yes this is the one that's being used in Project Initializer and >>>>>>> >> JBoss >>>>>>> >> Tools Launcher wizard. But there is no Quarkus runtime there, any >>>>>>> >> reason >>>>>>> >> it's only through the Web UI ? >>>>>>> >> >>>>>>> >> >>>>>>> >>> On Thu, Apr 23, 2020 at 11:51 AM Paul Robinson < >>>>>>> probinso at redhat.com> >>>>>>> >>> wrote: >>>>>>> >>> >>>>>>> >>>> Thanks Max, this is great news! >>>>>>> >>>> >>>>>>> >>>> I think this was the biggest hurdle to adoption of Launcher, so >>>>>>> I'm >>>>>>> >>>> really pleased to see that the team has been able to reach >>>>>>> >>>> consensus on >>>>>>> >>>> this. The long list of names you mention attests to how >>>>>>> >>>> deceptively complex this change is. >>>>>>> >>>> >>>>>>> >>>> Paul. >>>>>>> >>>> >>>>>>> >>>> On Wed, Apr 22, 2020 at 9:18 PM Max Rydahl Andersen >>>>>>> >>>> >>>>>>> >>>> wrote: >>>>>>> >>>> >>>>>>> >>>>> Heya, >>>>>>> >>>>> >>>>>>> >>>>> We (Naina and Max) are happy to announce that >>>>>>> >>>>> https://developers.redhat.com/launch/ no longer requires >>>>>>> >>>>> credentials >>>>>>> >>>>> upfront to use. >>>>>>> >>>>> >>>>>>> >>>>> Anyone can now go and generate example projects and download a >>>>>>> zip >>>>>>> >>>>> using many of our middleware runtimes within seconds. >>>>>>> >>>>> >>>>>>> >>>>> They can also deploy it to OpenShift and at that moment they >>>>>>> will >>>>>>> >>>>> be >>>>>>> >>>>> asked for credentials. >>>>>>> >>>>> >>>>>>> >>>>> This makes it at par with the experience you get in VSCode and >>>>>>> >>>>> Eclipse >>>>>>> >>>>> using the plugins we have. >>>>>>> >>>>> These plugins are utilizing the same backend launcher service. >>>>>>> >>>>> >>>>>>> >>>>> I want to thank everyone involved, Erik Jan De Wit, Tako >>>>>>> >>>>> Schotanus, >>>>>>> >>>>> George Gastaldi, Andy Damevin and Naina Singh to get this >>>>>>> >>>>> implemented >>>>>>> >>>>> and especially also Shoubhik Bose, Gorkem Ercan, Adi Sakala, >>>>>>> Parag >>>>>>> >>>>> Dave, Steve Speicher, Tiffany-Emil Jacob and Andrew Rubinger >>>>>>> in >>>>>>> >>>>> helping to >>>>>>> >>>>> move roadblocks out of the way to make life easier for our >>>>>>> users! >>>>>>> >>>>> >>>>>>> >>>>> Thank you! >>>>>>> >>>>> >>>>>>> >>>>> Some context: >>>>>>> >>>>> >>>>>>> >>>>> Launcher as an independent project/product is in maintenance >>>>>>> phase >>>>>>> >>>>> and >>>>>>> >>>>> will eventually retire. The work and ideas done in and around >>>>>>> >>>>> launcher are >>>>>>> >>>>> being merged/absorbed into the overall Red Hat Developer >>>>>>> >>>>> experience. The >>>>>>> >>>>> service at developers.redhat.com/launch/ is still alive and >>>>>>> also >>>>>>> >>>>> used >>>>>>> >>>>> by VSCode and Eclipse plugins to provide Quickstarts/Examples. >>>>>>> >>>>> >>>>>>> >>>>> We are not adding new features to it, but it is still relevant >>>>>>> to >>>>>>> >>>>> keep >>>>>>> >>>>> the examples up-to-date. Currently, that part is not covered >>>>>>> by >>>>>>> >>>>> the >>>>>>> >>>>> OpenShift Developer experience work in the Developer group. >>>>>>> >>>>> >>>>>>> >>>>> As we work together across Red Hat to improve our Developer >>>>>>> >>>>> Experience >>>>>>> >>>>> we?ll ensure things get better and more aligned. >>>>>>> >>>>> >>>>>>> >>>>> If you are interested in this topic of Developer Experience >>>>>>> from a >>>>>>> >>>>> middleware perspective please post and/or signup to >>>>>>> >>>>> middleware-devexp >>>>>>> >>>>> < >>>>>>> https://post-office.corp.redhat.com/mailman/listinfo/middleware-devexp >>>>>>> > >>>>>>> >>>>> . >>>>>>> >>>>> >>>>>>> >>>>> p.s. sorry for the wide net but thought this change was worth >>>>>>> >>>>> sharing. >>>>>>> >>>>> >>>>>>> >>>>> Thank you, >>>>>>> >>>>> Naina and Max >>>>>>> >>>>> This mailing list is limited to Red Hat specific and product >>>>>>> >>>>> related >>>>>>> >>>>> conversations about Quarkus. For technical discussions, use >>>>>>> >>>>> https://groups.google.com/d/forum/quarkus-dev >>>>>>> >>>> >>>>>>> >>>> >>>>>>> >>>> >>>>>>> >>>> -- >>>>>>> >>>> >>>>>>> >>>> Paul Robinson >>>>>>> >>>> >>>>>>> >>>> ENGINEERING MANAGER >>>>>>> >>>> >>>>>>> >>>> He/Him/His >>>>>>> >>>> < >>>>>>> https://medium.com/gender-inclusivit/why-i-put-pronouns-on-my-email-signature-and-linkedin-profile-and-you-should-too-d3dc942c8743 >>>>>>> > >>>>>>> >>>> >>>>>>> >>>> Red Hat >>>>>>> >>>> >>>>>>> >>>> *Red Hat respects your work life balance. Therefore there is no >>>>>>> >>>> need to >>>>>>> >>>> answer this email out of your office hours. >>>>>>> >>>> * >>>>>>> >>>> >>>>>>> >>> >>>>>>> >> >>>>>>> >> -- >>>>>>> >> >>>>>>> >> Jeff Maury >>>>>>> >> >>>>>>> >> Manager, DevTools >>>>>>> >> >>>>>>> >> Red Hat EMEA >>>>>>> >> >>>>>>> >> jmaury at redhat.com >>>>>>> >> @RedHat Red Hat >>>>>>> >> Red Hat >>>>>>> >> >>>>>>> >> >>>>>>> >> >>>>>>> >> >>>>>>> > >>>>>>> > >>>>>>> > -- >>>>>>> > *TAKO SCHOTANUS* >>>>>>> > SENIOR SOFTWARE ENGINEER >>>>>>> > Red Hat >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> Jeff Maury >>>>>> >>>>>> Manager, DevTools >>>>>> >>>>>> Red Hat EMEA >>>>>> >>>>>> jmaury at redhat.com >>>>>> @RedHat Red Hat >>>>>> Red Hat >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> -- >>>> >>>> *Best,* >>>> >>>> Naina Singh >>>> >>>> Senior Product Manager >>>> >>>> naina.s at redhat.com +19194506323 >>>> >>>> @madhatter_ns >>>> NOTE:THE PRODUCT FEATURES AND SCHEDULES >>>> MENTIONED IN THIS EMAIL DON'T CONSTITUTE COMMITMENTS. >>>> >>>> -- >> /max >> https://about.me/maxandersen >> > > > -- > > *Best,* > > Naina Singh > > Senior Product Manager > > naina.s at redhat.com +19194506323 > > @madhatter_ns > NOTE:THE PRODUCT FEATURES AND SCHEDULES > MENTIONED IN THIS EMAIL DON'T CONSTITUTE COMMITMENTS. > > -- /max https://about.me/maxandersen -------------- next part -------------- An HTML attachment was scrubbed... URL: