I welcome, and encourage everyone to participate in this discussion. If you do not participate, we can only assume you concur with what we come up with.
I do not wish to impose my thinking on this group, rather I really want this to be a group action. My thinking for the scope of activity for this group is as follows:
We decide, as a group, what base modules to include in "baseline" DruForum. Each module would be subject to a cost/benefit analysis to be ultimately included. We don't want to spend a lot of time (or $$) on this aspect, although if it is a module most users of the result would want, it makes sense to leverage our resources and jointly fund the 'activation' or 'integration' for the benefit of all rather than each paying for the work separately.
We decide, as a group, on the basic format and construction of the end result. Although some of this is obvious I feel it is important to codify. For example, I suggest we create separate modules for groups of functionality. I suggest the functionality is designed around objects that then are 'connected' to objects in netFORUM (rather than co-mingling the object and the connectors), etc.
We also offer suggestions for functionality not currently available and vote on the ranking of desirability. Each customer member to have an equal vote and each developer member adding knowledge to the discussion and helping us brainstorm the processes.
I suggest a RAD, or 'continuous improvement' approach wherever feasible so we start producing usable code as soon as possible. Obvious functionality should be approved rapidly and worked on quickly. Of course, this brings up the issue of funding. We cannot fund anything before we know what it will cost and we won't know the cost until it is specified... etc.
We need to arrive at a reasonable compromise on this process.
Again, this is only 'my thoughts' at this point. I strongly urge you to participate in this discussion & make your voice heard. It doesn't matter what you 'contribute' in other ways but we need your brain power if we are to make this a success.
Regards,
Paul
Comments
Do the Ayes have it?
Is this arrangement satisfactory to all? This is the first step in moving this project along. Once we agree on this, we can move on to the baseline functionality.
Regards,
Paul
Regards,
Paul
Aye
Paul,
Sounds like a great plan- Thanks for pulling this together.
n
Greetings all, Sorry for the
Greetings all,
Sorry for the 2 week silence. The machine I use @ work had problems and I was 'crippled' by trying to repair that while keeping up with the work at hand.
I presume this scope is accepted by all and we can move on from here. I look forward to everyone's participation and hope all get everything they want from this effort!
Thank you,
Paul
Regards,
Paul
Additional note on the scope
Additional note on the scope of the group...
It is intended that this group becomes an ecosystem of customers and developers that "come and go" in terms of participation. The cooperative development process creates a reliable 'supply' of knowledgeable developers and insulates customers from the risks of single-source development while taking advantage of the best knowledge of both platforms. The group also acts as a marketplace for developers to
Regards,
Paul
Regards,
Paul