From neugens.limasoftware at gmail.com Mon Sep 3 15:26:23 2018 From: neugens.limasoftware at gmail.com (Mario Torre) Date: Mon, 3 Sep 2018 17:26:23 +0200 Subject: CFV: New Project: Skara In-Reply-To: <86ebdd98-0ac4-4f5f-9645-3fb3e4cfd344@oracle.com> References: <86ebdd98-0ac4-4f5f-9645-3fb3e4cfd344@oracle.com> Message-ID: Vote: Yes. (I admit I'm *very* skeptical on the move to git, but I think it makes sense to explore options to improve the workflow and indeed a project is a good way to do that, I do hope the project will produce an healthy stream of data throughout its life until we either get the JEP mentioned or it's decided things stay the way they are - or any other result in between). Cheers, Mario Il giorno mer 29 ago 2018 alle ore 23:12 joe darcy ha scritto: > > I hereby propose the creation of the Skara Project with Joe Darcy as the > Lead and the Build Group as the sponsoring Group. > > The source code management (SCM) system of a software project is a > fundamental piece of its infrastructure and workflows. Starting in > February 2008, the source code of different JDK releases and supporting > projects has been hosted in Mercurial repositories under > http://hg.openjdk.java.net/. Code reviews of JDK changes are typically > conducted as discussions in mailing lists over small patches sent to one > or more lists or over webrevs hosted on cr.openjdk.java.net. Since 2008, > many open source projects have successfully adopted more efficient SCM > and review tooling, in some cases provided by third parties. > > In order to help OpenJDK contributors be more productive, both seasoned > committers and relative newcomers, the Skara project proposes to > investigate alternative SCM and code review options for the JDK source > code, including options based upon Git rather than Mercurial, and > including options hosted by third parties. > > The Skara project intends to build prototypes of hosting the JDK 12 > sources under different providers. > > The evaluation criteria to consider include but are not limited to: > > * Performance: time for clone operations from master repos, time of > local operations, etc. > > * Space efficiency > > * Usability in different geographies > > * Support for common development environments such as Linux, Mac, > and Windows > > * Able to easily host the entire history of the JDK and the > projected growth of its history over the next decade > > * Support for general JDK code review practices > > * Programmatic APIs to enable process assistance and automation of > review and processes > > If one or more prototypes indicate a different SCM arrangement offers > substantial improvements over the current situation, the Skara project > will shepherd a JEP to change the SCM for the JDK. > > Skara previously had a call for discussion > (http://mail.openjdk.java.net/pipermail/discuss/2018-July/004801.html) > and was a topic at the OpenJDK Committers? Workshop > (http://cr.openjdk.java.net/~darcy/Presentations/ocw-2018-08-01-skara.pdf). > A range of passionate opinions were expressed regarding the choice of > SCM for the JDK, but the prototype imports of the JDK sources to hosting > providers: > > https://github.com/Project-Skara/jdk.git > https://gitlab.com/jddarcy/jdk.git > > have demonstrated much shorter clone times, on the order of one to three > minutes as compared to fifteen minutes to over a half hour from > hg.openjdk.java.net. > > The envisioned future iterations of prototypes could explore how to > adapt JDK development practices to better conform to conventions on > different SCMs. For example, some syntax changes in JDK commit messages > would work more naturally with git tooling. Such prototypes would be > published and made available for comment. > > Joe is a reviewer in the JDK project, the lead of the CSR > (Compatibility & Specification Review) group > (http://openjdk.java.net/groups/csr/), previous lead of Project Coin > (http://openjdk.java.net/projects/coin/), initial moderator and > inaugural release manager for OpenJDK 6, and was the lead for JEP 296: > Consolidate the JDK Forest into a Single Repository > (http://openjdk.java.net/jeps/296). > > Initial reviewers are Tim Bell (tbell), Joe Darcy (darcy), Erik Duveblad > (ehelin), Erik Joelsson (erikj), Mark Reinhold (mr), Tony Squier > (squierts), Tiep Vo (tiep), and Robin Westberg (rwestberg). > > Votes are due by September 12, 11 am Pacific Time. > > Only current OpenJDK Members [1] are eligible to vote on this motion. > Votes must be cast in the open on the discuss list. Replying to this > message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [2]. > > -Joe Darcy > > [1] http://openjdk.java.net/census#members > [2] http://openjdk.java.net/projects/#new-project-vote > -- pgp key: http://subkeys.pgp.net/ PGP Key ID: 80F240CF Fingerprint: BA39 9666 94EC 8B73 27FA FC7C 4086 63E3 80F2 40CF Java Champion - Blog: http://neugens.wordpress.com - Twitter: @neugens Proud GNU Classpath developer: http://www.classpath.org/ OpenJDK: http://openjdk.java.net/projects/caciocavallo/ Please, support open standards: http://endsoftpatents.org/ From christian.tornqvist at oracle.com Mon Sep 10 15:34:44 2018 From: christian.tornqvist at oracle.com (Christian Tornqvist) Date: Mon, 10 Sep 2018 08:34:44 -0700 Subject: CFV: New Project: Skara In-Reply-To: <86ebdd98-0ac4-4f5f-9645-3fb3e4cfd344@oracle.com> References: <86ebdd98-0ac4-4f5f-9645-3fb3e4cfd344@oracle.com> Message-ID: Vote: yes > On Aug 29, 2018, at 10:58 AM, joe darcy wrote: > > I hereby propose the creation of the Skara Project with Joe Darcy as the Lead and the Build Group as the sponsoring Group. > > The source code management (SCM) system of a software project is a fundamental piece of its infrastructure and workflows. Starting in February 2008, the source code of different JDK releases and supporting projects has been hosted in Mercurial repositories under http://hg.openjdk.java.net/. Code reviews of JDK changes are typically conducted as discussions in mailing lists over small patches sent to one or more lists or over webrevs hosted on cr.openjdk.java.net. Since 2008, many open source projects have successfully adopted more efficient SCM and review tooling, in some cases provided by third parties. > > In order to help OpenJDK contributors be more productive, both seasoned committers and relative newcomers, the Skara project proposes to investigate alternative SCM and code review options for the JDK source code, including options based upon Git rather than Mercurial, and including options hosted by third parties. > > The Skara project intends to build prototypes of hosting the JDK 12 sources under different providers. > > The evaluation criteria to consider include but are not limited to: > > * Performance: time for clone operations from master repos, time of local operations, etc. > > * Space efficiency > > * Usability in different geographies > > * Support for common development environments such as Linux, Mac, and Windows > > * Able to easily host the entire history of the JDK and the projected growth of its history over the next decade > > * Support for general JDK code review practices > > * Programmatic APIs to enable process assistance and automation of review and processes > > If one or more prototypes indicate a different SCM arrangement offers substantial improvements over the current situation, the Skara project will shepherd a JEP to change the SCM for the JDK. > > Skara previously had a call for discussion (http://mail.openjdk.java.net/pipermail/discuss/2018-July/004801.html) and was a topic at the OpenJDK Committers? Workshop (http://cr.openjdk.java.net/~darcy/Presentations/ocw-2018-08-01-skara.pdf). A range of passionate opinions were expressed regarding the choice of SCM for the JDK, but the prototype imports of the JDK sources to hosting providers: > > https://github.com/Project-Skara/jdk.git > https://gitlab.com/jddarcy/jdk.git > > have demonstrated much shorter clone times, on the order of one to three minutes as compared to fifteen minutes to over a half hour from hg.openjdk.java.net. > > The envisioned future iterations of prototypes could explore how to adapt JDK development practices to better conform to conventions on different SCMs. For example, some syntax changes in JDK commit messages would work more naturally with git tooling. Such prototypes would be published and made available for comment. > > Joe is a reviewer in the JDK project, the lead of the CSR (Compatibility & Specification Review) group (http://openjdk.java.net/groups/csr/), previous lead of Project Coin (http://openjdk.java.net/projects/coin/), initial moderator and inaugural release manager for OpenJDK 6, and was the lead for JEP 296: Consolidate the JDK Forest into a Single Repository (http://openjdk.java.net/jeps/296). > > Initial reviewers are Tim Bell (tbell), Joe Darcy (darcy), Erik Duveblad (ehelin), Erik Joelsson (erikj), Mark Reinhold (mr), Tony Squier (squierts), Tiep Vo (tiep), and Robin Westberg (rwestberg). > > Votes are due by September 12, 11 am Pacific Time. > > Only current OpenJDK Members [1] are eligible to vote on this motion. Votes must be cast in the open on the discuss list. Replying to this message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [2]. > > -Joe Darcy > > [1] http://openjdk.java.net/census#members > [2] http://openjdk.java.net/projects/#new-project-vote > From vladimir.kozlov at oracle.com Tue Sep 11 16:27:32 2018 From: vladimir.kozlov at oracle.com (Vladimir Kozlov) Date: Tue, 11 Sep 2018 09:27:32 -0700 Subject: CFV: New Project: Skara In-Reply-To: <86ebdd98-0ac4-4f5f-9645-3fb3e4cfd344@oracle.com> References: <86ebdd98-0ac4-4f5f-9645-3fb3e4cfd344@oracle.com> Message-ID: Vote: yes On 8/29/18 10:58 AM, joe darcy wrote: > I hereby propose the creation of the Skara Project with Joe Darcy as the Lead and the Build Group as the sponsoring Group. > > The source code management (SCM) system of a software project is a fundamental piece of its infrastructure and > workflows. Starting in February 2008, the source code of different JDK releases and supporting projects has been hosted > in Mercurial repositories under http://hg.openjdk.java.net/. Code reviews of JDK changes are typically conducted as > discussions in mailing lists over small patches sent to one or more lists or over webrevs hosted on cr.openjdk.java.net. > Since 2008, many open source projects have successfully adopted more efficient SCM and review tooling, in some cases > provided by third parties. > > In order to help OpenJDK contributors be more productive, both seasoned committers and relative newcomers, the Skara > project proposes to investigate alternative SCM and code review options for the JDK source code, including options based > upon Git rather than Mercurial, and including options hosted by third parties. > > The Skara project intends to build prototypes of hosting the JDK 12 sources under different providers. > > The evaluation criteria to consider include but are not limited to: > > ??? * Performance: time for clone operations from master repos, time of local operations, etc. > > ??? * Space efficiency > > ??? * Usability in different geographies > > ??? * Support for common development environments such as Linux, Mac, and Windows > > ??? * Able to easily host the entire history of the JDK and the projected growth of its history over the next decade > > ??? * Support for general JDK code review practices > > ??? * Programmatic APIs to enable process assistance and automation of review and processes > > If one or more prototypes indicate a different SCM arrangement offers substantial improvements over the current > situation, the Skara project will shepherd a JEP to change the SCM for the JDK. > > Skara previously had a call for discussion (http://mail.openjdk.java.net/pipermail/discuss/2018-July/004801.html) and > was a topic at the OpenJDK Committers? Workshop > (http://cr.openjdk.java.net/~darcy/Presentations/ocw-2018-08-01-skara.pdf). A range of passionate opinions were > expressed regarding the choice of SCM for the JDK, but the prototype imports of the JDK sources to hosting providers: > > ??? https://github.com/Project-Skara/jdk.git > ??? https://gitlab.com/jddarcy/jdk.git > > have demonstrated much shorter clone times, on the order of one to three minutes as compared to fifteen minutes to over > a half hour from hg.openjdk.java.net. > > The envisioned future iterations of prototypes could explore how to adapt JDK development practices to better conform to > conventions on different SCMs. For example, some syntax changes in JDK commit messages would work more naturally with > git tooling. Such prototypes would be published and made available for comment. > > Joe is? a reviewer in the JDK project, the lead of the CSR (Compatibility & Specification Review) group > (http://openjdk.java.net/groups/csr/), previous lead of Project Coin (http://openjdk.java.net/projects/coin/), initial > moderator and inaugural release manager for OpenJDK 6, and was the lead for JEP 296: Consolidate the JDK Forest into a > Single Repository (http://openjdk.java.net/jeps/296). > > Initial reviewers are Tim Bell (tbell), Joe Darcy (darcy), Erik Duveblad (ehelin), Erik Joelsson (erikj), Mark Reinhold > (mr), Tony Squier (squierts), Tiep Vo (tiep), and Robin Westberg (rwestberg). > > Votes are due by September 12, 11 am Pacific Time. > > Only current OpenJDK Members [1] are eligible to vote on this motion. Votes must be cast in the open on the discuss > list. Replying to this message is sufficient if your mail program honors the Reply-To header. > > For Lazy Consensus voting instructions, see [2]. > > -Joe Darcy > > [1] http://openjdk.java.net/census#members > [2] http://openjdk.java.net/projects/#new-project-vote > From dalibor.topic at oracle.com Wed Sep 12 15:13:45 2018 From: dalibor.topic at oracle.com (dalibor topic) Date: Wed, 12 Sep 2018 17:13:45 +0200 Subject: CFV: New Project: Skara In-Reply-To: <86ebdd98-0ac4-4f5f-9645-3fb3e4cfd344@oracle.com> References: <86ebdd98-0ac4-4f5f-9645-3fb3e4cfd344@oracle.com> Message-ID: <6576bb41-fe20-f592-8af0-cbfd2212552f@oracle.com> Vote: Yes. -- Dalibor Topic | Principal Product Manager Phone: +494089091214 | Mobile: +491737185961 ORACLE Deutschland B.V. & Co. KG | K?hneh?fe 5 | 22761 Hamburg ORACLE Deutschland B.V. & Co. KG Hauptverwaltung: Riesstr. 25, D-80992 M?nchen Registergericht: Amtsgericht M?nchen, HRA 95603 Komplement?rin: ORACLE Deutschland Verwaltung B.V. Hertogswetering 163/167, 3543 AS Utrecht, Niederlande Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697 Gesch?ftsf?hrer: Alexander van der Ven, Jan Schultheiss, Val Maher Oracle is committed to developing practices and products that help protect the environment From neugens.limasoftware at gmail.com Tue Sep 25 14:47:27 2018 From: neugens.limasoftware at gmail.com (Mario Torre) Date: Tue, 25 Sep 2018 16:47:27 +0200 Subject: HTTPS enabled for remaining OpenJDK subdomains In-Reply-To: <20180925144348.9730A20AB2C@eggemoggin.niobe.net> References: <20180925144348.9730A20AB2C@eggemoggin.niobe.net> Message-ID: Great news, thanks! Cheers, Mario Il giorno mar 25 set 2018 alle ore 16:45 ha scritto: > > We?ve enabled HTTPS for {cr,hg,mail}.openjdk.java.net, and > for openjdk.java.net itself: > > https://cr.openjdk.java.net > https://hg.openjdk.java.net > https://mail.openjdk.java.net > https://openjdk.java.net > > Please try using HTTPS with these subdomains, and report any > problems to ops at openjdk.java.net. After we shake these out > for a couple of weeks we?ll configure redirects and policies > so that these subdomains are HTTPS-by-default. > > - Mark -- pgp key: http://subkeys.pgp.net/ PGP Key ID: 80F240CF Fingerprint: BA39 9666 94EC 8B73 27FA FC7C 4086 63E3 80F2 40CF Java Champion - Blog: http://neugens.wordpress.com - Twitter: @neugens Proud GNU Classpath developer: http://www.classpath.org/ OpenJDK: http://openjdk.java.net/projects/caciocavallo/ Please, support open standards: http://endsoftpatents.org/ From martijnverburg at gmail.com Tue Sep 25 15:09:43 2018 From: martijnverburg at gmail.com (Martijn Verburg) Date: Tue, 25 Sep 2018 16:09:43 +0100 Subject: HTTPS enabled for remaining OpenJDK subdomains In-Reply-To: References: <20180925144348.9730A20AB2C@eggemoggin.niobe.net> Message-ID: Awesome! Thanks for making OpenJDK that little bit more secure. On Tue, 25 Sep 2018 at 15:48, Mario Torre wrote: > Great news, thanks! > > Cheers, > Mario > Il giorno mar 25 set 2018 alle ore 16:45 ha > scritto: > > > > We?ve enabled HTTPS for {cr,hg,mail}.openjdk.java.net, and > > for openjdk.java.net itself: > > > > https://cr.openjdk.java.net > > https://hg.openjdk.java.net > > https://mail.openjdk.java.net > > https://openjdk.java.net > > > > Please try using HTTPS with these subdomains, and report any > > problems to ops at openjdk.java.net. After we shake these out > > for a couple of weeks we?ll configure redirects and policies > > so that these subdomains are HTTPS-by-default. > > > > - Mark > > > > -- > pgp key: http://subkeys.pgp.net/ PGP Key ID: 80F240CF > Fingerprint: BA39 9666 94EC 8B73 27FA FC7C 4086 63E3 80F2 40CF > > Java Champion - Blog: http://neugens.wordpress.com - Twitter: @neugens > Proud GNU Classpath developer: http://www.classpath.org/ > OpenJDK: http://openjdk.java.net/projects/caciocavallo/ > > Please, support open standards: > http://endsoftpatents.org/ > -- Cheers, Martijn (Sent from Gmail Mobile) From stokito at gmail.com Tue Sep 25 16:02:35 2018 From: stokito at gmail.com (Sergey Ponomarev) Date: Tue, 25 Sep 2018 19:02:35 +0300 Subject: HTTPS enabled for remaining OpenJDK subdomains In-Reply-To: References: <20180925144348.9730A20AB2C@eggemoggin.niobe.net> Message-ID: Hi, great job! I made small test: cr.openjdk.java.net Redirect from HTTP to HTTPS: no, this can be definetely made Upgrade-Insecure-Requests: ignored HSTS - none SCP: yes, but may be more strict. Use SCP Evaluator to debug. mail.openjdk.java.net Redirect from HTTP to HTTPS: yes Upgrade-Insecure-Requests: ignored HSTS - none SCP: yes, but may be more strict. hg.openjdk.java.net Redirect from HTTP to HTTPS: no, maybe it's better to keep without a redirect to avoid some HG problems Upgrade-Insecure-Requests: ignored HSTS - none SCP: yes, but may be more strict. openjdk.java.net Redirect from HTTP to HTTPS: no, this can be definetely made Upgrade-Insecure-Requests: ignored HSTS - none SCP: yes, but may be more strict. On Tue, 25 Sep 2018 at 17:48, Mario Torre wrote: > Great news, thanks! > > Cheers, > Mario > Il giorno mar 25 set 2018 alle ore 16:45 ha > scritto: > > > > We?ve enabled HTTPS for {cr,hg,mail}.openjdk.java.net, and > > for openjdk.java.net itself: > > > > https://cr.openjdk.java.net > > https://hg.openjdk.java.net > > https://mail.openjdk.java.net > > https://openjdk.java.net > > > > Please try using HTTPS with these subdomains, and report any > > problems to ops at openjdk.java.net. After we shake these out > > for a couple of weeks we?ll configure redirects and policies > > so that these subdomains are HTTPS-by-default. > > > > - Mark > > > > -- > pgp key: http://subkeys.pgp.net/ PGP Key ID: 80F240CF > Fingerprint: BA39 9666 94EC 8B73 27FA FC7C 4086 63E3 80F2 40CF > > Java Champion - Blog: http://neugens.wordpress.com - Twitter: @neugens > Proud GNU Classpath developer: http://www.classpath.org/ > OpenJDK: http://openjdk.java.net/projects/caciocavallo/ > > Please, support open standards: > http://endsoftpatents.org/ > -- Sergey Ponomarev , skype:stokito From mark.reinhold at oracle.com Tue Sep 25 17:10:43 2018 From: mark.reinhold at oracle.com (mark.reinhold at oracle.com) Date: Tue, 25 Sep 2018 10:10:43 -0700 Subject: HTTPS enabled for remaining OpenJDK subdomains In-Reply-To: References: <20180925144348.9730A20AB2C@eggemoggin.niobe.net> Message-ID: <20180925101043.219048284@eggemoggin.niobe.net> 2018/9/25 9:02:35 -0700, Sergey Ponomarev : > I made small test: > > cr.openjdk.java.net > Redirect from HTTP to HTTPS: no, this can be definetely made > Upgrade-Insecure-Requests: ignored > HSTS - none > SCP: yes, but may be more strict. Use SCP Evaluator > > to debug. > > ... Thanks -- we?re aware of all of these issues. As I said, we?ll configure such redirects and policies after we test unforced HTTPS for a couple of weeks. - Mark