I see there hasn’t yet been a great response so far to the relaunched BugMash Mondays, although Steffen cleared a few in the first week. Is there anything I can do to help generate more response? Are the DHQ posts OK, or could I improve them? Here’s the last post, so you can read it to see what you think: https://www.joindiaspora.com/posts/2734912
Look forward to your comments on this week’s list, and on what else I could do to encourage more people to help.
#4069 would be fine, though I’d keep the list at 5 per week. #3529 is not really a newcomer thing but we really could use the help of a dev experienced with the RTL stuff to make the experience on Diaspora better, so it might be worth including it, simply to call out for that.
The reviews of the last week were awesome and I think that this could motivate other devs when they see that something is going on. I also think that we should keep the post as short as possible. How about something like this: http://piratepad.net/7ypOjOND7C
@goob you should click on the button at the bottom right of the input text in loomio to activate markdown syntax
Well, maybe the weekly post is not the best approach because too repetitive and not enough specific. What about some really specific posts like “Looking for a RTL specialist
You have knowledge about language in right to left and want to help improve diaspora? Please join this discussion (https://github.com/diaspora/diaspora/issues/3529)!”
@steffenvanbergerem - that’s fantastically helpful. Thanks. I had forgotten about the weekly reviews. Not being a developer, I hadn’t paid too much attention to bugmash posts in the past other than just to see that something was happening. I’ve added your suggestions.
@jonnehass - thanks also for your input.
@flaburgan - thanks for the markdown tip. I had forgotten about that button. You may be right about specific posts, and that was something I had also thought would work well, but it’s something I would not be able to do. I’m struggling simply to compile a short list of bugs each week, as I’m already out of my depth technically. So if the devs would prefer specific posts like that, someone else would have to write the posts. I could then edit them and post from DHQ account, but I wouldn’t be able to compile or write the posts.
I’ll post a list of bugs today anyway, and you can decide among yourselves what is going to be most helpful for you as developers in the coming weeks. I’ll help in any way I can, although with those limitations I’ve just mentioned.
Uhm, for the SCSS issue somebody said he’ll have a look into it, so I’d postpone that a week. Also not sure I like the term “admin tasks”. For the email one (4182) we got an open PR.
You’re right, ‘admin tasks’ is not an elegant way of putting it. I was thinking of routine maintenance/updating rather than bug fixes. And if ‘straighforward’ is misleading, I’ll change it to ‘an important ongoing task’. And I’ll remove the SCSS task and 4182. It was an error to include that last one, and thanks for pointing it out.
Right, I think we’re all set unless anyone else has an issue to suggest?
I also can’t see any other pull requests which look in a state of completion, to be included in the ‘last week review’.
So this week’s proposed list is simply last week’s, minus the one bug which was fixed.
Here it is. If you know of any other issues you’d like to included, or of any pull requests you’d like included in last week’s review, please give the issue number here. And if you have any other ideas for me.
