Due to recent discussions in this forum here:
Myth No.1: "Geeklog is worse than [x] because they do not have a start-page for non-geeks"
So lets have a look at it, what is Geeklog? Geeklog is - as it says - a "Geek's Log". So it is not like Mozilla. Other teams might have some geeks in their team. We have _only_ geeks. The rest of the other teams are politicians, salespeople and marketing. We do not have a marketing team. We do not have a designer at hand. We are happy we have a logo! What a shame of course. But we do not have all of this. Does that make the CMS worse? No. Does it make it less accessible? Maybe. Probably some people feel turned away because of this. But to be honest, the features of Geeklog are as such (just take the permissions) that a non-geek might have serious trouble getting through it. I had trouble when I tried to understand it the first time. But still ... if someone would come and say "hey guys, I like your software, I cannot code, but I can make a great intro-site for non-geeks, I am sure I would pay the domain, probably the webspace and make sure that we get that running.
Conclusion: Confirmed, but ready to change, just throw ressources at us please, while we code!
Myth No 2: "Geeklog is loosing users because everyone thinks its dead! No-one knows when the next version comes out, nobody knows what features it will have!"
Well we are geeks but at the same time employees, fathers, husbands etc, we have other things to do than to market our own work by writing a blog on what we are currently working on. We are a small team. Look how many people contributed the majority of code to the last version 1.4.1.
I normally announce in the dev-list what I am about to do next as soon as I think it will take a certain time to complete and ask for input. But as people stated correctly, we do not write up what we expect to have in the next version. Why? Because we do not know. We never sit together in a conference and discuss this. I personally prefer to tell what I have done instead of telling what I will do since saying what I will do might be as well a weather forecast. Many things that I tried to do in code in the past turned out to be impossible. So is geeklog loosing people because of this? Well I have never ever installed a software because of what it might have in the future. I look how active the forum is. I look if the last release or bugfix was more than 2 years ago. I look if there were significant improvements in the last release.
Conclusion: Plausible for some, busted for the majority.
Myth No 3. "Geeklog has a too long release cycle!"
Personally I would like to see all features that are in CVS already since some time live. But on the other hand, I _hate_ upgrading my websites. There are too many files, settings, things I forgot, hacks etc to watch out for. In addition to that, many other people complain if the version are released too quickly. That is also one reason why we have plugins, so other people can release new versions w/o the core code to be pushed out too often. So if you think its slow, you might not represent the majority of the users.
Conslusion: Plausible for some, busted for the majority.
Myth No. 4 "The Core team is a Gentlmen's Club that does not let other people in"
What? Sure, Confirmed, only because I LOVE beeing in clubs!
Well, I admit that we do not have a sign on the door that says "Core developers wanted". But we do have a mailing list and a forum where we talk to many developers. But finally, we are people who work together. And we have to get along. If we do not get along, GL goes nowhere. So if people want to become core developers, there are many criteria. You have to write code that is applicable for many, not just for you. You have to show that you write code that fits the coding standards both in quality as we as in style. You have to have a style of communication that everybody in the core team is comfortable with. You have to stick to announcements and promises and to a certain degree to timelines as they are announced. If one of those fail in the eyes of one of the core team or maybe more, you better start forking.
Why that is like that? Because many cooks spoil the code. And only the amount of fixes I have to do to user-contributed code is enough to make me think to stop doing it. Other core devs are already angry at me once a month because of the mistakes I make in my own code, so I rahter care about that. Only the list of things still amiss in the gloogle summer of code projects that make a "perfect system" out of a "well-working code" show where the issues are. Read the dev-list and you know what I am talking about.
Finally, you can ask "Can I be a core guy" and get a straight answer. You can ask "why not" and might receive none at all. I wonder how many people who ask you "can we date/be friends/work together" get a straight, honest, and _written_ answer from you. We do this here because we like it. If we are stressed out by someone asking in a rude way why this or that does not exist or does not work, we do not have the impression if it gets more fun when this person becomes a core dev.
I also wonder how many other teams in the same size handle that differently. And what their turnover in team members are. Finally all mistakes in the code have to be reset by Dirk and not the person who messed it up. And to that note, the last person who got kicked out because there was simply too much to clean up after was a girl. So we had a girl as a core dev, just not for a long time. One last question is why we need more core developers? If we have trouble today coming up with a planned featurelist for the next release, how can that become better if more people contribute code? The people who want to become core devs just want to see their own code in the core. They do not want to join because they want to write documentation of existing code, manuals or other things that are good to have besides the code. So it only become more complicated with more coders.
Conclusion: Busted. Just because we dont roll out the red carpet for you, does not mean we are elitist asocial women-hating selfindulged bastards.
Myth No. 5 "Geeklog is a Sellout because Blaine posted that NexPro article on the frontpage".
Well if Dirk or someone else would have posted an article on how Geeklog is becoming bigger because there is another company supporting it and oops - they are selling that product? - well nobody would have cared. People whould have said "wow great, more support/applications/whatever for GL! Now Blaine wrote it... well he is the epxert on the topic so he better write that text. We are not fake enough to write advertorials here. GL is for/from Geeks. Where is my marketing team?? :kickcan:
Conclusion Busted. You sell out if you sell something. GL does not sell anything. We take donations and bounties. Its all in the wording, isn't it? Where was that marketing book again?