Recent Open Source Lab Mini Project Report

On
Issues in Recent Open Source Project
Submitted to
MUMBAI UNIVERSITY
In partial fulfillment of requirement for the award of degree of
Bachelor of Engineering
Information Technology Semester-VII

Submitted By

Sr No Name ID No.
1 Bhavesh Madhavi VU4F2122023

2 Parag Bokare VU4F2122030

3 Devdatta Thorat VU4F2122031

4 Shubham Karande VU4F2122037

Under the guidance of

Prof. Neeta Ingale

Assistant Professor

Department of Information Technology

Vasantdada Patil Pratishthan's College of Engineering & Visual
Arts
UNIVERSITY OF MUMBAI
(AY 2024-25)
 CERTIFICATE

This is to certify that the project entitled “Issues in Recent Open Source Project” is bonafide
work of Bhavesh Madhavi (VU4F2122023), Parag Bokare (VU4F2122030), Devdatta Thorat
(VU4F2122031), Shubham Karande (VU4F2122037), submitted to University of Mumbai in
partial fulfillment of requirement for the award of degree of “Bachelor of Engineering in
Information Technology-Semester-VII”

Prof. Neeta Ingale

Assistant Professor

Dr. Pradip Mane Dr. Alam N.Shaikh

Head of Department (IT) Principal
 Project Report Approval for BE.

This project report entitled “Issues in Recent Open Source Project” by Bhavesh
Madhavi (VU4F2122023), Parag Bokare (VU4F2122030), Devdatta Thorat (VU4F2122031),
Shubham Karande (VU4F2122037), is approved for the degree of Bachelor of Engineering
in Information Technology.

Examiners

1.

2.

Date:

Place: Mumbai – 22

Submitted by:

Sr No Name ID No
1 Bhavesh Madhavi VU4F2122023
2 Parag Bokare VU4F2122030
3 DevdattaThorat VU4F2122031
4 Shubham Karande VU4F2122037
 ACKNOWLEDGEMENT

We the students from Vasantdada Patil Pratishthan’s College of Engineering, Mumbai of

Fourth Year Engineering in the Department of ‘Information Technology’ have great pleasure
in presenting our efforts of developing the project named as Issues in Recent Open Source
Project
We would like to express our heartfelt gratitude to Dr. Pradip Mane, Head of the IT
Department, for providing us with inspiration, invaluable guidance, and timely suggestions
throughout our Mini project journey.
We acknowledge our deep sense of gratitude to my Guide, Prof. Neeta Ingale, Assistant
Professor in Information Technology, who helped us to complete this project work
successfully.
 INDEX
Sr. Title Page No.
No.
1 Introduction 1
.
1.1 Fundamentals of OSS 1
1.2 GPL 1
1.3 Different ways to contribute to OSP 2

2 Contribution to Open source 3

.
2.1 Introduction 3
2.2 Problem Definition

2.3 Objectives

2.4 Submission of contribution snapshots (Results) 3

2.5 Source code 8

3 Contribute to Open Source in Technologies. 12

3.1 Introduction 12
3.2 Problem Definition 19

3.3 Objectives

3.4 Submission of contribution snapshots (Results)

3.5 Source code

4 Contribute to Open Source in Network Management 23

4.1 Introduction 23

4.2 Problem Definition

4.3 Objectives

4.4 Submission of contribution snapshots (Results)

4.5 Source code

5 Contribute to Open Source in Application & Cloud Services.
5.1 Introduction
5.2 Problem Definition

5.3 Objectives

5.4 Submission of contribution snapshots (Results)

5.5 Source code

6 Conclusion
7 References
 1. INTRODUCTION

1.1 Fundamental of OSS

Open source is a term that originally referred to open source software (OSS). Open Source
Software (OSS) are user-friendly and are available as commercial and free licenced software.
Therefore, these are easy to use by anyone, anywhere. Open source is easily modifiable as its
core code is publicly accessible. As OSS is originated from the framework of software
development, it designates a set of values and initiatives, those that embrace, celebrate open
exchange, collaborative participation, rapid prototyping, clearness, and community
development. It is widely accepted by a number of people and organisations. The software
allows to outlook the code, but it does not allow the conversion or modification of the code .
Open source software is code that is designed to be publicly accessible—anyone can see,
modify, and distribute the code. Open Source Software have been growing enormously in the
field of information technology. Open Source Software (OSS) is a software whose source
code is accessible for alteration or enrichment by other programmers. The fundamentals of
Open Source Software (OSS) revolve around key principles that define its development,
distribution, and usage. These include:
1. Free Redistribution
OSS can be freely shared, copied, and distributed without restrictions. Users are allowed to
share the software with anyone, whether for free or for a fee.

