In v1, the Center doesn't show software in third-party repositories at all. In v2 it will, though, and your scenario is a useful contribution to the design of that feature. As I said, "Get Software" will likely become a section with "Free Software" and "Paid Software" subsections, but I was supposing that wouldn't happen until v3. The example of a private repository of site-licensed software, though, shows that we'd need to have subsections for v2. Something like:
Get Software
|– Free Software
|– MyExample Repository
'– Medibuntu Repository
That way, we wouldn't be incorrectly assuming any particular non-ubuntu.com repository was "free software". I've added a reminder to the spec about this. <https://wiki.ubuntu.com/SoftwareCenter?action=diff&rev2=218&rev1=217> Thanks!
That leaves the suggestion of changing "Get Software" to "Available Software". I did consider that wording early in the design process, but I thought "available" was a little too vague -- people might misconstrue "available" as "available on my computer". That said, I plan to organize user testing on the navigation in general soon, and if it shows the wording needs changing, we'll try "Available".
In v1, the Center doesn't show software in third-party repositories at all. In v2 it will, though, and your scenario is a useful contribution to the design of that feature. As I said, "Get Software" will likely become a section with "Free Software" and "Paid Software" subsections, but I was supposing that wouldn't happen until v3. The example of a private repository of site-licensed software, though, shows that we'd need to have subsections for v2. Something like: /wiki.ubuntu. com/SoftwareCen ter?action= diff&rev2= 218&rev1= 217> Thanks!
Get Software
|– Free Software
|– MyExample Repository
'– Medibuntu Repository
That way, we wouldn't be incorrectly assuming any particular non-ubuntu.com repository was "free software". I've added a reminder to the spec about this. <https:/
That leaves the suggestion of changing "Get Software" to "Available Software". I did consider that wording early in the design process, but I thought "available" was a little too vague -- people might misconstrue "available" as "available on my computer". That said, I plan to organize user testing on the navigation in general soon, and if it shows the wording needs changing, we'll try "Available".