[openssl-project] Copyrights, AUTHORS file, etc.

2018-03-12 Thread Salz, Rich
For some background you can take a look at 
https://github.com/openssl/openssl/pull/5499 and the blog posts here: 
https://www.openssl.org/blog/blog/categories/license/

The OMC voted in 2014 to work to an eventual change of license to Apache 2. 
That led to the CLA’s. We had calls with various open source folks who we 
thought could help us. This include Max Sills from the Google open source 
office, Gervais Markham who led the Mozilla relicensing effort, someone from 
GitHub (to talk about CLA automation), and probably another person who I am 
forgetting.  We also talked with our legal counsel, Mishi Choudhary of the 
Software Freedom Law Center.

Around 2Q 3Q 2015 the discussions were completed, and we had coalesced around a 
plan. There was no formal OMC vote (it was called the openssl-team at that 
point). But there were no objections.  OMC members can skim the archives, 
starting around July 2015 if they need to refresh their memories.

The key points of the plan are

  *   Move to Apache license
  *   Require CLA’s from all contributors
  *   Reach out to everyone we can identify and get them to approve of the 
change, or not
  *   Have a uniform copyright in all source files that points to the license 
and authors separately, for easier maintenance

The “removing some code” blog post gives more details about the scripts we 
developed and what code we removed. Since then, nobody else has asked for their 
code to be removed.

The file/copyright changes happened during the 1.1.0 release.

We’re on the verge of being able to change the license, and as we said in our 
last press release, we are hoping and planning to do that for 1.1.1

The PR that marks part of this has a -1 from Tim, which is a hold.  That means 
we have to discuss and the OMC vote on this.  This email is intended to give 
the background and start the discussion.

So what are your objections Tim, and what do you want to see done differently? 
And also, please explain why it is better than the current plan.

___
openssl-project mailing list
openssl-project@openssl.org
https://mta.openssl.org/mailman/listinfo/openssl-project

[openssl-project] Updated 1.1.1 release timetable

2018-03-12 Thread Richard Levitte
Following the vote to change the coming release dates, the release
timetable has been change to the following:

  * 13th February 2018, alpha release 1 (pre1)
  * 27th February 2018, alpha release 2 (pre2)
  * 20th March 2018, beta release 1 (pre3)
- OpenSSL_1_1_1-stable created (feature freeze)
- master becomes basis for 1.1.2 or 1.2.0 (TBD)
  * 3rd April 2018, beta release 2 (pre4)
  * 17th April 2018, beta release 3 (pre5)
  * 1st May 2018, beta release 4 (pre6)
  * 8th May 2018, release readiness check (new release cycles added if
required, first possible final release date: 15th May 2018)

See https://www.openssl.org/policies/releasestrat.html for a reminder
of all details.

Cheers,
Richard

-- 
Richard Levitte levi...@openssl.org
OpenSSL Project http://www.openssl.org/~levitte/
___
openssl-project mailing list
openssl-project@openssl.org
https://mta.openssl.org/mailman/listinfo/openssl-project


Re: [openssl-project] VOTE report: Push the release of 1.1.1 beta1 (pre3) forward one week

2018-03-12 Thread Richard Levitte
The vote closes today with 6 +1's, 0 -1's and one not voted.

In other words, the 1.1.1 pre3 (beta1) release is pushed to Tuesday,
March 20th, and the dates following are to be adjusted accordingly.

Cheers,
Richard

In message <20180310.114546.780593698922932617.levi...@openssl.org> on Sat, 10 
Mar 2018 11:45:46 +0100 (CET), Richard Levitte  said:

levitte> I started a vote moments ago on the OMC list with the content that
levitte> follows.  The OMC will vote on it, hopefully on time, and the
levitte> resulting tally will be posted here.
levitte> 
levitte> Vote text:
levitte> 
levitte> NOTE: THREE DAY VOTE
levitte> Why?  Because beta1 is currently scheduled to be released in three
levitte> days.  A longer voting period would hold the release hostage in
levitte> practice, and thereby force a push of the release date regardless of
levitte> the vote result.
levitte> 
levitte> --
levitte> topic: Push the release of 1.1.1 beta1 (pre3) forward one week
levitte> 
levitte>Reason: we have a number of unreviewed PRs on github marked
levitte>1.1.1 and time is getting short.
levitte> 
levitte>All other current future release dates will be pushed one week 
as well.
levitte>https://www.openssl.org/policies/releasestrat.html will be 
updated.
levitte>An official announcement should be made.
levitte> Proposed by Richard Levitte
levitte> Public: yes
levitte> opened: 2018-03-10
levitte> closed: -mm-dd
levitte> THREE DAY VOTE!
levitte> 
levitte> -- 
levitte> Richard Levitte levi...@openssl.org
levitte> OpenSSL Project http://www.openssl.org/~levitte/
levitte> ___
levitte> openssl-project mailing list
levitte> openssl-project@openssl.org
levitte> https://mta.openssl.org/mailman/listinfo/openssl-project
levitte> 
___
openssl-project mailing list
openssl-project@openssl.org
https://mta.openssl.org/mailman/listinfo/openssl-project