Consolidate efforts?

[happycollision]

@stollcri, @optikfluffel, @raulchedrese, @denny-trebbin, @brandc87

I don't think that the Elixir + Nova community is all that big at the moment. What do you all say to starting an org that houses all the Elixir-related Nova efforts that you've all started? I know that some of you have already combined efforts a bit. So should we take that further?

It'd be nice if there was one, canonical, syntax support extension. One language server extension. One formatting extension. Etc. I know that there isn't that much fragmentation now, but it might be nice for people to realize we are all communicating and only actually publishing the best version of each of these things.

My proposal would be to create an org called nova-elixir on GitHub. From there, we'd pull in the existing repos that you all have created. Next we'd combine the two "ElixirLS" repos into one extension and archive the old ones (including the "Elixir" extension which is already included in Raul's "ElixirLS"). I'd suggest just calling the new extension "Elixir". The formatter could stay separate at first, then could be merged into the new "Elixir" extension. Eventually the org would have four archived repos and one active one.

If there is a need/desire that someone has for Elixir snippets or other things Elixir-related, that could be its own extension/repo under the org.

In addition, we could remove the old versions of the extensions from Panic's directory (assuming that is possible). Then when someone wants to work with Elixir in Nova, it is obvious what extension(s) to install and exactly where to go to contribute.

I realize that none of you have asked for your work to be pushed into another place or combined with other code, but I figured I'd suggest it to everyone because that is exactly what I was looking for 😅 when trying to find "the best" Elixir extension for Nova.

We'd have to iron out a few details, surely. But is this idea worth pursuing?

[denny-trebbin]

Good idea.
I'm myself also the author of Polis and I couldn't figure how to unpublish extensions. Maybe contacting the support works but I doubt we could request unpublishing (abandoned) extensions in the name of the original authors.

I would join forces with my private account @Fibric rather than with my current work account @denny-trebbin

[stollcri]

@happycollision I think it would be great if you were willing to pull all of those things together. Feel free to use any code in this repo. When I created this extension the documentation was basically nonexistent, so I drew "inspiration" from the extensions which existed at the time. By the way, you can peek at the other extensions you have installed by digging through /Applications/Nova.app/Contents/SharedSupport/Extensions/.

I wouldn't worry about unifying all of the other extensions. If you can pull together the best practices, then the extension will naturally rise to the top. And when that happens the other extensions will get tired of requests to add features from the top extension and just refer people that way. I'm sure the other extension devs would support your efforts; if they are like me they are not necessarily passionate about Nova extensions, they just needed some functionality and shared the results for others with the same need

[raulchedrese]

Hey @happycollision,

My repo is an attempt to unify @stollcri's language definitions with support for LSP features and auto formatting in a single extension. I would love for others to contribute to the repo and I'd be happy to move it to an org at some point if there is interest.

Much like @sollcri I'd rather be writing Elixir than making Nova extensions but I would like to have access to the same features I get in Visual Studio Code from a single extension.

Will we create an organization, and if so, when and who will establish it before inviting others?

[happycollision]

I’ll go ahead and get it set up today.

[happycollision]

Related good news: Panic is planning on releasing the source for some of their built in extensions: https://twitter.com/panic/status/1334580265205735424?s=20

[denny-trebbin]

@happycollision thanks for the invite. But you invited my work account. Please add @Fibric instead as I'm not planing to spend time on the project while I'm on the clock.

[happycollision]

Please have a look at the repo I've started @stollcri and @raulchedrese. It combines both of your originals into one, preserving history. In particular, have a look at the commits from today and we can discuss any changes necessary to move forward. More work to come!

https://github.com/nova-elixir/nova-elixir/commits/master

[happycollision]

At this point, I'd love to make @stollcri and @raulchedrese collaborators on the new repo. But that is only if you both are interested in moving development over there.

There are a couple things to square away:

1. We need a license, or at least to acknowledge @stollcri's MIT license from before. I temporarily removed it, because I wasn't sure how to address the need. It needs to be replaced... though I am not sure where. Project root? Syntax folder? I've got a discussion thread to figure it out.
2. If this will now represent all our efforts on syntax and LS going forward, we should probably submit it to Panic (I have no idea how that works yet) and drop the original two. Yeah?

I've got a PR up in the new repo that fixes inline fn defs. If we aren't cool with consolidating everything or aren't cool with doing any of this in the near future, I am happy to PR that same thing into this repo as well.

[lessless]

Thank you for all your efforts folks!
The Nova's speed is unparalleled.

[lessless]

@brandc87 @raulchedrese are you guys still ok with deleting current ElixirLS extensions and publishing nova-elixir/nova-elixir instead?

[lessless]

Peeps, Nova is a great editor, but it definitely misses syntax highlight for Elixir...