Ask / Submit
5

Together: usage of roadmap tag after updates [answered]

asked 2014-02-07 11:06:38 +0300

foss4ever gravatar image

updated 2014-02-15 01:48:44 +0300

Now that we have had few system updates that have had questions open here in Together. Many of those have been tagged with roadmap befeore the upgrades to inform community that the issue/feutures are being worked on. Just before the upgrade jan14 appeared to some of those questions to indicate that an mplementation is scheduled to a specific system udate. Additionaly a text [Implemented in 1.0.3.8] has been added to those questions afterwards by moderators that have had the request implemented in the Jan/2014 update.

The suggestion here concerns the usage of roadmap tag which is still present in questions that have jan14-tag in them and 'implemented in 1.0;3.8' text in the title. Those questions have also beeen closed, so doesn't all this mean that they are resolved, implemented and are not anymore in the road-map?

Thus I suggest that roadmap tag removed from all questions that have been conpletely resolved, i.e. questions that have 'jan14' tag in them and text '[Implemented in 1.0.3.8]' in the title. Also this practice should be continued in the future too. This way we maintain a clear view of what is going to happen knowing that the roadmap tag refers only to things ahead of us.

What do you.think?

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by chemist
close date 2014-02-15 15:30:37.085317

Comments

Wouldn't this discussion fit nicely under "cleaning up together"? I suggest closing this as too localized.

simo ( 2014-02-07 11:17:31 +0300 )edit

@jjaone I'm sorry you felt that way. I see your question both relevant and important, it's just that if every tag had its own question, we would have a lot of more questions here... That's why I suggested "too localized". However, I hope this will be discussed there and a good solution will be found.

simo ( 2014-02-07 11:45:03 +0300 )edit

re-opened cause the question and temporary answer had got some vptes. I really hope this time that we get proper answer to this so that the big picture of planned features and fixes could be seen in the question metadata after each update too.

foss4ever ( 2014-02-15 01:39:23 +0300 )edit
1

I agree. If there is some reason to keep track of these roadmapped-and-resolved questions, the tag in them could be changed to roadmap-completed or something similar.

ssahla ( 2014-02-15 01:59:33 +0300 )edit

4 Answers

Sort by » oldest newest most voted
3

answered 2014-02-15 14:20:59 +0300

eric gravatar image

No tag removal, please. The intention with it is to combine it with the Month/year to reflect what was delivered. From the list of items you clearly what is done or planned to be. We're continuously bringing improvements to this process and once we have done some needed modifications in Askbot, it will be much clearer, hopefully :)

So as already mentioned several times, please avoid at all cost touching the reserved tags and follow the guidelines, thanks!

edit flag offensive delete publish link more

Comments

Thanks for the Answer, the intention of this question was not to try to touch thpse reserved tags, but to clarify what is the convention in using them. Now, if roadmapand e.g. jan14 are used together to indicate that feature was in planning but has been implemented, and roadnap alone neans there is still work going on, then it is easy enough to know what is gping on. The addition of [Implemented in x.x.x.x] to the question titles was one cause of confusion, cause there are now that, roadmap, and jan14 indicators all pointing to sinular kind of things, without clear semantics and practices.. These things this question tried to clarify, not to seek permission to start fiddling with reserved tags or anything like that.

foss4ever ( 2014-02-15 14:46:47 +0300 )edit

Also it is good to know that more tools are on their way to help us all to keep track on the progress of Together questions, issues, suggestions and their current statuses and future prospects.

foss4ever ( 2014-02-15 15:05:15 +0300 )edit
2

@jjaone: once we bring the granularity on the [Closed] suffix, it should really help clarifying, or so we hope :)

eric ( 2014-02-15 15:50:18 +0300 )edit
2

answered 2014-02-07 11:36:46 +0300

foss4ever gravatar image

updated 2014-02-15 01:43:47 +0300

Update: question re-opened.

Note that this is not an answer actually, but just a reminder that the problem still persists (and probably the question should be opened again) cause currently the community has no way of knowing which of the roadmapped topics are for real and which ones are already completely or partially resolved. Before rhis upgrade the usage and understanding about roadmap was clear and consistent but now as long as they are still living side-by-side in topics that have been already Implemented the.semantics have become blurred.

edit flag offensive delete publish link more
2

answered 2014-02-15 04:14:09 +0300

Stefanix gravatar image

updated 2014-02-15 06:25:52 +0300

As we get more updates, the situation will become more complicated. Roadmaps also change and we can't expect to get this site permanently synced with the actual roadmap.
1) Each post related to a specific device problem or feature request should have a mandatory user assigned tag with the current SW level, e.g. current SW 1.0.3.8. Not each user will update his device immediately. We will see many different versions in the field and need to know to which version the question is related to.
2) The roadmap tag (reserved for Jolla usage) should state the SW release AFTER which we can expect the improvement. E.g. roadmap 1.0.2.5+. Ideally those tags would be updated as soon as the target release is confirmed (remove the '+' and correct the version). But this way, even without updating the tag, this information remains valid, unless the item has been removed from the RM. E.g. I know with the above tag that the improvement in question might be already in 1.0.3.8, or with the tag roadmap 1.0.3.8+ I have to wait at least for the next update. Alternatively the release name could be used, as future public release version numbers can change.

Edit: Actually the question was about handling the tags AFTER improvement implementation. Of course they SHOULD be updated to implemented <version> as suggested by @jjaone. My suggestion could be part of the solution to make roadmap tags more meaningful in case of delayed / no roadmap tag updates.

edit flag offensive delete publish link more
-1

answered 2014-02-15 01:55:23 +0300

chemist gravatar image

Roadmap is a Jolla assigned tag, keep it that way! Ask eric to have it sorted on their end and contribute to the existing questions/wikis about roadmap and tags please.

edit flag offensive delete publish link more

Comments

Thats why this question is here to clarify it's usage. And because we can't touch that tag it cannot be sorted out by us, but forum moderators. cc: @eric

foss4ever ( 2014-02-15 02:14:08 +0300 )edit

Bedides: question is relevant and certainly not oudated, cause there are many questions with roadmap tag even if they are not in roadmap anymore.

foss4ever ( 2014-02-15 02:16:14 +0300 )edit

and some are partially done and so on, that is nothing we need to discuss but have moderators sort it out and make us aware of in the related questions!

chemist ( 2014-02-15 13:59:38 +0300 )edit

Together forum is exactly the place for us, the community and moderators to discuss and clarify these kinds of things, we are all using to share knowledge to make this forum and the Jolla/SailfishOS better and more suited to the needs of the whole community. I see no problem in opening up also the reasons to do things in particular way. Knowing is better than guessing ;)

foss4ever ( 2014-02-15 14:54:53 +0300 )edit

Question tools

Follow
2 followers

Stats

Asked: 2014-02-07 11:06:38 +0300

Seen: 372 times

Last updated: Feb 15 '14