Changes

Jump to: navigation, search

OSD & DPS909 Fall 2020 - Release 0.1

8,613 bytes added, 9 September
Created page with "=Release 0.1= ==Due Date== Friday September 25th. ==Overview== You are tasked with building a command-line tool for finding and reporting dead links (e.g., broken URLs) in..."
=Release 0.1=

==Due Date==

Friday September 25th.

==Overview==

You are tasked with building a command-line tool for finding and reporting dead links (e.g., broken URLs) in a set of files. Your tool can be written in any programming language.

This first release is designed to expose you to the common workflows and tools involved in contributing to open source projects on GitHub. In order to give every student a similar learning experience, we will all be working on the same project. NOTE: in subsequent releases, students will have more freedom to work on different projects.

==Learning Goals==

In addition to the actual code you will write, the ultimate goal of this first release is to help you gain experience in many aspects of open source development and contribution, specifically:

* gaining some experience in a programming langauge by building a real-world tool
* working with the basics of git, including branches, commits, etc.
* creating open source projects on GitHub
* filing, triaging, and working with Issues on GitHub
* writing about your own work via your Blog

==Requirements and Features: Implement All==

You must complete all of the following requirements and features:

* pick a name for your tool. Try not to pick a name that is already used by other projects.
* create a GitHub Repo for your project, see https://docs.github.com/en/enterprise/2.15/user/articles/create-a-repo
* choose an OSI Approved Open Source Licence for your project and include a LICENSE file in your rep, see https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/licensing-a-repository
* choose a programming language. You can use a language you know and love, or something new that you've never used before and want to learn.
* create a command-line tool in your chosen language. It must support all of the following:
** running the tool with no arguments should print a standard help/usage message showing how to run the tool, which command line arguments can be passed, etc.
** running the tool with a filename should cause the file to be processed. For example, <code>tool_name index.html</code> should check for broken links in the file named <code>index.html</code> in the current directory.
** when processing a file, the tool should look for all URLs using the <code>http://</code> and <code>https://</code> schemes. Every <code>http://</code> or <code>https://</code> URL in the given file should be processed.
** when processing a URL, your tool should attempt to do a network request of the given URL and check the resulting HTTP code. To begin with, an HTTP <code>200</code> result should be considerd "good" and a <code>400</code> or <code>404</code> considered "bad." Any other result should be "unknown"
** after a URL is processed, print it to out along with whether it was good, bad, or unknown. Each URL should get its own line.

==Optional Features: Pick 2==

In addition to the required features, you are asked to pick 2 of the following optional features to include in your submission:

* colourize your output. Good URLs should be printed in green, bad URLs in red, and unknown URLs in gray
** running the tool with the <code>v</code> or <code>version</code> argument should print the name of the tool and its version
* support both Windows and Unix style command line args (e.g., <code>--version</code> vs. <code>/v</code>)
* allow passing multiple file paths to your tool vs. a single path
* allow passing directory paths vs. file paths, and recursively process all children under that directory
* allow passing glob patterns (e.g., *.txt) to find files to process
* add support for non-text file formats, looking for URLs within binary data (e.g., UTF-8 strings embedded in binary)
* add support for more HTTP result codes. For example, redirects with <code>301</code>, <code>307</code>, <code>308</code> (i.e., follow the redirect to the new location)
* add support for timeouts, DNS resolution issues, or other server errors when accessing a bad URL. A bad domain, URL, or server shouldn't crash your tool.
* add a command line flag to allow checking for archived versions of URLs using the WayBackMachine, see https://archive.org/help/wayback_api.php
* add a command line flag to allow specifying a custom User Agent string when doing network requests.
* add a command line flag to allow checking whether <code>http://</code> URLs actually work using <code>https://</code>
* add support for parallelization, using multiple CPU cores so your program can do more than one thing at a time
* optimize your network code so that you only request headers vs. downloading full bodies (e.g., use <code>HEAD</code>)
* come up with your own idea. If you have an idea not listed above, talk to your professor and see if it's OK to implement that (it probably is).

==Getting Help==

For this assignment, everyone must do their own work, but that doesn't mean you can't talk to your colleagues. At every stage of your work, make sure you ask for help, share ideas, and get feedback from others in the class. Please use [https://seneca-open-source.slack.com Open Source Slack] to help with communication.

Try using community-based, open, collaborative development practices. This means talking with others about your work, and talking to them about theirs, asking for and giving help, and focusing on people as well as code. It also means doing this in public (e.g., on Slack) instead of in private. The goal is to support each other and for us to start building a communinity.

==Requirements==

You will be graded on the following. Please make sure you have addressed everything that makes sense below:

* One Issue filed for a bug fix
* One Issue filed for a new feature (on a separate repository from the bug fix)
* Professional and respectful interactions in your issue with the maintainer.
* Proper Pull Requests are completed for both Issues you filed
** An Issue should be filed before your create your Pull Request. The Issue must have a complete subject and description of the problem or change you believe needs to be made.
** The Pull Request should reference the Issue Number in its description (e.g., "Fixes #7: Add feature to do ...")
** Changes must be made on a new branch (e.g., if you are fixing Issue 123, use issue-123 as your branch name)
** Proper code to fix your Issue
** Code follows style of the original repository author
** Co-ordination with other student/community Pull Requests. Make sure you don't duplicate another fix or change that someone else has already done.
** All review comments have been addressed, and subsequent commits have been added to correct any problems. Ideally your Pull Request is merged.
* Reviews of Other Student's Pull Requests
** Compare the Pull Request to the related Issue it is trying to fix. Has everything been covered?
** Confirm that there are no other related Issues or Pull Requests that might conflict with this Pull Request
** Review code and other changes, making comments and suggestions about any improvements you can see, or other issues that need to be addressed
* Blog Post
** Discussion of the changes you made. What was your process? What did you learn? What would you do differently next time, or what worked and you would do again?
** Link to the Issues you filed, and discuss the bug/problem/addition you wanted to address.
** Link to the Pull Requests you created, and discuss the fix.
** Link to the Pull Requests you reviewed, and discuss what you did and found.
** Discussion of what you did to address your review comments.
** Evidence of Community Involvement. Could be Issues you worked in to help others, help you gave people on Slack, mentoring or other help you gave people in person. How did you engage with the community of developers working on Filer?
* Add Info to Table Below

==Submission==

When you have completed all the requirements above, please add your details to the table below.

{| class="wikitable"
! Name
! Blog Post (URL)
! GitHub Repo (URL)
! Language (e.g., Java)
|-
|Example Name
|https://example.com/blog/1
|https://github.com/example/tool-name
|JavaScript
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-

Navigation menu