Introducing new members on community - 22 Feb 16

[alefattorini (Alessio Fattorini)]

Ehi Jason, thank to answering my call! Well we have many people here from Australia like @Greg @WillZen @sraellis
Which kind of company your employer is? IT sector or something else?

@jasonhurd

So far things are looking good although from what I can tell the GUI is a bit limited compared to what the packages can actually achieve. In order to get into a lot of the packages functionality you still need to access through the terminal.

I would like to expand on the design aspect of your concerning, could you please make same example?
In the meantime I suggest you this discussion:

RFC: interface complexity level

I don’t like very much the ability to change the listening port from the web interface except for few exceptions. A good example of this exceptions can be SSH or OpenVPN (as pointed out by @stephdl (https://github.com/nethesis/nethserver-openvpn/pull/2). Changing ports for these kind of daemon is a well-known practice. But if we want to give this chance to the user, I don’t see any problem for non-critical services like FTP, but I’d strongly discourage for other important services (like IMAP/…

Btw, thanks for your words of appreciations you can help us to make the product even more user-friendly.

Provide your voice in NethServer development and roadmap

Continuing the discussion from Is the e-smith layer is a pain?: We need them in this community. We need to know where we have room for improvements. We need to have different points of view. Everyone will follow his own path, someone will become a developer, someone a tester, someone will write documentation. We need to remove obstacles from every possible path. To me, more than 15 years ago, the templates system appeared as a simple and powerful tool, but I understand that: someone mig…