Yep, WIAB is currently migrating to Apache, however, that is not a obstacle if you willing to contribute. http://www.waveprotocol.org has the info to get you started. From my personal experience, the best way to contribute is to install the WIAB server, run the web client and see what bothers you. It could be a missing feature or annoying bug. And the good news are - there are plenty of both. If you - decided to take on something - make sure to check the open issues at http://code.google.com/p/wave-protocol/issues/list to ensure that no one else is already working on it, and if not - open a new issue to let everybody else know that you want to get started. Well, the issues might migrate soon to the Apache Jira and the source to Apache SVN but i guess you got the idea. Don't be afraid to submit a patch, even if it is not accepted right away, you ll get constructive feedback, and IMHO, the only way to get a real feedback on your attempt to contribute, is by submitting a patch. Have fun!
2011/2/24 João Neves <[email protected]> > Hi everyone, > > I've been reading about the migration of Wave into the ASF's incubator > projects for a while and I've been really interested in messing around with > Wave for quite a while. My involvement with Wave has been somewhat distant > lately, although I've built a somewhat successful robot when Google first > announced it (Wikify) and I'd be interested in delving deeper into the > actual core of Wave. > > I've seen that at this stage the primary concern is probably switching all > the infrastructure around the project, but I'd like to know how could I get > started in getting involved with this project. :-) > > Cheers! > > -- > João Neves >
