Re: [Arianne-general] Organisation & leadership

[<x51...@fe...>]

> > I see only one direction, but it is written nowhere, there are no
> rules about
> > how to reach there. Perhaps we should change this... read below.
> > 
> > > > No really, I hate rules. If I have rules to do my work, I need to
> > > > expect an obscene amount of money to do it. :)  ...  I will 
> > > > continue to ALPHA 2 release even if I have to do it alone. 
> > > > :-/ Perhaps I am not the best, but I am very persistent on
> > > > my work. 
> > > 
> > > This is the problem Miguel.  Leading a project with more than one 
> > > person requires some rules.
> > 
> > Well, but all the rules are obviously...
> > - "Try" to follow specifications.
> > - "Try" to follow design.
> > - "Try" to follow code style on a already written file.
> > 
> > And a new one.
> > - "Try" to not to use TABS.
> > 
> > And I mean try, because design is constantly getting outdate because
> of
> > new ideas. And none can stops a great idea. 
> 
> No-one wants to stop a great idea.  We want to stop it being *coded*,
> and added in to the codebase, prematurely.

I am not adding anything that isn't on the roadmap.
I dunno if you know what is coded actually on the code... but if you know, you 
should/could understand why I keep adding functionality, instead of 100% 
stability.

> > > > ... as project driver, it is my responsability to do what none
> wants,
> > > > to make code work, to write docs, and to organize work. 
> > > 
> > > The docs and the work organisation is 'setting the rules', 
> > > 'communicating the rules', and 'altering the rules'
> > > 
> > > The rules are there to help us.   To help prevent 2-week long
> > > discussions about things  like 'tabs vs. spaces'.
> > 
> > And do you think that it is a solution to say "You MUST use SPACES",
> > and if they don't use themm what? Anyway if someone want to write a
> > style doc as a recomendation, I will place it on the web page.
> 
> Better to phrase as 
> 
> "On the Arianne project, there are currently 10 coders on the project,
> and 
> more are joining every week.  So it is all our interest to ensure that
> we find 
> each others' code readable with the least amount of effort.
> 
> Please help us keep the code maintainable and readable by:
> 
>      * Using 1 tab as an indent.
> 
>        There are as many platforms and editors used as there are
>        coders!  Using tabs to indent means that the code will always
>        be correctly indented, no matter which editor is used, on any
>        platform.

Hehe, we have agreed that no TABS...

>      * <repeat for as many guidelines as we adopt>"
> 
> But there is no good publishing a style guide, if the project founder
> and 
> leader says - 'style guides are useless - everyone should be completely 
> free to do as they want''

You have to diference two personson me, the coder and the project leader.
The project leader should have never wrote this thread, and will never tell you 
not to follow and arianne doc, the coder, the friend, will tell you that he 
thinks that rules are useless on OSS, and you just need to supply a confortable 
way of working so people can feel happy about what he does.

> > > We want you to lead Miguel.  We also want you to lead well.  And to
> lead
> > > well, you need to accept that leading is more than just coding
> faster than
> > > the rest of us can keep up with.
>  
> > The problem is a ethical conflict between leading and commanding.
> > I can lead, and I do. 
> 
> You lead by example Miguel.  Unfortunately, two of your examples 'code
> in 
> haste', and 'anarchy's fine'

These are the coder's opinion.
And I don't say that "Anarchy's fine", Arianne has a small organization, simply 
that there is no a "What <devel>|<designer>|<RP> to do today?"
 
> > I show Arianne to everyone and try to get new people to
> > the project. 
> 
> This is salesmanship, not leadership.

No a salesmanship sell, I just try to get more people to the project. :)

> > But I don't command ( too much ), I don't like to say do this or
> > do that, if I were do that by someon I would really expect to be
> payed.
> 
> In a large, collaborative project there *needs* to be some common 
> objectives.  

*ejem* Roadmap *ejem*
 
> When it's for fun, it's even *more* important not have some folk undoing
> the 
> work of other folk - there's nothing worse than having your work
> destroyed 
> by someone else, when you don't have the consolation of saying 'Ah well,
> at least I got paid for it.'

Yes, I totally agree with you here. But no rules can't avoid that.

Euan: Do you want to drive the next release of Arianne?

                  Miguel Angel Blanch Lardin
 
             -- http://www.arianne.cx -- Arianne --
The free open source massively multiplayer online role playing game

nuclear cia fbi spy password code encrypt president bomb iran irak korea cuba
Ala yihad mosad kgb free freedom human rights yugoslavia kosovo ebola dna 
 
                    -- Echelon must die --