List view
No additional details were added for this assignment.
Overdue by 10 month(s)•Due by March 8, 2025•4/5 issues closedSubmit the PPT of your project that you present in the final class.
Overdue by 8 month(s)•Due by May 3, 2025•0/1 issues closedEnter Web URL
Overdue by 8 month(s)•Due by May 3, 2025•0/1 issues closedThis is a detailed report mentioning all the things in POC in much detail plus the packages you have used, and your tech-stack. This is where you can talk about your market research, how you learned about the problems you are solving, why your solution has the potential to solve the existing problems, and how the project could be taken further. There is no page limit for this one.
Overdue by 8 month(s)•Due by May 3, 2025•0/1 issues closedA small 1-2 page white paper (feel free to look up on Google the templates. Do not hesitate to be creative). The POC should consist of what problem you are solving, what challenges you overcame, where your solution may be applied and how it could create an impact. You are welcome to put a figure here. You could include additional pages for references if any.
Overdue by 8 month(s)•Due by May 3, 2025•0/1 issues closedNo additional details were added for this assignment.
Overdue by 9 month(s)•Due by April 2, 2025•0/1 issues closedNo additional details were added for this assignment.
Overdue by 10 month(s)•Due by March 22, 2025•0/1 issues closedPrepare and submit presentation of tools or technology you will be using, dataset along with sources. Setting up environments. Literature review Technology or tool selection Dataset selection Initial project design
Overdue by 11 month(s)•Due by February 18, 2025•3/3 issues closedComplete and submit ASSIGNMENT_NAME
No due dateComplete and submit the capstone project proposal
Overdue by 11 month(s)•Due by February 7, 2025•2/2 issues closed- Objective: To synchronize the local repository with the remote (upstream) repository, make necessary changes based on feedback received, and update the documentation in the repository after a thorough review of the contribution documentation. 1. Review the contribution documentation in the repository to understand the required guidelines and best practices. 2. Fetch changes from the upstream repository to your local repository. 3. Pull changes from the upstream's master branch to sync your local repository with the central repository. 4. Make edits, save, add, and commit changes in your local repository based on the feedback received. 5. Update the documentation in the repository to reflect the changes made and ensure adherence to the contribution guidelines. 6. Push the changes from your local repository to your forked repository on GitHub. - Completion Criteria: The local repository should be updated with changes from the upstream repository, necessary edits should be made, and the documentation in the repository should be updated to reflect the changes and adhere to the contribution guidelines.
No due date•1/1 issues closed- Objective: To submit a pull request using best practices and request review of the changes made in the forked repository. - Tasks: Create a pull request from the newly created branch to the original repository. 1. Provide a clear and descriptive title for the pull request. 2. Write a detailed description of the changes made and the purpose of the pull request. 3. Request a review from relevant project maintainers or team members. - Completion Criteria: The pull request should be created, with all necessary details provided, and a review requested from project maintainers
No due date•1/1 issues closed- Objective: To establish a fork of the original repository and create a properly named branch for the intended contributing objective. - Tasks: 1. Fork the original repository to your GitHub account. 2. Clone the forked repository to your local machine. 3. Create a new branch with a name that reflects the intended contribution objective (e.g., feature/add-new-feature, bugfix/update-readme). 4. Make and stage changes in the new branch. 5. Commit the changes to the branch. 7. Push the branch to your forked repository on GitHub. - Completion Criteria: The forked repository should have a new branch with the intended changes pushed to it."
No due date•1/1 issues closed