Touch maintainer members from inside. They have great insight but somehow seem to stop working for the project.
People especially who made these interviews (maintainers) know there are some infeasible aspects found in FRAME and the intended people do not want to use FRAME (at least until these points are improved)
and since these bleeding issues not solved, or even mentioned most of the maintainers stopped working for the project
Re ask their opinions on what to do next (be it re thinking how the user needs are formalized, developing new architecture methodologies and how we do things in EA) and restart discussions around some points, follow up these issues with all parties (but individually) until they are fixed.
Many things are beyond the project lifespan (6 months) and this is actually work done for "maintenance" or the next FRAME NEXT project. I know this fact. so please curb my enthusiasm and lets find the most realistic one.
Make very frequent telcos with everyone, (vincent willi holger richard, austriatech)
There is problem in maintainers telcos. nothing is being seriously discussed / addressed, or things move VERY slow. to break this, the telcos should be done with individuals, one to one basis.
There is a lot of work load on Benjamin. I might help with technical issues faster.
I learned how to make bulk changes in the current Repository and i am willing to learn more about using EA.
I want to establish better contact with Benjamin and help him modifying the model. With no/little help from Sparx this could be an acceleration point.
Go over the interviews with Richard, find answers to existing problems, create solution / defense for un addressed issues
Contact the interviewer (Maintainer) with the findings from Richard.
Touch maintainer members from inside. They have great insight but somehow seem to stop working for the project.
People especially who made these interviews (maintainers) know there are some infeasible aspects found in FRAME and the intended people do not want to use FRAME (at least until these points are improved)
and since these bleeding issues not solved, or even mentioned most of the maintainers stopped working for the project
Re ask their opinions on what to do next (be it re thinking how the user needs are formalized, developing new architecture methodologies and how we do things in EA) and restart discussions around some points, follow up these issues with all parties (but individually) until they are fixed.
Many things are beyond the project lifespan (6 months) and this is actually work done for "maintenance" or the next FRAME NEXT project. I know this fact. so please curb my enthusiasm and lets find the most realistic one.
Make very frequent telcos with everyone, (vincent willi holger richard, austriatech)
There is problem in maintainers telcos. nothing is being seriously discussed / addressed, or things move VERY slow. to break this, the telcos should be done with individuals, one to one basis.
There is a lot of work load on Benjamin. I might help with technical issues faster.
I learned how to make bulk changes in the current Repository and i am willing to learn more about using EA.
I want to establish better contact with Benjamin and help him modifying the model. With no/little help from Sparx this could be an acceleration point.