Author Archives: Evelina Rosser

COULD YOU EXPLAIN MORE ABOUT THE PROCESS OF CONTRIBUTING TO AN EXISTING OPEN SOURCE PROJECT FOR A CAPSTONE

The first step is to find an existing open source project that interests you and that you think you could potentially contribute value to. Some good places to search for open source projects include GitHub, SourceForge, GitLab, and similar platforms where many open source developers host and manage their code. You’ll want to browse through projects in areas that align with your skills and interests. Consider factors like the project’s activity level, number of open issues, how beginner-friendly it seems, and whether the codebase looks accessible enough for you to potentially make meaningful contributions as a new contributor.

Once you’ve identified a few potential projects, review their documentation to understand what types of contributions they are looking for and any guidelines they have for new contributors. Pay close attention to contribution guidelines and style guides, as following these properly will be important for having your code merged. You may also want to look at the project’s issue tracker to get a sense of common issues and potential ones you could help resolve. At this point, it’s a good idea to join the project’s communication channels like Slack or Discord if they have them to start to engage with core developers.

With a potential project in mind, the next step is to pick an issue or feature that interests you and seems achievable within the scope of a capstone. Review the issue description and any conversations thoroughly to fully understand what is being requested. You may need to ask clarifying questions in the issue. For enhancements or new features without an existing issue, you’ll need to provide a clear proposal in a new issue before beginning code work. Get explicit agreement that your proposed contribution would be a good fit for the project.

With an agreed upon task, you are ready to start coding! Be sure to fork the project’s repository to your own GitHub or other hosting account before making any code changes. As you work, document your process through comments in the code and updates in the applicable issue. Write thorough tests to validate your code works as intended. Check any style guides and follow the project’s code formatting and quality standards. Commit changes to your fork frequently with detailed, self-explanatory commit messages.

Once you have completed your task and tested your changes, you are ready to submit a pull request for review. A high-quality pull request is important, so take time to write a description clearly explaining your changes and how to test them. Request reviews from one or more core committers listed on the project. Be sure to address all feedback in the pull request conversations, even making additional commits if needed. Having an effective review process is important to learn from before the code is merged.

With all feedback addressed, the pull request is ready for final merging once all reviewers have approved. Celebrate your first open source contribution! Consider additional issues you could take on, or ways to otherwise continue engaging with and supporting the community. You’ll want to document your experience contributing to the open source project as part of your capstone paper or report. Highlight what you learned, challenges you overcame, and how contributing aligns with your academic and career interests and goals going forward.

Maintaining a good relationship with the open source project you contributed to can be valuable for references or future collaboration opportunities. Continue engaging on communication channels, consider taking on more significant issues, or potentially helping with overall project management tasks if your contributions are appreciated. Promoting your work on social media is also an excellent way to demonstrate your skills and experience to potential employers.

Contributing to an open source project can be a highly rewarding learning experience when done right. Taking the time to thoughtfully select a project, clearly define the scope of your work, communicate effectively, and thoroughly test your code will serve you well throughout your software development career. It’s a process that takes patience but pays off in learning valuable new skills that can also be highlighted on your resume or capstone. With practice, contributing to open source can become very natural ways to both learn and give back to the community.

CAN YOU PROVIDE SOME EXAMPLES OF CAPSTONE PROJECTS IN OTHER FIELDS OF STUDY AT HUMBER COLLEGE

The Business Administration – Supply Chain Management program requires students to complete a capstone project that involves a real-world supply chain analysis and improvement plan for a local organization. For example, one group of students partnered with a mid-sized manufacturing company to analyze inefficiencies in their procurement and inventory management processes. Through interviews with stakeholders and data collection, the students identified areas of waste. They then developed a set of recommendations to streamline workflows between suppliers and internal departments. This included adopting new technology for tracking incoming shipments and automated replenishment systems. The students presented their findings to the company’s executive team in a formal report and presentation that was over 15,000 characters. They received positive feedback and the company is in the process of implementing some of their proposed changes.

In the Computer Programming program, the capstone involves designing and developing a functional programming project from concept to deployment. A recent group created a web application for a client in the sports and recreation industry. They identified a need to modernize and streamline the registration, payment and communication systems currently in use for various sports leagues, classes and camps. Over several months, the students worked through all phases of the software development lifecycle to deliver a customized solution. This included creating user stories, wireframes, database models, frontend and backend coding, testing, troubleshooting and deployment. The final program contained over 25,000 lines of code and additional documentation. It allowed the client to better manage registrations online, process payments securely, generate reports and send mass communications to participants through automated emails and text messages. The students documented the entire process in a comprehensive technical report exceeding 20,000 characters.

