-
-
Notifications
You must be signed in to change notification settings - Fork 598
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feedback from a reddit user #144
Comments
A lot of things woven inhere touch the monetization (marketing) or forming some revenue model. Not that I am opposing it, but being clear about future plans is perhaps the most important "marketing" for FOSS people. |
@LeBaux A short summary of how me and @ErikBjare discussions on monetization has been that we would love to develop ActivityWatch more if we got some revenue for it, but it's hard to do without sacrificing some of our core ideals for this projects (FOSS and privacy). For now we only do this in our spare time. Crowdfunding works but there's not enough money in that for us to sustain the project on, it only helps us pay the server costs. So our only plan for monetization and marketing is to improve ActivityWatch and being active on social media by notifying our users of the new features so more people use it and can help us get either more contributors or more money from crowdfunding. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Closing since the action points have been moved/referenced to more specific issues. |
Someone who wishes to remain anonymous reached out to me on reddit with some amazing feedback. All bolded text is mine.
And then a few days later once I replied to him:
The text was updated successfully, but these errors were encountered: