You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Dawid Weiss (Jira)" <ji...@apache.org> on 2020/05/19 09:02:00 UTC
[jira] [Created] (SOLR-14497) Move the project to become Apache TLP
Dawid Weiss created SOLR-14497:
----------------------------------
Summary: Move the project to become Apache TLP
Key: SOLR-14497
URL: https://issues.apache.org/jira/browse/SOLR-14497
Project: Solr
Issue Type: Task
Security Level: Public (Default Security Level. Issues are Public)
Reporter: Dawid Weiss
This issue is about the process of moving Solr to become an Apache TLP.
Elements to handle (as sub-tasks)?
h4. Preparation
# Figure out formal steps to be taken with Apache Board to set up TLP project for Solr.
# Figure out the initial committership, PMC members, chair.
# Separate the code (and build) from Lucene so that Solr can be built independently. This applies to 8.x and master (9.x).
# Determine what happens with mailing lists (and their archives). Are new mailing lists going to be set up or the existing ones aliased somehow?
# Determine what happens with CI and build servers.
# [add more here]
h4. Execution
# Code: clone Lucene/Solr git to Solr TLP, add a TLP marking tag.
# Send an information about any potential mailing list changes, etc. to previous addresses.
# Add redirects from old Solr site/ javadoc/ any other addresses to TLP locations.
# [add more here]
h4. Post-transition
# Reorganize Lucene repository (remove Solr, move lucene folder upward).
# [add more here]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org