Hi all, Sorry for the delay in replying to this. Here are my thoughts on the questions put forth by Micheal-
1) What is the objective (just provide maven jars to a repo? fully mavenize the project? etc)? I am of the opinion that we should fully mavenize the project so that it becomes a standard structure, lowers the entry barrier for newbies and establishes a standard pattern for new modules that may come in. 2) What are the benefits of what we are proposing? Why should we move to maven? a. Lower the entry barrier for new comers b. Move to a standard project structure c. Make modules explicit and make it easy to develop and test individual modules 3) Who is really committed to work on this? Count me in. 4) What is the general approach for adding maven support (just writing poms? moving source around? etc)? I have tried both the approaches in past. Our final goal should be to move the sources into their own maven modules. But for the sake of least friction we can start with just writing POMs. Though we should not delay moving the sources to very late as that may cause more trouble than it may right now. 5) How will the development cycle of the developers who are not working on this be impacted? Let me put into 2 parts good and bad Bad – a. Temporary interruption of work when we move the sources. b. Getting habituated to the new project structure for non maven guys may take some time (not much though, still some time) Good – a. We will be able to support many more IDEs for development than just eclipse b. Being in standard format, project structure will be easier to comprehend c. Modular structure will promote modular thinking while developing new features d. Tests will be explicitly written in the test sources section and not in just a spate package e. Anyone can just build a particular module and test it along with other modules reducing the build/deploy/test times. 6) What are our deliverables? Other than the mavenized project, do we need to provide documentation or tutorials to show others how to work with the new system? a. Mavenized Projects b. Documentation explaining the structure to non maven guys c. Documentation to get started with development quickly 7) What are the various modules we would propose having and what is the purpose of each (simply stating that we stick with the current jars is not enough info)? I am not very through with the module structure but I think the following modules should be good to start and then we go on to split further if need be – a. Protobufs b. Model c. OT d. Wave-API e. Robot-API f. Server g. Console-Client h. Rich Text Editor i. Web Client j. Concurrency control k. Federation Missed something? 8) What group ids / artifact ids should we use? Group id should be – org.apache.wiab or org.waveprotocol.wiab Artificat ids are same as artifact names. 9) What are the timelines and milestones? TBD based on what we decide to achive. Regards, Rohit The diamond cannot be polished without friction, nor man perfected without trials http://mytechrantings.blogspot.com On Sun, May 1, 2011 at 9:24 PM, Michael MacFadden < [email protected]> wrote: > All, > > Let's start a new thread focused on planning out what a possible move to > maven would look like. I know it's easy to dive in to the code and just > start playing around, but if not done right, we are going to get a lot of > push back from others on moving to maven. We need to plan this out and > identify exactly what we intend to do, who is going to do it, how were are > going to do it, and when it will be done. The discussion of this should > happen on the mailling list, and the results of the discussion should be > captured in the development wiki (which I can set up). > > > The following questionnaire should help us get going. I realize that some > of this discussion has already taken place. I would suggest simply > answering the questions for yourself in this thread. If we need to discuss > a particular question lets start a separate thread for each question. I > don't want to distract people from filling out the "survey". Thanks. > > > ~Michael > > > Questions: > > 1) > What is the objective (just provide maven jars to a repo? fully mavenize > the project? etc)? > > > 2) > What are the benefits of what we are proposing? Why should we move to > maven? > > > 3) > Who is really committed to work on this? > > > 4) > hat is the general approach for adding maven support (just writing poms? > moving source around? etc)? > > > 5) > How will the development cycle of the developers who are not working on > this be impacted? > > > 6) > What are our deliverables? Other than the mavenized project, do we need to > provide documentation or tutorials to show others how to work with the new > system? > > > 7) > What are the various modules we would propose having and what is the > purpose of each (simply stating that we stick with the current jars is not > enough info)? > > > 8) > What group ids / artifact ids should we use? > > > 9) > What are the timelines and milestones? > > >
