Hi Sunil Thank you for your advice and attention.
The Hadoop submarine development team needs a separate repo for several reasons: 1. We have developed a separate submarine website to introduce the functions and features of submarine. The common practice is to put it in the gh-pages branch of the repo repository, automatically generate HTML code, and update the website. 2. We also want to associate github's repo with apache jira. It can automatically synchronize the status of the issue on github, and the comments will be automatically synchronized to Apache's jira. There are some other open source projects managed like this. Very good experience. Making these settings requires some administrative privileges with repo. 3. We also need to create different branches for different versions for version management. So, we need a separate repo repository. thank you for your support. :-) Best Regards Xun Liu > On Aug 16, 2019, at 5:25 PM, dashuiguailu...@gmail.com wrote: > > +1 ，Agree that independent development of submarine can better adapt to the > development of machine learning > > > > dashuiguailu...@gmail.com > > From: Xun Liu > Date: 2019-08-16 12:43 > To: common-dev; yarn-dev; hdfs-dev; submarine-dev > Subject: Thoughts about moving submarine to a separate git repo? > Dear Submarine developers, > > My name is Xun Liu, I am a member of the Hadoop submarine development team. > I'm one of the major contributor of Submarine since June 2018. > > I want to hear your thoughts about creating a separate GitHub repo under > Apache to do submarine development. This is an independent effort of > Submarine spin-off from the Hadoop project [ > https://lists.apache.org/thread.html/3fab657f905d081b536d9081dc404f7fd20c80eb824c857bc8e16e3b@<submarine-dev.hadoop.apache.org>]. > However, once the spin-off is approved, this effort can benefit the > follow-up processes as well. > > Submarine dev community has a total of 8 developers and submits an average > of 4 to 5 PR per day. > But there are a limited number of Hadoop committer actively help review and > merge patches, which causes development progress delays. > > So we created an external GitHub repo [ > https://github.com/hadoopsubmarine/submarine] and moved all the code for > the Hadoop submarine project into the external Github repo. > In this way, everyone can review the code for each other, and now the > development progress of Hadoop submarine is very fast. > > Also, now Submarine has little dependency on Hadoop, we want to have a > separate CI/CD pipeline to release and test submarine instead of every time > build whole Hadoop. Putting Submarine under Hadoop will introduce > unnecessary dependencies to Hadoop's top-level pom.xml. > > Our development process still complies with the development rules of the > Hadoop community: first, create a ticket in the submarine JIRA, and then > develop, in the external GitHub repo repository, the title of each PR will > be accompanied by the JIRA ID number. > > Once the Apache Github repo is created, we going to move all external > commits to the new Apache Github repo. > > Any suggestions are welcome! > > Best Regards > Xun Liu --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
