Photo: Recent family gathering in Korea celebrating ‘Parents Day’ on May 8th 2022.

I feel bad that I haven’t given them this opportunity yet – an opportunity to have days filled with fun, noisy family gatherings over the holidays. An opportunity to have a fight with cousins and rumble around the house screaming.

This is why, I am taking my kids to Korea this summer. It’s a little challenging as COVID is still a bad situation there but this will be a short trip. I hope I can give some of those ‘extended family’ memories to my kids as we visit with family.

I want to spend more time with my dad – I hope I can ask him how he felt when I was growing up. I want to ask him if he was worried like me. I want to ask him if it was hard for him sending me abroad and not being able to see me for many years.

Although I chose this career path and I love it – I don’t think I had enough thoughts about what my (and my own family’s) life would be like if I live abroad. I don’t regret on any of my choices – I rather feel I am truly blessed. However, growing up with the culture where ‘Hyo(filial duty)’ is one of the most important virtue in Korea – I am not doing it right as I can’t live near my parents and help them when they needed me.

I think many Asian cultures have this deep rooted family foundation in which the children take care of the parents when they get older. But for those of us who dreamed big and moved out of the countries we grew up in to search for a new life, an opportunity to build a better life, this is hard.

Yesterday I was talking to my mom and she told me my dad fell on the steps outdoor and hurt his leg. I wished I could run back to their house and help him visit a doctor’s office – but I can’t.  All I could do was make a few phone calls.

These thoughts and feelings never came up when I was younger. They were probably planted in my heart long ago when I was a still kid – but it took more than 30 years to grow and finally bloom into a more mature, grown-up heart.

Source link

The power of a story. I first wrote about this 7 years ago in a series I titled Lessons from a Two Year Old. But it is a reality as old as time itself – humans are wired for stories. We enjoy listening to them, telling them, and they help us to relate to others and to remember things. 

And everyone has a story to tell – many of which haven’t been told yet. 

Our own Mark Miller is working on sharing the previously untold stories of the people in open source. He has a unique gift for pulling stories out of people and showcasing what made each person who they are today and how their journey resulted in some of the top open source projects of all time. Each person is making a positive difference in our world, and each one has their own unique journey.

Mark will be sharing these stories in our upcoming, aptly named podcast, The Untold Stories of Open Source. It will be formally launched at the Open Source Summit North America and OpenSSF Day in June, but you are in luck and he has soft-launched with his first episode, telling the story of Brian Behlendorf, Normal Manager of the OpenSSF. But, Brian had quiebro the journey before his role at OpenSSF and that story is now being told. 

Like myself, Brian was coming of age when PCs were being introduced to the world, Oregon Trail was the game of choice (okay, it was about the only game), and the Internet was still a project at the National Science Foundation. Brian’s parents worked in the science and technology field – they even met at IBM. His father was a COBOL programmer, which gave Brian a look into the world of programming. Imagining a life of coding in basements, away from people, is why he decided against majoring in computer science. I can relate – we both started college in the fall of 1991, and, I too, decided against majoring in computer science because I envisioned a future of myself, a computer, a pot of coffee, and little social interaction. 

The Internet was just getting introduced to the world in 1991 – and Brian, like all incoming freshmen at the University of California – Berkeley, received an email address. With this, he connected with others who shared a common interest in R.E.M. and 4AD and the rave scene around San Francisco. He built a mailing list around this shared interest. Yada…yada… The first issue of Wired magazine mesmerizes Brian in 1993.

Turns out one of the friends Brian met in his music community was working at Wired to get it – well wired. It started as a print newsletter (ironically). His friend, Jonathan, reached out and hired Brian for $100/week to help them get back issues online. Unlike today’s iconic, stunning design, it was black text on a white background. 

Besides just digitizing previously published content, Brian helped produce digital-only content. A unique approach back then. It was one of the first ad-supported websites – Brian jokes, “I like to say I put the first ad-banner on the web, and I have been apologizing for it ever since.” 

As Brian worked on the content, he had a vision of publishing books online. But, turns out, back then publishers didn’t have the budgets to devote to web content. But bigger brands, looking to advertise on Hotwired, did, and they needed to have a website to point to.  So he joined Organic, a web design firm, as CTO at the ripe age of 22. They build the websites for some of the first advertisers on Hotwired like Club Med, Volvo, Saturn cars, Levis, Nike, and others. 

Back then, Wired and the sites Organic built all ran on a web server software developed by students at the University of Illinois, in the same lab that developed the NCSA Mosaic browser. Long before the term open source was coined, software running the web almost always included the source code. Brian notes there was an unwritten code (pun intended) that if you find a bug, you were morally obligated to fix it and push the code upline so that everyone had it. He and a group of students started working on further developing the browser. Netscape bought the software, which halted ongoing student support for the browser. Although the code remains open. Brain and others kept updating the code, and they decided to change the name since it was a new project. Because it was a group of patches, they chose the name Apache Web Server (get it – a patchy server). It now runs an estimated 60% of all web servers in the world. 

