Hey all,
I would like to ask what’s the prefered way to start contribute for users in the
Ubuntu community helping shaping Ubuntu’s future with ideas like we used
to have Ubuntu brainstorm ? or Launchpad wishlists ?
I like to hear your ideas!
1 Like
Moved to the Lounge which is for more general discussions.
There are many ways to contribute, see the documentation here:
https://ubuntu.com/community/docs/contribute/ubuntu-development
Thanks
2 Likes
The folks who are active and involved with a project get to make the decisions.
Their ideas get implemented.
It’s that simple.
Ubuntu has always been based upon contribution of code and effort more than upon contribution of “ideas”. Every developer I know has too many projects already. They are not looking for more.
They are certainly not interested in the fire-and-forget ideas common to the old Ubuntu Brainstorm. That’s why Brainstorm isn’t around anymore.
The ‘Project Discussion’ category here at Ubuntu Discourse is a good place to get involved and talk about the future of Ubuntu. However, let’s clarify that it is intended for discussion and involvement. It’s not a good place for fire-and-forget.
5 Likes
Ideas?
In my previous life as an employee I was once introduced by my supervisor to a new manager as: “This is Graham. He is our ideas man.” Some people see problems. I tried to see solutions. It did not mean that anybody listened to me.
I suggest that before discussing Ubuntu’s future we become familiar with the present plans and intentions for a future Ubuntu.
Consider the Roadmap for Ubuntu 26.10
Ubuntu 26.10 stonking stingray roadmap.
Did we see this statement:
Much of the work happening in Ubuntu 26.10 is part of a broader vision for Ubuntu 28.04 LTS
How far into the future can we see? Decisions have already been taken. Software engineers have been given their tasks. I keep in mind that Ubuntu is based on other software projects. What future do those software engineers plan for their project? Is our idea better placed with one of those projects and not Ubuntu?
Regards
3 Likes
If someone wants to compile a formal “Feature Request”, with all the requisite details,
-
is there a defined format that must be followed?
-
is there a “contents guidance” or what is expected to be provided as part of that formal request?
-
is there a defined channel via which that “compiled Feature Request” must be submitted?
Thank you.
3 Likes
It varies by project. Ubuntu is merely a distro – a compliation of thousands of upstream projects.
Best practice for most feature requests is to ask upstream directly using the format/method/channel preferred by that project.
For example, ideas to improve the Gnome desktop should generally go to the Gnome developers.
Ubuntu doesn’t have a “customer service” desk to route feature requests to the correct upstream. Figuring out who to contact and how to phrase it is generally responsibility of the requestor. Folks who have done research on the project and the feature generally learn these along the way.
-
Volunteers here at Ubuntu Discourse are often willing to help do some detective work to find the right upstream. Their willingness is usually proportional to the amount work the author is also willing to put in.
-
Paying Canonical customers should ask their support contact for assistance.
It’s also possible to file a “wishlist” bug on Launchpad. However, there is no guarantee that anyone will forward the bug to the right project or act on it at all. Forwarding is done by volunteers, and more volunteers are always welcome. Some projects pay attention to wishlist bugs. Some do not.
6 Likes
So, the channels are …
For Commercial support,
- approach the defined support contact; and
For Community support,
-
if issue is related to known non-Ubuntu package, approach the package developer directly thru their own specified channel/process;
-
if issue is related known Ubuntu package, approach Community “experts” thru the Lounge to help clarify and amplify specifics related to the request, at which point such a request would be directed to the channel that such experts identify as most appropriate; and
-
if issue is related to a Feature or function for which the Requestor is … unsure as to its “placement” in the overall eco-system … or … uncertain as to the best way to describe or implement the requested Feature, again approach the Lounge with an initial outline explaining the problem being addressed, rather than the specifics of implementation, but also accompanied by the Requestor’s conceptualization of where and how they believe the Feature would be integrated into the overall scheme of things, at which to Community experts would again clarify and direct as appropriate.
Woud that be a reasonable paraphrasing of pathways for submission?
3 Likes
You idea is to set up a formal, defined channel for presenting ideas. I think that you missed something.
Volunteers here at Ubuntu Discourse are often willing to help do some detective work to find the right upstream. Their willingness is usually proportional to the amount work the author is also willing to put in.
Are you offering to be the lead in a group of volunteers who will be the access point or portal that opens the way for someone to present their idea to the right project committee?
It seems to me that your “paraphrasing” is more of a re-phrasing that puts all the work on others. Are you willing to do detective work and become such an expert as you refer to?
Ahh, brainstorm. That was a fun experiment.
My personal opinion is that ideas are cheap. If you want something to change in Ubuntu, the most effective path is to either design and build it yourself, create a demo or proof of concept, or convince (or pay) someone else to do so.
A concrete example: I built snapupdates.popey.com because I was frustrated that the official Snap Store frontend felt stale and out of date. The act of building it — rather than just requesting it — apparently caught Canonical’s attention. They’ve since updated the official site, incorporating features I’d implemented, and it even got a mention in Mark Shuttleworth’s keynote at the recent Ubuntu Summit.
I’m fairly confident none of that would have happened if I’d simply posted a wishlist item and hoped someone would pick it up. Demonstrating the thing is far more compelling than describing the thing.
That said, not everyone has the skills or time to build something themselves, and that’s completely understandable. Launchpad bugs and Discourse threads do have value for surfacing ideas — but pairing them with even a rough mockup, a proof of concept, or a clear offer to help with testing or documentation dramatically increases the chance anyone acts on them.
Also, worth noting I 100% used AI to build snapupdates.popey.com .
4 Likes
Thank you everyone for the ideas and input to this thread
What about the ubuntu desktop team? is that still a road
to implement changes or other Ubuntu flavours?
My main goal to start this threat is to make it easier for everyone
a perfect harmony between the Devs and the ubuntu user community
and contributers.
I love your new snapupdates website, wich i also missed as feature we used
to have to list latest snaps, we use your rss at #techrss on libera aswell
1 Like
Sure. Up to a limit.
e.g. if the ‘ideas’ are:
- Stop doing something I don’t like
- Replace core components with something else
- Ship new applications or features in the default install
Then there are significant implications, depending on which of these, and what the ideas are.
e.g.
- “I don’t like snaps, don’t ship by default” - that ship has sailed, and anyone suggesting this will have near zero chance of success.
- “Don’t ship AI features in the next release” - the company and engineering team have clearly set out their stall here. Get involved in the conversation but don’t say “Don’t do that” because that is a hollow request. Bring data and evidence, and make a compelling argument beyond “I don’t want it”. (and don’t say “nobody wants it”, because again, I’d refer to getting data).
- “Add this other app to the desktop” - that requires maintenance from the desktop and security team. Someone has to pay for that. People need a very compelling argument for this.
Finally, if you personally have something specific you’d like to ideate, please mention it now. Otherwise we’re just dancing around the topic.
2 Likes