PROBLEM/ISSUE WHICH MEANS THAT
1 a)
b)
c) and so on...
2 a)
b)
3 and so on...
OBJECTIVE INDICATOR OF SUCCESS
1 a)
2 a)
3 and so on...
Whenever I get a job in the business world, it's always to figure out what's wrong with things and fix them in new and innovative ways.The suggestions offered are simply a means of formalizing this process.
The devs thought it was neat I wanted to change things so they're for the idea.This is encouraging. If the devs support the redesign it indicates they see the current sidebar as needing improvement (something is causing pain).
I made a kind of general mockup of what that entails a few weeks ago shown here: http://www.kevinghadyani.info/files/ebox/eBox%20Profiles.htmlIn the example graphic the end nodes (shown in green) are a mixture of package name and descriptipons. A couple of examples:
Is it intentional that VPN is under Security and Infrastructure? Shouldn't it be just under Security?Hello JAK,
Core was something I made up myself. It's the one that contains what's in ALL other eBox configurations.In which case we may have problems with community members thinking the graphic provided represents the finished structure. Might it be a good idea to design the structure at this stage and obtain agreement on it?
We should, though, make sure to keep with the developer's current vision of 5 compartments, semi-overlapping...The agreement is essential and does require input from the devs (Javi?) but it may be possible to produce a solution that is not "semi-overlapping".
I'm all for the functional names rather than the module ones for instance or have the modules also have function names. Then, if someone wanted, they could enable specific parts of the Instant Messenger plugin by enabling Jabber and Made-Up-IM-Server-Name if they felt like it. Right?My preference is for descriptive names rather than module/package names. Using both seems clumsy and confusing. I would stick with what it does rather than what it is.
I should first ask if the devs are going to use other kinds of groupware or something else other than Samba for instance.It may be possible to design a structure that will accommodate changes such as these. Again the input from the devs has cropped up. The redesign is such a central part of using eBox that it will be difficult to do without establishing what it is to achieve.