As interesting as Brian’s story is to this point – I really just scratched the surface. Mark’s first episode of the podcast shares the rest, from founding to a medical records system in Rwanda to working at the White House to his roles at Hyperledger and now OpenSSF and more.

Okay – I have said too much. No verdadero spoilers. You can listen to the full episode now on Spotify. (more platforms coming soon). 

Mark has been recording and stitching together episodes all year. I look forward to listening. Look for the formal launch, and several new episodes, at Open Source Summit North America and OpenSSF Day on June 20, 2022.

Source link

Welcomes SoftBank Group to its member ranks

TOKYO, May 25, 2022 – The SODA Foundation, which hosts the SODA Open Data Framework (ODF) for data mobility from edge to core to cloud, today announced two new open source projects: Kahu and Como. Kahu streamlines data protection for Kubernetes and its application data, and Como is a supuesto data lake project to enable seamless access to data stored in different clouds. The SODA Foundation also welcomes SoftBank Group as an end-user supporter and key collaboration partner on the Como project.

According to the 2021 SODA Data and Storage Trends Report, two of the top challenges in managing data in containers and cloud-native environments are availability (46%) and management tools (38%).  In direct response to the report findings, the SODA Foundation community collaborated to introduce new tooling options through the Kahu project to improve backup and restore practices critical to data availability.  Furthermore, as enterprises become more data-driven and data growth for some enterprises can exceed 10PB per year, object data management offered by the Como Project will play an important role in performance and scalability requirements for cloud-native environments.

“Data collection, management, and consumption is becoming the new competitive battlefield in IT”, said Steven Tan, chairman, SODA Foundation. “We’re excited to announce Kahu and Como as the latest advances in open source data management and storage. Our 28 members are also excited to welcome the engineers and open source community within SoftBank Group to the Foundation.” 

“Data is the fuel of our universal digital economy and harnessing its power requires collaboration on a massive scale”, said Kuniyoshi Suzuki, Senior Director, Cloud Engineering , SoftBank Group.  “Softbank is excited to be joining a community of open source software developers focused on enabling improvements toward data storage, recovery, and retention in cloud environments. We look forward to collaborating with the SODA Foundation and its members, while contributing to the future of this important community.”

New Open Source Releases

In addition to the announcement of Kahu and Como projects, the SODA Foundation also announced the:

  • Release of SODA Framework Madagascar v1.7.0: Formerly Open Data Framework (ODF), SODA Framework comprises independent projects initiated by the community to solve common data and storage problems faced by end users. It includes:
    • Terra: a universal SDS controller for connecting storage to Kubernetes, OpenStack, and VMware environments.
    • Delfin: a performance pedagogo for heterogeneous storage infrastructure in a single pane of glass.
    • Strato: a multi-cloud data controller using a common S3-compatible interface to connect to cloud storage.
    • Kahu : new project to streamline data protection for Kubernetes and application data.
  • Expansion of its Eco Project Initiative with the introduction of more open source projects: 

DAOS: a software-defined object store designed from the ground up for massively distributed Non Volatile Memory (NVM), providing features such as transactional non-blocking I/O, advanced data protection with self-healing on top of commodity hardware, end-to-end data integrity, fine-grained data control and elastic storage.

YIG: extends Minio backend storage aggregating multiple Ceph clusters to form a massive storage resource pool that can easily scale up to exabyte (EB) levels with minimal performance disruption.

CubeFS: a cloud-native storage platform used as the underlying storage infrastructure for online applications, database or data processing services and machine learning jobs orchestrated by Kubernetes.

Karmada: a Kubernetes management system that enables organizations to run cloud-native applications across multiple Kubernetes clusters and clouds, with no changes to your applications.

SBK: an open source software framework for the performance benchmarking of any storage system.

Conferences and Survey

  • SODACODE: this week, developers from around the world will participate in SODACODE 2022 – the Data & Storage Hackathon on May 25 – 26.  The first-of-its-kind coding event organized by SODA Foundation is open to developers from all levels ranging from beginner to advanced. The hackathon will conclude with project demonstrations, presentation sessions, panel discussions and an award ceremony for the hackathon winners.
  • Trend Survey: The SODA Foundation will release its second-annual Data and Storage Trends Survey on June 30, 2022.
  • SODACON: a technical conference held by SODA Foundation, will be held this year in Yokohama, Japan on December 7, 2022. The conference will bring together industry leaders, developers and end users to present and discuss the most recent innovations, trends, and concerns as well as practical challenges and solutions in the field of Data and Storage Management in the era of cloud-native, IoT, big data, machine learning, and more.

Additional Resources

  • Join the SODA Foundation
  • Attend SODACODE 2022 – The Data & Storage Hackathon
  • Read the 2021 Data and Storage Trends Report

