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

How about an organization? #508

Closed
predragnikolic opened this issue Feb 6, 2019 · 7 comments
Closed

How about an organization? #508

predragnikolic opened this issue Feb 6, 2019 · 7 comments

Comments

@predragnikolic
Copy link
Member

predragnikolic commented Feb 6, 2019

Hello,
Lately I been thinking about how we could improve the user experience for other people.

What if we create an organization like this https://github.com/SublimeLinter, in our case SublimeLSP
or something other...

And in that organization we could create repositories for language handlers:
LSP-typescript
LSP-rust
LSP-python
LSP-php
LSP-intelephense

And when one language handler is done, submit a PR to package control.


I always wanted to create these language handlers.
The reason I didn't do it is because I don't want the repositories to be directly associated with my github accont. Because maybe some day in the future I will lose interest in sublime or some other reason... I don't want the repos to be unmaintained.

I don't see that problem if we have an organization. All the repositories are in the SublimeLSP organization. And there will hopefully always be people who will do contributions.

NOTE: I have no experience in github organizations :D I just think this could be a good idea to consider

@tomv564
Copy link
Contributor

tomv564 commented Feb 14, 2019

Yes, I've wanted to do this for a while, great to hear there is interest.

One issue to plan for is moving the repo for this package (people's git remotes and Package Control as well)

@predragnikolic
Copy link
Member Author

Here is a useful link. https://help.github.com/articles/transferring-a-repository/#whats-transferred-with-a-repository

When you transfer a repository, its issues, pull requests, wiki, stars, and watchers are also transferred. If the transferred repository contains webhooks, services, or deploy keys, they will remain associated after the transfer is complete. Git information about commits, including contributions, is preserved. In addition:

If the transferred repository has any forks, then those forks will remain associated with the repository after the transfer is complete.

But Package Control may be a problem.
One way around this is just to leave this repo at your account :)

@randy3k
Copy link
Contributor

randy3k commented Feb 15, 2019

I believe that PC will just follow the redirected repo. Anyway, it’s also easy to submit a PR to package control channel.

@predragnikolic
Copy link
Member Author

Made the first step :)
https://github.com/sublimelsp

If someone are interested in getting in, please say in the comments :)

@tomv564
Copy link
Contributor

tomv564 commented Mar 3, 2019

Great job! I'll move some of my LSP-addon packages there when I get some free time!

@tomv564
Copy link
Contributor

tomv564 commented Jun 9, 2019

Just want to update, I haven't forgotten about this but want to catch up on some neglect in this repo before moving it!

@tomv564 tomv564 added this to the Release 1.0.0 milestone Nov 15, 2019
@tomv564
Copy link
Contributor

tomv564 commented Dec 21, 2019

LSP is now moved to the @sublimelsp org!

@tomv564 tomv564 closed this as completed Dec 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants