Talk:Tutorials and documentation

The change from just "tutorials" to "tutorials and documentation"

I thought I should justify why I renamed this page. This page was serving about the same purpose before, but not everything listed was a tutorial, so it wouldn't be obvious to look on this page for general information and having a separate page for documentation/general info doesn't seem necessary. What I'd like to see is this page become is sort of the next page people go to after looking through the user manual, a hub connecting users to all the information they want. For the most part the information is already out there, but it's often difficult to find.

Later on it would make sense to further break down the lists to "Basic tutorials/information" and "Advanced tutorials/information", so stuff most users would be interested in would be in basic while information only some people are interested in would be in advanced. But that's just my idea for organization, if anyone has a better one please share it.
--Cheese 07:11, 6 July 2010 (MEST)

Good idea. If necessary, this page can later become a wrapper for other more specific pages (and I think there will be several iterations of that process)

--Tsh 11:10, 6 July 2010 (MEST)

User/Dev split

I guess this is as good a place as any to raise this question. The wiki has grown up with the view of serving two groups of people, users and devs. It is also split into hardware and software views of the pandora. I am struggling with this then it comes to organising some of the information. Rather than split users i think it makes sense to partition information into the different levels of experience, dispense with the idea of a hardware vs software split (where does 'power' fit in that domain) and split hardware modding/fixing (extra leds, button fixes, nub replacement) off into a 5th area. We'd then end up with this sort of categorisation (and maybe group them together to start):

• (User) Troubleshooting (brand new user can't power up)
• (User) All users (menu managers, installing apps, day to day usage, games, installable apps, peripherals)
• (User+) Advanced User (Linux guides, editing configs, SD boots, recovery, opkg, extend, toolchain, scripts, pnd packaging)
• (AppDev) Application developer (pandora libraries - so more specific than user+)
• (Firmware) OS and Firmware contributor (develop, debug, improve)
• (Hardware) Modifications (case, nubs, leds. Anything involving soldering or a dremel)

I'd then put battery stuff under firmware, and there is a nicer split between user OS hacking, and OS stuff which is likely to be pushed into the GIT and back out as a new release. --Tsh 14:04, 16 July 2010 (MEST)