In a recent thread, Michael suggested moving other wave-related projects to Apache. Right now, the Wave Extensions Gallery: - Is hosted on my GitHub account (github.com/zmyaro/wave-extensions-gallery ). - Is technically “owned” by me (as far as GitHub is concerned; I am open to contributions from anyone). - Has all its bugs listed on GitHub's issue tracker. - Has its wiki hosted on GitHub (there is not a lot there, but there is still some content). - Has Google+ and Facebook pages that I run. - Has its official instance hosted on a Google App Engine app for which Yuri and I are admins. It is accessible from waveextensions.org or wavygallery.appspot.com.
Basically, I want to know everything that would have to change if the project were moved to Apache. Some specific questions include: - What is the process for moving the code from GitHub to Apache (and can you confirm I can still use git—I know WIAB had to switch to svn)? - I assume I would have to import issues into Jira. What is the process for doing that? What happens to comments on those issues? What about comments that reference commits? - Would anything have to happen to the Google+ and Facebook pages? - Would anything have to happen to the App Engine instance? - What would Apache own? What would I keep ownership of? - What else would have to change that has not been mentioned in answers to my previous questions? I apologize for sounding so worried and paranoid; I am kind of new to this, and I figure getting these questions answered here will help me (and anyone else who is new to this) understand the situation for current and future wave-related projects that we may want to make part of Apache Wave. Thank you! —Zachary “Gamer_Z.” Yaro
