Sidebar

TechTip: Open Source, Dipping Toes

General
Typography
  • Smaller Small Medium Big Bigger
  • Default Helvetica Segoe Georgia Times

If you're anything like me, you want to participate in the open-source community but don't want to screw things up. I invite you to participate in a safer side of open source.

I ended my previous open-source article with the following open-ended question:

"At the end of the day, open source means community. It means IT professionals coming together and sharing information, ideas, and code. Will you participate?"

Sometimes, knowing what to do first is the hardest part of engaging in the open-source community. It's for that reason I am going to use this article to document the entire storyline of me engaging in an open-source scenario.

I get daily updates from the LinkedIn IBM i OSS group. Being informed is the first step of being part of the IBM i open-source community. You can overcome the vast amounts of new terminology only by exposing yourself to it on a regular basis. In short, subscribe to that LinkedIn group. It also would be good to get a Twitter profile and follow the #IBMiOSS hashtag.

As I was sipping my coffee this morning, I received an email update from the LinkedIn group where Chris Hird was declaring an update to his recently released open-source project. You can see a screenshot in Figure 1.

 070816bartell figure1

Figure 1: Chris Hird announces an update to his FTPCLNT project.

I don't currently have a need for an FTP client on my IBM I, but I am intrigued to see what Chris has been working on. Being curious is a personality ingredient that's important in being part of the open-source community. I set aside a couple times a day for my curiosity to take place (otherwise, I would be curious all day long). I come into work early to review social media and my inbox to get a pulse of what's going on. I also review over lunch.

I clicked the github.com link from the LinkedIn update and was presented with the project page for the FTPCLNT GitHub page, as shown in Figure 2.

 070816bartell figure2

Figure 2: Here’s the FTPCLNT GitHub project home page.

I notice a few things out of the gates that could be enhanced. The FTPCLNT project has a README.md file but it could use some additional formatting, and the project is also missing the declaration of which license it operates under. I could stop at this point and keep my thoughts to myself, but that wouldn't help the FTPCLNT project to go further. Instead, I engage and endeavor to remedy the two things I believe should be addressed. This is my opinion, and Chris might not agree, and we'll learn whether he does at a future point in time.

So how do I engage at this point? As a first step, I want to make modifications to the README.md file so the RELICGET command is in a code block to make it easier to read. I do not have authority to edit the ChrisHird/FTPCLNT project, so I need to "fork" the repo and make the changes in my own copy. Click the "Fork" button in the upper right to make your own copy of the repository, as shown in Figure 3.

 070816bartell figure3

Figure 3: Fork a repository by clicking this icon.

Figure 4 shows the result of forking the repository. As you can see, it now has my profile in the URL path and declares where it was forked from. You can also see that it brought over the entire history (note the 30 commits).

 070816bartell figure4

Figure 4: The repository has been forked.

At this point, I could clone this repository to either my IBM i or my laptop and make the changes to the README.md, but for changes like this I usually just edit the file in GitHub. Click the edit pencil as shown in Figure 5.

 070816bartell figure5

Figure 5: Edit the README.md file.

Figure 6 shows the GitHub file editor. The .md file extension stands for Mark Down, a method of adding things like headings, code sections, bolding, links, and imagesall while using text. You can learn more about Mark Down here.

 070816bartell figure6

Figure 6: Make changes to README.md using MarkDown syntax.

As I am making my changes, I will often click the "Preview changes" tab to see how things look. Figure 7 shows the "Preview changes" tab using red to show which lines have been changed or removed and green to convey added lines.

 070816bartell figure7

Figure 7: Preview changes to see what's been added, changed, or removed.

I think this looks better and am now ready to save the changes. Saving changes is called "committing" in Git nomenclature. The commit form is below the file editor, as shown in Figure 8. The best practice is to have a succinct title. I don't often add an extended description unless it's necessary, and in this case it's not.

 070816bartell figure8

Figure 8: Commit changes to history.

