Skip to content

Start newsletter#11 #200

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

Closed
wants to merge 3 commits into from
Closed

Start newsletter#11 #200

wants to merge 3 commits into from

Conversation

sunjon
Copy link

@sunjon sunjon commented Sep 22, 2020

A rough draft attempt to cover some of the 0.5 features/timeline; LSP, Tree-sitter, vim-conf, etc.

There's no detail yet on the highlighted changes section or in general, and there's some overlap in what's already covered in newsletter#10/4.4.

@tjdevries
Copy link
Contributor

For LSP & Lua, you could link directly to my talks about them from vimconf, as I think they give good info 😆

I can put the links here if you want them.

@sunjon
Copy link
Author

sunjon commented Sep 22, 2020

For LSP & Lua, you could link directly to my talks about them from vimconf, as I think they give good info laughing

I can put the links here if you want them.

Yes please, direct links to any of the content would be good (and any accompaying slides)

@teto
Copy link
Member

teto commented Sep 22, 2020

@sunjon Great initiative. Note that we are open to other type of blog posts than just the release ones, so anyone should feel free to propose a blog post focusing on either LSP or tree-sitter etc.

@@ -0,0 +1,242 @@
---
layout: newsletter
title: "Newsletter #11 - **AWESOME TITLE HERE**
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"halfway there" (with respect to the 1.0) :)

@teto
Copy link
Member

teto commented Nov 2, 2020

Ideally I would envision 2 companion blog posts: about LSP and treesitters. These are brand new introductions and too complex to mix with a newsletter (introduction + technical setup + current state/ecosystem and what's next). These could serve as the official soft reference (in contrast to :help or nvim-lspconfig). Then there is always the matter of writing those. I believe @vigoux might have something for treesitter ? as for LSP, if there is no volunteer I can come up with something.

@vigoux
Copy link
Member

vigoux commented Nov 2, 2020

I have been doing some things, but nothing significant yet, I'll try to have it ready soon.

@teto
Copy link
Member

teto commented Nov 15, 2020

I've put @sunjon 's template on https://github.com/neovim/neovim/wiki/newsletter-%2311-:-the-0.5-release so that we can collaboratively edit it.

@janlazo janlazo mentioned this pull request May 9, 2021
15 tasks
@rockerBOO
Copy link
Contributor

What is currently needed to push this? Looks like some sections need to be finished up.

I think the 0.5 release commit has a good overview of what has changed as well.

@bfredl
Copy link
Member

bfredl commented Jul 3, 2021

probably it would make sense to move the too unfinished parts to a new wip newsletter #11 and finish off the parts relevant to the release (and yes some stuff could be copied over from the release commit).

@clason clason mentioned this pull request Jul 5, 2021
@clason
Copy link
Member

clason commented Jul 12, 2021

and it's published: https://neovim.io/news/

thanks @sunjon for the first draft, that was very helpful!

@teto teto closed this Jul 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants