Bugmash Mondays - bug suggestions

As we’re trying to get Bugmash Mondays up and running again, it would be excellent to have a place where developers can suggest bugs suitable for inclusion each week. This seems as good a place as any.

Ideally, we’ll give eight bugs to the community each week (that was the stated goal when Bugmash Mondays were started) - some quick fixes and some suitable for newcomers, others can be a bit more complex. If we can’t find eight suitable, I’ll post whatever we have.

I’ll bump this thread each Saturday, and then if bugs can be suggested here over Saturday and Sunday, I’ll post from the Diaspora HQ account on the Monday.

Hope this isn’t an inappropriate place for this thread - it seems the best place.

Note: This discussion was imported from Loomio. Click here to view the original discussion.

For 17 June 2013:

I see Stefan did a great job fixing a few of the bugs from last week. Ones which seem to be left over are:

Are each of these suitable for bugmash? And what others can we add? I can’t see any that look suitable to me, would welcome suggestions.

I think it’s perfectly reasonable to roll unclaimed bugs into the next BugMash. That way, people will still know which problems are still happening.

It’s more a case of ‘are these three remaining bugs suitable for bagmash Monday?’ - I had to just pick a few last week, a bit of a guess, and include the ones that no one said ‘definitely not that one!’, so I thought it as well to check now.

I’m posting here so I can properly include @jonnehass and @florianstaudacher , among others, in the discussion.

@goob I think you should look at new comer tasks even if they are not bugs :wink:

@flaburgan I have done, but the problem is I do not have the technical knowledge to know if it is suitable for inclusion - and some of them look as though they have been put on hold for one reason or another (going on the discussion), so it would really help me to have suggestions from people who actually know the state of the code.

OK, @flaburgan @seantilleycommunit @jonnehass @florianstaudacher @jasonrobinson and anyone else:

Here are my suggestions. Are any of these not suitable?

Thanks in advance.

The embedded media one might be a little bit tricky, but if someone has the chops to do it, by all means go ahead!

These are all good bugs, though. :slight_smile:

#4143 is a lot of work, while it can be done by a newcomer it’s probably nothing we should invite people to do as that could give a negative experience.

I think https://github.com/diaspora/diaspora/issues/4077 could be an easy and quick one for newcomers

Thanks, @steffenvanbergerem - I didn’t include that as I wasn’t sure whether the commits from Movilla on that thread had solved the issue. If it’s still live, I’ll include it.

Hmm you’re right. The commits from Movilla would solve the issue but there was no status update on that PR for 2 months.

Thanks. I’ll leave it off in that case, just to be on the safe side. We’ve got seven bugs now, and I’ll say ‘if you want to tackle another bug, post on the thread for that bug first to discuss it with the devs’.

@goob your link to http://wiki.diaspora-project.org/wiki/How_to_work_on_bugs in your post is not correct: the redirection to the new domain works but the page does not exist.

Well the page does exist, the redirect should just go from http://wiki.diaspora-project.org/wiki/ to http://wiki.diasporafoundation.org/

Fixed! :slight_smile:

@seantilleycommunit the link still not goes to a page :stuck_out_tongue:

Oh, thanks, Fla. That was cut and pasted from last week, before Sean had transferred the wiki. Sorted now (and it produces a valid page when I click on it, or your link below to the old domain also works for me).

Thanks everyone for your input this week. Hope you get some useful contributions from this, and possibly one or two new developers. Until next weekend!

@flaburgan, the link you’ve provided seems to redirect just fine for me: http://wiki.diaspora-project.org/wiki/How_to_work_on_bugs

@seantilleycommunit @flaburgan keep in mind that browsers cache redirects.