Is this tool still maintained?

[greatandli...@gmail.com]

I have been testing miro community and initially really liked what I saw, but I'm running up against a number of irritating bugs.  Based on the age of the last entry on this mailing list, I'm curious if there is a long term interest in supporting this tool?  Some of the bugs are minor, some are surprisingly fatal.  Here's a few off the top of my head (I scanned the bug list and didn't see any of these, at least that I could recognize):

1.) Link to FAQ from dashboard gives 404.
2.) Submit a video consistently gives an error but eventually is successful if you repeat it often enough on the same video.
3.) User feed from Youtube is unreliable among similar users (ie, some user videos feeds eventually pull in their videos, some never pull in their videos).
4.) Links to youtube user's website gives a 404 if there is a space between their first name and their last name of their user profile (which is very common).
5.) Widget tool doesn't reload the widget example if user changes options.  Reloading the page for the user just puts it back to the default settings.
6.) Widget embedded in a webpage references thumbnails from the domain that it is embedded in and not the miro community domain.  ie, localdomain.com/thumbs/adjust/localtv/...

I could go on, but I'm ready to give up as I feel like the tool is not usable as is and I can't spend any more time on it if the product is being EOLd.  Is there someone here that could comment on the future of this tool?

Thank you and best regards,
Richard

[Stephen Burrows]

Hi, Richard,

Thanks for reporting these bugs.

1) I just pushed a fix for this. Thanks!

4) This is a known issue and is fixed in a future version which we should be rolling out soon. (http://bugzilla.pculture.org/show_bug.cgi?id=19740)

The rest are not known issues, but they're not as easily fixable as the broken link; it would be great if you could put them into our bug tracker so that we can deal with them.

Miro Community is not being EOLd. Our development team is very small, and we do have to prioritize some bugs above others, as well as continuing to work on the future of the platform. If there is a particular bug that you'd like to see fixed, but we're not getting to it fast enough for you, we would certainly welcome any patches. And if you are ever unsure about whether we're still working on MC, you can always check our commit history on github.

Best,

Stephen

[Richard Griffith]

Thanks very much for your reply Stephen,

I had actually looked at what I thought was the github repo and found one that was very old (>3 months) and had a failing build status (maybe it was a fork?).  Not sure what I was looking at because this time I migrated to it and I see something very different.  Sorry about that, my mistake.

I will submit a bug for the remaining items on the list. 

Thanks again,
Richard

[Stephen Burrows]

Our develop branch (which is what github shows you by default) hadn't been touched since September. Our ongoing work has been on the release/1.9.1 branch, which I just merged into develop yesterday. So until yesterday, going to our repository would have initially given the impression that nothing had happened for three months. We can try to do a better job of merging regularly into develop, but I can also highly recommend the network view for getting a look at work on all the branches and forks.

Best,

Stephen

[Stephen Burrows]

Hi, Richard,

I believe that the issue you were seeing with embedded widgets may have been resolved, but since I wasn't ever able to reproduce it, I can't verify the fix. Could you check whether it now seems to be working for you?

See also: http://bugzilla.pculture.org/show_bug.cgi?id=19788

If the bug is still present, we may be able to get the solution into this release; but since we haven't been able to reproduce it, I'll need to delay resolving the bug to a later release if I don't hear back from you.

Best,

Stephen