Provide your voice in NethServer development and roadmap

[alefattorini (Alessio Fattorini)]

Continuing the discussion from Is the e-smith layer is a pain?:

@filippo_carletti

@zamboni

I see many people here just begging for features or complaining for missing things

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:

1. someone might find it complex
2. year over year, things change and we may find something “better” than templates

I’d like to start from Filippo’s post for invite every NethServer’s friend to make its voice heard:

• Submitting ideas in the Feature Category
• Chiming in existing proposals and improving the discussion with their point of view
• Giving likes to the other good ideas

Make sure your feature isn’t already made or planned.
This is a list of TOP features by likes, views and replies.
http://community.nethserver.org/c/feature/l/top/all

In such way, you can truly provide your voice in NethServer development and roadmap. While I can’t promise developers will implement every idea I can say that these ideas will be actively monitored.

So, making a recap, we WANT beggars of new features, we WANT people with different points of view.

Are you not a developer? Totally fine, but you have to convince the community to support your proposal, being ready to discuss and defending such feature or improvement. Let’s try to explain us WHY and HOW NethServer should have this! You have to persuade many people

• Have you already checked within the community to see if a similar request exists?
• What problem are you trying to solve?
• Don’t give us the solution, describe the problem first. Why do you want to solve this problem? Explain the real benefit.
• What kind of difficulties has your client encountered? Give me some examples.
• Describe the solution you would implement. If possible, provide some examples or screenshots, even from products other than NethServer
• How often have you felt the need to implement this feature? For example, how many complaints have you received from your clients?
• If it’s a bug, have you been able to reproduce it consistently? How?

Just and example: I’m not a skilled developer, I know nothing about Ruby on Rails but I’m an active member of Discourse Community. I filled bugs and submitted my point of view on many features, suggesting a lot of them.
I’m not a “beggar” since I can’t do more than that, I won’t do better than that, I’m just a pretty expert of the interface but I can and I MUST give my opinion and send my requests since I know the product very well.

[Jim]

Hello,

Can we have a little feedback about theses features proposals?

We understand that there’s priorities, there’s things that seem easier to implement than other…
It would be pleasant to know if a feature is in progress or not.

[alefattorini (Alessio Fattorini)]

Can we tag them with Planned, In Progress and Implemented?

So you can search them with:
category:feature tag:planned

http://community.nethserver.org/search?q=category%3Afeature%20tag%3Aplanned

In the list they might appear like

What about?

[Jim]

Sure, It’s a simple good idea

I think it’s simple and effective