TRACKER/FLYSPRAY: When and How to use it

[Hakan]

Originally Posted by nohal

Yes, there is. See the attached for location of the button.

Thanks Pavel, if it was that easy, but my view is as the screen shot here. No such button. I may have restricted rights?
Thanks
Håkan

[nohal]

Hakan...
Try now. I have checked the tracker configuration and you had a "privilege" to be a sole member of a slightly misconfigured user group. Don't ask me how that could have happened, I have no idea...
Maybe you will have to log-out/log-in so that the change is propagated to your session.

Pavel

[Hakan]

Pavel...
Hmmm... I've slight idea about the history, but never mind. Now I see all buttons.
Many thanks.
Håkan

[AISEAG]

Hey Guys, What's going on, NO changes since mid May

Most wanted features :
FS#246 (Chart Search function for objects (e.g., buoys, nav aids, lighthouses, islands, place names...) is leading with 15 votes (+0 from previous report Mid-March),
note :#FS246 is partially answered with the Objsearch Plugin

FS#224 (ALARM Depth - Warnings when route crosses area shallower than shallow or safety depth) is following with 12 votes (+0 from previous report)

FS#1195 (NMEA 2000 Connection support)is in the third place with 11 votes (+2 from previous report)

See thread relating to "OpenCPN 4.1925 version - post #1" where Bdbcat is asking for your collaboration.
FYI : 450 pending requests in the portfolio and over 2/3 are with a very little number of votes.


Be an actor of OpenCPN :
>> as a User :
>>>>>> Do not hesitate to check Tracker/Flyspray and, when your request has been implemented and tested, to ask for its closure.

>>>>>> by browsing thru the portfolio and by voting for the request(s) that is(are) essential to you, this will help the development team

Serge

[rgleason]

Serge,
I am trying to add a plugin to the dropdown Project List.
I am able to rename the plugins to be more organized and correct. (Some names changed)
However I seem to have forgotten how we ADD a new project for one of the new plugins.

It is Sean's pi_Projections plugin. Can you advise how, since you are the guru on Tracker? Thanks.

[rgleason]

With OpenCPN 4.2.0 released, we should all be checking Tracker.

1. Close all tasks that you opened (OP=Original Poster or Person) that have been fixed or are no longer current or applicable.

2. Look particularly at OpenCPN Feature Requests, OpenCPN 4.1.x and all the Plugins

The plugin tasks particularly appear to be out of date. Please close your OP tasks that no longer apply or are fixed. If they still apply, please leave an appropriate comment so we know you have looked at the problem again.

Thank you.

[rgleason]

It it time to clean up tracker, in particular OPENCPN FEATURE REQUESTS.

Please check all your entries to make sure they are current. If they are not current please close them! It is best if the Original Poster close their entries.

The easiest way I have found to do this is to
1. Log into Tracker OpenCPN::OpenCPNAll Projects: Tasklist
2. Select "All Projects" from the right dropdown.
3. In headings, click on "Opened by" to sort up or down alphanumerically.
4. Find all of your posts by clicking on the pages.
5. Inspect each post to make sure it is current and has not been fixed.
6. Close any tracker posts that are out of date and no longer apply.

There are many pages of Feature Requests. These have gotten unmanageable and many are outdated. They must be cleaned up before the programmers will be able to effectively use Tracker to direct their efforts.

So please give us a big assist and CLOSE YOUR OUTDATED TRACKER ENTRIES!!!

Thank you.

[rgleason]

OpenCPN Feature Requests is back up to 8 pages, for a brief time it was down to 7 pages.

CLOSE ALL YOUR OLD OUTDATED FEATURE REQUESTS PLEASE!

We need to get this Feature Request List to become more focused, so the Developers can know what is really needed. For every new request we should be able to Close another!

[rgleason]

Thanks to all who have been helping to clean up and clean out Tracker.
We have made great progress lately with bdbcat and nohal help.
02-Opencpn-3.3.x Beta 1 task
03-Opencpn-4.0.x Stable 6 tasks (down from over 40)
04-Opencpn-4.1.x Beta 2 tasks
05-Opencpn-4.2.0 Stable 21 tasks (down from over 40)
With just a little more effort and some luck, we may be able to close Projects 02,03 & 04 above. If any of you have opened these tasks or can help with information or testing it would be very appreciated.

Our other goal is to reduce, consolidate & prioritize the ridiculous number (165) of
00-OpenCPN - Feature Requests
to something more reasonable like 100 so that those who help with programming can focus more easily on the top items.

We certainly have more feature requests than we do programmers, so if you have a feature request that is low priority or is outdated, no longer needed, or completed, please advise in the Tracker item so we can close it.

If you are a programmer at all familiar with C++ please try to knock off some of the easier feature requests which will not be done by the main crew. This load needs to be distributed. Together we can also clean up and out Feature Requests! Thanks.

[rgleason]

