[needs-packaging] StageLight Basic - a DMX512 stage lighting & device controller and interface

[Tree MendUs]

URL:
http://stagelightbasic.sourceforge.net/

Description:

StageLight Basic is simple easy to use lighting scene editor and sequencer designed so anyone that has operated a basic lighting console will be able to learn how to use it in about 10 minutes.
It has been designed for schools, churches, traveling performers, shops, homes (Christmas lights anyone), and really small theaters.
Using the DMX4Linux drivers and possibly some others it will have access to a variety of DMX512 interfaces, including some freely available parallel port designs.

StageLight Basic is exactly what it says - BASIC! It is not meant to be a whizz bang, do it all program with lots of bells and whistles, it is designed to be basic and simple to use. This should ultimately lead to reliability due to its simplicity. Over time features may be added, but the ultimate goal is for stability and simplicity of use.

useful links
DMX4Linux drivers at http://llg.cubic.org/dmx4linux/
DMX512 control protocol at

StageLight Basic is being developed on the GNU/Linux operating system using the FLTK Graphical User Interface Library and the DMX4Linux Hardware drivers.

SLAVE Lighting (previously Light-n-Easy) has released StageLight Basic under the GNU/GPL Licensing from Version 0.0.13 and the project has been moved to Sourceforge and can be found at http://sourceforge.net/projects/stagelightbasic/
SLAVE Lighting has started working on a new advanced version of StageLight aimed for more commercial situations, and has discontinued major work on StageLight Basic but has released it to the GNU/Linux community instead. SLAVE Lighting will continue some development on StageLight Basic as they feel that it is a worth while project.

License: GNU GPL

Notes:
also http://sourceforge.net/projects/stagelightbasic/

[Chris Coulson (chrisccoulson)]

Instead of touching up your bug reports, why not have a go at packaging some of these instead?

[Tree MendUs (tree-mendus-deactivatedaccount)]

Thank you for the suggestion Chris.
Welcome to you joining of the Bug Squad last month.

1a) re packaging

Before now, I have been looking for, and finding some information for how to do packaging.
e.g. https://wiki.ubuntu.com/PackagingGuide/Complete
I have watched a few videos (Daniel Holbach).
I was even looking at how to do packaging even before I realized that "needs-packaging" request system on launchpad existed.

How ever, I am not sure that I have learned enough, or that what I have learned is what I need to know.
I am interested in doing packaging at launchpads PPA, where it is possible to generate packages for various CPU architectures.
Another advantage of PPA for me is that it is a standardized way to do it, and I don't have to do any further research to gather a kit together to do it - as there appear to be several alternative methods/programs, for each step, and different ways of setting up one's own PC to do it..

1b) MOTU team - multimedia
https://wiki.ubuntu.com/MOTU/Teams/Media
Their page has the following statement;

"Try to get every package we find in the web to get included into Ubuntu's repository where possible. Our goal is to provide YOU with as many multimedia related software as possible."

I believe that this MOTU team would benefit from and appreciate, the work that I have done submitting needs-packaging bug requests, because a significant percentage of the requests are for multimedia programs. e.g. this one for handling stage lighting. Topics have included GUI front ends for transcoders, video editors, audio editors, capture programs, voip programs, speech related programs, graphics, 3D image and information, medical imaging systems, 2D and 3D CAD (BRL Cad is exceptionally good), and more.

But there are other MOTU teams who (I imagine) would be interested in getting (asap) the other needs-packaging bug requests I have supplied.

1c) An improvement to the needs-packaging system would be if the submitter could suggest a category for the program, which would help direct the request to the appropriate MOTU team, whose expertise would be most suited to assessing the request, and processing it speedily.

I have tried to make this easier for the bug triagers, by using related words in the tags field of the needs-packaging submission. But sometimes, somebody sees fit to remove them (and usually doesn't explain why).

2a) more that I am thinking of helping with - backports

I would also like to do backports, so programs can run on older versions of Ubuntu on machinery which is a few years old.

But apart from issues with confidence (which is not always helped with this bug system), I do not think that packaging is part of my current skill base, and would prefer to avoid risk of (further) trouble by making sure I am quite familiar with procedures/processes and am well practiced (having done some example exercises), before I begin a foray into packaging.

2b) more that I am thinking of helping with - bug handling

https://wiki.ubuntu.com/BugSquad
https://wiki.ubuntu.com/BugSquad/KnowledgeBase
https://wiki.ubuntu.com/Bugs/Responses
https://launchpad.net/~ubuntu-bugcontrol/+members

3) Insecure lifestyle prevents me from...

[Brian Murray (brian-murray)]

*** This is an automated message ***

This bug is tagged needs-packaging which identifies it as a request for a new package in Ubuntu. As a part of the managing needs-packaging bug reports specification, https://wiki.ubuntu.com/QATeam/Specs/NeedsPackagingBugs, all needs-packaging bug reports have Wishlist importance. Subsequently, I'm setting this bug's status to Wishlist.