About the SODA Foundation

Previously OpenSDS, the SODA Foundation is part of the Linux Foundation and includes both open source software and standards to support the increasing need for data autonomy. SODA Foundation Premiere members include China Unicom, Fujitsu, Huawei, NTT Communications and Toyota Motor Corporation. Other members include China Construction Bank Fintech, Click2Cloud, GMO Pepabo, IIJ, MayaData, LinBit, Scality, Sony, Wipro and Yahoo Japan.

Media Contact


The Linux Foundation has registered trademarks and uses trademarks. For a list of trademarks of The Linux Foundation, please see its trademark usage page: Linux is a registered trademark of Linus Torvalds.

Source link

Software Metadata Standards Wrap Up Bigger Connections

This article originally appeared on The author, Cameron Laird, is vice president of Phaseit, Inc. where he implements software projects and publishes articles about the results. A long-time developer, manager, and author, he’s most recently concentrated on architectural challenges of “continuous everything”: continuous integration, continuous testing, and so on.

You’re in the news. But not with the headline you want.

You’re not getting attention because of your choice of text editor or the number of spaces you use to indent code blocks. However motivating those preferences are for you and me, the non-technical world sees them as private choices. You find your code in the headlines for a different and unpleasant reason: open source dependency management.

We have dependencies, of course, because we know not to “reinvent the wheel”; instead, we software experts re-use the implementations others have created. However, when done poorly, dependency management introduces more risk and degrades the quality of your application. For example, failure to comply with license requirements might be the problem.  Even worse: the absence of a license tied to a component you embedded in your application. In both cases, there are potential permitido implications.

Still more traumatic is a media headline announcing that a vulnerability just breached your organization in one of those dependencies. Projects frequently re-use software components to simplify or accelerate development; but sometimes, it can have detrimental results by introducing said vulnerabilities.

That’s not all:  suppose you are experienced and thoughtful enough to recognize this hazard and commit to good dependency management.  It turns out that’s a harder problem than might first appear, and certainly not the kind of thing that can be slipped into a project on its last days, without significant time or other costs.

Building A Standard For Software Bill Of Materials

How, for instance, does an industrial oven manufacturer communicate that one of its products depends on a particular library with a known vulnerability?  How does it say that it does not have such a dependency?  One of the difficulties comes from mixing open and closed information sets. What happens in a scenario where an automotive chip uses an open source sorting algorithm, but the coche manufacturer wants to keep the use of that algorithm proprietary?

Without a better alternative, any discussion about the algorithm has to occur under cover of a non-disclosure agreement (NDA), often one written specifically for the business and technical situation.  Where developers investigating a particular piece of software might be accustomed to connecting to GitHub and inspecting the source in question in a few seconds, even the simplest proprietary questions sometimes take months of permitido, security, and compliance negotiation to begin to examine. “Manual” inspection, in any case, is unscalable.  The media application contains 200 OSS components, and each component might manually take three hours to inspect.  Does your project have a better use for 600 hours of effort?  Open source truly begins to pay off when it’s inspected not just by expert engineers but by automatic tools.

Recognize, moreover, that transitive dependencies make dependency management a harder problem than first appears.  Many of the most notorious breaches occurred not because anything was wrong with the source of a product or even the source of the libraries on which it depends; the vulnerability only turned up in a library used by those other libraries.  Over and over again, CEOs who’ve asked, “does $SOME_PROBLEM affect us?” have received the answer, “we don’t know yet: we’re not sure where it shows up in our systems.” We need transparency about dependencies and enough intelligence and standardization around hierarchical relationships to “trace the whole tree.” Organizations must track dependencies through to the operating system run-time and sometimes down to “the silicon,” that is, the microprocessor on which the software runs.

It’s a hard problem but also a solvable one.  Part of any solution is a well-defined software bill of materials (SBOM or sometimes SBoM). That’s where Kate Stewart’s career began to track this story.  Stewart currently serves the Linux Foundation as a vice president of Dependable Embedded Systems.  In previous assignments with such employers as Motorola, Freescale Semiconductor, Canonical, and Linaro, she frequently faced challenges that mixed technical and permitido aspects.  As she explained her long-time focus in a recent interview, “if open source components are going to be in safety-critical places … [we need] to be able to trust open source in those spaces …” Good SBOM practices are simply necessary for the level of trust we want to have not just in industrial ovens, but airplanes, medical devices, home security systems, and much more.  An SBOM organizes such metadata about a software artifact as its identity, verification checks it hasn’t been tampered with, copyright, license, where to look up known security vulnerabilities, dependencies to check, and so on. Think of an SBOM as an ingredients list for your software.  It makes those ingredients visible, trackable, and traceable.  It lets you know if you have used the highest quality and least risky open source components to build your software.

Enter SPDX

