Open GoogleCodeExporter opened 8 years ago
Original comment by billdaly111@gmail.com
on 26 Mar 2012 at 8:09
There's a lot of good stuff in here, but it definitely needs to be split up
into individual issues; kind of defeats the purpose if it is not
Original comment by turne...@gmail.com
on 10 Apr 2012 at 11:05
[deleted comment]
Yeah I agree with that. Bill made this decision to clean up the open issue list.
And mark my open issues as won't fix.
Those you can search here. But this can create confusion. Because some of them
are really tagged good as won't fix and some of them are just marked won't fix
for the clean up.
I mentioned on this topic. Only the summary of the Issues I wish you look into.
So it makes it easier for you. Anyway you got the ability to open up closed
tickets again. If you want that.
MEDIUM PRIORITY - (in my opinion)
Issue 51 : XBMC Navi-X repository
Issue 69 : Download issues files on github
Issue 76 : type=html open with firefox
Issue 79 : Downloading video of videofriender
LOW PRIORITY - (in my opinion)
Issue 21 : rss & atom , hide date
Issue 24 : xbmc now playing on navi-x script
Issue 25 : type=special_search_playlists
Issue 27 : message to download or play video because of buffering issues
Issue 28 : optional feature to not dowlnoad thumbnails
Issue 35 : Download always have name of extension
Issue 40 : Cannot Open File
Issue 67 : download and delete color information in file name
Issue 77 : feature request view : media:info
Original comment by tikkiebr...@gmail.com
on 13 Apr 2012 at 7:06
Hey Guys, I ran this by both of you so this was a mutual decision, not just a
"me" decision. If anyone would like to go ahead and re-open all the tickets, be
my guest, but if you are going to re-open them, make sure you go through the
list and only include workable tickets... no reason to have tickets that can't
be resolved due to XBMC limitations or overly complicated feature requests that
cannot or will not ever be fulfilled.
Anything else is cool with me. Otherwise, it's a waste of space. Thanks fellas.
Bill
Original comment by billdaly111@gmail.com
on 13 Apr 2012 at 7:17
Apparently I also got the ability to tag tickets open or close on this project.
But I rather leave that up to the developer in question to decide this. Since
this is in my opinion the proper way. Anyway I went though the list and post
those tickets on my previous reply. However I can't comment about issues on the
list that will not ever be fulfilled. Again that is for the developer in
question to decide.
Offtopic - tagging issues
When there are many open issues on your project. Tagging the issues type and
priority is very handy. I see this already being done. But from this discussion
I just want emphasize it. So you don't feel that the open issue list is
cluttered. For example this is the link to not view low priority issues -->
http://code.google.com/p/navi-x/issues/list?&q=-label%3Alow . This is just an
example. Read here more about it -->
http://code.google.com/p/navi-x/issues/searchtips .
Original comment by tikkiebr...@gmail.com
on 14 Apr 2012 at 9:43
Fair enough Tikkiew. :D
We are all friends here as far as I'm concerned. I personally would recommend
until we fins a dedicated developer for Navi-X for XBMC again, we wait to break
off these tickets. I also think that the dev would be able to run through the
list and tell us what's doable or not for sure.
I say we leave it all in one ticket until a dev can re-parse all tickets again
and tell us what is doable or not, hence why I chose to wait on this for a dev.
When I say dev, Turner is doing awesome work, but even he told me he can't dev
new features cause he just doesn't have the time. Until we find that dev, I say
we keep your notes in one all inclusive ticket. Just my thoughts... what do you
think? Thanks.
Bill
Original comment by billdaly111@gmail.com
on 14 Apr 2012 at 7:27
Original comment by turne...@gmail.com
on 24 Apr 2012 at 11:07
Hey Turner,
Thanks for clearing up that you are officially the primary developer for
Navi-X. Didn't mean to insult anyone. I will just e-mail you all next time when
it's not appicable in a technical sense or is more of a response than technical
feedback on a ticket.
Thanks fellas!
Bill
Original comment by billdaly111@gmail.com
on 24 Apr 2012 at 5:17
Original issue reported on code.google.com by
billdaly111@gmail.com
on 26 Mar 2012 at 8:07