stahta01:
From your lack of submitting patches can I assume you have no plans to submit patches in the future?
Well, as you can read in my posts, my intention in this thread is to discuss about design decisions about C::B. Decisions take place before implementation; I cannot tell you what I could program before knowing what to program precisely. No need to do assumptions.
To all:
For the rest,
there are two kinds of replies: participating to a reflection, or doing something else.Personally, I am interested in replies proposing constructive things, in the theme of this thread: suggestions about the overall design of C::B.
Design aspects can be, for example:
- Integration of different frameworks by default or not. Which ? How ? From setup or after install ? Using help files and how ?
- Additional possibilities by plugins, by integration ? A mix of both, and how ?
- Participation of users. What opinion can be taken into account, and how ? Can different opinions and groups lead to forks, or distributions (internal or external) ?
- Choices about priorities. Documentation over code addition, or debugging, or new platform adaptation ? What is more efficient in a long term ?
There are many things to discuss about design.
Some are details, others are structural.
Good decisions can only be taken after a wide discussion, reflection and synthesis. Otherwise, I see no future.