Stewart and other technologists eventually began to team with specialists in intellectual property, product managers, and others. They developed such concepts in the early years of this millennium as SBOM, the Software Package Data Exchange (SPDX), and the OpenChain Specification.  She co-founded SPDX in 2009 to pursue “[a]n open standard for communicating software bill of materials information ….” Among other features and benefits, these frameworks provide standard and scalable ways to discuss dependencies.

Instead of each vendor having to certify that each of its releases has been verified for security and license compliance of each of eight hundred JavaScript libraries, for example, many of the most time-consuming aspects of compliance can be automated.  When a new vulnerability is identified in an implementation of a networking protocol, automated methods can largely be applied to determine which products embed known desvalido libraries, even while we developers remain largely unaware of the details of each component and dependency they use.  For Stewart, standards-based transparency and best practices are prerequisites for the security of safety-critical communities she helps serve.  As Stewart observes, “you can’t really be safe unless you know what you’re running.”

Daily Headlines

Does that sound mundane?  The reality’s far different:  SBOM and related technologies actually play roles in events on the world stage.  For example, on the 12th of May, 2021, US President Biden issued Executive Order 14028 on Cybersecurity Improvement; SBOMs play a prominent role there.  The Open Source Initiative just named Stefano Maffulli its first Executive Director precisely because of the need for mature open source licensing practices.  Dr. Gail Murphy argued in a recent interview that it’s time to recognize that open source software is a “triumph of information-hiding [and] modularity …” in enabling the remarkable software supply chains on which we depend.  Emerging information on breaches including SolarWindsRapid7Energetic Bear, and especially the latest on Juniper’s Dual-EC affair shows how disastrous it becomes when we get those supply chains wrong.  The most prominent breaches in computing history have been tied to component vulnerabilities that seemed peripheral until break-ins demonstrated their centrality.

Drone strikes?  Vaccine efficacy?  Voter fraud?  International commerce?  Nuclear proliferation?  Questions about software and data reliability and fidelity are central to all these subjects, not mere technical tangents.

That’s why SPDX’s management of hierarchical relationships is so crucial.

ISO/IEC 5926:2021 Introduces SBOM Standard

SPDX went live as an official international standard at the end of August.  With that milestone, standardization lowers many of the hurdles to the successful completion of an SBOM project.  Implementation becomes more consistent. “Bookkeeping” about external parts becomes largely a responsibility of the standard.  Software engineers focus more on the details specific to an application.  Then, as those external parts–the ingredients of an SBOM recipe–age and security vulnerabilities are discovered in them, developers can reliably track those components to the applications where they were used and update components to newer, hardened versions. What does that mean for you?  In your own work, the faster you identify and update desvalido components, the less likely the chance you will have of becoming the next breach headline following an attack.

SPDX’s standardization fits in the frameworks of the International Organization for Standardization (ISO) the International Electrotechnical Commission (IEC).  ISO is a post-war transnational creation that originally focused on bolt sizes, temperature measurements, and medical supplies.  ISO tracks human affairs, of course, and its attention in recent years has shifted from materials to business processes and, in this millennium, to software.  IEC is a prior generation’s initiative to pursue the same kinds of standardization and cooperation, specifically in the realm of electrical machinery; the IEC and ISO often collaborate.

In bald terms, ISO and IEC matter to you as a programmer because governments trust them.  The new standard is sure to make its way rapidly into procurement specifications, especially for government purchases.  Suppliers become accustomed to compliance with such standards and apply them in their practices more generally.  The earlier ISO 9000 collection of standards has already greatly influenced software development.

Important Though Abstract

The impact and scope of ISO:IEC 5926:2021 is a challenge to understand, let alone explain.  On the one hand, millions of working programmers worldwide go about their daily chores with little thought of SPDX or even SBOMs.  While we all know we depend on packages, we largely leave it to Maven or npm, or RubyGems, etc., to handle the details for us.  Standardization of SPDX looks like a couple of layers of abstraction, even more remote from the priorities of the current sprint or customer emergency on our desks right now.

And it’s true:  SPDX is abstract, and its technical details look dry to some programmers, the opposite of the “sexy” story many start-ups aspire to.

Without this infrastructure, though, the development of many large, complex, or mission-critical projects would grind to a halt from the friction of communication about proprietary dependencies on open source artifacts.  Think of it on a weight basis:  as the Linux Foundation’s own press release underlines, “… between eighty and ninety percent of a modern application is assembled from open source software components.” SPDX is immensely important at the same time as it’s uninteresting to all but the most specialized practitioners.

