Hi, Having followed up with a few people over the past few days, I think I have a good idea of what people want in the near term from the project (and, importantly, how much time people will have to help move things along).
Dave Neary wrote: > First up, what have we gained in the move? What new features are enabled > by the move to Verona, and what improvements does it bring in video & > audio quality? I'm still not exactly clear what Verona gives us that we didn't have with the old wifo. Vadim, could you give us an idea of what we can expect now that we've moved to Verona in terms of improvements? Some of the things I do know about are that the mediastreamer upgrade means that adaptive bandwidth/quality now works, a new mediastreamer means we should have better quality video in video calls, and > Then, what do we want to fix/stabilise before calling QuteCom 3.0? And > what stuff needs to be done around the project (site, docs, services)? > And what should our top priority features be? I'd like to see us do a release now that we have published Verona, and we have a buildable softphone. While there are no doubt bugs to be fixed before we can call it a 3.0, the software has picked up some major improvements that we should try to get tested. In terms of pre-3.0 things, I'd split them into 3 categories: Project roadmap, provide entry points for community to grow, and features & stability. In terms of tasks which we can distribute across a larger number of users, I would like to verify how well QuteCom works with different SIP providers, and catalog the config options needed for each of them. For a new user, I'd like us to document how to get a SIP account, testing your sound & video set-up, making calls to other users, how to find others, how to invite friends to join the network, etc. Ideally, I would like to see us have a drop-down box with a list of providers you could choose from, so you just choose provider, and insert username & password. No more mucking around with realm, gateway, proxy, etc. I would also really like to concentrate on streamlining the website for community contributions, and adding tasks to the roadmap which are high priorities for the project, but for which MBDSys doesn't have resources to do them - these would be great entry points for developers looking to develop a feature or improve the software and get involved in the project. For features, I'd like us to be feature equivalent with 2.2 in terms of the user interface, even if we add some interesting features in the back end. From what I can tell, Hold/Resume and call transfer have not yet been implemented with QuteCom/Verona. I think we need to get them done. In general, beyond specific features, I'd like to see us create and maintain a good project roadmap, containing the release criteria for the next release, the major achievements which will be the focus for the release after that, and the wishlist for the feature after that. I'd like to ensure that the roadmapping process is open, and I'll be kicking that off as soon as we make a release. Finally, in terms of stability, we need to establish release criteria pretty quickly. I don't think that we should include every bug we find as a blocker for 3.0, but we should ensure that our users have the best experience possible when they try the software for the first time. If we succeed at this, we will gain wider distribution & possibly inclusion into Linux distros at the end of the year. Does anyone have anything else that they'd specifically like to see addressed before we can call QuteCom 3.0? Cheers, Dave. -- Dave Neary dne...@free.fr Tel: +33 9 51 13 46 45 Cell: +33 6 77 01 92 13 _______________________________________________ QuteCom-dev mailing list QuteCom-dev@lists.qutecom.org http://lists.qutecom.org/mailman/listinfo/qutecom-dev