2. Open Source Code

The source code is made available to the public, allowing users to view, modify, and improve
the
software. This transparency is essential for collaboration and trust.

3. Permission to Modify
Users are free to modify the software according to their needs. They can customize it, add
features, fix bugs, or improve the code, and in many cases, they can redistribute the modified
version.

4. No Discrimination
OSS is open to everyone, regardless of who they are or what their purpose is. It does not
discriminate against any individuals, organizations, or fields of endeavor.

5. License Requirements
OSS is governed by specific open-source licenses (e.g., MIT License, GNU General Public
License). These licenses ensure that the software remains open and free for all to use, modify,
and distribute.

6. Derived Works
The license must allow users to create derivative works from the original software. While
some licenses may require sharing those changes with the community, others may allow
private modifications.

7. Collaborative Development
OSS encourages collaboration among a global community of developers. Many contributors
from various backgrounds can work together to improve the software, often leading to faster
development and more secure and reliable software.

8. Transparency
With access to the source code, users can understand how the software operates, ensuring
accountability and security. There are no hidden features, such as spyware, which can exist in
closed-source software.

9. Community-Driven Innovation
The community drives the development of OSS, ensuring that the software is continuously
evolving based on real user needs and contributions. The open-source model fosters rapid
innovation and problem-solving.

10. Flexibility
OSS offers flexibility for users to adapt the software to different environments, business
models, or personal preferences. This is especially beneficial for companies or developers
needing tailored solutions.

11. Interoperability
OSS encourages compatibility with other systems and software, avoiding vendor lock-in.
Many OSS solutions are designed to integrate easily with various platforms and technologies.
 1.1 GPL

The GNU General Public License (GPL) is one of the most widely used open-
source licenses, created by the Free Software Foundation (FSF) under the GNU Project. Its
primary goal is to ensure that software licensed under it remains free (as in freedom, not
necessarily price) and open for all users. The GPL is a copyleft license, which means that
any derivative works must be distributed under the same or similar license terms. The GPL
also requires that users make the source code available when distributing copies of
software. The GPL has transformed software development by fostering collaboration and
transparency among developers. It also allows teams to build on existing projects without
legal barriers to innovation.

Key Features of GPL:

1. Freedom to Use:
Users are free to use the software for any purpose, without any restrictions on how
or where it can be used.
2. Freedom to Study and Modify:
The source code must be made available, allowing users to study how the
software works, make changes, or improve it to suit their needs.
3. Freedom to Distribute:
Users can freely distribute copies of the software, either in its original form
or modified form. They can share it with others or even sell it.
4. Copy left Clause:
One of the most distinctive features of the GPL is its copy left provision. If
someone modifies and redistributes the software (whether as is or in a modified
form), they must also release their modifications under the GPL. This ensures that
derivative works are also open source and free.
5. Preservation of Freedom:
The GPL is designed to prevent "proprietary hijacking" of open-source code. If you
distribute a modified version of GPL-licensed software, you cannot place
additional restrictions that would prevent others from enjoying the same freedoms.
1.3 Different ways to contribute to OSP

There are several ways to contribute to Open Source Projects (OSP), and they don't always
require deep technical skills. Whether you're a developer, designer, writer, or user, there are
many ways to make valuable contributions:

1. Code Contributions

 Bug Fixes: Identify bugs or issues in the project and submit fixes for them. Start with
beginner-friendly tags like "good first issue" or "beginner-friendly" in repositories.
 Feature Implementation: Suggest new features or contribute by
coding enhancements and implementing requested features.
 Refactoring Code: Improve the readability, structure, or performance of existing
code without changing its behavior.
 Writing Tests: Help projects by writing unit tests, integration tests, or end-to-end
tests to improve test coverage.

2. Documentation

 Writing or Improving Documentation: Update project documentation, clarify

instructions, or write new guides. Good documentation is crucial and often lacking in
open-source projects.
 Translating Documentation: Help translate the documentation into other languages
to make the project more accessible to a global audience.
 Tutorials and How-to Guides: Create step-by-step guides or tutorials on how to use
the software, deploy it, or implement specific features.

3. Design Contributions

 UI/UX Improvements: If the project has a graphical interface, suggest improvements

in user experience and interface design.
 Graphic Design: Contribute by designing logos, website assets, or other visual
content for the project.
 Website or Documentation Design: Help improve the overall look and feel of
the project's website or documentation site.

4. Reporting Bugs and Issues

 Bug Reports: If you find a bug, report it in detail, including steps to reproduce the
