Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

discussion archives for license development list should be merged and made publicly available #468

Open
peterspdx opened this issue Sep 29, 2016 · 2 comments
Labels
🏷 status: label work required Needs proper labelling before it can be worked on
Projects

Comments

@peterspdx
Copy link
Contributor

peterspdx commented Sep 29, 2016

When we moved the licenses@ list from ibiblio, a new discussion archive was started. Here is the earlier archive (from CC's very beginning thru November 2015): http://lists.ibiblio.org/pipermail/cc-licenses/, which is linked to on https://creativecommons.org/about/get-involved/.

Here is the archive for the list now that it has moved:
https://creativecommons.email/mailman/private/licenses/

  1. Merge the two archives if possible
  2. Update the link on /get-involved/ to the merged archive
  3. Ensure the archive is publicly accessible even if the list is moderated
  4. Post an update to licenses@ when completed so the community is aware
@rheaplex rheaplex removed their assignment Sep 7, 2018
@TimidRobot
Copy link
Member

TimidRobot commented Apr 17, 2019

For additional context and related tickets, see ibiblio - Creative Commons Internal Wiki.

@cc-open-source-bot cc-open-source-bot added the 🏷 status: label work required Needs proper labelling before it can be worked on label Dec 2, 2020
@kgodey kgodey added this to [TEMPORARY] Deprioritize in Active Sprint Dec 2, 2020
@kgodey kgodey removed this from [TEMPORARY] Deprioritize in Active Sprint Dec 2, 2020
@kgodey kgodey added this to Pending Review in Backlog Dec 2, 2020
@kgodey kgodey moved this from Pending Review to Tech Support (IT) in Backlog Dec 17, 2020
@metinoy

This comment was marked as spam.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🏷 status: label work required Needs proper labelling before it can be worked on
Projects
Backlog
  
Tech Support (IT)
Development

No branches or pull requests

5 participants