![]() Sample groups: the way the samples are mapped is okay, but if you do it like that, allow grouping them and minimising groups (like a group of layers in gimp or photoshop, or like the beat and bassline editor) Goals: Take a good program and set your goal to make it better that (f.i.: fl studio) ![]() make the images bigger, I know it would make the package bigger, but it would make editing them also simpler. Skinning: make it go deeper, make the standard skin look slicker and less playfull, make icons smaller. the real programming, and the things around it. To start I would like this to be divided into two groups. In general everyone (even users) can submit ideas, developers can then suggest solutions, and give it a like or dislike function.įinally the head also should provide guidelines (just like was done with the wiki) I’m not saying HEAD are more then subgroups, we’re a community not a factory, but structure is needed, else the project will explode in non-coherent side projects)īecause development can’t do everything at the same time make an ideabox.Īdd an idea shoutbox to the website and make an interface so developers can vote and suggest (like the ubuntu ideabox.). Subgroup (these recieve the newsletters which include shortterm goals) SubHEAD (this involves 2 or 3 people of every subgroup, they interact with the head and eachother and send newsletters to the members of there subgroups) HEAD (few people who set the guidelines and future goals) ![]() In my opinion the general structure should be like this: Second, use subgroups, I know we aren’t making a whole OS but artwork-people don’t have something about discussions about the implent of delay codes. Now I’m not a part of the ubuntu development group,only artwork (so I don’t know if you can do something like this with codewriters). At ubuntu we set a goal and give it a deadline, people hear from it by newsletter and start working, we post the pictures online (flickr)and after that we start rating them (and commenting). I’m not going to write a list of points here, it would be to compicated.įirst, set short term goals that are thight (f.i.: add velocity). The first is one about the structure of the community, the second is about the program itself, and the third is about marketing and getting the word out. We’ve got ourselves a foundation for a great program! Although I must say that what we have up till now is awesome, major things have already happened. The things that great are already done, therefor they don’t need this special attention. That list of things stands below.īUT, before I start I want to say that this list, is one that summarizes the improvement points of LMMS. I opened Tomboy note and wrote everything down of which I think improvements can be made. So I’ve looked at FL studio one more time. When I look at LMMS’s community I can’t help to see some things of which I believe they might work better on another way. So this isn’t the first community I’m in. ![]() You should know I’m a part of the Ubuntu-artwork group. But we all know this way is going to long and hard. So I might not see the whole picture, nevertheless I think LMMS have GREAT potential to become worthy competitor for things like Renoise and FL-studio. Hi there, I’m using LMMS intensively only for a few weeks.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |