On Tue, Jun 21, 2011 at 7:08 PM, Aleksandar Kovac <alex.open.design@...400...> wrote:
On Jun 22, 2011, at 7:48, Josh Andler <scislac@...400...> wrote:
if Inkscape is around in 2111 in some form, I think it will just be called Inkscape.
Just Inkscape is the goal then! :) but seriously, youre right, inkscape is the key thing! version is an important but secondary information.
Just Inkscape is indeed the goal! Version numbers are very secondary to the dev community. Unfortunately they're much more important to the average user. If cost is of no issue, do I want a 1995 Honda Civic or a 2011 BMW Whatever? I'd go with the 2011 hands down. 1995 BMW Whatever vs 2011 Honda Civic, again... 2011 wins.
There's no box where inkscape's version number must be stuck in big letters in its glory to sell more. Inkscape is not a part of proprietary software marketing mess, and I we should stop thinking about the version number as an element of branding and guide our thinking towards it's purpose, what it means, and how this info should get to users and contributors.
We really are part of the proprietary software marketing mess mentality. Is it our issue? Only as much as other software makes it so. With Chrome & Firefox switching to rapid release cycles, IE will start to be viewed as "immature" by new users (number-wise). Features are secondary to the formula of "how long have you been making this product and what version are you on?"
For Inkscape it is important branding-wise to establish that the software is mature and we've had a lot of releases and progress since the project began. I guess the problem really is we're not looking to get sales, we're looking to offer really solid alternatives to the industry standard tools, which can empower users, with the bonus of it being at no cost.
We need vintage, let's use a timecode that's been mostly stable for a couple of centuries or so. ;) YYYY-MM-DD (i believe that this numbering can even be simply and exactly translated into any calendar writing style on this planet, depending on the culture). It is a human timecode! linear, lean and simple and, if there's a need for finer divisions, those are ready, too. hh-mm-ss. ;)
Then, it seems we need an indication of 'stability'. And, from what is visible in the duscussion there are 3 main 'states' of inkscape to be marked. How about colors? Red, yellow and green. Colors seem to be tested and stable since, well... Easily translatable. You can paint it, you can write it's name... and these three are globally recognizable too. Green - go! It's fine and safe! Yellow - you can try but it's better to wait a bit with this one. Red - stop, this is not for you. ..its for those who know ;)
Let's say I thought you were being serious in any way... The discussion of handling branches in no way affects users downloads. There is never anything for the average user but "here's the current supported and recommended version". That's it. What happens on the development/testing side of things vs the end-user releases is completely different.
Cheers, Josh