Nice to Have

[Sonwon1]

There are currently 127 Issues labeled 'Nice to Have'. Many of these are over a year old. What are the plans to address the issues labeled 'Nice to Have'?

[scaidermern]

There are at least two options:

• Find a magician to solve them.
• Fix them one after another whenever time permits.

[Sonwon1]

I know of at least one that doesn't need a magician to solve and I can even create the algorithm for it! The code needed is already in the base code, only thing missing is the algorithm and a little code to apply it.

They cannot all take a magician to solve what is the plan for those?

[scaidermern]

I know of at least one that doesn't need a magician to solve and I can even create the algorithm for it! The code needed is already in the base code, only thing missing is the algorithm and a little code to apply it.

Maybe try to create a pull request then.

[Sonwon1]

I know of at least one that doesn't need a magician to solve and I can even create the algorithm for it! The code needed is already in the base code, only thing missing is the algorithm and a little code to apply it.

Maybe try to create a pull request then.

Easy for you to say, my coding skills are weak and I have never coded anything in Java or Kotlin. On top of that I have never worked with Github. It is better for a pull request to be completed by a developer familiar with Osmand, the software language and Github. I can create an algorithm though! :) In fact the workaround that is already posted makes an excellent starting point for creating the algorithm.

[Sonwon1]

This is getting off topic, back to topic please. Since no one has posted the current project plan to address the issues labeled 'Nice to Have' should I assume there are no plans? Can the project manager please weight in?

[mikehgentry]

Have you read the description (if you click on 'Labels' on the front issues page)? It says "Should be fixed but there is no priority or no possibility to fix it within current horizon planning".

That seems pretty self-explanatory to me? It isn't closed as "wontfix", because they do intend to fix it (and it's implied that they will accept appropriate patches). But they don't have a plan for when they're going to fix it.

One can debate whether a specific bug should be labelled "nice to have" of course.

[Sonwon1]

Have you read the description (if you click on 'Labels' on the front issues page)? It says "Should be fixed but there is no priority or no possibility to fix it within current horizon planning".

That seems pretty self-explanatory to me? It isn't closed as "wontfix", because they do intend to fix it (and it's implied that they will accept appropriate patches). But they don't have a plan for when they're going to fix it.

One can debate whether a specific bug should be labelled "nice to have" of course.

Thank you for the reply.

The oldest Nice to Have's are from 2015 so 10 years old. After 10 years I would guess most users will give up, forget about it or move on.

I would like it better if there was a quarterly review process and a decision made if a "Nice to Have" will ever get done. If it will get done then place it in the project plan. If it is technically beyond the capacity of the hardware or software then say so and close the issue. Otherwise you are leaving users hoping something will be improved when it is not going to happen and it leaves the perception that issues are labeled "Nice to Have" to bury them. I don't believe this is the intention however it does leave that perception.

I think Osmand can do better with better planning and communications.

[vshcherb]

Sometimes we go over the issues with "Nice to have", combine them and fix. We don't close them cause they they are legitimate issues and I would say with 5-10% chance it will be ever implemented.

[vshcherb]

There is no sense in reviewing old issues, we write a plan for next year and combine all issues with Nice to have under that umbrella. We fix the most critical issue on the go and we sometimes include small & easy to implement features

[Sonwon1]

Thank you for the reply.

After 10 years though?

I am not here to cause trouble I just believe the system is broken. I also admit I have never worked on an open source project. So you understand my prospective is mostly with hospital and banking systems as a project manager. Maybe I am expecting to much from an open source project however I do not think so, I casually follow Linux kernel development and it appears to be much tighter over there.