Skip to content
This repository has been archived by the owner on Jan 1, 2021. It is now read-only.

Unpublish this package #29

Open
aminya opened this issue Oct 10, 2020 · 11 comments
Open

Unpublish this package #29

aminya opened this issue Oct 10, 2020 · 11 comments

Comments

@aminya
Copy link
Member

aminya commented Oct 10, 2020

This is just taking the name of debug. Please remove it to allow others using the name

@atom-community

I want to start a debugger package in @atom-ide-community. If you transfer this package there, I can continue developing this.

@UziTech
Copy link
Member

UziTech commented Nov 1, 2020

Should we use this repo for a debugger package or unpublish it?

I am trying to clean up some packages in atom-community. Archiving the ones that are not used.

@aminya
Copy link
Member Author

aminya commented Nov 1, 2020

I already went with atom-ide-debugger:
https://atom.io/packages/atom-ide-debugger

Instead of unpublishing, we can just forward this package to atom-ide-debugger using package-deps. This is the first package that shows up in any search.

@UziTech
Copy link
Member

UziTech commented Nov 1, 2020

sounds good to me 👍

@UziTech
Copy link
Member

UziTech commented Nov 1, 2020

I don't know if you saw but I invited you to be an owner in atom-community. I am going through the repos and archiving any that were used for placeholders.

Looks like these packages should be unpublished since they are just placeholders:

  • environment
  • formatter
  • lint
  • run
  • debug
  • captain-hook
  • formatter-coffeescript
  • test
  • builder

@UziTech
Copy link
Member

UziTech commented Nov 1, 2020

It looks like the only real packages in atom-community are:

  • markdown-preview-plus
  • autocomplete-paths
  • sync-settings
  • language-scala

@aminya
Copy link
Member Author

aminya commented Nov 1, 2020

Thanks for the invite! Shouldn't we use this opportunity for forwarding? The published ones have been on atom.io/packages forever and no one has had any complaint.

Using package-deps, we can just make these packages installers for our maintained packages.

I am interested in these specifically:

environment
formatter
lint
run
debug
test
builder

@UziTech
Copy link
Member

UziTech commented Nov 1, 2020

I feel like that could get a little confusing for users to know which repo to post issues to. I would rather unpublish or just make the package pop up with a notification saying this package is deprecated use x instead.

@UziTech
Copy link
Member

UziTech commented Nov 1, 2020

we should probably add them to the deprecated packages list

@aminya
Copy link
Member Author

aminya commented Nov 1, 2020

We can close the issues or even archive the repository giving a link to the main repo.

The only one which we have a replacement for are debug and lint.

We can use the name of other ones to make new cool packages. We should transfer those to atom-ide-community.

@aminya
Copy link
Member Author

aminya commented Nov 1, 2020

we should probably add them to the deprecated packages list

My point is that this does not solve the issue. These names are already taken, and there is no way to recover this. I am saying that we can take this opportunity for good.

@UziTech
Copy link
Member

UziTech commented Nov 1, 2020

Sounds good. I'll let you do that. It is getting late (or early depending on how you look at it) here so I should probably go to bed before I screw something up.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants