What types of changes does your PR introduce? Put an x in all boxes that apply
[x] New addition to list
[ ] Fixing bug in existing item in list
[ ] Removing item from list
[ ] Changing structure (organization) of list
Proposed Changes
MakeItHome is a UI extension for macOS. It’s been on the App Store for a year and a half, but it’s been open source for a short time. It's a pretty complex app to develop, and it's very useful and often essential if you used to use it.
It need user base to continuing its development, mainly for feedbacks and motivations. Due to the lack of feedback, for the moment there are still common issues, that I'm fixing constantly.
This adding to the list may be a lot important for the existence of the project, seen that due to the lack of trust of users and disillusion about the market, is pretty hard to obtain more than 1 download daily, even if it's a free app.
I really appreciate your support and I hope this pull request doesn't seems a request from "a spammer".
The open source "community" it's in development. I also need feedbacks from developers to know about what writing a code documentation.
PR Checklist
Put an x in the boxes once you've completed each step. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.
[x] I have read the CONTRIBUTING guide
[x] I have explained why this PR is important
[ ] I have added necessary documentation (if appropriate)
Further Comments
I hope that this list can contribute to create interest to an effectively innovative feature too much ignored.
Feel free to edit the description if you feel it appropriate.
Types of Changes
What types of changes does your PR introduce? Put an x in all boxes that apply
Proposed Changes
MakeItHome is a UI extension for macOS. It’s been on the App Store for a year and a half, but it’s been open source for a short time. It's a pretty complex app to develop, and it's very useful and often essential if you used to use it.
It need user base to continuing its development, mainly for feedbacks and motivations. Due to the lack of feedback, for the moment there are still common issues, that I'm fixing constantly.
This adding to the list may be a lot important for the existence of the project, seen that due to the lack of trust of users and disillusion about the market, is pretty hard to obtain more than 1 download daily, even if it's a free app.
I really appreciate your support and I hope this pull request doesn't seems a request from "a spammer".
The open source "community" it's in development. I also need feedbacks from developers to know about what writing a code documentation.
PR Checklist
Put an x in the boxes once you've completed each step. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.
Further Comments
I hope that this list can contribute to create interest to an effectively innovative feature too much ignored. Feel free to edit the description if you feel it appropriate.
Thank you.