[GD5] Android: no music

[Wend1go]

Android games currently play no music at all:
http://compilgames.net/forum/viewtopic.php?f=19&t=10461
(there is a workaround playing the music file as a sound but loading takes a couple of seconds)

@4ian : I noticed you aren't around in the forum that often recently. Is it ok if I go on adding the issues from the forum to Github?

[4ian]

@4ian : I noticed you aren't around in the forum that often recently. Is it ok if I go on adding the issues from the forum to Github?

That's a good question :)
My main issue is that there is a lot of things going on on the forum, and I have to concentre only on the most important subjects otherwise I'm going to use all my time without being able to actually work on GDevelop and fix/improve things.
To achieve this, I'm more looking at GitHub issues than the forum as issues should be properly formatted (high signal/low noise issue). To help me, you can open issues but only if:

• It's something that is really urgent. (like lots of games broken or build services down like a few days ago - thanks for reporting it btw).
• You verified the bug and have a proper game for reproducing the issue.
• You follow the template that I made for the issues.
• You've included any information about error message or workaround.

Basically, when you open an issue, tell to yourself "I'm going to have 4ian to look at this instead of working on GDevelop next feature or fixing a bug - what should I do so that he have everything to fix it asap?". Please please please follow the template that I've created about bug report, everything is in it! :)

In the case of this issue, if I want to look at the issue, I'm going to spend maybe ~30 minutes trying to reproduce it. This can be down to 1 minute if you give me a link to the game + all the step by step way to trigger the issue. 😄

If we don't do this, the risk is that we will have a huge mess of issues both on the forum and here - which is not good at all.
So let's try to keep this place as high quality as possible :)
=> Hope everything make sense. Let me know if you have suggestions or another system in mind. I'm still trying to see what his the most efficient approach for handling this and keeping a good feature/bug fix/community handling ratio.

Would you be able to quickly get a game with the sound problem there? 😃

[Wend1go]

Sounds like a good idea. I'll try to stick to the template next time.
I sent you a PM with a link to my Sakawochi game as an example on the forum.

[ddabrahim]

Let me know if you have suggestions or another system in mind

The problem is that most users are on the forum and since the majority do not code, they don't use GitHub and they have also no clue what is going on. The problem they are experience either a bug or only a mistake but can be sure only if someone review their problem who knows GD in and out but there is no one to review the problems from a technical point of view as you would prefer. And there are not only bugs, once in a while most successful products do need to listen to what the users need which may be does not solve any problem, but only improve quality of life, all products and services need quality of life improvements and frankly you totally ignore this kind of topics. I understand why but it doesn't change the fact you do.

For example, I did suggest to you a system years ago, for reporting problems and requesting features which was this:

A system similar to trello, if trello or something else could be used for this, great..
Anyone can open a ticket, describe the problem or idea they have, may even recommend solutions and people could vote and also flag this tickets as important, useful, confirmed..etc. Once in a while you could just go and look through all the tickets and thanks to the votes and flags and the visual representation you could immediately find the most important ones. You could also add your own flags or add them to groups and categories as an indication of what your decision has been and as a reminder what would be your plan without need to go to the forum and need to read through all the trash and start conversion with people know nothing about how GD works inside but feedback from developers still important. You read a problem and take note then nothing for months, no fix, no reply makes *users disappointed.

This system would be a mix of road map/bug report/feature request all in one board nicely organized

It was my suggestion/request years ago and it would be still my suggestion for the present.

In case you doesn't like this, an other solution could be to allow people submit their project directly from GD for bug report, describe what the problem is and how to reproduce it. But it is exactly what you trying to avoid as you would need to review every single project submitted but at least there would be a project to open and run and decide in a minute if it a bug or not and then decide if it an important one or not.

Either way, you definitely should dedicated few days in a month to review bug reports and feature requests submitted by the users either on the forum or on a public board like trello or through allow people to submit their project directly from GD and leave GitHub to the people who are playing with the source. An important fact to consider, unlike some other projects here at GitHub GDevelop is targeting people who do not code, and so GitHub does not suit them and it does not suite you but there is no one looking after them on the forum either.

