Hello,
I must agree with DricuS.
As an experienced developer (must be ~15 years now...) I would also like to help in developing Media Portal. What kept me off was that there isn't a description of the concepts or architecture so that it is nearly impossible to get to know the software.
The second thing is, that the project pages are packed full of information, but it hard to actually find the useful stuff(which would be the concept and architecture description ;-)
To really start with helping, it would also be nice to have an overview about the current contributers and their respective roles: Who do I have to talk to if I want to do a specific thing in the project? The project planning site is a good start, but unfortuanately, the tasks are not described in detail, and are not assigned to anyone.. where to start...?
So for a start, I think it would be very helpful to separate the Media Portal and MPII pages, so that one knows what is relevant for which version. As a second step, it would be great to have a rough concept description, and a description of what features should be in the first release version. A use case diagram would be really helpful... and someone who feels responsible for these features and can take decisions
Maybe this seems very bureaucratic, but I really think this would help 'outsiders' to get into development of the project and develop the things that are really needed.
Ok, so much for (hopefully positive) critizism. So if I can help you (e.g. with helping you setting up the concept or architecture documentation), please contact me (e.g. send me a private message..).
I would really like to contribute to such a cool project!
Regards,
Michael |