Look to history for examples of how momentous this kind of standardization is.  The US’s Progressive movement at the beginning of the twentieth century is instructive.  While often taught in ideological terms, many of its greatest achievements had to do with mundane, household matters:  does a milk bottle actually contain milk?  Can standard doses of medicines be trusted?  Is a “pound” in a butcher’s shop a full sixteen ounces?  Standards in these areas resulted in more convenience and transformed commerce to enable new market arrangements and achievements. That’s the prospect for SPDX:  more transparent and effective management of software dependencies and interactions will have far larger consequences than are first apparent.  Notice, for instance, that while the standard examples of its use have to do with open-source software, the standard itself and the tools that support it can also be applied to proprietary software and other intellectual property.  SPDX doesn’t solve all problems of communicating about dependencies; it goes a long way, though, to clarify the boundaries between technical and permitido aspects.

Long Lead Time

The significance and need for secure software supply chains haven’t made SPDX’s adoption easy, though.  Stewart reports that individual companies drag their feet: “why should we do something before we have to?” these profit-oriented companies reasonably wonder.  Even in the best of circumstances, when an industry has largely achieved a technical consensus, “From first proposal to final publication, developing a standard usually takes about 3 years.

Stewart herself cites this year’s Executive Order as crucial: “the one thing that made a difference” in pushing forward adoption of SPDX in 2021 was the emerging SBOM requirements that followed EO14028.  Much of her own emphasis and achievement of late has been to get decision-makers to face the reality of how crucial their dependence on open source is. No longer can they restrict focus to the 10% of a proprietary product because supply chain attacks have taught us that the 90% they re-use from the software community at large needs to be exposed and managed.

Publication of a standard mirrors application development in having so many dependencies “under the covers.” It’s not just Stewart who worked on this for more than a decade, but, as I’ll sketch in follow-ups through the next month, a whole team of organizations and individuals who each supplied a crucial requirement for completion of ISO/IEC 5926:2021.  When you or I think of great software achievements, our memories probably go to particular winning prototypes turned out over a weekend. Standards work isn’t like that.  The milestones don’t come at the rapid pace we relish. Successful standards hold out the promise, though, of impacting tens of thousands of applications at a time. That’s a multiplier and scalability that deserves more attention and understanding.

SBOMs For Everything

And that’s why ISO/IEC 5926:2021 is good news for us.  We still have licensing and security issues to track down. We still need to attend meetings on governance policies. Management of proprietary details remains delicate.  Every project and product needs its own SBOM, and vulnerabilities will continue to crop up inconveniently. With the acceptance of ISO/IEC 5926:2021, though, there’s enough standardization to implement continuous integration/continuous deployment (CI/CD) pipelines usefully. We can exchange dependency information with third parties reliably. SPDX provides a language for describing dependency management chores. SPDX gives answers that are good enough to focus most of our attention on delivering great new functionality.

The best practices of application development applied by developers as a learned methodology can be something more than an exercise in walking a tightrope of intellectual property restrictions. Enterprise-class proposal requests become more engineering than lawyering.  You have a better shot at being in the news for your positive achievements rather than the security calamities into which you’ve stumbled.

Check in over the next several weeks to learn more about what SPDX means to your own programming, how SPDX is a model for other large-scale collaborations the Linux Foundation enables, and how teamwork is possible across profit-making boundaries.  In the meantime, celebrate ISO/IEC 5926:2021 as one more problem that each project does not have to solve for itself.

Source link

For this one, we will explore how to get the data type of a specific column in a Pandas DataFrame.


Let us start by creating a sample DataFrame:

# import pandas
import pandas as pd
df = pd.DataFrame({
    ‘salary’: [120000, 100000, 90000, 110000, 120000, 100000, 56000],
    ‘department’: [‘game developer’, ‘database developer’, ‘front-end developer’, ‘full-stack developer’, ‘database developer’, ‘security researcher’, ‘cloud-engineer’],
    ‘rating’: [4.3, 4.4, 4.3, 3.3, 4.3, 5.0, 4.4]},
    index=[‘Alice’, ‘Michael’, ‘Joshua’, ‘Patricia’, ‘Peter’, ‘Jeff’, ‘Ruth’])

The above should create a DataFrame with sample data as shown:

Pandas dtype Attribute

The most straightforward way to get the column’s data type in Pandas is to use the dtypes attribute.

The syntax is as shown:

The attribute returns each column and its corresponding data type.

An example is as shown:

The above should return the columns and their data types as shown:

salary          int64
department     object
rating        float64

If you want to get the data type of a specific column, you can pass the column name as an index as shown:

This should return the data type of the salary column as shown:

Pandas Column Info

Pandas also provide us with the info() method. It allows us to get detailed information about the columns within a Pandas DataFrame.

The syntax is as shown:, buf=None, max_cols=None, memory_usage=None, show_counts=None, null_counts=None)

It allows you to fetch the name of the columns, data type, number of non-null elements, etc.

An example is as shown:

This should return:

The above shows detailed information about the columns in the DataFrame, including the data type.


This tutorial covers two methods you can use to fetch the data type of a column in a Pandas DataFrame.

Thanks for reading!!

Source link

