> On 21 Aug 2023, at 1:35 pm, kekronbekron > <[email protected]> wrote: > >> I intend to leverage the z/OS Open Tools ports as they spare me the effort >> of continuous maintenance. > > That sounds like it's going to lead to RS offering supported option of stuff, > relying on other people's open sourced work... with what amount of giving > back involved?
There is zero chance of RS offering commercial support for code ported by the z/OS Open Tools community. They don’t need to. If they thought there was a market for a tool that they would just provide their own port. I’m not quite sure what you mean by “giving back”? If you’re talking about upstreaming changes then we’ve had this conversation before many times. The maintainers of open source projects, such as Python, want nothing to do with z/OS patches in their mainline code. That’s why IBM and Rocket keep their own patch files. > In other words, what's the value add apart from the comfort of support, and > the SMP/E install option? > Comfort? That's hardly the case. Deploying anything into production without proper support is unheard of. If you're just a casual enthusiast downloading development tools for personal use, that's one thing. However, when an organization aims to adopt Git for managing critical source code, no responsible IT manager would be at ease without round-the-clock support. This principle applies universally, encompassing mainframes and all systems alike. Support is a must, either directly from the product vendor or through services provided by specialized organizations. As an example, consider enterprise Linux distributions like RHEL, which are predominantly constructed from open source software. RedHat (now IBM) or SUSE stands behind them, delivering essential support. Same for cloud operators. > > - KB > > ------- Original Message ------- > On Monday, August 21st, 2023 at 10:12, David Crayford <[email protected]> > wrote: > > >> On 19/8/2023 6:18 pm, Sebastian Welton wrote: >> >>> On Fri, 18 Aug 2023 19:33:03 +0800, David [email protected] wrote: >>> >>>> I'm feeling a bit puzzled here! Bash doesn't come pre-installed with >>>> z/OS; rather, it's a tool ported by Rocket, so there shouldn't be any >>>> compatibility problems, right? If IBM decides to include zsh, which is >>>> considered superior to bash, this could be a game-changer. >>>> Currently trying this one out >> >> >> If you're using it don't forget to star the repo on Github. That really >> helps the maintainers gauge how many people are using the port. >> >>> not too sure if there is any Rocket influence or not: >> >> >> Not that I know of. The distinction between the z/OS Open Tools >> initiative and Rocket's ported tools lies in Rocket's provision of >> commercial support and SMP/E packaging. Customers tend to approach >> open-source solutions on z/OS cautiously, especially after the >> Shellshock incident with bash. Rocket remains vigilant about addressing >> any new Common Vulnerabilities and Exposures (CVE), promptly releasing >> patches. Bash is a dependecy for Git, which holds significant importance >> as a ported tool. In recent customer presentations, the predominant >> focus has been on modernization, involving Git integration, whether >> directly or through bridging from existing legacy SCM systems. >> >> I extend my appreciation to IBM for their commitment to the z/OS Open >> Tools initiative. The community is commendable, well-guided, and staffed >> with highly skilled engineers. Numerous packages have been ported, some >> of which I have undertaken myself, like CMake. I intend to leverage the >> z/OS Open Tools ports as they spare me the effort of continuous >> maintenance. >> >>> https://github.com/ZOSOpenTools/bashport >>> >>> Sebastian. >>> >>> ---------------------------------------------------------------------- >>> For IBM-MAIN subscribe / signoff / archive access instructions, >>> send email [email protected] with the message: INFO IBM-MAIN >> >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