After the changes are committed, you will be presented with a screen similar to Figure 9. Notice the changes were committed to my personal repository. Chris doesn't yet know about my changes. You can see the commit has a unique id of 500a6637 and both Chris and I are now seen as contributors.

 070816bartell figure9

Figure 9: Changes are committed to my personal fork.

I am now ready to share my changes with Chris so they can be included back into the parent repository. Figure 10 shows how to click on the "Pull requests" tab and then select the "New pull request" button.

 070816bartell figure10

Figure 10: Do a new pull request.

You will now be presented with a screen that compares the changes you've made in your fork to those that currently exist in the parent repository, as shown in Figure 11. Notice it declares these changes can be merged automatically because there aren't any merge conflicts. A merge conflict can exist when two people have modified the same line of a file; then a human decision needs to be made as to how the conflict should be resolved. Select the "Create pull request" button.

 070816bartell figure11

Figure 11: Create the pull request.

You will now be presented with a screen where you can make changes to the pull request subject or description, as shown in Figure 12. In this case, the defaults will be used. Selecting the "Create pull request" button will finalize this process and notify Chris that somebody has made a pull request. Chris then has the opportunity to accept or reject the changes.

 070816bartell figure12

Figure 12: Finalize the pull request.

After the pull request is submitted, you will be presented with the screen shown in Figure 13. Notice we are in project ChrisHird/FTPCLNT on the "Pull requests" tab. The world can now see this change because it is public. Others could also comment on the changes made to convey any concerns or voice support for the changes. Remember, at this point Chris still hasn't accepted the changes into the parent repository.

 070816bartell figure13

Figure 13: The pull request is complete and awaits acceptance or rejection.

The next thing I wanted to look into was the fact the license isn't declared. After digging some more, I found Chris does in fact have the license included in this repo and it is included in every file, as shown in Figure 14.

 070816bartell figure14

Figure 14: The copyright found at the top of source files.

I am of the opinion this should be included in at least the README.md if not also a separate file named LICENSE in the root of the repo. I determine to make a change to the README.md (simplest solution) and need to navigate back to my fork of this project. Figure 14 shows where you can click to see all forks of this repository, and Figure 15 shows the resulting screen.

 070816bartell figure15

Figure 15: View and select a fork.

In this case, I select the "aaronbartell" fork so I can get back to my repository and begin making a second round of changes to README.md. There are a variety of ways to get back to my fork, including going to my GitHub home page. Once back in my fork of FTPCLNT, I navigate to the README.md, select it, and edit it with the content shown in Figure 16.

 070816bartell figure16

Figure 16: I added a license section to README.md.

From here, I go through the same process of creating a pull request and submitting it to Chris. Again, it's up to Chris as to whether he accepts this second pull request into the parent repository. That's a key aspect to open source with GitHub and Bitbucket: I can't commit changes directly to the parent repository; instead I can only suggest changes via pull requests. This allows all changes to be adequately filtered by the repo owners to make sure all the code and changes are good.

Now it's your turn. The community is aggregating a list of IBM i open-source repositories on this Git-controlled wiki. Not all of them are in Git repositories, but for the ones that are, feel free to peruse them and see if there are small changes you could make to clarify the project like I did in this article.

What other questions do you have about the "how" of open source? Please comment below or email me at This email address is being protected from spambots. You need JavaScript enabled to view it. with any questions you have.

Aaron Bartell

Aaron Bartell is Director of IBM i Innovation for Krengel Technology, Inc. Aaron facilitates adoption of open-source technologies on IBM i through professional services, staff training, speaking engagements, and the authoring of best practices within industry publications andwww.litmis.comWith a strong background in RPG application development, Aaron covers topics that enable IBM i shops to embrace today's leading technologies, including Ruby on Rails, Node.js, Git for RPG source change management, and RSpec for unit testing RPG. Aaron is a passionate advocate of vibrant technology communities and the corresponding benefits available for today's modern application developers. Connect with Aaron via email atabartell@krengeltech.com.

