Tag Archives: light ubuntu

lubuntu – how to get involved

Julian Lavergne from France posted ways to get involved into lubuntu on the mailing list of the project and I am reposting his suggestions here.

This is a quick summarize for people wanted to help on Lubuntu. In general, all tasks will be documented on the Subteams pages:

== Participate to the LXDE project ==
This is the most efficient way to contribute to Lubuntu. If you want a functionality, translate a package etc … you should directly work with LXDE.

== Create an artwork for Lubuntu ==
We don’t have an original artwork, and it’s an important goal for Lucid. Some works began on the LXDE forum, but there is a lots to do to create a complete set of artwork. Currently, it could be nice to have:

  • 1 wallpaper
  • 1 icon set
  • 1 GTK engine
  • 1 login manager theme (for lxdm)
  • Custom configuration for GTK theme in the session
  • 1 openbox theme
  • 1 banner for logout
  • 1 logo for the main menu
  • 1 background image for lxpanel
  • 1 cursor
  • Specific icons for lxpanel
  • 1 splash screen (for usplash or/and plymouth)

Please see https://wiki.ubuntu.com/Lubuntu/SubTeams/ArtworkSubTeam/Documentation for details.
If you want to work on artwork, you should contact the Ubuntu Art Team. There are a very good experience on making artwork for K/X/Ubuntu etc … It’s also important to work on the artwork, as a complete set. It’s better to submit a wallpaper + icon set + gtk engine together than separately.

IMPORTANT NOTE : We didn’t have currently decide the colors of the artwork. We should discuss and decide this on the next IRC meeting. But you can create some mockups to add them to the discussion :)

== Triage bugs on Launchpad ==
We need to manage bug reports for many packages (mostly, the LXDE core packages).
See https://wiki.ubuntu.com/Bugs/HowToTriage/ for an overview of the triaging on Ubuntu.
The current packages and bugs are here: https://bugs.launchpad.net/~lubuntu-packaging/+packagebugs
Most important to know is:

  • Is the bug is correctly affected?
  • Is the bug still reproductible by user in Ubuntu 9.10? By you?
  • Is there a solution/patch available on the bug? Upstream? In another distribution?

== Fix bugs / Develop features ==
If you want to work on a bug, you should affect it to you so people know you are working on it. If you want to implement a feature, or working on a patch, you should open a bug on Launchpad, so people can eventually help you. I’ll try to add a TODO list for packagers who want to help but want some mentoring or ideas (See https://wiki.ubuntu.com/Lubuntu/SubTeams/CodingAndPackagingSubTeam for futur information).

== Testing ==
We may have some ISO to test near the Alpha 1 of Lucid, it’s a good occasion to test if it’s working, and report bugs. You don’t need to know how to code for this, just use Lubuntu and report bugs/complain about it. You can also install a command line Lucid system in VirtualBox and install lubuntu-desktop package by “sudo apt-get install –no-install-recommends lubuntu-desktop”. Another way is to test a pristine lxde session by installing the lxde package, and see if no Lubuntu specific patch cause problems in a standart LXDE session. To report bug, do ubuntu-bugs the_name_of_the_package_affected. If you don’t know, use ubuntu-bug lubuntu-meta, we’ll triage it for you :) Testing (and reporting problems) is critical, because developers can only try to fix problems if there are reported.

== Improve the Documentation ==
Our wiki ( https://wiki.ubuntu.com/Lubuntu ) can always be improved. If you intend to do massive changes, please inform the mailing list before.

Feel free to add others tasks if you have any in mind. Some others tasks will probably appear in the futur on this mailing list or on the SubTeams pages. Also, you can ask any questions on any of those items on the mailing list.

Thanks in advance for your help :)