July 5, 201510 yr perhaps adding another thread isn't the best idea considering the title but I think this sub-forum has too many pinned threads. I suggest splitting the Docker subforum into sections like 'Getting started / Guides / How-tos', 'Now you're up and running, here's where to find support', 'Repositories and Container dicussion / maintainer announcement threads / look at the new shiny we've released!'. I dont think it need be any more complex than that. Reduce the number of pinned threads to a bare minimum too. It's way too much at present.
July 5, 201510 yr As someone new to unraid/docker it was very confusing and hard to navigate. It seems like the separate threads for "OFFICIAL GUIDE" can be consolidated. As well as all the 'repo' threads, those can be consolidated to a master repo thread, but then again I'm pretty sure I've seen one of those.
July 5, 201510 yr unpin dockerization of popular applications and smidion's repository. Back in the day when they were the only two repos, pinning served a purpose. Now they don't. Plus, it's so much easier to get to the support threads without searching either by using CA or the repositories thread. Move the best practices thread into the Development Forum. Consolidate LT's how to-s either into their own sub forum or incorporate into the FAQ Create a FAQ subthread. Move the noobie guide and the FAQ into it.
July 5, 201510 yr it's been suggested before (by others, including myself) and there was talk of it from LT sometime after 6.0
July 5, 201510 yr http://lime-technology.com/forum/index.php?topic=39282.0 i'm sure i remember seeing somewhere mention of it on the horizon after 6.0 (maybe cross purposes on my part there)...
July 5, 201510 yr Author http://lime-technology.com/forum/index.php?topic=39282.0 i'm sure i remember seeing somewhere mention of it on the horizon after 6.0 (maybe cross purposes on my part there)... I saw this at the time but thought a reminder couldn't hurt.
July 6, 201510 yr Until the awaited forum reorg happens... I'm a pinner and un-pinner, is there a consensus as to what should be unpinned?
July 6, 201510 yr I think everyone is agreed a reorg is necessary, and the sooner the better. To push the ball down the road, here's a starter proposal for the Docker area. * "Docker, Getting Started" -> contains all guides, FAQ's, etc, but NO support threads (relatively light use, but heavily read) * "Docker Support" -> ALL support, both installation, upgrades, troubleshooting, etc; seems too hard to separate them (very heavy use, but hard to subdivide) * "Docker Development" -> Docker discussion, maintainer to maintainer talk, how to develop xyz, etc (light to moderate use) * "Docker Announcements" -> no support, just announcement threads with their own feedback (probably light use)
July 6, 201510 yr No problems with that proposal except that generally the announcement threads are also the support threads
July 6, 201510 yr No problems with that proposal except that generally the announcement threads are also the support threads Right, only too true. To have an announcement board, the Way Things Are Done would have to change. Don't suppose that the authors might be interested in working with 2 topics per repository and/or container? One would be strictly for support, the other topic would be for the official post, first announcement, description, installation instructions and links, etc, with additional news and announcements and tips and FAQs posted to this topic, but no support, keeping it short. It would be a way to start fresh, creating a new 'official' post (for Announcements board) and a new Support topic, and rename the old one as an archive. First post in each would cross-link, and Community Applications would also have both links (if Squid is willing). Just a crazy idea, probably too hard to make it happen ... If not, then the following - * "Docker, Getting Started" -> contains all guides, FAQ's, etc, but NO support threads (relatively light use, but heavily read) * "Docker Support" -> ALL repository threads, their announcements and ALL support, both installation, upgrades, troubleshooting, etc; seems too hard to separate them (very heavy use, and hard to subdivide) * "Docker Development" -> Docker discussion, maintainer to maintainer talk, how to develop xyz, etc (light sporadic use)
July 6, 201510 yr No problems with that proposal except that generally the announcement threads are also the support threads Right, only too true. To have an announcement board, the Way Things Are Done would have to change. Don't suppose that the authors might be interested in working with 2 topics per repository and/or container? One would be strictly for support, the other topic would be for the official post, first announcement, description, installation instructions and links, etc, with additional news and announcements and tips and FAQs posted to this topic, but no support, keeping it short. It would be a way to start fresh, creating a new 'official' post (for Announcements board) and a new Support topic, and rename the old one as an archive. First post in each would cross-link, and Community Applications would also have both links (if Squid is willing). Just a crazy idea, probably too hard to make it happen ... If not, then the following - * "Docker, Getting Started" -> contains all guides, FAQ's, etc, but NO support threads (relatively light use, but heavily read) * "Docker Support" -> ALL repository threads, their announcements and ALL support, both installation, upgrades, troubleshooting, etc; seems too hard to separate them (very heavy use, and hard to subdivide) * "Docker Development" -> Docker discussion, maintainer to maintainer talk, how to develop xyz, etc (light sporadic use) Best bet would be for the authors to create a separate support thread for each container. Probably not going to happen however. Beyond that if anyone wants to actually propose multiple threads like that for the templates (and apply the pressure on the author to actually modify the templates) then i will make sure that CA supports it
July 6, 201510 yr Best bet would be for the authors to create a separate support thread for each container. As a user, I would definitely prefer this. Cramming support for 10 dockers into a single thread makes it very difficult to find relevant information.
July 7, 201510 yr Author Best bet would be for the authors to create a separate support thread for each container. As a user, I would definitely prefer this. Cramming support for 10 dockers into a single thread makes it very difficult to find relevant information. Done. I invite you to go look at the top of this subforum now. All you can see is my 7 threads and a jillion pinned ones. Come on LT, sort this out!
July 7, 201510 yr Probably could un-pin all the repo support threads since we have Squids plugin now.
July 7, 201510 yr As part of a larger suggestion I have coincidently highlighted this very issue directly to LT. Hopefully that will get it some attention
July 7, 201510 yr Best bet would be for the authors to create a separate support thread for each container. As a user, I would definitely prefer this. Cramming support for 10 dockers into a single thread makes it very difficult to find relevant information. Done. I invite you to go look at the top of this subforum now. All you can see is my 7 threads and a jillion pinned ones. Come on LT, sort this out! Appreciate it, hopefully others follow suit. Do you have a link to each thread from your repo post? That'd be helpful as well.
July 7, 201510 yr unpin dockerization of popular applications and smidion's repository. Probably could un-pin all the repo support threads since we have Squids plugin now. Done.
July 7, 201510 yr Best bet would be for the authors to create a separate support thread for each container. As a user, I would definitely prefer this. Cramming support for 10 dockers into a single thread makes it very difficult to find relevant information. Done. I invite you to go look at the top of this subforum now. All you can see is my 7 threads and a jillion pinned ones. Come on LT, sort this out! Appreciate it, hopefully others follow suit. This is great, thanks ironicbadger!
July 7, 201510 yr Author Best bet would be for the authors to create a separate support thread for each container. As a user, I would definitely prefer this. Cramming support for 10 dockers into a single thread makes it very difficult to find relevant information. Done. I invite you to go look at the top of this subforum now. All you can see is my 7 threads and a jillion pinned ones. Come on LT, sort this out! Appreciate it, hopefully others follow suit. Do you have a link to each thread from your repo post? That'd be helpful as well. Good idea. I'll get on that.
July 7, 201510 yr Best bet would be for the authors to create a separate support thread for each container. As a user, I would definitely prefer this. Cramming support for 10 dockers into a single thread makes it very difficult to find relevant information. Done. I invite you to go look at the top of this subforum now. All you can see is my 7 threads and a jillion pinned ones. Come on LT, sort this out! Appreciate it, hopefully others follow suit. Do you have a link to each thread from your repo post? That'd be helpful as well. Good idea. I'll get on that. I need a moment of silence, my small world of fame is now gone. Good-bye sticky. You will be missed. :'(
July 7, 201510 yr Best bet would be for the authors to create a separate support thread for each container. As a user, I would definitely prefer this. Cramming support for 10 dockers into a single thread makes it very difficult to find relevant information. Done. I invite you to go look at the top of this subforum now. All you can see is my 7 threads and a jillion pinned ones. Come on LT, sort this out! Appreciate it, hopefully others follow suit. Do you have a link to each thread from your repo post? That'd be helpful as well. Good idea. I'll get on that. I need a moment of silence, my small world of fame is now gone. Good-bye sticky. You will be missed. :'( well at least you have had a sticky..... (that just sounds so wrong, lol)
July 8, 201510 yr unpin dockerization of popular applications and smidion's repository. Probably could un-pin all the repo support threads since we have Squids plugin now. Done. The question is now.... how do we inform users about squids plugin. They shouldnt have to be forum ninjas to know what exists.
July 8, 201510 yr unpin dockerization of popular applications and smidion's repository. Probably could un-pin all the repo support threads since we have Squids plugin now. Done. The question is now.... how do we inform users about squids plugin. They shouldnt have to be forum ninjas to know what exists. **Secretly hoping LT brings it into the default UI like they did with Dockerman and VM-Manager. Both were community additions to the community built WebGUI (god I love this community)**
Archived
This topic is now archived and is closed to further replies.