keith Wrote:So guys, should we have the other thread 'faq/issues/etc' be the 'bleeding list bugs' thread, or should we continue to have 2 different threads, one for 'from apt-get' and a nightly one for bug list/organization?I think that your best bet is to split it into 2 threads, as you've suggested:
Maybe we should break it out, so we have a FAQ/installation/etc one thats geared for apt-get/new folks, and then a bug list one as well, that may list bugs from the repo, but also nightlies.
Kind of a 'this is FAQ on how it should work' 'now here's the bug list on broken things'.
- known issues (repo AND nightlies)
Having both sets of known issues in one thread would be nice for comparison of what's been fixed, and what functionality may be lost by upgrading to the nightly build.
I'd imagine that keeping the nightly issues up-to-date might be a challenge, but would be helpful if it can be done.
BTW; I'd recommend reserving at least the first 3 slots in the thread - the word limit is maxed out on the issues post and the FAQ post of the current thread.
Quote:If we do go down that route, I want to try to keep the FAQ thread specific to iOS/ATV2 just like the bug list thread.Totally agree. Just make sure you've got a link to the wiki for general FAQs, and then the rest can be all iOS specific
Quote:Also should these threads be locked so we don't get troubleshooting on the threads themselves? I'm against locking threads AND continuing to post in them usually, but since the platform is fairly mature/usable now, I am not against this use of it for organizational purposes.Personally, I'd recommend keeping the thread open. It's been very useful to have people report bugs in replies to the current issues/FAQ thread. It's made it easier to (mostly) keep on top of things than if that facility wasn't there. When I made that thread, I did try to make it clear that
"new issues should be confirmed beyond your own personal experience before posting them here"
Inevitably perhaps, there were still plenty of people who didn't read that and posted there for troubleshooting anyway, but on balance it has been helpful to have. Troubleshooting posters were usually dealt with in a single reply, and if not they were directed to start a new topic.
You could take a more stern approach and delete troubleshooting posts. If you do that then people will probably learn pretty quickly that this thread isn't the place for those kind of posts.
Either way, if you're planning on keeping the first post(s) up to date, then doing that is what really counts. The end user should be able to get all the information they need from that first post, and not have to go digging through the thread to find issues. Ultimately the rest of the thread is there to help you keep the first post up to date. If you want that help, keep it open; if you don't think that you need it, or if you think that risk of troubleshooting spam will be more of a hindrance than help then leave it closed.
As mentioned in the post below this one, the last nightly thread did become difficult to use; from a standpoint of trying to find what issues were present. This was because new issues were being reported and discussed, but not necessarily confirmed, or put into a single post. What I was proposing in keeping the new thread open was that you use it to pick up confirmed bugs which have already been discussed elsewhere on the forum. As these are presented to you, rather than having to hunt them out yourself, then they're easier to add to a single list of bugs. I suggested this approach as it serves to 'lighten the load' of keeping track of what's going on. This might not be necessary if you're managing to keep track of all changes and bugs anyway.