IIRC, there weren't any third party modules WIAB didn't use already. Also, in the long-term I am not certain that having the import code in the main tree is worth it, since the migration GWave -> WIAB is a one-time event (mostly).
On 17 January 2012 18:42, Kirill Kostyuchenko <[email protected]> wrote: > Hello Yuri! > > He wrote a message to wave-dev, that he could not add this to main tree, > due to 3dpary code such walkaround authorization code, GAE code and > something else. > > We could add Apache License heasers and format code style. > Just tell more details what to do. > > 2012/1/17 Yuri Z <[email protected]> > >> Another issue - Andrew published his patch on GitHub, but he >> didn't officially committed it as a patch to WIAB via the Review >> Board<https://reviews.apache.org>. >> So, officially speaking - he didn't make any contributions to Apache Wave >> yet. I believe it wouldn't take too much effort to make the patch comply >> with WIAB standards - like adding Apache License headers and maybe code >> style formatting or some small modifications. >> >> On Tue, Jan 17, 2012 at 7:50 PM, Yuri Z <[email protected]> wrote: >> >> > How about adding other options to fundwiab.com? I think Flattr >> > <http://flattr.com/>is the most convenient method for micro payments. >> > >> > >> > On Tue, Jan 17, 2012 at 7:36 PM, Kirill Kostyuchenko < >> [email protected]>wrote: >> > >> >> Please apply attached patch to the main index.html. >> >> >> >> I added links to WaveImport utility and http://fundwiab.com site. >> >> >> > >> > >>
