What is the most important in an open source project?
- The code?
- The developers?
- What the users think?
Well, I guess all of these things are important.
So, let's look at the installers on these accounts:
- Uwe's installer is simple code and works.
- Uwe's has been the most stable development resource.
- Uwe's installer is the most popular among novice users and gives the
least support.
- Joost's installer is difficult to understand.
- Joost is an expert, but disappears from time to time.
- Joost's installer is more popular among expert users, and works
without administrative privileges.
Now it is clear that it *does not* solve the problem if Joost extends
the installer with the features that Uwe's installer has. This might
make it more popular among users and reduce support, but the most stable
resource will *NOT* be able to fix bugs.
If Joost's installer should have a chance to become a base for team
work, the most stable and dedicated resource - Uwe - has be able to work
with it.
In my mind, it is clear that neither installer is perfect. But it is
*NOT* clear that the best base is Joost's.
Therefore, I think Joost's installer should be properly documented such
that other people can understand it. Also, it should be able to bundle
all components that Uwe's does.
And similarly, Uwe's installer should work without administrative
priviledges.
And when there is code that needs to be developed further, it should go
in the SVN so that others can help.
It is *ABSURD* that Uwe's code can not be put in SVN - this is EXACTLY
preventing team work.
Regards,
Asger
