Would it be '“baron” like in BeOS, or will Haiku follow the tradition and pick the name of someone with proven (sp?) “bug-finding” skills instead?
I have nothing against Baron, but I think that maybe Haiku’s devs could find a new “Baron” out there, among the not-coders in our beloved platform.
What do you think?
Would it be '"baron" like in BeOS, or will Haiku follow the tradition and pick the name of someone with proven (sp?) "bug-finding" skills instead?I have nothing against Baron, but I think that maybe Haiku’s devs could find a new “Baron” out there, among the not-coders in our beloved platform.
What do you think?
I vote “Axel”
I vote "Axel"
Mmm, I was thinking in not “using” actual Haiku’s developers… “it’s their job” to find/fix bugs after all 
I was thinking in Haiku’s devs voting/picking the name of “just a user” from our comunity, that has proven valuable in the bug-hunting fields.
Just a thought.
umccullough wrote:I vote "Axel"Mmm, I was thinking in not “using” actual Haiku’s developers… “it’s their job” to find/fix bugs after all
I was thinking in Haiku’s devs voting/picking the name of “just a user” from our comunity, that has proven valuable in the bug-hunting fields.
Just a thought.
Me! :-p
No, I vote Axel as well. Or have each file owned by its team leader - media apps are Marcus, etc…
Or stick with Baron. It might actually break some shell scripts otherwise.
Walter, of course. 
yeh I was going to say Walter I’ll bet :lol:
LOL@h_ank’s Bob link…you’ve convinced me.
MYOB, do you know of any particular shell scripts it would break? I don’t know much about shell scripting so I’m kinda curious how that could work.
I definitely like the idea of Axel being the default and team leaders’ names being used everywhere else, with a bit of Walter thrown in on items of special interest, and I am also utterly convinced that we all need to spend much more time and consideration on this crucial issue.
Kev
Walter seems appropriate.
Why not Adam? (I’m not religious, I just like Adam and what it represents)
Or… you can say that Haiku itself owns your filesystem.
Axel = Lexa maybe?
Just some ideas.
Doca
Walter, of course. :)
Walter works too 
…and is slightly more universal and fair to the whole team.
I vote for Axel
Axel
The only logical successors which come to my mind are lord, duke, earl, count, countess, king, queen, emperor, and imperator.
But I think the new user name should reflect that Haiku is open source, unlike BeOS, therefore “parliament” or “assembly” would be more appropriate. Slightly OT,but I think the New Zealand parliament is called “beehive” (due to the architecture of the building), we could make a “BeHive” out of that.
Or, how about a boring, but simple “user”? Or “root”, for the Unix guys?
And I propose that because a haiku has 5, 7 and again 5 syllables, all files come with 575 rights.
And I propose that because a haiku has 5, 7 and again 5 syllables, all files come with 575 rights.
What an impressive coincidence! :shock:
So the group can do anything, whilst the owner and everyone who isn’t included in the group may only read and execute? The idea looks interesting when read, but won’t work well when we finally get multiple user capabilities.
I vote Axel :D.
What about simply “you” ?
Since, after all, you do own your files, why give them to someone else?
And since Haiku is open source, it belongs to everyone, so even if I am using someone else’s machine, the system would still belong to me 
maybe you should get to choose your own 
root, haiku, parliament, or you are my votes. I think parliament is the most unique though ââ¬â it represents the fact that in the opensource world, all contributions are helpful and important (just like in parliament or the senate)
‘you’ is a bad choice. Why? Haiku will almost certainly be a multi-user operating system one day, and not everyone using a system will own the system files and such. ‘parliament’ and such don’t really work, I think. Your system is run by an administrator, not a legislature.
I think we should just stick with ‘baron’. It’s one of those little bits of BeOS that makes it BeOS.