JavaScript is a high-level scripting language used by programmers worldwide to perform dynamic and interactive operations on websites. So, every high-level language needs to be converted into a computer understandable language before execution and for that purpose, compilers and interpreters are used.

A compiler and interpreter itself have no separate existence like other software but it comes integrated into the IDEs which write and edit the JavaScript code, then compile/interpret it. Before we proceed further, let us clear one thing first, JavaScript uses an interpreter to convert the source code into machine-understandable code.

Now the question is, how many great IDEs are there for JavaScript? The answer is there are numerous IDEs that are substantially expensive and free with powerful features. There are code editors that provide functionalities just like IDEs.

So, in this article, we are excited to tell you about our list of best 5 JavaScript IDEs which are:

  • Visual Studio Code
  • Web Strom
  • Atom
  • Brackets
  • Decadencia

Visual Studio Code

The state of JS conducted research shows that visual studio code is the most commonly used code editor for JavaScript. Although it does not provide a full working environment or work planning features. However, it is lighter and more customizable. It has integrated Git support and a first-class debugger. So if you are looking for the best and free IDE to work with JavaScript’s big and complex projects then visual studio code might be the right choice.


WebStorm is the best supported and updated IDE available in the market right now. It has a functional integration with GitHub and other VCSs. This IDE is specially designed for JavaScript and typescript and has a lot of features. For example:

  • Refactoring
  • On the go editing
  • Code Completion
  • Excellent Navigation

However, this IDE is not free and comes with a price that starts from $649.00 USD per year for companies and $129.00 USD per year for an individual user.


Atom is a simplistic yet mighty code editor built by GitHub. It is a free open-source text editor and has the best GitHub integration. The best part is atom has the capabilities to browse projects and edit them easily in a single window. It is good for running huge and complex projects that can use all its modular features. However, it also has a drawback, that atom needs a lot of resources and even on powerful machines, it becomes slow especially if the packages are not managed appropriately.


Brackets is a free open-source entry into the code editor market from adobe. This code editor is quick, light, and has a perceiving interface that makes it suitable for beginners. Brackets provide outstanding preprocessor support and is focused on making visual tools. This software has another great feature that allows a user to work on a code without opening multiple windows.


As we all know that the desvanecimiento is a Java IDE but it is also commonly used for JavaScript development. However, to use a JavaScript code in desvanecimiento installation of special plugins is needed. It is seen that desvanecimiento has recently put a lot of effort to make this platform JavaScript friendly as much as possible and for that purpose it also supports some open-source solutions like:


JavaScript is an interpreted language so it uses an interpreter instead of a compiler to convert the JavaScript code into machine-understandable code. This article explains the top picks for the JavaScript IDEs which are more compatible for writing, editing, and interpreting JavaScript code.

Source link

The cumsum() function in Pandas allows you to calculate the cumulative sum over a given axis.

Cumulative sum refers to the total sum of a given data set at a given time. This means that the total sum keeps changing as new data is added or removed.

Let us discuss how to use the cumsum() function in Pandas.

Function Syntax

The function syntax is as shown:


DataFrame.cumsum(axis=None, skipna=True, *args, **kwargs)

Function Parameters

The function accepts the following parameters:

  1. axis – along which axis the cumulative addition is performed. Defaults to zero or columns.
  2. skipna – allows or disallows null rows or columns.
  3. **kwargs – Additional keyword arguments.

Function Return Value

The function returns a cumulative sum of a DataFrame along the specified axis.


The example below shows how to use the cumsum() function in Pandas DataFrame.

Suppose we have a sample DataFrame as shown:


