Difference between revisions of "DPS909/OSD600 Fall 2017 Release 0.2"
(→4. Submission) |
(→4. Submission) |
||
| Line 230: | Line 230: | ||
|- | |- | ||
| 26 | | 26 | ||
| − | | | + | | HarshKumar Patel |
| − | | | + | | https://github.com/devtools-html/debugger.html/pull/5051 |
| | | | ||
|- | |- | ||
Revision as of 00:24, 8 January 2018
0.2 Release
Your second, and final release is due Friday Jan 5th.
You are asked to find and fix a bug or bugs in any open source project on GitHub. Unlike your first release, you can work on any open source project, not just Mozilla. Below you will find a suggested set of projects and tools to consider.
NOTE: this release needs to be larger than your first, which could mean working on a more complicated bug, or doing more bugs (e.g., more smaller bugs). You must extend yourself from what you did in your first release and demonstrate some growth. Having said that, don't extend yourself so far that you fail to complete the work. Spend time assessing your skill and goals, and work to find bug(s) that match.
1. Possible Projects
You can work on any open source project for this release. Not all projects are good choices, however, and you are encouraged to discuss your choice with your professor.
One way to find projects is to look at the following:
- 24 Pull Requests - similar to the Hacktoberfest bugs, with lots of project/bug ideas for you to contribute to in December.
- GitHub's Trending projects - you can see which projects are trending on GitHub, and maybe find one that would be interesting to you. Try limiting the language to one you want to work in (e.g., JavaScript).
- GitHub Explore - list of many projects categorized into topics. Maybe you'll find one that you like there.
As was previously the case, you can also work on a Mozilla project. The most successful projects for our students so far have been:
- Thimble code editor/learning tool (node.js, HTML5) "Good First Bug"
- Firefox Activity Stream (JS, CSS) dev docs "Good first bug"
- Firefox JavaScript Debugger (React, JS) bugs, more bugs.
- Pontoon localization tool (Python, JS, HTML5) unedited bug list
- Neon (Rust bindings for node.js) see recent post about ways to get involved
- Rust (programming language, sites, and project) contribute docs, "easy" bugs, Crates.io package manager "easy" bugs, other ideas for contributing to Rust and tooling
The other Mozilla project areas are also still available:
- Addons Server (Python/Django Server and API) "good first bug"
- A-Frame WebVR framework "help wanted, easy"
- Firefox Dev Tools (JavaScript, CSS, React, etc) "easy" bugs.
- Mozilla Network site (Python web app) "help wanted"
- Network Pulse API (Python REST API server) "help wanted"
- Testpilot experimental feature tool (React, HTML5, JS) "good first bug"
- PDF.js (JavaScript PDF viewer used in Firefox) "good-beginner-bug"
- Firefox Mobile iOS (Objective-C, Swift, iOS) "good first bugs"
- Firefox Mobile Android (Java, C++, JS) "good first bugs"
- Balrog Update Service (Python) https://github.com/mozilla/balrog - some potential bugs: 1396859, 1138418, 1374638, 1386400
- Build/Automation Tool: Linting (Python, JS) Possible bugs, talk to your professor if interested
- rr (C++ debugging tool for Linux) "goodfirstbug", good podcast about what rr is here.
2. Project Scope
This release needs to be "more" than your first, but defining what "more" is can be hard. What I want to see is that you've consciously taken on a larger and/or more complex piece of work. Where your first release was about learning git, GitHub, how to contribute to a new project, and the like, this release should be a more intermediate task. Perhaps you focused on a documentation issue in your first release, and this one will be about writing code. Or maybe you worked on a fix, and this time you want to try and take on adding a feature. Or maybe you worked on one but, and this time you're going to work on two.
Whatever you do, I want to show some growth during this release. Stretch yourself to do "more" than you did last time, even if that's only a small step--making progress requires that you go a bit further each time.
If you think you're finished after working on this for a few days, it's a good sign that you probably need to pick more bugs to add to your release. This should take you some time, and you have 1 month to do it.
3. FAQ
- Can I work on some random open source project from GitHub? Yes. But make sure you are picking a project that is active (is anyone still working on it?), wants contributions (not all do), is open to new people, etc. Don't work on something that won't be supportive.
- Can I start my own open source project and work on that? No. This project is about contributing to existing, large, open source projects, which involves learning many skills, tools, and processes that will be valuable to you in your career as a developer.
- Can I work with a partner, or in a group? No. You can collaborate with others in the course (or from Mozilla) on your bug(s), but you need to "own" your own bug, and do the work yourself. Having people give you advice or help, and doing the same for others, is fine. However, "help" doesn't mean one person does it all.
- Can you help me, I'm totally lost, I have no idea what to work on. I'd suggest you work on Thimble https://github.com/mozilla/thimble.mozilla.org.
- Can I work on something I don't know (e.g., Rust, Firefox, ...)? Yes. As long as you're willing to push yourself to learn what you need to know, you can do it. You have 4 weeks to accomplish this, which is lots of time to research, learn, fail, and succeed.
- What if I write a fix and the project rejects it, will I still get marks? Yes. You will be marked on the process, how you work, and what you create. Projects will almost certainly reject your first attempt in code review, and offer comments on what to fix. It might take a few rounds of review/re-submission for you to get your bug(s) finished. That's normal.
- When should I start working on my bug? Now. Fixing a bug in a large code base you don't know takes lots of time. You have lots of time (1 month), don't waste it. Work on your bug every few days for a short amount of time; don't leave it until a few days before it's due.
- Where can I go for help? You can talk to your classmates on Slack. You can also reach out to the developers in their communication channels (Slack, gitter, mailing list, irc, etc). Each project/tool at Mozilla has its own communication channels, and you are encouraged to join them. Be bold, introduce yourself, and get started working in community.
- What do I do if someone else is already working on a bug? You need to communicate your intent to work on something. Leave a comment in a bug, and let people know you are interested in working on it. If someone else is working on it, but hasn't made progress in a long time, you can leave a polite question asking if it's OK for you to take it over. If another student also wants to work on a bug, come see your professor for help finding another suitable issue.
- How do I submit my work? You need to have a Pull Request or Attachment Patch (i.e., completed code) for your bug submitted to the correct bug tracker. You also need a blog post discussing your process, what you learned, the fix, etc. See below.
4. Submission
You need to do the following in order to complete this release
- Find and fix your bug(s).
- Follow-up on any review comments you receive in pull requests, an try to get your work merged. This may not be possible in the time we have, but make sure you aren't the reason it doesn't happen.
- Blog about your work as you do it, and upon completion. You should document how you do what you do, what you did, what you learned, etc. Make this a record of your abilities that will help show people what you're capable of doing.
- Add any bugs you work on to the DPS909 & OSD600 Fall 2017 Bug List