issue, error logs, and screenshots if possible. This helps developers fix problems
faster.
 Feature Requests: Suggest new features that could improve the software. Provide a
detailed explanation of how the feature would work and its potential impact.

5. Testing and Quality Assurance

 Testing New Features: Test new features or updates in a project and report any
issues. This helps maintainers ensure that the software works as expected.
  Cross-Platform Testing: Test the software on different operating systems and
devices to ensure compatibility.
 Performance Testing: Identify areas where the project could improve in terms of
speed or efficiency and provide feedback or solutions.

6. Community Involvement

 Answering Questions: Help other users by answering their questions on GitHub

issues, Stack Overflow, Reddit, or project-specific forums and chat rooms.
 Mentoring New Contributors: Help onboard new contributors by mentoring them
through the process of contributing to the project.
 Creating Tutorials or Videos: Share your knowledge about the project by creating
tutorials, videos, or blogs explaining how to use or contribute to the software.
 2. Contribution To Open Source
2.1 Introduction

In an era where collaboration and innovation drive technological advancement, open source
software (OSS) has emerged as a powerful movement that champions transparency,
community, and shared knowledge. Open source projects invite individuals from diverse
backgrounds to contribute their skills, ideas, and creativity, creating an environment where
software can evolve rapidly to meet the needs of its users.

Contributing to open source projects not only allows individuals to enhance their coding
abilities and collaborate with experienced developers but also fosters a sense of belonging
within a vibrant community. It is an opportunity to work on meaningful projects, solve real-
world problems, and create software that can benefit millions of users around the globe.

Whether you are a seasoned developer, a designer, a writer, or someone passionate about
technology, there is a place for you in the open source community. This guide will explore
the various ways you can contribute to open source projects, the benefits of doing so, and
how you can get started on your journey to becoming an integral part of this collaborative
ecosystem.

To contribute to Open Source projects, developers can:

- Submit bug reports: Identifying bugs and reporting them to the community helps
improve the software.
- Fix bugs: Developers with the necessary skills can resolve issues by writing and
submitting patches.
- Code contributions: Add new features, optimize existing ones, or refactor the codebase.
- Documentation: Write or update manuals, tutorials, and API documentation, which
is crucial for helping other users and developers.
- Community Involvement: Help with code reviews, testing, and participating in
discussions or forums to assist others
 2.2 Problem Definition

Describe the bug

When typing in the devices to include via the UI it wipes out all my Alexa devices and
doesn't include the device that I asked it to include. When I clear the 'included device' field
and update the configuration the devices have still disappeared. The only way for me to get
them back is to completely wipe the Alexa media player account and start again by
configuring the account again.

To Reproduce

To produce this bug I just need to add a device in the 'included device' text box via the UI

Expected behavior

I would assume that adding a device in the 'included device' text box would include just that
device on the Alexa app and I would also assume it wouldn't get rid of all my Alexa devices
within home assistant. In addition I would also assume if I cleared the 'included device' text
box then all my devices would return but they don't even after a reconfiguration or home
assistant restart.

2.3 Objectives

 Preserve Device Integrity:

 Correct Functionality of Device Inclusion:

 Enhance User Experience:

 Prevent Data Loss:

2.4 Snapshot
s Issue 1:-
https://github.com/includeos/IncludeOS/compare/master...Bhavesh9908:IncludeOS:master
Issue 2:-

https://github.com/SerenityOS/serenity/compare/master...shubhamvk03:serenity:master
 3. Contribute to Open Source in Technology

3.1 Introduction

 Open-source contributions are essential for improving and evolving technology, particularly in
software development.
 Open-source projects allow developers to collaborate, introduce new features, fix bugs, and
enhance the overall functionality of applications.
 Contributing to various technologies helps enhance user experience and promotes innovation across the
tech landscape.

3.2 Problem Statement

Issue 1:-
The issue pertains to a bug or incomplete implementation in data structures or algorithms,
specifically within Python. This could be related to the performance of an algorithm, incorrect
outputs, or compatibility issues with certain Python version

Issue 2 :-
Encountering an error or bug in a Python algorithm that affects functionality or causes unexpected
behavior when executed. This could involve incorrect implementation of a specific algorithm,
performance issues, or missing functionality.

3.3 Objectives :-
Issue 1 :-
• Reviewing the algorithm's implementation for logical errors.
• Optimizing the code to improve execution speed.
• Ensuring the algorithm works across different datasets and scenarios without causing errors.

Issue 2 :-
• Fixing incorrect outputs or optimizing the code for better performance.
• Ensuring the implementation adheres to best practices for algorithm design.
 3.4 Snapshots

