Replies: 11 comments 17 replies
-
|
I would start by showing signs of life and announcing early alpha versions as alot of things that we don't use regularly but that others have used in the past, might be broken. Alot of users might also have moved on to other task managers. Possibly put a link from the taskcoach.org to the github page. For example, the twitter/x feed is dead, even though some people asked for news on the project. There are still 488 twitter followers of the taskcoach project. It doesn't really matter if we like x/github/MS, etc or not, if you want to reach users, using these platforms might be necessary. If you want to also have a non-commercial platform opensource presence, we could have a mastodon/fediverse account. But at the same time, multiple platforms, plus the website, etc. makes more work and might confuse users. Do you have access to the taskcoach.org emails? The twitter account? etc? |
Beta Was this translation helpful? Give feedback.
-
|
I went through all the old SourceForge tickets and processed the Linux ones. As any action on a ticket might email people involved, I figured that closing the Linux ones with a reference to this GitHub repo would be appropriate. I moved some that I tested as still relevant into the issues here. Most I closed with an appropriate message. I didn't even look at the ones marked MacOS or Windows. Some of those might not be OS-specific, but acting on them could get attention from MacOS or Windows users. So, I figure we can wait until there's a MacOS or Windows package worth testing. We have enough to do anyway, not looking for tasks to fill time. There are other feature-requests and things to get into, but I think this was enough of a step for now |
Beta Was this translation helpful? Give feedback.
-
|
I started transferring old UserVoice requests. I am selecting relatively trivial ones first. I'm deleting from the old list anything totally outdated or worth simply rejecting. I am waiting for later to add any significant items that would require more work and design discussion and so on. |
Beta Was this translation helpful? Give feedback.
-
|
Windows version is now building and running. See v2.0.1.1 - Windows Build Updates and Fixes However, in doing this, I found that the whole date/time system needs to be refactored to have the code run seamlessly on windows, linux, macOS, etc. The current workaround should be fine for now, but the work needed to be done is noted in: TODO - Datetime and Timezone Refactoring |
Beta Was this translation helpful? Give feedback.
-
|
@realcarbonneau superb! (For Task Coach, and practically for a bunch of Windows Task Coach users; though I don't like that Windows is what it is in the world) I have not followed it, but isn't Windows today something like Apple wherein Microsoft makes it weird for people to just get software from wherever? Like is their some signing or override of security settings or something else that we need to document for users to do these days aside from just install a build downloaded from GitHub? I will go ahead and transfer over issues from Windows users (of those that might still be relevant) and otherwise announce this for people to test once you say that things are worth more people testing and we have documented whatever people need to know about installing and running the updated software |
Beta Was this translation helpful? Give feedback.
-
|
@realcarbonneau unfortunately, at https://github.com/taskcoach/taskcoach/releases (not the link to any specific release), there are now so many assets that I had to click "Show all 15 assets" to reveal the Ubuntu .deb packages |
Beta Was this translation helpful? Give feedback.
-
|
On the topic of issue organization, we should have a label for each of the main functionalities of taskcoach, so it's easier to get an overview of all issues/requests for a features. Eg. I added categories and manual ordering. As the need comes up, feel free to add Effort, Notes, Calendar, Sync, Email, etcs |
Beta Was this translation helpful? Give feedback.
-
|
Because we have alot of issues now, please put the label "Active User" on issues that you feel current users are being blocked by or inconvenienced by. I will prioritize these first. @wolftune |
Beta Was this translation helpful? Give feedback.
-
|
macOS build |
Beta Was this translation helpful? Give feedback.
-
|
FYI, there are as of this writing 662 requests from the UserVoice export that I have not opened issues for. I am bringing up some when the topic arises for other reasons. I went through and opened issues for the most obvious and important ones that seem likely in-scope. Many are totally out of scope, some are confused, some are nice but low-priority, some are incompatible. I don't have the vote-count or the follow-up comments unfortunately. In past years when we did use UserVoice, I regularly closed and consolidated issues to reduce the bulk… My plan is to eventually get through all of them, just ignoring ones that are not worth mentioning, opening issues as appropriate otherwise. And when something marked "moved from UV" is completed I'll specifically check whether we have an email for the requester to tell them it is fixed (we don't have emails for all of them). And regardless, when we get to an even better point with the program overall and hopefully an updated main website and such, I could eventually just do one bulk announcement to every email we have from the UserVoice request set. Similarly, I can email everyone who opened a bug or support in SourceForge even if they were closed before recently (I have only done actions on tickets that were open). That is my thinking about future one-time announcement to help more people realize that the update is available. |
Beta Was this translation helpful? Give feedback.
-
|
One bit of great news: https://sourceforge.net/projects/taskcoach/ is now successfully loading the GitHub releases and anyone downloading from SourceForge is actually getting the updated GitHub releases. There's also a link saying that the project moved to GitHub. Anyone following the SourceForge project ought to have been notified, though I'm not sure that happened as I haven't myself seen any such notifications… |
Beta Was this translation helpful? Give feedback.



Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
For @realcarbonneau especially but anyone can discuss: how soon does it make sense to start going through all the old SourceForge tickets and telling people that development is continuing here, that people can try the new versions and report issues here, and so on?
My thinking is finish going through the old issues, inviting the transition, opening new GitHub issues for outstanding specific bugs and requests, and close the SourceForge issues. Then, after that, we can move on to getting Jerome to update the website…
Beta Was this translation helpful? Give feedback.
All reactions