|
|
|
|
|
|
by asermersheim
4024 days ago
|
|
|
We just found out about this thread 10 minutes ago, and we have been on reddit for the past 8 hours answering questions. We are stunned by the level of interest and feedback. We have been using git from day 1 in house for our version control and that will be available to the public shortly. We have been focusing on outreach to the local SF Bay area developer community, and we presented CopperSpice at the SF Bay Area Association of C/C++ users meeting in February. You are welcome to peruse the meeting notes and our slides: http://www.meetup.com/SFBay-Association-of-C-C-Users/events/...
https://docs.google.com/presentation/d/1Sxei-Em6cnYbE0Zj16j6... In terms of 'backing any of it up', the code speaks for itself. I am happy to answer any specific questions you may have. |
|
|
- You are based on Qt 4.x. Why? The 5.x branch is better in every respect (yes, bugs, but that's fixable). This project is breathing life into a version of the lib which really should be dead. I think this is a net negative for Qt.
- Why is this the first most of us in the Qt community hear about it? The project is basically coming out of nowhere, imposing itself as this shiny new thing when it has critical flaws and the only point of contact is an email address and a forum with 0 posts in it. Feels like it was developed in complete secrecy.
- (minor) Autotools build system, really? You're not going to get much respect about this from most Qt devs. Why not just use cmake?
- I'm concerned about the entire way this project came forward. You don't have a git repository. You claim you will but claiming things is easy - the question it immediately raises is why don't you have a git repository yet? (And this comes back to what I was saying earlier about developing this in secret).
The lack of a repository is the second most important issue after 4.x, I think. Git repos aren't just "the code". They're insight into how development happens (are commits clean and readable? is it easy to contribute?), insight into who contributes (is it a corp? how many people are working on this?), into whether upstream changes are being pulled down, etc.