Currently there are 166 Feature Requests in tracker. This is a tribute to some passionate users, however even with the alphanumeric "Summary" sorting system that we have developed to keep "like" feature requests together this is far too many items to address and to expect the team to program. This list needs to be groomed and culled to become meaningful and useful.

So how is the focus of the next features programming effort going to be determined?
1. "Merit" or "Need" as decided by the programmers.
2. "Popular request" known as VOTING.

Are there ways that this outrageous number of requests can be reduced to something manageable, like 40-60? I can do it pretty quickly.

1. Disregard all items with less than 7 votes. The list goes down to 3 items, very simple job now.
In my opinion, there is absolutely no reason to program any feature request that has less than 5 votes, because there is too little demand for the effort. If I were a programmer, I would then do something much higher on my own internal priority list, quite frankly. Therefore I suggest that everyone who cares about this program and the features, takes a good hard look at every item and vote for the ones you want to see implemented. Hopefully there will be an marked increase in VOTING activity.

2. Make a new Project called "Unvetted Feature Requests" and move all items with less than 4 votes into this Project. You can be sure that most of these items will probably not receive any attention from the developers because they already have higher priorities. I expect we will be doing this soon.

3. Cull the list, eliminating duplicate and similar requests. - Please help, by leaving comments.

4. Join items together that are in the same program area (UI, RM, WP, AIS etc) creating a simpler and more comprehensive list for the programmers to tackle.

5. Accept that "Unvetted Features" will not be implemented except by junior volunteer programmers.

PLEASE USE THIS LINK TO MAKE YOUR COMMENTS IN ANOTHER THREAD

Current state of "00-Opencpn Feature Requests"
13 votes (1)
11 votes (1)
9 votes (1)
6 votes (2)
5 votes (2)
4 votes (4)
3 votes (9)
2 votes (26)
1 vote (50)
0 votes (70)
----------------
Total= 166

[rgleason]

Here is the new Vetted > 4 Vote Project List (8 Items)

OpenCPN::OpenCPN00 - OpenCPN Feature Requests Vetted > 4 Votes: Tasklist

I suggest you guys get active VOTING for the features you want.

If I were a programmer I would not bother looking at any Feature Requests that have less than 5 votes, there are too many other priorities.

[rgleason]

Jon Gough writes:

I would appreciate it if the list of items in flyspray was updated with votes for what is required so that I know what is the more important updates to add.

Please give Jon the courtesy of VOTING.

[rgleason]

It is impossible to implement all 158 individual feature requests, however 78 items have no vote, which drastically simplifies the problem. Perhaps Requests which do not have the Original Person's vote + one other supporting vote (two votes) should be in a separate "Feature Requests -no vote" project.

An astounding 145 items (158 total) would be moved to the "No Vote" category.

GET BUSY AND VOTE FOR WHAT YOU WANT DONE!
IT IS THE ONLY WAY FOR THE PROGRAMMERS TO KNOW.

OpenCPN::OpenCPN00 - OpenCPN - Feature Requests: Tasklist


HOW TO VOTE

Register in Tracker.
OpenCPN::OpenCPNRegister new user

Then Login OpenCPN::OpenCPNAll Projects: Tasklist

At the upper right Dropdown list select "00-OpenCPN Feature Requests"

Click on the "Vote" column to sort by Votes.
Click on the "Summary" column to sort into similar request types
Click on the "Status" column to sort by status.
..and so on.
To read more about a Feature Request, highlight it and left click.
To VOTE for the item find "VOTE" and click on the number.


WE HAVE ABSOLUTELY NO VOTING RESTRICTIONS !!!
OTHER THAN YOU CANNOT VOTE TWICE FOR A GIVEN ITEM.

[rgleason]

Log into Tracker
Login OpenCPN::OpenCPNAll Projects: Tasklist
Upper right dropdown select "All projects"
Just above the dropdown find "My Searches"
Select "Tasks I reported"

Look at how many votes for each task there are.
Sort by votes.
If you have Feature Requests with Votes=0 you should vote for them.

[I just did this for mysef, and I am finding I am limited to one vote per day]
I am going to find out if this limit can be increased.

[rgleason]

There are now 14 items. When the list hits 20 items, the number of votes required will increase!
OpenCPN::OpenCPN00 - OpenCPN Feature Requests Vetted > 4 Votes: Tasklist

Also there are still about 50 feature requests with Votes=0
This fact assures that the item has a slim possibility of gaining any attention by the developers as even the authors have not voted for the the item!

See if you recorded some of these items
OpenCPN::OpenCPN00 - OpenCPN - Feature Requests: Tasklist

Go to the link above.
Then pick "My Searches" in the first line next to your name.
Then pick "Tasks I reported" from the dropdown.
Those are the tasks you reported with Vote=0

All of these should have at least TWO VOTES, one by you and one by someone else who wants the feature, otherwise we should close it.

We are considering closing some of these VOTE=0 Feature Requests pretty soon, to pare down this ridiculous Feature Request List of 151 Items.