General Feedback...

[VitalBodies]

First of all I really like the program/project!


Additionally I would like to give some general feedback.

The current interface looks nice and will support a greater density of features.
One comment about the interface is that it tends to mask some of the power of the program while at the same time making the program both more powerful and easier to use.
To have CURRENT videos showing someone (well versed in MakeHuman) using the program would really demonstrates the power of the program. I saw some earlier videos on Youtube by doing a keyword search for "MakeHuman".
Some of the videos helped to show just how powerful the program is, that is hiding under a new simpler interface.
The videos (at least for me) invited more experimentation and showed just how custom/detailed/individual of a human one can make.
Very nice.
Embed some into the blog...

Eventually it would be nice to have the deb files for Ubuntu/Debian located where they do not cause a warning when Ubuntu does an update of MakeHuman.
I am not sure if that is the Launchpad of somewhere else as I am not an open source programmer.

A few more ultra high quality renders (Eye Candy) might also be nice to have on the site and blog where you can not miss seeing them. I think this helps artists decide what the limits of the program are, and if they are high enough to bother using the program and overcoming the learning curve.
They also create some inspiration and what a dedicated artist can achieve.

No matter what I suggest, I know you are all busy and are making headway on every front (and there are many) and that you most likely thought of all these things any way.
But in support, I offer my humble feedback...

UPDATE: I mentioned on another post to consider using open source fonts and file formats where possible. An example might be TIF vs PNG:
http://en.wikipedia.org/wiki/Tif
http://en.wikipedia.org/wiki/Portable_Network_Graphics

[joepal]

Eventually it would be nice to have the deb files for Ubuntu/Debian located where they do not cause a warning when Ubuntu does an update of MakeHuman.
I am not sure if that is the Launchpad of somewhere else as I am not an open source programmer.

This can only be avoided if either a) the packages are accepted into an ubuntu/debian/whatever official package repository or b) the user manually accepts and install a key file with the signature for the repository we're currently using. The same problem and warning arises with all third party repositories that are not part of the ubuntu official servers (medibuntu, virtualbox...), and basically means "hey, you're using a repository other than our official ones, are you sure you know what you're doing?".

As for solutions, for a) this is not likely and not very practical with a package updated nightly. Once makehuman is released as a final stable release, this could be discussed though. For b) this is possible but not trivial for the common user. It would include importing a key file, probably on console prompt, and the only thing the user does by that is saying he doesn't care whether the server is authenticated or not and is prepared to believe that the server is what it says it is without further warnings.

Anyway, for now, I'm inclined to leave the error message as it is to further stress to potential users that this is not finished code and that they use the stuff at their own risk.

[VitalBodies]

Eventually it would be nice to have the deb files for Ubuntu/Debian located where they do not cause a warning when Ubuntu does an update of MakeHuman.
I am not sure if that is the Launchpad of somewhere else as I am not an open source programmer.

This can only be avoided if either a) the packages are accepted into an ubuntu/debian/whatever official package repository or b) the user manually accepts and install a key file with the signature for the repository we're currently using. The same problem and warning arises with all third party repositories that are not part of the ubuntu official servers (medibuntu, virtualbox...), and basically means "hey, you're using a repository other than our official ones, are you sure you know what you're doing?".

As for solutions, for a) this is not likely and not very practical with a package updated nightly. Once makehuman is released as a final stable release, this could be discussed though. For b) this is possible but not trivial for the common user. It would include importing a key file, probably on console prompt, and the only thing the user does by that is saying he doesn't care whether the server is authenticated or not and is prepared to believe that the server is what it says it is without further warnings.

Anyway, for now, I'm inclined to leave the error message as it is to further stress to potential users that this is not finished code and that they use the stuff at their own risk.

I did not notice being offered a key but I will watch for that. You see quite a few warnings on the forums about installing software that gives you warnings...
Not sure what the Launchpad offers but might be worth a look, if you have not checked it out. https://launchpad.net/+tour/index
Not sure that would help or even relate to the warnings.

[joepal]

I did not notice being offered a key but I will watch for that. You see quite a few warnings on the forums about installing software that gives you warnings...
Not sure what the Launchpad offers but might be work a look if you have not checked it out. https://launchpad.net/+tour/index
Not sure that would help or even relate to the warnings.

No, you're not offered a key, you never are. The user will have to take the explicit steps on his own initiative to remove the warning. For examples on how this look on other major software sources, see

http://www.virtualbox.org/wiki/Linux_Downloads (scroll down to debian instructions)

https://help.ubuntu.com/community/Medibuntu (at add the repository)

Now, none of this applies to the makehuman nightly repository since there's no way I'm paying 200 euro for a key file from a certificate authority, and with a home-produced key file my guess is you'd get warnings anyway.

I guess we could move to PPA/launchpad instead of hosting it on our side, but I doubt it would be as easy since I'm using two build machines to automatically upload debs and update package files via NFS.

[VitalBodies]

From your position you see and know all that you do.
My position was from the view point of removing obstacles for new users.
Not so much for the nightly builds but the end user version.
I agree, a key does not seem like the best use of $200 or a real solution.

Being new, my view is pretty limited and the number of vantage points I can look from are limited.
Yet to offer feedback is fun and can be supportive.

At the same time, you folks have many many view points to balance and gain from - time, money, equipment, timing, resources and on and on.
The Launchpad came to mind as a way to automate things and expand but at the same time is one more thing to learn.
Intuitively the PPA/Launchpad seemed like it can offer support that you might not hardly know you need, just when you need it down the road when everything gets really overloaded.
Might have been the perfect solution, or might not work for the way one thinks, the time to invest or ones current set up or who knows.

If your two build machines could automatically upload to the PPA/Launchpad, this might have been a nice solution.
Plus you would be in a position for the ever heavier server/support/bug reporting/code exchange load as MakeHuman gets more popular.
The countless resources the launchpad offers for projects combined with advanced tools for tracking/communication/interaction, add to that it was free - for open source projects.
Somehow it just seemed like it would make things easier, especially over time.
But only you and your team would know one way or the other.

The fun part is that we get to give feedback and offer suggestions and you/your team get to be at choice and do what is best - what ever that might be.