Stefan, Nothing says that Apache is the right place for all projects. It definitely isn't. Apache isn't even the right place for all developers. It may not suit you.
In my own work, I contribute to some projects which are small and which aren't important enough to have a large community. I control some of them myself according to my whim. Or I am happy to cater to the whims of what others would like. I also contribute to much larger projects which are big and are very important. Some of these systems underly large-scale commercial systems and it is critical to know that the projects will survive me or any other contributor leaving the project. It is also critical to know that all of the licensing is done well and there won't be any surprises if these projects are used. >From your descriptions of your project, it sounds like it may be better in the first category rather than the second. The biggest clue is that the Apache social and licensing machinery doesn't make any sense in the context of your project. If you needed the things that Apache offers a project, then those rules would make massive sense. Since they don't make sense, we can infer you don't need them. Projects and developers often grow and change, however, so having a taste of Apache may be a good thing for you to keep in the back of your mind. On Mon, May 18, 2015 at 11:35 AM, Stefan Reich < stefan.reich.maker.of....@googlemail.com> wrote: > Lots of rules, Americans in the background... I don't see that it works. > > Why don't we spend our time just PRODUCING SOMETHING? > > All you'd have to do is connect programmers to projects. Simple. Why all > the rules? > > Cheers > Stefan >