https://github.com/TheAlgorithms/Python/compare/master...Bhavesh9908:Python:master

3.5 Source Code :-

Issue

2:

-https://github.com/TheAlgorithms/Python/compare/master...shubhamvk03:Python_DSA:maste

r
 4 Contribute to Open Source in Network Management

4.1 Introduction
 Contributing to open-source projects in network management
significantly enhances the capabilities of tools like NetworkX, which
is

widely used for network analysis and visualization.

● Open-source contributions not only fix bugs but also introduce new features,
improving the robustness of networking tools for a variety of users,
including
researchers, developers, and network engineers.
● By addressing technical issues, contributors can help
optimize performance and usability, ultimately

4.2 Problem Statement

Issue 1 :- Error function is not well. Make the new changes for it.
There is issue in the client chat its fetching errors and the function is not well.

Issue 2 :-
A "file is not launching" issue typically means the system or software is unable to open the
requested file. This could be due to a variety of reasons like unsupported file format,
corrupted file, or missing software to handle the file type. Checking the file extension,
ensuring the correct software is installed, and verifying that the file is not corrupted are basic
troubleshooting steps to resolve the issue.

4.3 Objective
Issue 1 :-

To identify and fix the error in the malfunctioning function to ensure it operates correctly
and performs its intended task without failure. The aim is to improve the reliability,
accuracy, and efficiency of the function while eliminating any bugs or logic errors affecting
its performance.

Issue 2 :-
To investigate and resolve the issue preventing the system/component from launching
properly, ensuring smooth startup and functionality. The goal is to identify any underlying
configuration, code, or dependency issues and implement fixes that restore normal operation
during launch
 4.4 Snapshots

ISSUE 1 :-
https://github.com/nmap/nmap/compare/master...shubhamvk03:nmap:master
ISSUE 2 :-
https://github.com/netdata/netdata/compare/master...Bhavesh9908:netdata:master
 5 Contribute to Open Source in Application & Cloud Services.

5.1 Introduction

 Contributions to open-source projects in application and

cloud services enhance functionality and user experience.
● Community-driven efforts address technical issues and improve
the robustness of configuration management tools like Nacos.
● Resolving problems and implementing new features ensures tools
meet the evolving needs of developers and organizations.

5.2 Problem Statement

Issue 1 :-
In this I noticed that CI check was failing. I'm not sure what the problem is. In my repo, the
check passes.
I'm suspecting we have to correct the configuration on bitrise for this repo.

Issue 2 :-
Local environment configuration is not respected for app file storage .

5.3 Objectives

Issue 1 :-
The objective of solving the issue with the CI (Continuous Integration) check failure is to
ensure that the project's automated build and testing processes are functioning correctly
across different environments, including Bitrise.

Issue 2 :-

To identify and resolve the issue where the local environment configuration for file storage is
not being respected. The goal is to ensure that the application correctly follows the defined
local storage paths and settings, enabling seamless file saving, retrieval, and management
based on the specified environment configurati
5.4 Snapshot

s Issue 1 :-

https://github.com/serverless/serverless/compare/main...shubhamvk03:serverless:main
Issue 2 :-
https://github.com/apache/airflow/compare/main...shubhamvk03:airflow:main
 6 Conclusion

In conclusion, contributing to open source projects is a rewarding and enriching

experience that not only benefits the community but also enhances one's skills and
knowledge. By participating in open source, individuals can collaborate with talented
developers worldwide, address real world problems, and create impactful solutions.
The open source community fosters innovation, creativity, and inclusivity, allowing
individuals to make meaningful contributions, regardless of their background or
expertise. As the open source ecosystem continues to grow, it's essential to recognize
the value of collaboration, sharing, and community-driven development. By
embracing open source principles, we can build a more equitable, transparent, and
technologically advanced future for all.
By tackling real-world problems such as layout bugs, camera access,

multilingual support, and network management challenges, we gained valuable

insights into key aspects of software development, including debugging, code
contribution, and user experience improvement.
Throughout the project, our technical skills were enhanced, and feedback from the
open-source community allowed us to refine our solutions. The experience
underscored the significance of open-source contributions in driving modern software
development, giving us the opportunity to actively engage with this dynamic and
rapidly evolving ecosystem.

7 References

1) https://github.com/droidconKE/droidconKE/issues/24
2) https://github.com/coremob/camera/issues/18
3) https://github.com/alandtse/alexa_media_player/issues/2556
4) https://github.com/beeware/toga/issues/2867
5) https://github.com/sam123127/CHATAPP11/issues/1
6) https://github.com/KotlinID/simple-kotlin-android
7) https://github.com/sam123127/TRANFER/pull/2