Of course, I know there are differences, and yes I think we need at least a few iterations and cooperation of different projects.
How I really like to work with such projects is that I roughly think about a solution, then experiment, see what works and finally when I have a working POC I involve people and we work together on finalizing stuff. I strongly believe in "Emergent design" and it is based on the assumption that (especially in open-source) experiments, trying different things and sometimes failing - but learning from that and moving forward - is the best approach. I think this kind of project is perfect for such approach - where you can gradually add groups of projects that do things similarly and then incrementally add new patterns.Taking into account that it is not "business critical and the whole cycle of board reviews takes many moths, it seems ideal for such approach. This will undoubtedly take a while to complete and sort out all the issues and since I am doing it in my free time, I hope I can engage others - especially those who seem to be vitally interested in making it work. I do not have "all answers" yet (or even I have almost none now) and I hope not only myself but also people from other projects can be involved and we can all learn something new. Having all answers upfront is a bad idea for such kind of community project, where I hope to engage others. > By the way, how are you going to let people know about the changes to the > reporter tool? Speaking of others being involved in the project- would you like to help with that part? I am happy to hear some suggestions for that part especially? What do you think will work best? Any ideas there ? J. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
