Implement kite promotion?

[bindlock]

Hello.

16c11d8
Could you add the way to disable it?

[bfis]

As I understand the function of this package, it should not even be in there at all.

[bfis]

As I understand the function of this package, it should not even be in there at all.

[neumond]

Time for adblock for atom 🤦‍

kite-minimap-wrapper > div {
    display: none;
}

[neumond]

Time for adblock for atom 🤦‍

kite-minimap-wrapper > div {
    display: none;
}

[d4rr3ll]

Even with the above css tweak this still leaves the minimap gutter behind. Definitely needs a disable option. Disabled the whole package for now.

[d4rr3ll]

Even with the above css tweak this still leaves the minimap gutter behind. Definitely needs a disable option. Disabled the whole package for now.

[krzysztof-sikorski]

"Toggle minimap" command leaves the advertisement visible and any further toggling just duplicate the advertisement without showing the actual minimap 😡

I would not mind the promotion if it was implemented correctly (for example disabled by default and with customizable position and max size), but right now the behaviour is simply obnoxious 👎

[krzysztof-sikorski]

"Toggle minimap" command leaves the advertisement visible and any further toggling just duplicate the advertisement without showing the actual minimap 😡

I would not mind the promotion if it was implemented correctly (for example disabled by default and with customizable position and max size), but right now the behaviour is simply obnoxious 👎

[krzysztof-sikorski]

And now the editor just freezed after I comitted code changes via commandline 😡

I do not have time nor patience to investigate whether the cause was this package, minimap-git-diff, or some other junk - I may revisit this package in the future, but right now I consider it broken and worth only uninstalling 🔥

[krzysztof-sikorski]

And now the editor just freezed after I comitted code changes via commandline 😡

I do not have time nor patience to investigate whether the cause was this package, minimap-git-diff, or some other junk - I may revisit this package in the future, but right now I consider it broken and worth only uninstalling 🔥

[erikgeiser]

For now you can use this workaround:
apm install minimap@4.27.1

It's just insane that someone would consider it to be a good idea to shove adds in (almost) every atom user's face.

[erikgeiser]

For now you can use this workaround:
apm install minimap@4.27.1

It's just insane that someone would consider it to be a good idea to shove adds in (almost) every atom user's face.

[stevenafranklin]

After wasting time with this broken package I closed Atom and opened Sublime Text. If this advertisement is still here on Monday morning I'm uninstalling Atom.

[stevenafranklin]

After wasting time with this broken package I closed Atom and opened Sublime Text. If this advertisement is still here on Monday morning I'm uninstalling Atom.

[iron0012]

This is not cool at all. Kind of crazy that anyone would think this is okay.

[iron0012]

This is not cool at all. Kind of crazy that anyone would think this is okay.

[cbarrick]

I see how this can be a useful feature for some. However, I do not want it. This feature should be an external plugin.

Additionally, this feature does not work with minimap-autohide, which is a real bug and reason enough to revert the change.

@abe33 Why does this feature live here instead of kite/atom-pugin?

[cbarrick]

I see how this can be a useful feature for some. However, I do not want it. This feature should be an external plugin.

Additionally, this feature does not work with minimap-autohide, which is a real bug and reason enough to revert the change.

@abe33 Why does this feature live here instead of kite/atom-pugin?

[bindlock]

Looks like @abe33 made new release (4.28.1) with button which hides the docs.
a4dc07b

Click on button updates config.cson:

minimap:
    ...
    disablePythonDocLinks: true
    ....

[bindlock]

Looks like @abe33 made new release (4.28.1) with button which hides the docs.
a4dc07b

Click on button updates config.cson:

minimap:
    ...
    disablePythonDocLinks: true
    ....

[krzysztof-sikorski]

This is still opt-out instead of opt-in. Even if you opt-out, the package still generates links in the background, instead of completely disabling the "feature". And if you ever change your mind about ads and toggle disablePythonDocLinks in the settings file, you get a nice fat low-level error 👎

So yes, the package is still broken and not worthy being used.

[krzysztof-sikorski]

This is still opt-out instead of opt-in. Even if you opt-out, the package still generates links in the background, instead of completely disabling the "feature". And if you ever change your mind about ads and toggle disablePythonDocLinks in the settings file, you get a nice fat low-level error 👎

So yes, the package is still broken and not worthy being used.

[neumond]

Can I block package versions like I do in pip requirements files?
Like this <=minimap@4.27.1

[neumond]

Can I block package versions like I do in pip requirements files?
Like this <=minimap@4.27.1

[petKitsune]

@krzysztof-sikorski "This is still opt-out instead of opt-in."