In the Medical Laboratory Technology program, the capstone consists of a major independent research project where students apply theories and techniques learned throughout the program. One such project investigated the prevalence of drug-resistant organisms in patients admitted to a specific intensive care unit at a nearby hospital. The student worked with the hospital’s infection control team to collect bacterial samples from patients over a defined period. They then isolated, identified and performed antibiotic sensitivity testing on any pathogenic organisms found. Through statistical analysis of the results, the student was able to determine how drug resistance had changed over time in that unit compared to published data. An in-depth 15,000 character research paper was written, outlining the objectives, methodology, findings and conclusions. It provided valuable information for the hospital on ongoing surveillance of antimicrobial resistance patterns.

In the Creative Advertising program, the capstone involves developing a comprehensive integrated marketing campaign for a real client. One group partnered with a social enterprise focused on poverty alleviation. Through competitive research and stakeholder interviews, they identified a need to better promote new community initiatives launching in the upcoming year. The students then crafted positioning statements, brand guidelines, a fully-designed website, various collateral pieces, a three-month social media plan and measurement metrics. They also developed a 15-minute video highlighting the client’s work that was shared on their channels. A 25,000 character proposal outlined each element of the integrated campaign and how it would help achieve business and fundraising goals. The campaign launched after receiving the client’s approval and endorsement. It resulted in increased community support and partnerships.

These are just a few examples that illustrate how Humber College capstone projects provide real-world, applied learning experiences for students. Through meaningful industry-focused work, capstones allow students to gain valuable skills, contribute solutions and showcase their talent to potential employers. The multi-phase nature and extensive documentation required exceeds 15,000 characters of detail. This confirms capstones are an impactful part of applied programs at Humber College.

REPORTERS STABBING DEMO BACKFIRES ME

The ill-advised plan by several news outlets to infiltrate last night’s protest demonstration in downtown Neptune with undercover reporters posing as participants has become an unfolding debacle with serious consequences. What began as an attempt to capture exclusive footage and insights from within the demonstrators’ ranks has instead threaten the safety of journalists and damaged trust in the media.

As the evening began, thousands gathered peacefully in Constitution Park to march against recent legislation perceived as limiting civil rights and individual freedoms. Chanting and holding signs decrying government overreach, the demonstrators soon set off down Main Street towards the State Capitol building, as had been approved in their public rally permit. Meanwhile, a handful of reporters from competing local stations had other intentions, seeking to break important stories and gain an advantage by mingling covertly with the protest crowd.

Disguising their press badges and avoiding overt cameras or recorders, two reporters from Channel 5 News and one from the Daily Telegraph inserted themselves at the fringes of the march. Hoping to capture candid interviews and raw footage without subjects aware of their media affiliations, the journalists blended in, chanting along and blending into conversations to listen in discreetly. Their supervisors back at the stations believed an insiders’ view would bring compelling reports that evening. But almost immediately, things began to go wrong.

As the swaths of people streamed down the sidewalks, an outlier group of several dozen broke off, veering onto the street in an unsanctioned march. Shouting increasingly confrontational slogans and brandishing more antagonistic signage, this splinter faction took on a visibly more abrasive tone. Uncomfortable with the direction of this rogue segment, the undercover reporters attempted to ease away and rejoin the approved protest route. In the squeeze of bodies, one was inadvertently bumped into the splinter group.

Spotted speaking quietly into his wrist mic, this journalist was suddenly exposed by an alert participant and his covert identity unveiled. “You’re with the media!” accused the man, roughly confronting the revealed reporter. “We don’t want your lies!” Within moments, an angry mob had surrounded the vulnerable journalist, slapping the camera from his hands and tearing at his clothes amid shouts of “Fake news!” and worse expletives. One assailant produced a pocketknife and slashed at the reporter, narrowly missing his throat but leaving a long, bleeding gash across his shoulder.

By now, the assault had attracted scores of onlookers and escalated the confrontation dangerously. Without the ability to lawfully defend himself or publicly identify as press without exacerbating the violence, the injured reporter staggered away as best he could, disoriented and losing blood. His covert colleague from Channel 5 and the Daily Telegraph reporter, now also recognized, fled in opposed directions to avoid a similar mobbing. One managed to escape down a side alley, but the Telegraph journalist was pursued by several assailants, tackled to the ground, and repeatedly kicked in the ribs and kidneys before losing consciousness.