[4ian]

I do understand that there is a gap between the forum and GitHub and that this is making it harder to suggest idea for most people and for me to see the global tendency and the main pain points to address.

We need a system where each individual can contribute but where I can still see the big picture. Otherwise I'm going to get flooded by everything and won't make any progress on GD. (For example, if there are 15 messages a day, and each message is taking me 2 minutes to read/assess, it's 30minutes less for GD everyday, so 3.5 hours each week - which is the equivalent of one small bug fix or small feature).

Trello is nice but people can't write themselves cards, only comments. That may be indeed a good thing as we can make a card about idea, and whenever an idea is asked and not yet present I can create a card for it. People can vote so that we can see the tendencies/global pain points.

It would be like the roadmap (https://trello.com/b/qf0lM7k8/gdevelop-roadmap), probably I can reuse it, but everything would be there - and we can comment on the cards instead of using GitHub for enhancements.

Also maybe moderators can help me because if lots of people are commenting and I need to go through to all of it, I will still losing hours doing so each week.
Remember that for example today I spent 1 hour merging Pull Requests/fixing small things, there is a bug reported by @Lizard-13 that I've not answered yet, an example that was given to me that I need to rework and add to GD, two games to add to the website showcase and I won't have time for any of these.
Having a consolidated way of adressing enhancements/feature requests is then essential.

So the plan is:

• Update the Trello roadmap to add a lot more of columns to triage feature requests.
  • Close all issues on GitHub related to enhancements and make card for them on Trello - enabling people to vote and comment. Will keep a link to the discussion on GitHub though.
  • Each week/day I (or some other people having access to the trello board - typically contributors (or people asking me to do it)) update the trello to add missing cards. Existing ideas should not be duplicated - otherwise we lose clarity.
• On GitHub, only bugs with clear reports will be kept on issues
  • This is so that we have a clear view of what is to be fixed (which is as important, if not more, than feature requests).
• Forum and discord will stay privileged way to discuss about GDevelop between users - but for asking features people can either go on the trello roadmap (for not developers) or on GitHub (for reporting bugs or opening pull requests).

What do you think? If you're ok I'll go ahead and make this tomorrow.
It's not perfect as bug reporting is still a bit hard - but this entry barrier should help having the issue on GitHub being reported with high quality (i.e: an example game linked to the bug reported) (bugs are super expensive to investigate, at least 10minutes to verify it, then between 5 minutes to a few hours to see if it's really broken and if there is something to fix without breaking the whole engine).

[4ian]

Development discussion will be kept on the Pull requests (or on the trello card if nothing was started yet) or issues - so all technical discussions will still be on GitHub. Trello will be an interface for all the non developers users to ask for thing and see what is done.

[4ian]

@blurymind @ddabrahim @Wend1go @Lizard-13 @Bouh Let me know if you think having all the enhancements discussed on Trello is a good idea :) Might bring more visibility which is a good thing at the end.

[Lizard-13]

Sounds fine to me, and I can help with the trello cards at least once a day :)

[Wend1go]

I haven't really used Trello until now, if you think it is suitable for the task then go for it.

[blurymind]

I trust your judgement :)

…

On Tue, 17 Jul 2018 19:25 Wend1go, ***@***.***> wrote: I haven't really used Trello until now, if you think it is suitable for the task then go for it. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#556 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGMbVYuHJLMryuI2lfwAkdFl-3o0RFO-ks5uHg_lgaJpZM4VRcJv> .

[Bouh]

I already use trello to see the progress of some features.
In the category "Enhancements ideas 💡" I already use the thumb as a way to say that it must be a priority or then say this feature is a great idea!

I deal with the Discord being the administrator on it.
I read each messages and I can explain to people the good steps of request, bug and questions.

[4ian]

@Bouh I've added you as a member of the trello board :)
Blurymind and Lizard-13 are already members.

The idea is to check from time to time votes and re-order cards if needed (let's put the most voted cards at the top).
If a suggestion is coming back a lot, we can create a card provided that it's properly explained what the feature/improvement is.
I'll add more in the next days!