yup :(
I don't like ad systems
its back to 4.27.1

[petKitsune]

@krzysztof-sikorski "This is still opt-out instead of opt-in."

yup :(
I don't like ad systems
its back to 4.27.1

[kbrose]

Definitely against company policy to upload code to external servers. This is the kind of BS that makes companies completely lock down the software developers can use. Very disappointed.

[kbrose]

Definitely against company policy to upload code to external servers. This is the kind of BS that makes companies completely lock down the software developers can use. Very disappointed.

[erikgeiser]

Seems like the developer is ignoring our concerns. If there won't be any update on the situation in the near future someone should really think about forking the project and publish it on apm. I don't think many people are okay with the ads and everyone I know that uses Atom also uses minimap, so I guess there is a huge demand for a fork.

[erikgeiser]

Seems like the developer is ignoring our concerns. If there won't be any update on the situation in the near future someone should really think about forking the project and publish it on apm. I don't think many people are okay with the ads and everyone I know that uses Atom also uses minimap, so I guess there is a huge demand for a fork.

[tedohayer]

This has given me a very negative opinion of Kite.

[tedohayer]

This has given me a very negative opinion of Kite.

[jlozano]

Hi, folks -- Juan from Kite here, thank you for the feedback, we appreciate it.

Wanted to clarify a few things as well as provide updates on your feedback.

Clarification

• The minimap plugin does not upload your code to any third party services. Your code is analyzed locally by the plugin to generate static links to relevant documentation on Kite.
• If you disable the links by choosing to opt-out, we do not analyze or generate any links in the background.

Feedback

• We have decided to leave the feature as opt-out since many users have found it useful. However, we have added two easy ways to disable the links:
  1. the x in the corner of the links box
  2. the settings for the minimap plugin.
• I believe we have addressed the bugs around disabling the links; please let us know if you still encounter them.
• We only show a maximum of 5 links. Thus there is a max size for the links box.
• Pressing the chevron now collapses the links.

[jlozano]

Hi, folks -- Juan from Kite here, thank you for the feedback, we appreciate it.

Wanted to clarify a few things as well as provide updates on your feedback.

Clarification

• The minimap plugin does not upload your code to any third party services. Your code is analyzed locally by the plugin to generate static links to relevant documentation on Kite.
• If you disable the links by choosing to opt-out, we do not analyze or generate any links in the background.

Feedback

• We have decided to leave the feature as opt-out since many users have found it useful. However, we have added two easy ways to disable the links:
  1. the x in the corner of the links box
  2. the settings for the minimap plugin.
• I believe we have addressed the bugs around disabling the links; please let us know if you still encounter them.
• We only show a maximum of 5 links. Thus there is a max size for the links box.
• Pressing the chevron now collapses the links.

[rgawenda]

Please tell us one single reason for this to be in the main minimap instead of a minimap plugin. I just don't get it.

Sample reasons may include:
It does need Internet connection, so it costs money.
It is not part of the map.
It is language dependent.

Or:
Being a plugin makes it less useful for those who liked it.

[rgawenda]

Please tell us one single reason for this to be in the main minimap instead of a minimap plugin. I just don't get it.

Sample reasons may include:
It does need Internet connection, so it costs money.
It is not part of the map.
It is language dependent.

Or:
Being a plugin makes it less useful for those who liked it.

[krzysztof-sikorski]

If you disable the links by choosing to opt-out, we do not analyze or generate any links in the background.

I'm sorry, I got a different impression from reading commit a7147ec. I re-checked it now and I see I was wrong (see the condition on https://github.com/atom-minimap/minimap/blob/master/lib/main.js#L397).

The minimap plugin does not upload your code to any third party services. Your code is analyzed locally by the plugin to generate static links to relevant documentation on Kite.

Does not upload yet. With the way this advert was introduced we have no guarantee some tracking code will not be sneaked in in the future. In fact the links already contain source=minimap tracking parameter...

many users have found it useful

How exactly did you determine that? Do you mean initial "WTF is this?" traffic to your website?

[krzysztof-sikorski]

If you disable the links by choosing to opt-out, we do not analyze or generate any links in the background.

I'm sorry, I got a different impression from reading commit a7147ec. I re-checked it now and I see I was wrong (see the condition on https://github.com/atom-minimap/minimap/blob/master/lib/main.js#L397).

The minimap plugin does not upload your code to any third party services. Your code is analyzed locally by the plugin to generate static links to relevant documentation on Kite.

Does not upload yet. With the way this advert was introduced we have no guarantee some tracking code will not be sneaked in in the future. In fact the links already contain source=minimap tracking parameter...

many users have found it useful

How exactly did you determine that? Do you mean initial "WTF is this?" traffic to your website?

[petKitsune]

many users have found it useful

ad tricks 101

[petKitsune]

many users have found it useful

ad tricks 101

[erikgeiser]

Isn't the idea behind a modular editor like atom that you get a basic editor and you add packages until the editor does what you need. I like to have a minimap like in sublime, so I install the minimap. Maybe I like to try kite sometime, then I will search for a kite package, maybe also for a minimap-kite package if I wan't related stuff displayed in minimap. The atom-minimap github account itself harbors a lot of minimap-* packages. Shouldn't they be included in minimap itself according to the many users have found it useful logic? No, because the idea is that every user can and should decide for himself what he wants.

Now you come into the equation @jlozano. Kite is just mindlessly shoved into anyone's face. What do you imagine happens when every plugin dev just add stuffs related to corporate stuff from the company he works at or other projects of his. You can't possibly think this is a good idea. Maybe someday you get a competitor and people wan't to use their product instead of kite, their minimap would still display (or at least contain) kite related stuff.

Is your vision of atom as a platform that any package should just becomes an ad canvas? Or are you in any way special that you should advertise but not others? Should open software in general be a ad platform? It's a slippery slope.

[erikgeiser]

Isn't the idea behind a modular editor like atom that you get a basic editor and you add packages until the editor does what you need. I like to have a minimap like in sublime, so I install the minimap. Maybe I like to try kite sometime, then I will search for a kite package, maybe also for a minimap-kite package if I wan't related stuff displayed in minimap. The atom-minimap github account itself harbors a lot of minimap-* packages. Shouldn't they be included in minimap itself according to the many users have found it useful logic? No, because the idea is that every user can and should decide for himself what he wants.

Now you come into the equation @jlozano. Kite is just mindlessly shoved into anyone's face. What do you imagine happens when every plugin dev just add stuffs related to corporate stuff from the company he works at or other projects of his. You can't possibly think this is a good idea. Maybe someday you get a competitor and people wan't to use their product instead of kite, their minimap would still display (or at least contain) kite related stuff.

Is your vision of atom as a platform that any package should just becomes an ad canvas? Or are you in any way special that you should advertise but not others? Should open software in general be a ad platform? It's a slippery slope.

[krzysztof-sikorski]

Another thought:

We only show a maximum of 5 links. Thus there is a max size for the links box.

If I was ever interested in automatically generated documentation links, I would like to freely browse all of them instead of getting just an arbitrarily chosen sample. It should be a completely independent widget and not a "box" shoved inside minimap area and consuming its vertical space.

In other words, this "feature" does not work well even for its intended target 👎

[krzysztof-sikorski]

Another thought:

We only show a maximum of 5 links. Thus there is a max size for the links box.

If I was ever interested in automatically generated documentation links, I would like to freely browse all of them instead of getting just an arbitrarily chosen sample. It should be a completely independent widget and not a "box" shoved inside minimap area and consuming its vertical space.

In other words, this "feature" does not work well even for its intended target 👎

[rgawenda]

Here's a patch I've verified against current branch that undoes the damage of 16c11d8

remove-kite.patch.txt

[rgawenda]

Here's a patch I've verified against current branch that undoes the damage of 16c11d8

remove-kite.patch.txt

[p-e-w]

Minimap was the first Atom package I ever installed, and it has been with me continuously since 2014. But when I saw this, I clicked the "Uninstall" button without a second's hesitation.

It's obvious to any reasonable person that those ads, even if taken to be useful, have nothing to do with this package's functionality (documentation links vs. code navigation). The implementation is buggy (see recently filed issues), ugly (hardcoded module names), and works only for a single programming language. Predictably, the backlash (this issue) has been swift and substantial.

Still, a week passed without any response from the developer. Then comes @jlozano and adds insult to injury:

We have decided to leave the feature as opt-out since many users have found it useful.

I don't believe that. Have you even read this issue thread?!? Advertising is not a feature, and if such functionality (automatic documentation links) were desired, it would be links to Stack Overflow, Read the Docs, or some other established and trusted resource, not to a little-known startup product that is barely out of beta (no offense intended).

But hey – your roof, your rule. I have contributed not a single line of code to Minimap, and would never presume to tell the author what he can or cannot do with his own project. But for the love of all that is holy, stop trying to spin this as a "feature" that people want. It's not a feature, it's advertising – and people don't want it, you want it. The least you can do is own up to that.

Going forward, if this very bad example from the number one Atom package starts getting imitated by other package authors, the entire package ecosystem – and, by extension, the Atom editor itself – could be at risk. The only way to ensure this doesn't happen seems to be clear rules from the Atom team about what a package is and is not allowed to do if it wants to be listed in the official database. Should Atom become known as the only mainstream editor with "sponsored" packages? I hope not...

[p-e-w]

Minimap was the first Atom package I ever installed, and it has been with me continuously since 2014. But when I saw this, I clicked the "Uninstall" button without a second's hesitation.

It's obvious to any reasonable person that those ads, even if taken to be useful, have nothing to do with this package's functionality (documentation links vs. code navigation). The implementation is buggy (see recently filed issues), ugly (hardcoded module names), and works only for a single programming language. Predictably, the backlash (this issue) has been swift and substantial.

Still, a week passed without any response from the developer. Then comes @jlozano and adds insult to injury:

We have decided to leave the feature as opt-out since many users have found it useful.

I don't believe that. Have you even read this issue thread?!? Advertising is not a feature, and if such functionality (automatic documentation links) were desired, it would be links to Stack Overflow, Read the Docs, or some other established and trusted resource, not to a little-known startup product that is barely out of beta (no offense intended).

But hey – your roof, your rule. I have contributed not a single line of code to Minimap, and would never presume to tell the author what he can or cannot do with his own project. But for the love of all that is holy, stop trying to spin this as a "feature" that people want. It's not a feature, it's advertising – and people don't want it, you want it. The least you can do is own up to that.

Going forward, if this very bad example from the number one Atom package starts getting imitated by other package authors, the entire package ecosystem – and, by extension, the Atom editor itself – could be at risk. The only way to ensure this doesn't happen seems to be clear rules from the Atom team about what a package is and is not allowed to do if it wants to be listed in the official database. Should Atom become known as the only mainstream editor with "sponsored" packages? I hope not...

[djczaski]

I've disabled minimap for now. Anyone planning to fork and remove the kite ads?

[djczaski]

I've disabled minimap for now. Anyone planning to fork and remove the kite ads?

[krzysztof-sikorski]

@djczaski I accidentally found one such fork on Github, but it looks more like a temporary workaround than a long-term investment.

[krzysztof-sikorski]

@djczaski I accidentally found one such fork on Github, but it looks more like a temporary workaround than a long-term investment.

[lee-dohm]

👋 For those that don't know me, I'm the Community Manager for Atom. I've also been a user of the minimap package since its inception and I've been watching the comments on this issue since it was opened. Since it seems some are expecting some sort of response from the Atom team about this, I'll comment.

First, as a developer, I agree that the functionality described here makes more sense as a plugin for minimap than built in to the base package.

As a steward of the Atom editor and the Atom package ecosystem, I'm of course concerned about packages being used for nefarious purposes. But I'm also loathe to impose blanket rules on what is or isn't valid functionality for packages without some very well-thought-out rationalization and justification for those rules. I've been watching this topic hoping that the smart people here would give me some ideas 😉 Most of what I have seen so far has been:

1. The functionality is undesirable
2. The functionality is unnecessary
3. The functionality is buggy
4. The functionality is better implemented in a different way
5. Slippery slope arguments about advertisements killing Atom

I hope we can all agree that items 1 through 4 aren't valid reasons for keeping things out of the Atom package registry. We also all agree that Atom containing advertisements is undesirable.

So what constitutes an advertisement? I consider this an advertisement:

Its sole purpose is to get you to come buy something and, other than informing you of a jewelry business, has no useful benefit to the viewer. But the Kite functionality doesn't seem to have a sole purpose of getting one to buy something and does seem to provide benefit to some potential viewers even if it doesn't provide any benefit to others.[1]

So what if someone created a package that showed the latest Wall Street Journal headlines as links to the stories? The Wall Street Journal is a for-pay service and a lot of their content is behind paywalls. But I can see someone feeling that package would be very useful for them, especially if they already had a subscription. According to the logic I see being employed by the more vehement comments here, those links would be considered "advertisements" despite how very useful they might be to some. I have a hard time agreeing with that logic.

Now, with that said:

• I agree that some people find the Kite functionality not useful to them
• I completely understand if people want to uninstall minimap
• I strongly advocate for people who think that this is a problematic direction to fork the package and provide an alternative to the community (open source rules 🤘)

I'm definitely keeping my eye on this kind of thing and if advertisements become a problem, I'm sure that the Atom team will consider specific rules. I just don't think we're there yet.

[1] If providing benefit to some but not to others was a reason to not include functionality, pretty much every feature in Atom would have to be removed! I think we might still be able to have a box where you could type stuff ... maybe save the file 😆

[lee-dohm]

👋 For those that don't know me, I'm the Community Manager for Atom. I've also been a user of the minimap package since its inception and I've been watching the comments on this issue since it was opened. Since it seems some are expecting some sort of response from the Atom team about this, I'll comment.

First, as a developer, I agree that the functionality described here makes more sense as a plugin for minimap than built in to the base package.

As a steward of the Atom editor and the Atom package ecosystem, I'm of course concerned about packages being used for nefarious purposes. But I'm also loathe to impose blanket rules on what is or isn't valid functionality for packages without some very well-thought-out rationalization and justification for those rules. I've been watching this topic hoping that the smart people here would give me some ideas 😉 Most of what I have seen so far has been:

1. The functionality is undesirable
2. The functionality is unnecessary
3. The functionality is buggy
4. The functionality is better implemented in a different way
5. Slippery slope arguments about advertisements killing Atom

I hope we can all agree that items 1 through 4 aren't valid reasons for keeping things out of the Atom package registry. We also all agree that Atom containing advertisements is undesirable.

So what constitutes an advertisement? I consider this an advertisement:

Its sole purpose is to get you to come buy something and, other than informing you of a jewelry business, has no useful benefit to the viewer. But the Kite functionality doesn't seem to have a sole purpose of getting one to buy something and does seem to provide benefit to some potential viewers even if it doesn't provide any benefit to others.[1]

So what if someone created a package that showed the latest Wall Street Journal headlines as links to the stories? The Wall Street Journal is a for-pay service and a lot of their content is behind paywalls. But I can see someone feeling that package would be very useful for them, especially if they already had a subscription. According to the logic I see being employed by the more vehement comments here, those links would be considered "advertisements" despite how very useful they might be to some. I have a hard time agreeing with that logic.

Now, with that said:

• I agree that some people find the Kite functionality not useful to them
• I completely understand if people want to uninstall minimap
• I strongly advocate for people who think that this is a problematic direction to fork the package and provide an alternative to the community (open source rules 🤘)

I'm definitely keeping my eye on this kind of thing and if advertisements become a problem, I'm sure that the Atom team will consider specific rules. I just don't think we're there yet.

[1] If providing benefit to some but not to others was a reason to not include functionality, pretty much every feature in Atom would have to be removed! I think we might still be able to have a box where you could type stuff ... maybe save the file 😆

[vith]

What makes this an advertisement is not the content, but the context in which the content appears. If it was in a separate package, the links would be appropriate for the purpose of that package, and users who choose to install it would be getting what they expected.

In my view what's happened here is a transparent move to leverage the popularity of this package to promote an unrelated service.

This may be the first time it's happened in the atom package ecosystem but it's not a new phenomenon in general. If you look at web browser extensions, popular extensions often get sold off to another party who then adds ad-injection or other user-hostile code in an attempt at monetization. Browser vendors have been removing extensions that do this from their extension stores for years now.

So what's the difference between the atom-minimap kite promotion and, say, a Gmail checker browser extension getting an update that starts turning random words on all the pages you view into ad links?

Demographic specificity?

[vith]

What makes this an advertisement is not the content, but the context in which the content appears. If it was in a separate package, the links would be appropriate for the purpose of that package, and users who choose to install it would be getting what they expected.

In my view what's happened here is a transparent move to leverage the popularity of this package to promote an unrelated service.

This may be the first time it's happened in the atom package ecosystem but it's not a new phenomenon in general. If you look at web browser extensions, popular extensions often get sold off to another party who then adds ad-injection or other user-hostile code in an attempt at monetization. Browser vendors have been removing extensions that do this from their extension stores for years now.

So what's the difference between the atom-minimap kite promotion and, say, a Gmail checker browser extension getting an update that starts turning random words on all the pages you view into ad links?

Demographic specificity?

[jlozano]

Hi all,

Thank you for the input, product feedback and suggestions, we appreciate it.

Wanted to add some clarification on some points that were made:

1. The minimap plugin does not, and will never upload your code to any third party services.
2. We decided to hard code the module names to avoid making requests to our servers.

Kite's mission is to provide tools that make developers more productive, and we thought that providing links to documentation might be helpful to some users. We are sorry to hear that people on this thread have not found it useful. However, we plan to iterate on the feature to make it more valuable and will address any bugs that arise as quickly as possible. If we thought that this feature provided no value to users, we would not have gone in this direction. We hope to continue to work with you all to improve the feature going forward.

[jlozano]

Hi all,

Thank you for the input, product feedback and suggestions, we appreciate it.

Wanted to add some clarification on some points that were made:

1. The minimap plugin does not, and will never upload your code to any third party services.
2. We decided to hard code the module names to avoid making requests to our servers.

Kite's mission is to provide tools that make developers more productive, and we thought that providing links to documentation might be helpful to some users. We are sorry to hear that people on this thread have not found it useful. However, we plan to iterate on the feature to make it more valuable and will address any bugs that arise as quickly as possible. If we thought that this feature provided no value to users, we would not have gone in this direction. We hope to continue to work with you all to improve the feature going forward.

[MarvBob]

Ads are getting smarter...
If this feature is appreciated by a lot of people then why not put it in a separate package ? People who want it would install it. The problem is not that the feature is useless, it's that it's included in a package used to display a minimap of your code and it is a very different feature. Seriously, you would not expect your linter to provide a chat feature, it has no sense.
I can understand the point of this feature but not the fact that it's included in the minimap package. If you guys cannot understand this then I hope someone will fork minimap and keep it focused to its point.

[MarvBob]

Ads are getting smarter...
If this feature is appreciated by a lot of people then why not put it in a separate package ? People who want it would install it. The problem is not that the feature is useless, it's that it's included in a package used to display a minimap of your code and it is a very different feature. Seriously, you would not expect your linter to provide a chat feature, it has no sense.
I can understand the point of this feature but not the fact that it's included in the minimap package. If you guys cannot understand this then I hope someone will fork minimap and keep it focused to its point.

[djczaski]

Why is the kite functionality implemented directly in minimap? There's one reason -- promote the author's $tartup. It's right there in the commit message. It doesn't say anything about adding features to make developers more productive. It's simply to promote.

This could have been minimap-kite and nobody would have complained. This is a slippery slope indeed. I'm surprised others haven't done this already.

[djczaski]

Why is the kite functionality implemented directly in minimap? There's one reason -- promote the author's $tartup. It's right there in the commit message. It doesn't say anything about adding features to make developers more productive. It's simply to promote.

This could have been minimap-kite and nobody would have complained. This is a slippery slope indeed. I'm surprised others haven't done this already.

[Evpok]

@jlozano Seriously, at this point, do you still think that keeping this is the best course of action ? There is not a single comment on this issue supporting the addition (except yours). It seems to me that the only thing you will achieve if you persist is to alienate both minimap users and potential kite users. I am myself very enthusiastic about Kite, but this move is seriously making me reconsider.

Look, it is fair play : you tried it, it angers people and that might harm your startup and this community. Why wouldn't you just admit you made a mistake, remove this and make a minimap add-on out of it ? Obstination and denial will win you nothing here.

[Evpok]

@jlozano Seriously, at this point, do you still think that keeping this is the best course of action ? There is not a single comment on this issue supporting the addition (except yours). It seems to me that the only thing you will achieve if you persist is to alienate both minimap users and potential kite users. I am myself very enthusiastic about Kite, but this move is seriously making me reconsider.

Look, it is fair play : you tried it, it angers people and that might harm your startup and this community. Why wouldn't you just admit you made a mistake, remove this and make a minimap add-on out of it ? Obstination and denial will win you nothing here.

[magv]

Note that this kite integration seem to be causing issue #597 (the exception in question originates in kite-wrapper.js).

Also note that a similar sudden kite invasion was done in e.g. autocomplete-python package, and people aren't happy there either (autocomplete-python/autocomplete-python#285, autocomplete-python/autocomplete-python#299). This appears to be a marketing strategy by kite developers.

[magv]

Note that this kite integration seem to be causing issue #597 (the exception in question originates in kite-wrapper.js).

Also note that a similar sudden kite invasion was done in e.g. autocomplete-python package, and people aren't happy there either (autocomplete-python/autocomplete-python#285, autocomplete-python/autocomplete-python#299). This appears to be a marketing strategy by kite developers.

[neumond]

Huh. Starting to search any package where @abe33 is committer. Going to disable them all or even migrate to sublime.

[neumond]

Huh. Starting to search any package where @abe33 is committer. Going to disable them all or even migrate to sublime.

[neumond]

I think the most urgent atom feature for me now is plugin sandboxing and access system. Like "This plugin requires: access to web, writing access to filesystem, sounds, do you agree?". But I doubt it can be done easily.

[neumond]

I think the most urgent atom feature for me now is plugin sandboxing and access system. Like "This plugin requires: access to web, writing access to filesystem, sounds, do you agree?". But I doubt it can be done easily.

[dessant]

The transition of autocomplete-python is a bit odd, please see autocomplete-python/autocomplete-python#308.

[dessant]

The transition of autocomplete-python is a bit odd, please see autocomplete-python/autocomplete-python#308.

[erikgeiser]

@neumond There is no need for a sandbox. We should just collectively fight against these kind of practices before such thing becomes normal.

@lee-dohm As far as I can tell minimap is really popular and even a default feature of sublime. Would it be possible to integrate a fork without ads to the atom core addons?

I think the best course of action is to not give them any ground to establish this shady stuff in our favorite editor. The way @jlozano does not address any of our concerns and just feeds us shallow cookie cutter responses says a lot about kite. The idea of their service seems interesting but does anyone really want to submit your code to a company that has such a low respect for users and participates in those shady guerrilla advertisement in open source software?

[erikgeiser]

@neumond There is no need for a sandbox. We should just collectively fight against these kind of practices before such thing becomes normal.

@lee-dohm As far as I can tell minimap is really popular and even a default feature of sublime. Would it be possible to integrate a fork without ads to the atom core addons?

I think the best course of action is to not give them any ground to establish this shady stuff in our favorite editor. The way @jlozano does not address any of our concerns and just feeds us shallow cookie cutter responses says a lot about kite. The idea of their service seems interesting but does anyone really want to submit your code to a company that has such a low respect for users and participates in those shady guerrilla advertisement in open source software?

[lee-dohm]

@erikgeiser Taking on support of such a complex package isn't something that we have the bandwidth for right now. We would need people from the community to step up and handle that.

[lee-dohm]

@erikgeiser Taking on support of such a complex package isn't something that we have the bandwidth for right now. We would need people from the community to step up and handle that.

[p-e-w]

@lee-dohm: Glad to see this issue has the attention of the Atom team!

I don't think the definition of "advertisement" is anywhere near as blurry as you suggest above. Links to Wall Street Journal articles in a news reader app are part of the app's functionality, links to Wall Street Journal articles in a mobile game are advertisements. What we have here are links to a code documentation service in a code navigation package. The two are clearly unrelated, and the links were even identified as a "promotion" in the original commit message.

The autocomplete-python issues mentioned by @magv give rise to more concern, because they show that this practice is already starting to spread as feared (and not limited to displaying links in this case!). Note that although the Kite functionality is integrated in autocomplete-python, Kite isn't mentioned anywhere in the project's README. This is crossing the line into "deception" territory.

Regarding Atom package rules, how about this simple one for starters:

Packages must clearly state in their README what, if any, web services they communicate with, and what data they upload to these services.

In the long term, this rule should of course be technologically enforced, i.e. package internet access restricted and managed by Atom, but this issue seems too urgent to wait for such a solution to become available.

[p-e-w]

@lee-dohm: Glad to see this issue has the attention of the Atom team!

I don't think the definition of "advertisement" is anywhere near as blurry as you suggest above. Links to Wall Street Journal articles in a news reader app are part of the app's functionality, links to Wall Street Journal articles in a mobile game are advertisements. What we have here are links to a code documentation service in a code navigation package. The two are clearly unrelated, and the links were even identified as a "promotion" in the original commit message.

The autocomplete-python issues mentioned by @magv give rise to more concern, because they show that this practice is already starting to spread as feared (and not limited to displaying links in this case!). Note that although the Kite functionality is integrated in autocomplete-python, Kite isn't mentioned anywhere in the project's README. This is crossing the line into "deception" territory.

Regarding Atom package rules, how about this simple one for starters:

Packages must clearly state in their README what, if any, web services they communicate with, and what data they upload to these services.

In the long term, this rule should of course be technologically enforced, i.e. package internet access restricted and managed by Atom, but this issue seems too urgent to wait for such a solution to become available.

[lee-dohm]

Regarding Atom package rules, how about this simple one for starters:

Packages must clearly state in their README what, if any, web services they communicate with, and what data they upload to these services.

This is a much better suggestion and leaves out the hyperbolic "advertisement" statements.

I wasn't aware of the autocomplete-python events. Now that I am, I agree that this is a problematic pattern and have already planned to bring it up to the team on Monday.

[lee-dohm]

Regarding Atom package rules, how about this simple one for starters:

Packages must clearly state in their README what, if any, web services they communicate with, and what data they upload to these services.

This is a much better suggestion and leaves out the hyperbolic "advertisement" statements.

I wasn't aware of the autocomplete-python events. Now that I am, I agree that this is a problematic pattern and have already planned to bring it up to the team on Monday.

[lee-dohm]

@DevOpsJon No, there is not currently a permissions or sandboxing model on the roadmap. It is something we investigated in the past and something we would like to revisit in the future but there are no specific plans for when. Previous discussion around it can be found at atom/atom#1763.

[lee-dohm]

@DevOpsJon No, there is not currently a permissions or sandboxing model on the roadmap. It is something we investigated in the past and something we would like to revisit in the future but there are no specific plans for when. Previous discussion around it can be found at atom/atom#1763.

[hiromipaw]

I have just dis-installed atom.

[hiromipaw]

I have just dis-installed atom.

[laurieskelly]

@DevOpsJon the two people who commented on this issue are @adamsmith, the founder of Kite, who showed up after people weren't satisfied by the first explanations given by @jlozano, Kite's machine learning engineer, who has not committed any code to this repo and has not watched or starred it.

So when this issue arose, someone at Kite became aware of this and the person that they notified was the ML engineer & the ML engineer answered, not the contributor who wrote this plug-in (@abe33, who is a Kite employee, even though he doesn't list it on his linkedin [h/t @dessant]) or some kind of product or growth person.

This and their propagandistic response to this wave of negative feedback indicates to me that these Kite package integrations aren't a PR issue, they are existential. i.e., Atom users aren't Kite's customer pool; they are their product.

[laurieskelly]

@DevOpsJon the two people who commented on this issue are @adamsmith, the founder of Kite, who showed up after people weren't satisfied by the first explanations given by @jlozano, Kite's machine learning engineer, who has not committed any code to this repo and has not watched or starred it.

So when this issue arose, someone at Kite became aware of this and the person that they notified was the ML engineer & the ML engineer answered, not the contributor who wrote this plug-in (@abe33, who is a Kite employee, even though he doesn't list it on his linkedin [h/t @dessant]) or some kind of product or growth person.

This and their propagandistic response to this wave of negative feedback indicates to me that these Kite package integrations aren't a PR issue, they are existential. i.e., Atom users aren't Kite's customer pool; they are their product.

[laurieskelly]

PS - the Kite promotion within minimap doesn't really do much. Anyone concerned with the Atom ecosystem and its standards should mosey on over to autocomplete-python, 967,989 users.

Upthread, the founder mentioned something about a three-screen install process (he's talking about autocomplete-python in this issue on the minimap repo -- I think he's confused about which repo he's commenting on)

Anyway, if you install autocomplete-python and click-click-click through the install pages, did you just whitelist your entire user directory for them to upload? And download their app? And give them your email address?
@DevOpsJon @rgawenda @rodw

[laurieskelly]

PS - the Kite promotion within minimap doesn't really do much. Anyone concerned with the Atom ecosystem and its standards should mosey on over to autocomplete-python, 967,989 users.

Upthread, the founder mentioned something about a three-screen install process (he's talking about autocomplete-python in this issue on the minimap repo -- I think he's confused about which repo he's commenting on)

Anyway, if you install autocomplete-python and click-click-click through the install pages, did you just whitelist your entire user directory for them to upload? And download their app? And give them your email address?
@DevOpsJon @rgawenda @rodw

[hiromipaw]

I think atom developers should take responsibility for this and ban any plugin that collects user data. This is basically spyware. For the moment I am back to basic with vim.

[hiromipaw]

I think atom developers should take responsibility for this and ban any plugin that collects user data. This is basically spyware. For the moment I am back to basic with vim.

[getaaron]

I agree with @laurieskelly.

[getaaron]

I agree with @laurieskelly.

[Arcanemagus]

@hiromipaw Under your logic Atom should ban itself: https://github.com/atom/metrics

Granted that can be disabled by the user. The "kite promotion" here only sends them data if you click on a link it generates, the autocomplete-python implementation sounds like it might do more, I haven't looked into that one.

The benefit and price of Atom's package system is that it is extremely flexible in what can be accomplished within it. If you consider what this package does as collecting user data then you could say linter-eslint "collects user data" since it generates links to help pages for rules you have lint messages for. I have no control over the servers that documentation is hosted on, and those people are organizations that for the most part are just hosting the pages on GitHub, but it's the same basic functionality.

The major issue here is that this has no place being in the minimap package and is generating links to a company that is gathering user data. Oddly enough from @adamsmith's comment earlier it seems like they didn't think to actually use the data coming from the minimap integration, but I wouldn't trust that data not being used to incompetence.

Since it's been a bit since it was posted, for anyone interested @mehcode has forked this package and removed the Kite code, you can install it by running apm install minimap-plus, or by searching for minimap-plus within Atom.

[Arcanemagus]

@hiromipaw Under your logic Atom should ban itself: https://github.com/atom/metrics

Granted that can be disabled by the user. The "kite promotion" here only sends them data if you click on a link it generates, the autocomplete-python implementation sounds like it might do more, I haven't looked into that one.

The benefit and price of Atom's package system is that it is extremely flexible in what can be accomplished within it. If you consider what this package does as collecting user data then you could say linter-eslint "collects user data" since it generates links to help pages for rules you have lint messages for. I have no control over the servers that documentation is hosted on, and those people are organizations that for the most part are just hosting the pages on GitHub, but it's the same basic functionality.

The major issue here is that this has no place being in the minimap package and is generating links to a company that is gathering user data. Oddly enough from @adamsmith's comment earlier it seems like they didn't think to actually use the data coming from the minimap integration, but I wouldn't trust that data not being used to incompetence.

Since it's been a bit since it was posted, for anyone interested @mehcode has forked this package and removed the Kite code, you can install it by running apm install minimap-plus, or by searching for minimap-plus within Atom.

[hiromipaw]

@Arcanemagus that is not correct. It is one thing to collect some statistics and another thing to send user data to third party apps. Even if the company says it doesn't use the data, once this is collected and transmitted the user has lot control over it completely.

[hiromipaw]

@Arcanemagus that is not correct. It is one thing to collect some statistics and another thing to send user data to third party apps. Even if the company says it doesn't use the data, once this is collected and transmitted the user has lot control over it completely.

[bronson]

@Arcanemagus, the metrics package asks permission before sending anything. If you decline to give permission, it doesn't send anything.

[bronson]

@Arcanemagus, the metrics package asks permission before sending anything. If you decline to give permission, it doesn't send anything.

[Arcanemagus]

My point was the over broad statement of "any plugin that collects user data".

[Arcanemagus]

My point was the over broad statement of "any plugin that collects user data".

[bronson]

Well, "asks permission" is quite a bit better than "can be disabled"... But I have to agree that the original point is pretty silly!

[bronson]

Well, "asks permission" is quite a bit better than "can be disabled"... But I have to agree that the original point is pretty silly!

[bronson]

Wandering back toward topic, I wonder if a good first step would be to put together something like an Atom package code of conduct. I picture a list of best practices that well-behaved packages would agree to. If a packages says in the README that it conforms, then we can be confident that -- were a transgression found -- a revert would be quickly merged.

Never accessing services without explicit permission would be on that list. Also, I expect something about keeping packages focused would be on there too. For example, if you want to add, say, Python smarts to the minimap, you'd have to do it with hooks and additional packages. You couldn't just splat it in kitchen-sink style.

But, I gotta admit, that list might be pretty short.

[bronson]

Wandering back toward topic, I wonder if a good first step would be to put together something like an Atom package code of conduct. I picture a list of best practices that well-behaved packages would agree to. If a packages says in the README that it conforms, then we can be confident that -- were a transgression found -- a revert would be quickly merged.

Never accessing services without explicit permission would be on that list. Also, I expect something about keeping packages focused would be on there too. For example, if you want to add, say, Python smarts to the minimap, you'd have to do it with hooks and additional packages. You couldn't just splat it in kitchen-sink style.

But, I gotta admit, that list might be pretty short.

[jacobsee]

@bronson There is a more generic code of conduct in the footer of the Atom package listing. If it could be argued that this is unethical or unprofessional (which I believe there is a strong case for, given that Atom's own Metrics package asks permission), then this Kite integration would already be in violation.

[jacobsee]

@bronson There is a more generic code of conduct in the footer of the Atom package listing. If it could be argued that this is unethical or unprofessional (which I believe there is a strong case for, given that Atom's own Metrics package asks permission), then this Kite integration would already be in violation.

[bronson]

@jacobsee true, calling what Kite did unprofessional is plausible but that's pretty subjective... I'm hoping that, if a code was meant for the packages themselves, it could be nice and explicit.

One downside would be getting lawyered on your own side project by people using the Package Code of Conduct more like a weapon... That's probably guaranteed to happen at some point, alas.

[bronson]

@jacobsee true, calling what Kite did unprofessional is plausible but that's pretty subjective... I'm hoping that, if a code was meant for the packages themselves, it could be nice and explicit.

One downside would be getting lawyered on your own side project by people using the Package Code of Conduct more like a weapon... That's probably guaranteed to happen at some point, alas.

[abe33]

So, what can I say…

Firstly, I must apologize for not replying on this thread before. I'm not good when it comes to communication skills and this kind of crisis management has created me a huge stress. That might sound lame, but it's sadly true, we're not all equal when it comes to stress managament, and I'm really bad at that. I wish I had @lee-dohm's coolness and de-escalating skills.

Secondly, even if it may seems to come late, we've heard you and decided to revert all the changes related to the python links feature. The next release will no longer show anything. I'll also make sure that the relation between Kite and the minimap package are as clear as possible. I've been an employee at Kite for over half a year now and this plugin is now officially maintained by Kite.

Again I'm deeply sorry for all that story. I should have be most wary of all the potential misunderstandings that move could create and while we never sent any code, nor any request to a third party I can understand that this was not explicit enough and probably hard to justify anyway.

[abe33]

So, what can I say…

Firstly, I must apologize for not replying on this thread before. I'm not good when it comes to communication skills and this kind of crisis management has created me a huge stress. That might sound lame, but it's sadly true, we're not all equal when it comes to stress managament, and I'm really bad at that. I wish I had @lee-dohm's coolness and de-escalating skills.

Secondly, even if it may seems to come late, we've heard you and decided to revert all the changes related to the python links feature. The next release will no longer show anything. I'll also make sure that the relation between Kite and the minimap package are as clear as possible. I've been an employee at Kite for over half a year now and this plugin is now officially maintained by Kite.

Again I'm deeply sorry for all that story. I should have be most wary of all the potential misunderstandings that move could create and while we never sent any code, nor any request to a third party I can understand that this was not explicit enough and probably hard to justify anyway.

[lukaskollmer]

Thank you!

[lukaskollmer]

Thank you!

[dessant]

@abe33, could you also take care of this autocomplete-python issue? autocomplete-python/autocomplete-python#308

Especially that biased engine selection dialog.

[dessant]

@abe33, could you also take care of this autocomplete-python issue? autocomplete-python/autocomplete-python#308

Especially that biased engine selection dialog.

[mehcode]

@abe33 Would you willing to add me as a member of atom-minimap with write access to this repository?

It would go a long way towards repairing user relations if someone impartial (not attached to Kite) had access to the repository. I would do my part (triage, bugs, etc.) as a maintainer.

---

I started the fork that removed Kite and the community is currently in the process of moving to it. It's currently a featured package in Atom. It would benefit the community if we can all be on a single package.

[mehcode]

@abe33 Would you willing to add me as a member of atom-minimap with write access to this repository?

It would go a long way towards repairing user relations if someone impartial (not attached to Kite) had access to the repository. I would do my part (triage, bugs, etc.) as a maintainer.

---

I started the fork that removed Kite and the community is currently in the process of moving to it. It's currently a featured package in Atom. It would benefit the community if we can all be on a single package.

[petKitsune]

@mehcode "@abe33 Would you willing to add me as a member of atom-minimap with write access to this repository?"

yes please

i'm a bit paranoid when
"Sorry for that, but now we are completely honest"
comes around

[petKitsune]

@mehcode "@abe33 Would you willing to add me as a member of atom-minimap with write access to this repository?"

yes please

i'm a bit paranoid when
"Sorry for that, but now we are completely honest"
comes around

[getaaron]

In addition to giving @mehcode write access, please give write access to @laurieskelly

[getaaron]

In addition to giving @mehcode write access, please give write access to @laurieskelly

[dflock]

Yes, I won't be moving back to the base minimap package (from the @mehcode fork) until there are some impartial people with commit access to keep things honest.

[dflock]

Yes, I won't be moving back to the base minimap package (from the @mehcode fork) until there are some impartial people with commit access to keep things honest.

[lthibault]

I just uninstalled Kite.

It's a real shame as the service was good, but nothing is good enough to justify advertisements in my work-space. The fight against distraction is hard enough as it is without having to think carefully about where I'm clicking due to dark-pattern UI.

Please note that reverting code doesn't repair trust. As a general rule, don't f*#k with people's livelihoods.

Goodbye, Kite.

[lthibault]

I just uninstalled Kite.

It's a real shame as the service was good, but nothing is good enough to justify advertisements in my work-space. The fight against distraction is hard enough as it is without having to think carefully about where I'm clicking due to dark-pattern UI.

Please note that reverting code doesn't repair trust. As a general rule, don't f*#k with people's livelihoods.

Goodbye, Kite.

[rscircus]

Kudos to @mehcode for the fork! And the author @abe33 for the apology! I'm thinking, that @abe33 might not be responsible for this, but was "asked" by his employer (Kite) to do that.

[rscircus]

Kudos to @mehcode for the fork! And the author @abe33 for the apology! I'm thinking, that @abe33 might not be responsible for this, but was "asked" by his employer (Kite) to do that.

[diegoperini]

Any fork maintained by someone who isn't affiliated with Kite will be more trustworthy from now on. Adding @mehcode or anyone else here with write access won't resolve the trust issue on my side. I now prefer to use a minimap plugin with different maintainers as well as the ones who apologized here. I understand @mehcode 's intention to not to divide the community but sometimes a fork is not a division but a legitimate standing which reminds us not to mess with the ethos of open source software. If @mehcode or anyone else doesn't want to maintain a fork of this, it is still more reasonable to work without a minimap.

This comment is not intended to be a rage post for the Kite team, I hope they learn from their mistakes.

[diegoperini]

Any fork maintained by someone who isn't affiliated with Kite will be more trustworthy from now on. Adding @mehcode or anyone else here with write access won't resolve the trust issue on my side. I now prefer to use a minimap plugin with different maintainers as well as the ones who apologized here. I understand @mehcode 's intention to not to divide the community but sometimes a fork is not a division but a legitimate standing which reminds us not to mess with the ethos of open source software. If @mehcode or anyone else doesn't want to maintain a fork of this, it is still more reasonable to work without a minimap.

This comment is not intended to be a rage post for the Kite team, I hope they learn from their mistakes.

[robjac]

jfc; in an effort to appease some people's problem with my complaining in an issue section i've revised my message: shame.

[robjac]

jfc; in an effort to appease some people's problem with my complaining in an issue section i've revised my message: shame.

[aknooh]

Kite, taking over an open source project and adding ads and promotions to your company is not a cool move. The open source community is outraged at your business tactics.

[aknooh]

Kite, taking over an open source project and adding ads and promotions to your company is not a cool move. The open source community is outraged at your business tactics.

[jonhoo]

This thread is no longer constructive at this point, and should probably be locked. /cc @abe33

[jonhoo]

This thread is no longer constructive at this point, and should probably be locked. /cc @abe33

[dessant]

@jonhoo, we could also just stay calm and on topic.

@mehcode's request to be added as a maintainer did not get a public response from the Kite team, I think that is worth waiting out before severing communication channels.

[dessant]

@jonhoo, we could also just stay calm and on topic.

@mehcode's request to be added as a maintainer did not get a public response from the Kite team, I think that is worth waiting out before severing communication channels.

[jonhoo]

@dessant hehe, I think that's good advice in general. The original topic of the issue has been resolved, and it's unclear that further discussion here matters (especially given that this thread was linked to from all over the internet a little while back). As for adding @mehcode (and others) as maintainers, that should probably have its own, separate issue.

[jonhoo]

@dessant hehe, I think that's good advice in general. The original topic of the issue has been resolved, and it's unclear that further discussion here matters (especially given that this thread was linked to from all over the internet a little while back). As for adding @mehcode (and others) as maintainers, that should probably have its own, separate issue.

[abe33]

Hello there, I've added @mehcode as a collaborator with write access on this repo.

As for locking down this thread, I'll probably do that at some point, I just don't want to make it looks like I'm trying to shut down criticism.

[abe33]

Hello there, I've added @mehcode as a collaborator with write access on this repo.

As for locking down this thread, I'll probably do that at some point, I just don't want to make it looks like I'm trying to shut down criticism.

[mehcode]

I've been added as a collaborator. I'll do my part to prevent this from happening again. Thank you all for the support.

The original purpose of the thread is complete. If you have a bug or something to report, open another issue. If you want to keep venting, please do so elsewhere.

---

Thanks @abe33, I look forward to working with you to keep this awesome project going.

[mehcode]

I've been added as a collaborator. I'll do my part to prevent this from happening again. Thank you all for the support.

The original purpose of the thread is complete. If you have a bug or something to report, open another issue. If you want to keep venting, please do so elsewhere.

---

Thanks @abe33, I look forward to working with you to keep this awesome project going.

[dessant]

@abe33, the damage caused in autocomplete-python still has to be addressed, please discuss it with your team and make a statement over at autocomplete-python/autocomplete-python#308.

[dessant]

@abe33, the damage caused in autocomplete-python still has to be addressed, please discuss it with your team and make a statement over at autocomplete-python/autocomplete-python#308.

[mehcode]

@dessant This and that are two different projects. I haven't bothered to do anything about autocomplete-python because its effectively unofficially deprecated. Atom is doing a big push towards proper LSP integration and Python has an excellent language server. I'm sure someone (I'd like to if I get time) will make the package. That package (once it exists) would give you auto-complete plus a whole lot more.

[mehcode]

@dessant This and that are two different projects. I haven't bothered to do anything about autocomplete-python because its effectively unofficially deprecated. Atom is doing a big push towards proper LSP integration and Python has an excellent language server. I'm sure someone (I'd like to if I get time) will make the package. That package (once it exists) would give you auto-complete plus a whole lot more.

[adam-arold]

What about forking that repo and removing the crap from it then re-release it on a different name?

[adam-arold]

What about forking that repo and removing the crap from it then re-release it on a different name?

[dessant]

@mehcode, thanks for the pointers, that certainly seems like the correct path to take. I did look into the autocomplete-python codebase, and regardless of its legacy architecture, it is also a mess, using deprecated Jedi APIs and requiring the cherry-picking of Jedi commits to do a dependency update.

@adam-arold, a fork was already published for minimap: https://atom.io/packages/minimap-plus.
Though the plan is to keep this repository in check and continue the work here. There is no good reason to further fragment the community now that the Kite promotion was removed and @mehcode has joined the project.

[dessant]

@mehcode, thanks for the pointers, that certainly seems like the correct path to take. I did look into the autocomplete-python codebase, and regardless of its legacy architecture, it is also a mess, using deprecated Jedi APIs and requiring the cherry-picking of Jedi commits to do a dependency update.

@adam-arold, a fork was already published for minimap: https://atom.io/packages/minimap-plus.
Though the plan is to keep this repository in check and continue the work here. There is no good reason to further fragment the community now that the Kite promotion was removed and @mehcode has joined the project.

[MrStonedOne]

There is no good reason to further fragment the community

NO! Bad @dessant! Bad!

Do not spread this bullshit about fragmenting the community. The whole point of open source is that anybody is able to make a fork, and allow the community to decide. A fragmented community is good. Another name for it would be distributed.

The entire reason this was even a big deal was because there is no where near enough competition, there is always the "one" tool to do something. That "one" plugin that provides a function, with the runner up (if it exist) having no where near the amount of users.

As a user base, we have stop collesasing around these tools and start spreading out more. As it is, these open source projects become single point of failures or other wise big targets because everybody is obsessed with using the #1 project.

So stop stigmatizing forking as "fragmenting the community"

[MrStonedOne]

There is no good reason to further fragment the community

NO! Bad @dessant! Bad!

Do not spread this bullshit about fragmenting the community. The whole point of open source is that anybody is able to make a fork, and allow the community to decide. A fragmented community is good. Another name for it would be distributed.

The entire reason this was even a big deal was because there is no where near enough competition, there is always the "one" tool to do something. That "one" plugin that provides a function, with the runner up (if it exist) having no where near the amount of users.

As a user base, we have stop collesasing around these tools and start spreading out more. As it is, these open source projects become single point of failures or other wise big targets because everybody is obsessed with using the #1 project.

So stop stigmatizing forking as "fragmenting the community"

[mehcode]

This conversation has served its purpose. I've locked the thread. If you need to further vent, please do so off of this project's issue tracker.

[mehcode]

This conversation has served its purpose. I've locked the thread. If you need to further vent, please do so off of this project's issue tracker.