When the fracas was later broken up by police with non-lethal munitions, two injured journalists were hauled battered but living to the ER, where their colleagues quickly learned of the chaotic turn. News choppers soon showed aerial shots of the divided march, one faction still peacefully parading to the Capitol while the radical splinter group faced off angrily with riot cops. Reporters at the networks frantically tried to piece together how a supposedly routine assignment had ended so badly, endangering lives and sure to roil the public.

Both the networks and the newspapers immediately issued apologetic statements, clarifying their roles had been solely as observers and conveying regret for the injuries. They promised full cooperation with law enforcement’s ongoing investigation. This did little to quell a rising storm on social media, where images and clips of bloodied journalists inflamed round-the-clock criticism and conspiracy theories. Some commentators lambasted the media themselves as implicit in inciting unrest, while others accused shadowy interests of setting up the reporters to be attacked. In the heated fray, reasonable voices pleading for restraint and facts seemed lost.

Witnesses at the scene spread word of how the undercover masquerade violated trust and inflamed existing divides, escalating tensions for sensationalism with no care for consequences. Journalistic luminaries strongly condemned the gambit as unethically endangering lives for the sole pursuit of ratings and clicks. Even colleagues at the rival stations denounced the deception and lack of safeguards that risked deadly harm. Public opinion polls showed trust in traditional media nosediving to new lows as around-the-clock cable news panels analyzed it all.

In the aftermath, both news directors ‘resigned under pressure’, facing internal firings for greenlighting such a reckless, dangerous scheme without safe operational protocols. The injured journalists recovered but remained too traumatized to return immediately to duty. Lawsuits were soon filed alleging the networks were negligent in endangering staff. Both had carried heavy insurance but still braced for a maelstrom of costs. Criminal charges against identified assailants were likely but not expected to curb broader damages as America witnessed yet another institution lose its way.

The debacle offered a stark lesson. While exclusives and voyeuristic immersion sell viewers, trust, transparency and accountability to the governed community are journalism’s soul. Covert infiltration may get footage, but risks lives and legitimacy if safety is neglected for ratings’ sake. In future, all media must find honest, consensual means to observe and report rather than endanger any to advance parochial corporate aims. The public square is for all; media included best by serving truth, not hidden persuasion. If that simple wisdom had held, injuries may have been avoided and an uneasy nation spared further fracturing. Going forward, our eyes must remain open, but in daylight for all to see.

HOW ARE SELF DRIVING CARS BEING REGULATED AND WHAT POLICIES ARE IN PLACE TO ADDRESS LIABILITY AND SAFETY CONCERNS?

The regulation of self-driving cars is an evolving area as the technology rapidly advances. Currently there are no fully standardized federal regulations for self-driving cars in the United States, but several federal agencies are involved in developing guidelines and policies. The National Highway Traffic Safety Administration (NHTSA) has released voluntary guidance for manufacturers and is working to develop performance standards. They have also outlined a 5-level classification system for autonomous vehicle technology ranging from no automation to full automation.

At the state level, regulation differs across jurisdictions. Some states like California, Arizona, Michigan, and Florida have passed laws specifically related to the testing and operation of autonomous vehicles on public roads. Others are still determining how to address this new industry through legislation and policies. Most states are taking a phased regulatory approach based on NHTSA guidelines and are focused on monitoring how autonomous technology progresses before implementing comprehensive rules. Permit programs are also being established for companies to test self-driving vehicles in certain states.

One of the major challenges that regulators face is how to address liability when autonomous functions cause or are involved in a crash. Currently, it is unclear legally who or what would be responsible – the vehicle manufacturer, software maker, vehicle operator, or some combination. Some proposals seek to place initial liability on manufacturers/developers while the technology is new, while others argue liability should depend on each unique situation and blameworthiness. Regulators have not yet provided definitive answers, which creates uncertainty that could hamper development and adoption.

To address liability and safety concerns, manufacturers are strongly encouraged to implement design and testing processes that prioritize safety. They must show how autonomous systems are fail-safe and will transition control back to a human driver in an emergency. Black box data recorders and other oversight measures are also expected so crashes can be thoroughly investigated. Design standards may eventually specify mandatory driver monitoring, redundant technology backups, cybersecurity protections, and communication capabilities with other vehicles and infrastructure.

