osca-kampala-chapter / windows-musawo

A Windows optimization tool that automatically runs in the background of your device to routinely clean up Junk & improve performance, without you having to do it manually every single time.

Windows Musawo

Overview

A free solution that automatically runs in the background of your Windows Operating System Device to routinely clean up Junk files, save storage/space and improve performance, without you having to do it manually every time. Junk files are temporary files that were created so that your computer/device could perform a task, such as opening a document, viewing an image, or browsing the internet. These files are useful at the moment, but once they’ve served their purpose, they’re just junk, system junk files that clog up a device and cause poor performance.

This means that you don't necessarily have to spend time worrying about manually managing your windows device junk-related performance issues or installing resource hungry utilities that hog up all your system memory anymore. Instead, you’ll now focus that precious time on solving other more important problems because Windows Musawo helps you take care of that and it does all this quietly in the background without hogging up all your system resources like other alternatives out there, many of which are not even free on top of hogging your system resources. As professionals, while working with our Windows device, we want to spend our most valuable time working on more critical problems instead. Resultantly, making us more productive.

How can I contribute?

We welcome contributions! Many people all over the community have helped make this project better.

• Contributing explains what kinds of contributions we welcome
• Workflow Instructions explains how to build and test
• Windows Musawo v1.0.0 Roadmap explains the product direction for our next releases.

Filing issues

This repo should contain issues that are tied to Windows Musawo.

For issues, please file them here.

License

Windows Musawo is licensed under the MIT license.

windows-musawo's Issues

Create Product Backlog

Update project README

Add pointers to contribution guidelines

Technical Design Documentation

Document to explicitly talk about the software design and the reasons for the design choices that were made, purposely to onboard contributors faster easily. This document will be used for any new features that'll be added to the software, so should have support for collaborative comments from different contributors. A good choice of tool could be Google Docs.

Automatic and Manual disk cleanup

The goal is to have an optimization tool with full autonomy. The Optimization tool intends to work silently in the background of the user's device to routinely clean junk files that can slow down a user's device and internet browsers while doing all this without user's manual intervention. While achieving full autonomy of the optimization tool is our goal. We don't want to sacrifice performance and thereby prioritize performance and avoid hogging up a lot of system resources.

• Disk Cleanup should be able to run automatically in the background and perform disk clean up.
• Disk Cleanup should be able to run when user manually invokes it.

Design Product Logo

Design Brief

About Product: A free solution that automatically runs in the background of your Windows Operating System Device to routinely clean up Junk files, save storage/space and improve performance, without you having to do it manually every time. Junk files are temporary files that were created so that your computer/device could perform a task, such as opening a document, viewing an image, or browsing the internet. These files are useful at the moment, but once they’ve served their purpose, they’re just junk, system junk files that clog up a device and cause poor performance.

Inspiration:

• The Logo should be able to come across as Tech savvy, Futuristic, and Simple but still communicate the purpose of the product.
• It should be something that can easily be used as an icon. Ideas and suggestions by the Designer are highly welcome. Feel free to start a conversation in the comments section.
• Feel free to suggest theme colors not more than 3, the primary theme color should be one of those three.

Suggested Design Tool:

• Adobe illustrator or any other tool that can enable the designer produce vector graphics.

Expected Output:

• png file format for the Product Logo on a transparent background

Use Cases for the Logo Design:

• We intend to use Microsoft Store as our Distribution channel for the product (Windows Musawo). We are going to use this Logo there mostly and in our social media marketing campaigns. Be sure to look at the Microsoft Store and how apps display their logo to get an idea of how our Logo could fit in as well. For more clarity questions, start a discussion in the comments

Document Font styles used for the Design Assets

Document the Font styles used for all the Design Assets as we intend to have a common style used through out all our future designs. It'd be great to have all the design decisions well documented for future designers to follow.

For reference, these are the Design Assets that were recently added:

• PR: Update README
• PR: Windows Musawo Logo

Tasks:

• Add the name of the font style/typeface used in the designs to the design assets README file
• Similarly, add the color codes used in the designs to the design assets README file.

Update Contribution guidelines

Create Workflow guideline document (MD file) and add information and guidelines on how to build the project locally.

Prepare and add Contributing guidelines

A Markdown (MD) file to basically introduce new contributors to the guidelines to be followed while making their contribution to the repository

User custom settings

The user is our main focus and is the center of our motivation. A custom user experience with Windows Musawo is one of the main things. We are incorporating various custom user settings to enable the user customize the level of autonomy they might prefer the optimization tool to take on among others. Despite having the default settings for autonomous Disk clean up that our team recommends, We are giving the user the power to choose. This will enable them keep in control of their user experience.

• User should be able to choose how many background tasks they want active

Integrate project with Codacy

Fix broken links in Contributing guidelines docs

Design project GitHub cover image for social preview online

Design graphics for the project's repository. The first including the GitHub image for social preview online. Required dimensions (1280×640px for best display) pixels. You may suggest more ideas on this in comments. This task however highly depends on completion of #19

Create product Roadmap

Create a detailed Product Roadmap in Mark Down syntax that explicitly talks about the Product's direction and plans. Roadmap should be added to the docs folder. This is to enable stakeholders easily see the why and how of the product. The product Roadmap shall then be used to draft the entire Product Backlog.

configure CI/CD pipeline

Refactor: migrate codebase to 'WPF' from 'Worker Service'

There's a number of limitations that'll potentially hinder future extensibility of the software, among these include, the uncommon practice of developing User Interfaces(UI) for 'Worker Services'. WPF applications have more efficient ways of implementing UI. This is the main reason to refactor the project and migrate it to WPF instead of sticking with Worker Services that may limit extensibility.

System memory optimization

Similarly, the goal is to have full autonomy for memory optimization. If you use too much memory, or build up too much memory with a program running over time, performance is going to degrade. Using too much memory without releasing it to the heap (the virtual memory available as a resource to all programs) can result in running out of memory on the machine, requiring a reboot and potentially leading to many issues.

Ideally, in a well-written program, you use memory and then return it to the heap. That way there is always something on the heap to take from. Each program is allocated a piece of the heap. If a particular program (or programs) keep sucking up a disproportionate amount of the heap, program performance suffers until an eventual crash.

• Memory optimization should be able to happen autonomously in the background.
• Memory optimization should also be able to happen when manually invoked by the user