Hi, I am very optimistic we keep up the good work we have done in the past. This discussion was very helpful to understand most of our interests. If you lead a open source project and a company and both is very mixed up, it is sometimes very difficult to know, if everything goes in a good direction. I always like to make people happy. That's why we are doing open source and free software, right? Linuxtag 2007 was very successful, I was so happy about so many interested people coming to our booth, that I even don't want to miss anyone and wanted to talk to everybody. But that was a wrong decision, because on thursday evening my battery went low and I had no chance to regenerate. The Linuxtag organization, the GUUG and the FrOSCon e.V. had organized free food and drinks on every day. Fantastic. I even missed the great talk of Tommi on saturday.
So this kind of reflection of the past is very helpful. Otherwise you will wake up in the morning and suddenly you see that all your developers, users, employees and business partners hates you, because you went in a complete wrong direction. I have extracted following plans from the discussion: * I keep project leader ship¹, I think my mother already decided this many years ago ;) * Ralph Passgang will take care of FreeWRT 1.0 maintenance, I will provide him with all information and hardware he need to keep the branch stable and secure, nobody then he is allowed to commit to this branch without permission from him. send him patches or ask for permission. * Phil Sutter will try to integrate brcm-2.6 for Netgear WGT634u We decide later if brcm-2.4 for Netgear will be dropped or kept, depending on the success of the port, when I release FreeWRT 1.1 I have one Netgear for free for any interested developer to help Phil to succeed with the port. * Brcm-2.4 in 1.0 and 1.1 is kept. I never said I will remove it. Do you know how many hours I invested to get this shitfucking code from Broadcom running with 2.4.29 on my first Linksys WRT54GS v1.0? I can't tell you, because my professor for my diploma thesis would then ask to give my diploma back ;) * The time to always compare with OpenWrt is over, therefore I need a new slogan, I decided to use existing "code" from my beloved mail client, the second reason more pracmatical is that we know have no ballpens to promote our project * I like OpenWrt. I worked in the team a long time and the developers are nice and skilled hackers, Open Source projects should help each others. Felix Fietkau is still very often helping us, he is a friendly hacker and I like his work There are some more ideas from other developers, but I am feeling they are either unrealistic or not part of our goals. If you want to get things running you can do three things: * pay money to my company and I get stuff realized for you * shut up and hack * get someone who will work for you and realize your ideas That's the way to go in most of the other open souce projects I know of, too. I like to thank Ralph, because I think he understood most of my intentions and described it very good. (freeness of FreeWRT) Here is a list of supported hardware I would like to suggest for FreeWRT 1.1: * Asus WL500gP 2.4 * Linksys WRT54G3G 2.4 * Linksys WRT54GL 2.4 * Netgear WGT634u 2.6 * Routerboard RB532 2.4/2.6 And now, shut up and hack. bye Waldemar ¹http://www.beepworld.de/members76/sweet-darling/namensdeutung.htm http://www.behindthename.com/nm/w.php -- All embedded development kits suck. This one just sucks less. http://www.freewrt.org _______________________________________________ freewrt-developers mailing list [email protected] https://www.freewrt.org/lists/listinfo/freewrt-developers