Beyond technical standards, policies aim to protect users, pedestrians and other drivers. Issues like who is considered the operator, and what their responsibilities are, need to be determined. Insurance guidelines are still being formed as risks are assessed – premiums may need to vary depending on vehicle automation levels and who is deemed at fault in different situations. Privacy protections for data collected during use must also be implemented.

Gradual approaches are preferred by most experts rather than imposing sweeping regulations too quickly before problems can be identified and addressed. Testing of early technologies under controlled conditions is encouraged before deploying to the wider public. Transparency and open communication between government, researchers and industry will help identify issues and produce the strongest policies. While full consensus on regulation has not emerged, continued discussions are helping outline best practices for this revolutionary transportation innovation to progress responsibly and maximize benefits to safety. State and federal policies aim to ensure appropriate oversight and mitigation of risks as self-driving car technology advances toward commercial availability.

Self-driving vehicle regulation and policies related to liability and safety are still an emerging framework without full standardization between jurisdictions. Through voluntary guidance, permits for testing, legislation in some states, and proposals addressing insurance, data and oversight, authorities are taking initial steps while further adoption unfolds. Future standards may establish clearer responsibilities, fail-safes and oversight, but regulators are still monitoring research and facing evolving technical challenges to produce comprehensive yet flexible solutions. Gradual, safe progress backed by transparency and collaboration form the central principles guiding this complex regulatory process for autonomous vehicles.

WHAT ARE SOME IMPORTANT SKILLS THAT STUDENTS CAN GAIN THROUGH CYBERSECURITY CAPSTONE PROJECTS?

Cybersecurity capstone projects provide students with an invaluable hands-on experience that allows them to gain a variety of important technical skills as well as soft skills that are highly valued by employers. Some of the key skills students can acquire through completing a cybersecurity capstone project include:

Problem Solving and Critical Thinking: Students are presented with an open-ended cybersecurity challenge or scenario in their capstone project that requires them to research the problem, analyze it from different perspectives, and propose creative solutions. This mimics real-world security issues companies face, training students to think on their feet and solve complex problems methodically. Students learn to break down large problems into more manageable tasks while considering various constraints and factors.

Technical Skills: Capstone projects offer opportunities for students to implement and strengthen technical skills they have learned throughout their cybersecurity degree programs. Students may have to perform vulnerability assessments, penetration testing, malware analysis, security code reviews, and security architecture design as part of their projects. This hands-on experience allows them to familiarize themselves with industry-standard tools and technologies like Snort, Kali Linux, Metasploit, Nmap, Wireshark, etc. and apply their conceptual knowledge in practical scenarios. Strong technical capabilities are crucial for cybersecurity roles.

Communication Skills: Students work on their capstone projects individually or in teams, which requires collaboration with peers as well as faculty members over extended periods. They must articulate technical details as well as project requirements, status updates, findings, and recommendations effectively through written reports and oral presentations. This improves students’ abilities to succinctly present complex technical information to both technical and non-technical audiences – a key skill in this field.

Time Management: Capstone projects are usually long-term endeavors that extend over multiple months. Students learn the importance of creating structured project plans, estimating and allocating tasks, staying organized, prioritizing according to deadlines, and adapting to changes or roadblocks – all crucial project management skills. Through their capstone projects, students get exposed to real-world constraints of limited time and resources.

Leadership Skills: For group capstone projects, students may take on leadership roles to delegate tasks, track progress, coordinate resources, motivate team members, and resolve conflicts. This fosters the development of supervisory and mentoring abilities valued by hiring managers. Successful project completion also boosts students’ self-confidence and decision-making expertise.

Research Skills: Conducting a capstone project necessitates extensive independent research into the technical topic, emerging trends, standards, and best practices. Students learn to find credible sources, analyze relevant literature, document findings systematically, and apply their research to solve the assigned problem. This prepares them for continuing research tasks in industry.

Soft Skills: Completing a substantial capstone project requires strong time management, collaboration, presentation, organization, and project management abilities. Students also develop perseverance, assertiveness, accountability, and stress management skills in overcoming unexpected challenges that come with open-ended problems. These soft skills are transferable to all career domains and aid career progression.

Cybersecurity capstone projects provide students a compelling authentic learning experience that enables them to convert their theoretical knowledge into tangible deliverables and outcomes. The various technical and soft skills acquired through this rigorous hands-on experience directly benefit students’ future career preparation and marketability in the cybersecurity industry. Capstone projects create industry-ready graduates who can seamlessly transition into workplace roles and directly contribute value. Their problem-solving mindset and demonstrated capabilities through their completed capstone work give them an edge over others in securing top cybersecurity jobs and internships.