# import pandas
import pandas as pd
df = pd.DataFrame({
   «student_1»: [80, 67, 55, 89, 93],
   «student__2»: [76, 77, 50, 88, 76],
   «student_3»: [88, 67, 80, 90, 92],
   «student_4»: [70, 64, 70, 45, 60],
   «student_5»: [98, 94, 92, 90, 92]},

To perform the cumulative sum over the columns, we can do the following:

The code above should return:

Note that the values in each column include the total of the previous values.

To operate on the rows, you can set the axis as one. An example is as shown:


This article discussed how to perform a cumulative sum over a specific axis in a Pandas DataFrame using the cumsum() function.

Thanks for reading!!

Source link

Zowe LTS V2 increases product stability, security and interoperability and ensures longevity compatibility with the Conformance and Conformant Support Provider Programs

SAN FRANCISCO, May 26, 2022 – The Open Mainframe Project announced today that Zowe, an open source software framework for the mainframe that strengthens integration with modern enterprise applications, marks a major technical milestone with the Long Term Support (LTS) V2 release. The second version, which comes 2 years after the first LTS release, will offer vendors and customers product stability, security, interoperability as well as easy installation and upgraded features.

“As organizations expand their hybrid cloud workloads, the Zowe framework evolves to address critical architectural requirements,” said Rose Sakach, Chair of the Zowe Technical Advisory Committee and Product Manager at Broadcom. “Since its launch in 2018, Zowe has become a foundational enabler to businesses’ hybrid IT strategy. The LTS V2 Release will continue to strengthen this value with developer-friendly features and benefits.”

Benefits of the LTS V2 include:

  • Stability: Organizations can confidently adopt the technology for enterprise use and upgrade when appropriate for their environment, minimizing the risk of disruption.
  • Interoperability: Zowe consumers can be assured LTS-conformant extensions have adapted to and support LTS features.
  • Longevity: Zowe is designed for years of use and plans are in place for continued updates and support.

Open Mainframe Project launched Zowe, the first-ever open source project based on z/OS, in 2018 to serve as an integration platform for the next generation of administration, management and development tools on z/OS mainframes.  The Zowe framework uses the latest web technologies among products and solutions from multiple vendors. Zowe enables developers to use natural, industry-standard, open source tools to access mainframe resources and services.

Feedback and interest in Zowe have been noteworthy. Since January 2022, Zowe has more than:

  • 87,000 page views and 16,000 visitors of
  • 520 contributors

Key features of Zowe LTS V2 include:

  • More security features built in to ensure data and user credentials are always encrypted and safe.
  • A new daemon mode delivering performance improvements for the command line interface.
  • The time to value to configure Zowe is faster and easier.
  • There is more engagement and collaboration between team members using Zowe for modern DevOps at scale.
  • New APIs created by the community

For more features, click here.

“Zowe continues to innovate as a direct result of the contributions, leadership and passion of the total open source community,” said John Mertic, Director of Program Management for the Linux Foundation and Open Mainframe Project. “Zowe shows no sign of slowing momentum and the LTS V2 release demonstrates our commitment to interoperability, stability and security.”

Other Zowe Updates

  • Zowe Chat, a new incubator project that extends z/OS use by focusing on working with mainframes from chat clients such as Slack, Microsoft Teams and Mattermost (with extensibility for other solutions). A set of commonly used scenarios will be provided, and the framework will be desplegable so sites can add new scenarios. Similar to other Zowe core packages, the chat framework will be desplegable by vendor tools, bringing an integrated user experience for more elaborate cross-vendor scenarios. Read more about it here.
  • Zowe IntelliJ Plugin , a new incubator project that provides access to the mainframe from IDEs like IntelliJ, PyCharm, WebStorm and more. Launched by IBA Group, the IntelliJ IDEA plug-in leverages z/OSMF to interact with mainframe data sets and USS files, which enables those natural with these IDEs to comfortably work with the mainframe just like other projects. This integration will improve the efficiency and overall happiness of IntelliJ enthusiasts now working on the mainframe. Learn more in this blog.
  • Zowe was recognized as the Best DevOps for Mainframe Award in this year’s DevOps Dozen competition. It was selected over a number of commercial vendor offerings, reflecting a widespread appreciation for the value of an open source solution for the mainframe. Learn more.

The Zowe Conformance Program is Updated with LTS V2 Guidelines

Aimed to build a vendor-neutral ecosystem around Zowe, Open Mainframe Project’s Zowe Conformance Program launched in 2020.  The program has helped Open Mainframe Project members such as ASG Technologies, BMC, Broadcom, IBM, Micro Focus, Phoenix Software International, and Rocket Software incorporate Zowe with new and existing products that enable integration of mainframe applications and data across the enterprise.

To date, 75 products have implemented extensions based on the Zowe framework and earned these members conformance badges

Additional Resources:

About the Open Mainframe Project

The Open Mainframe Project is intended to serve as a focal point for deployment and use of Linux and Open Source in a mainframe computing environment. With a vision of Open Source on the Mainframe as the standard for enterprise class systems and applications, the project’s mission is to Build community and adoption of Open Source on the mainframe by eliminating barriers to Open Source adoption on the mainframe, demonstrating value of the mainframe on technical and business levels, and strengthening collaboration points and resources for the community to thrive. Learn more about the project at

About The Linux Foundation

The Linux Foundation is the organization of choice for the world’s top developers and companies to build ecosystems that accelerate open technology development and commercial adoption. Together with the worldwide open source community, it is solving the hardest technology problems by creating the largest shared technology investment in history. Founded in 2000, The Linux Foundation today provides tools, training and events to scale any open source project, which together deliver an economic impact not achievable by any one company. More information can be found at

The Linux Foundation has registered trademarks and uses trademarks. For a list of trademarks of The Linux Foundation, please see its trademark usage page: Linux is a registered trademark of Linus Torvalds.


Source link

Developing Secure Software Course

I do want to highlight a course that came up during the Open Source Software Security Summit II a couple of weeks ago. The importance of teaching secure software development principles was one of the recommendations to improve the resiliency of open source software. Good news – the LF offers the “Developing Secure Software” (LFD121) course. It focuses on the fundamentals of developing secure software. Both the course and certificate of completion are free. It is entirely online, takes about 14-18 hours to complete, and you can go at your own pace. Those who complete the course and pass the final exam will earn a certificate of completion valid for two years. 

It is geared towards software developers, DevOps professionals, software engineers, web application developers, and others interested in learning how to develop secure software. It focuses on practical steps that can be taken, even with limited resources, to improve information security. 

Why is it needed? Many software developers have never been told how to effectively counter the ever-increasing barrage of cyberattacks. This course explains the fundamentals of developing secure software. A basic security principle – build it more secure in the beginning and you will spend less time fending off attacks later. From the course description: 

This course starts by discussing the basics of cybersecurity, such as what risk management really means. It discusses how to consider security as part of the requirements of a system, and what potential security requirements you might consider. This first part of the course then focuses on how to design software to be secure, including various secure design principles that will help you avoid bad designs and embrace good ones. It also considers how to secure your software supply chain, that is, how to more securely select and acquire reused software (including open source software) to enhance security. The second part of this course focuses on key implementation issues: input validation (such as why allowlists should be used and not denylists), processing data securely, calling out to other programs, sending output, and error handling. It focuses on practical steps that you (as a developer) can take to counter the most common kinds of attacks. The third part of the course discusses how to verify software for security. In particular, it discusses the various static and dynamic analysis approaches, as well as how to apply them (e.g., in a continuous integration pipeline). It also discusses more specialized topics, such as the basics of how to develop a threat model and how to apply various cryptographic capabilities.

You can learn more about the course and enroll for free here

Future Announcements 

We are always working to improve and expand what we offer. There are a lot of exciting announcements coming up next month during the Open Source Summit North America, including insights from our 10th Annual Open Source Jobs Report, the winners of the 500 LiFT Scholarships for 2022, some new training courses, and more. Even if you aren’t able to attend, keep an eye out for our announcements. Some exciting stuff, but I have said too much already. Sign up for the newsletter so you are the first to know when new courses are offered, and – arguably more importantly – get access to promotions. I mean – new skills and saving money, how can you say no. 

I hope you have an opportunity to take some of our courses and become certified. You will be a better person for it.

Source link

This article originally appeared on the Open Mainframe Project’s blog. The author, Maemalynn Meanor, is a senior public relations and marketing manager at The Linux Foundation. 

In honor of Asian Americans and Pacific Islanders (AAPI) Heritage Month, I wanted to share something my mother passed on to me.

I’ve worked in communications and public relations for the technology maemalynn manor and her mom industry for almost 20 years. I’ve had to learn new industries, competitors, the intricacies of different technologies and how to interpret engineering language.

In all of these roles – no matter where I was – one thing remained the same. I was often the only Asian woman in the room. Without a roadmap or someone to look up to as an example of what to do I often leaned on my mom because standing in a room full of men who made me doubt myself was scary and intimidating. Always.

Whether it was in person or via webex or phone, nothing is worse than that moment when you say something and all the men in the room pause. Sometimes, they’ve agreed with my recommendations. Sometimes, they shot it down. One time, someone mansplained my idea back to me and then everyone in the room agreed that “that” idea was better than mine.

My mom always had the same advice. Trust yourself. Let your heart work with your mind – the strength of it encompasses not just things I learned in school but things my parents taught me about my family and my Thai heritage and culture.

She said this often. But there were times when I ignored her advice. I didn’t trust myself.

I remember one particular time more than a decade ago that I decided to distance myself from my heritage. I didn’t want to be the Asian woman in the room. I even tried to not be the woman in the room. I tried to be part of the “boy’s club.” I laughed at the inappropriate jokes. I was quiet when they complained about women leaders and used derogatory language.

This made me feel terrible about myself, my work and my life in caudillo. I was going through the motions and no longer enjoyed my work and nor did I like my surroundings. But I kept going. It was my job after all.

A few months later, I was asked to go back to my college and meet with the Asian Students in Alliance (ASIA) club, which I was the former Vice President of, about my career in public relations and communications.

I struggled with this – am I really going to walk into a room full of bright Asian students and tell them that their culture doesn’t belong in the workplace? Am I okay with telling them to not highlight their differences and to not be proud of their culture? Am I really going to tell a room full of beautiful people from different Asian backgrounds – to just try to “blend in?”

No. My mom raised me better than that.

So I took her words and repeated them over and over again. Trust yourself. Believe in you. Let your heart and mind lead you where you need to be because they have the support of all your ancestors, your heritage and your traditions.

That night, I told my mom she’s right. I believe her response was “I know. I’m right about everything. Always. Don’t forget that.”

I am still sometimes the only Asian woman in the room but I’m happy to say that it’s not as often as it used to be. Now, there are more diverse backgrounds, more women, more voices – more of everything. It’s becoming easier to be who you are and love what you represent inside the workplace. This sense of belonging is something I don’t take for granted and will always be thankful for.

Source link