Aaron lives with his wife and five children in southern Minnesota. He enjoys the vast amounts of laughter that having a young family brings, along with camping and music. He believes there's no greater purpose than to give of our life and time to help others.

BLOG COMMENTS POWERED BY DISQUS

LATEST COMMENTS

Support MC Press Online

RESOURCE CENTER

  • WHITE PAPERS

  • WEBCAST

  • TRIAL SOFTWARE

  • White Paper: Node.js for Enterprise IBM i Modernization

    SB Profound WP 5539

    If your business is thinking about modernizing your legacy IBM i (also known as AS/400 or iSeries) applications, you will want to read this white paper first!

    Download this paper and learn how Node.js can ensure that you:
    - Modernize on-time and budget - no more lengthy, costly, disruptive app rewrites!
    - Retain your IBM i systems of record
    - Find and hire new development talent
    - Integrate new Node.js applications with your existing RPG, Java, .Net, and PHP apps
    - Extend your IBM i capabilties to include Watson API, Cloud, and Internet of Things


    Read Node.js for Enterprise IBM i Modernization Now!

     

  • Profound Logic Solution Guide

    SB Profound WP 5539More than ever, there is a demand for IT to deliver innovation.
    Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects.
    The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the companyare not aligned with the current IT environment.

    Get your copy of this important guide today!

     

  • 2022 IBM i Marketplace Survey Results

    Fortra2022 marks the eighth edition of the IBM i Marketplace Survey Results. Each year, Fortra captures data on how businesses use the IBM i platform and the IT and cybersecurity initiatives it supports.

    Over the years, this survey has become a true industry benchmark, revealing to readers the trends that are shaping and driving the market and providing insight into what the future may bring for this technology.

  • Brunswick bowls a perfect 300 with LANSA!

    FortraBrunswick is the leader in bowling products, services, and industry expertise for the development and renovation of new and existing bowling centers and mixed-use recreation facilities across the entertainment industry. However, the lifeblood of Brunswick’s capital equipment business was running on a 15-year-old software application written in Visual Basic 6 (VB6) with a SQL Server back-end. The application was at the end of its life and needed to be replaced.
    With the help of Visual LANSA, they found an easy-to-use, long-term platform that enabled their team to collaborate, innovate, and integrate with existing systems and databases within a single platform.
    Read the case study to learn how they achieved success and increased the speed of development by 30% with Visual LANSA.

     

  • Progressive Web Apps: Create a Universal Experience Across All Devices

    LANSAProgressive Web Apps allow you to reach anyone, anywhere, and on any device with a single unified codebase. This means that your applications—regardless of browser, device, or platform—instantly become more reliable and consistent. They are the present and future of application development, and more and more businesses are catching on.
    Download this whitepaper and learn:

    • How PWAs support fast application development and streamline DevOps
    • How to give your business a competitive edge using PWAs
    • What makes progressive web apps so versatile, both online and offline

     

     

  • The Power of Coding in a Low-Code Solution

    LANSAWhen it comes to creating your business applications, there are hundreds of coding platforms and programming languages to choose from. These options range from very complex traditional programming languages to Low-Code platforms where sometimes no traditional coding experience is needed.
    Download our whitepaper, The Power of Writing Code in a Low-Code Solution, and:

    • Discover the benefits of Low-code's quick application creation
    • Understand the differences in model-based and language-based Low-Code platforms
    • Explore the strengths of LANSA's Low-Code Solution to Low-Code’s biggest drawbacks

     

     

  • Why Migrate When You Can Modernize?

    LANSABusiness users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
    In this white paper, you’ll learn how to think of these issues as opportunities rather than problems. We’ll explore motivations to migrate or modernize, their risks and considerations you should be aware of before embarking on a (migration or modernization) project.
    Lastly, we’ll discuss how modernizing IBM i applications with optimized business workflows, integration with other technologies and new mobile and web user interfaces will enable IT – and the business – to experience time-added value and much more.

     

  • UPDATED: Developer Kit: Making a Business Case for Modernization and Beyond

    Profound Logic Software, Inc.Having trouble getting management approval for modernization projects? The problem may be you're not speaking enough "business" to them.

    This Developer Kit provides you study-backed data and a ready-to-use business case template to help get your very next development project approved!

  • What to Do When Your AS/400 Talent Retires

    FortraIT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators is small.

    This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:

    • Why IBM i skills depletion is a top concern
    • How leading organizations are coping
    • Where automation will make the biggest impact

     

  • Node.js on IBM i Webinar Series Pt. 2: Setting Up Your Development Tools

    Profound Logic Software, Inc.Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application. In Part 2, Brian May teaches you the different tooling options available for writing code, debugging, and using Git for version control. Attend this webinar to learn:

    • Different tools to develop Node.js applications on IBM i
    • Debugging Node.js
    • The basics of Git and tools to help those new to it
    • Using NodeRun.com as a pre-built development environment

     

     

  • Expert Tips for IBM i Security: Beyond the Basics

    SB PowerTech WC GenericIn this session, IBM i security expert Robin Tatam provides a quick recap of IBM i security basics and guides you through some advanced cybersecurity techniques that can help you take data protection to the next level. Robin will cover:

    • Reducing the risk posed by special authorities
    • Establishing object-level security
    • Overseeing user actions and data access

    Don't miss this chance to take your knowledge of IBM i security beyond the basics.

     

     

  • 5 IBM i Security Quick Wins

    SB PowerTech WC GenericIn today’s threat landscape, upper management is laser-focused on cybersecurity. You need to make progress in securing your systems—and make it fast.
    There’s no shortage of actions you could take, but what tactics will actually deliver the results you need? And how can you find a security strategy that fits your budget and time constraints?
    Join top IBM i security expert Robin Tatam as he outlines the five fastest and most impactful changes you can make to strengthen IBM i security this year.
    Your system didn’t become unsecure overnight and you won’t be able to turn it around overnight either. But quick wins are possible with IBM i security, and Robin Tatam will show you how to achieve them.

  • Security Bulletin: Malware Infection Discovered on IBM i Server!

    SB PowerTech WC GenericMalicious programs can bring entire businesses to their knees—and IBM i shops are not immune. It’s critical to grasp the true impact malware can have on IBM i and the network that connects to it. Attend this webinar to gain a thorough understanding of the relationships between:

    • Viruses, native objects, and the integrated file system (IFS)
    • Power Systems and Windows-based viruses and malware
    • PC-based anti-virus scanning versus native IBM i scanning

    There are a number of ways you can minimize your exposure to viruses. IBM i security expert Sandi Moore explains the facts, including how to ensure you're fully protected and compliant with regulations such as PCI.

     

     

  • Encryption on IBM i Simplified

    SB PowerTech WC GenericDB2 Field Procedures (FieldProcs) were introduced in IBM i 7.1 and have greatly simplified encryption, often without requiring any application changes. Now you can quickly encrypt sensitive data on the IBM i including PII, PCI, PHI data in your physical files and tables.
    Watch this webinar to learn how you can quickly implement encryption on the IBM i. During the webinar, security expert Robin Tatam will show you how to:

    • Use Field Procedures to automate encryption and decryption
    • Restrict and mask field level access by user or group
    • Meet compliance requirements with effective key management and audit trails

     

  • Lessons Learned from IBM i Cyber Attacks

    SB PowerTech WC GenericDespite the many options IBM has provided to protect your systems and data, many organizations still struggle to apply appropriate security controls.
    In this webinar, you'll get insight into how the criminals accessed these systems, the fallout from these attacks, and how the incidents could have been avoided by following security best practices.

    • Learn which security gaps cyber criminals love most
    • Find out how other IBM i organizations have fallen victim
    • Get the details on policies and processes you can implement to protect your organization, even when staff works from home

    You will learn the steps you can take to avoid the mistakes made in these examples, as well as other inadequate and misconfigured settings that put businesses at risk.

     

     

  • The Power of Coding in a Low-Code Solution

    SB PowerTech WC GenericWhen it comes to creating your business applications, there are hundreds of coding platforms and programming languages to choose from. These options range from very complex traditional programming languages to Low-Code platforms where sometimes no traditional coding experience is needed.
    Download our whitepaper, The Power of Writing Code in a Low-Code Solution, and:

    • Discover the benefits of Low-code's quick application creation
    • Understand the differences in model-based and language-based Low-Code platforms
    • Explore the strengths of LANSA's Low-Code Solution to Low-Code’s biggest drawbacks

     

     

  • Node Webinar Series Pt. 1: The World of Node.js on IBM i

    SB Profound WC GenericHave you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application.
    Part 1 will teach you what Node.js is, why it's a great option for IBM i shops, and how to take advantage of the ecosystem surrounding Node.
    In addition to background information, our Director of Product Development Scott Klement will demonstrate applications that take advantage of the Node Package Manager (npm).
    Watch Now.

  • The Biggest Mistakes in IBM i Security

    SB Profound WC Generic The Biggest Mistakes in IBM i Security
    Here’s the harsh reality: cybersecurity pros have to get their jobs right every single day, while an attacker only has to succeed once to do incredible damage.
    Whether that’s thousands of exposed records, millions of dollars in fines and legal fees, or diminished share value, it’s easy to judge organizations that fall victim. IBM i enjoys an enviable reputation for security, but no system is impervious to mistakes.
    Join this webinar to learn about the biggest errors made when securing a Power Systems server.
    This knowledge is critical for ensuring integrity of your application data and preventing you from becoming the next Equifax. It’s also essential for complying with all formal regulations, including SOX, PCI, GDPR, and HIPAA
    Watch Now.

  • Comply in 5! Well, actually UNDER 5 minutes!!

    SB CYBRA PPL 5382

    TRY the one package that solves all your document design and printing challenges on all your platforms.

    Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product.

    Request your trial now!

  • Backup and Recovery on IBM i: Your Strategy for the Unexpected

    FortraRobot automates the routine tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:
    - Simplified backup procedures
    - Easy data encryption
    - Save media management
    - Guided restoration
    - Seamless product integration
    Make sure your data survives when catastrophe hits. Try the Robot Backup and Recovery Solution FREE for 30 days.

  • Manage IBM i Messages by Exception with Robot

    SB HelpSystems SC 5413Managing messages on your IBM i can be more than a full-time job if you have to do it manually. How can you be sure you won’t miss important system events?
    Automate your message center with the Robot Message Management Solution. Key features include:
    - Automated message management
    - Tailored notifications and automatic escalation
    - System-wide control of your IBM i partitions
    - Two-way system notifications from your mobile device
    - Seamless product integration
    Try the Robot Message Management Solution FREE for 30 days.

  • Easiest Way to Save Money? Stop Printing IBM i Reports

    FortraRobot automates report bursting, distribution, bundling, and archiving, and offers secure, selective online report viewing.
    Manage your reports with the Robot Report Management Solution. Key features include:

    - Automated report distribution
    - View online without delay
    - Browser interface to make notes
    - Custom retention capabilities
    - Seamless product integration
    Rerun another report? Never again. Try the Robot Report Management Solution FREE for 30 days.

  • Hassle-Free IBM i Operations around the Clock

    SB HelpSystems SC 5413For over 30 years, Robot has been a leader in systems management for IBM i.
    Manage your job schedule with the Robot Job Scheduling Solution. Key features include:
    - Automated batch, interactive, and cross-platform scheduling
    - Event-driven dependency processing
    - Centralized monitoring and reporting
    - Audit log and ready-to-use reports
    - Seamless product integration
    Scale your software, not your staff. Try the Robot Job Scheduling Solution FREE for 30 days.