| Re: [recommenders-dev] Introduction |
| Hi Zi, I'm not sure whether Doug already discussed the next steps with you. Thus, I copied my mail on this here and extended it a bit below to answer your questions. I also would like to continue this discussion on the mailing list to let the team know what has been discussed so far. >>>> Copied: Regarding the upload: The process is a bit more involved than "just upload" :) Your code has to be checked for IP violations by the Eclipse IP team before it can be checked in. Also one of the existing committers has to review the code and check that it satisfies Eclipse naming conventions etc. For a quick introduction to the IP process, please read these two pages: http://www.eclipse.org/projects/dev_process/ip-process-in-cartoons.php http://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf You and Zi should also read the collection of pages for new committers (especially the naming section) here: http://wiki.eclipse.org/Recommenders/CommitterResources So, how should we continue? I'd like to propose the following: 1. You put your code into a GIT repository hosted at eclipselabs.org/p/code-recommenders 2. One committer the reviews the code and checks it for accordance to naming conventions, legal stuff such as license headers etc, and potential privacy concerns. 3. In parallel, we setup a maven build for the project and create a build job for snipmatch. 4. If our review passed and the automated build works, you create a zip file from the repository and attach it to Eclipse's bugzilla. 5. I'll then initiate the official IP legal check. Please note that the legal process (step 5) may take up to 4 weeks until it got reviewed by the IP team. In the meanwhile, we (you, Zi, and committers) can continue development at Eclipselabs and start your committer election. If both processes completed, we move snipmatch to the repository at eclipse.org (moving to Eclipse.org before you have committer status doesn't make much sense since this would lock you out). Could you send me your and Zi's Google email addresses? I'll add you to the eclipselabs committer list and prepare a repository. IMHO we should move to eclipselabs as soon as possible and setup the automated build in the case we need emergency fixes. <<<<< Before we submit, though, I just have a couple of questions regarding the process. The main question I have is: Assuming there are no IP conflicts or other issues, how exactly will SnipMatch, a plug-in, be integrated into the core? I'm not sure I understand this question. Could you provide little more details on what exactly you wanna know or think of? Also, due to my lack of experience in the PDE, many features in the plug-in are implemented in ways that may be severely flawed or limiting. Will the guys on your end work with me to fix that, or are these problems expected to be addressed before submission? Sure! When we have access to code (e.g. hosted at eclipselabs.org), we'll look on how things got implemented and assist you on cleanup operations/provide feedback before we start the IP process. Actually, we have to review to code anyways before we start the IP process. There are also a few things more, I'd like to do such as using open-id (instead of requiring people to create a new account), adding a JAX-RS server front-end (so that we have a common backend for all webservices at Code Recommenders), moving from MySQL to CouchDB/Lucene or Jackrabbit/Lucene backend (common persistence technologies for all frameworks) etc. These things need to be discussed and best solutions have to be found. HTH Best, Marcel On 25.09.2011, at 08:26, Zi Ye wrote: Hi Marcel, Thanks, Marcel --
Eclipse Code Recommenders: w www.eclipse.org/recommenders tw www.twitter.com/marcelbruch g+ www.gplus.to/marcelbruch |