Whoops! Forgot about that. Posted an update, thanks. Justin M. Keyes
On Sat, Jan 7, 2017 at 1:37 PM, Przemysław Pietrzkiewicz <pietrzkiew...@gmail.com> wrote: > Thanks, Justin! Would it be possible to post a link to each newsletter as a > bountysource campaign update when it's released? > > Currently the last bountysource update still says that nvim approaches it's > first release - this might be misleading to people not looking beyond the > bountysource page. > > > On Fri, Jan 6, 2017, 11:06 Justin M. Keyes <justi...@gmail.com> wrote: >> >> Madis, >> >> Thanks for the support. >> >> > Do you think it would be possible to publish brief weekly updates >> > somewhere on what has been happening and what's the plan for next week >> >> The roadmap and milestones should give a fair idea of long-term plan, >> as well as current progress: >> >> https://neovim.io/roadmap/ >> https://github.com/neovim/neovim/milestones >> >> Current activity can be estimated by the "pulse" page: >> >> https://github.com/neovim/neovim/pulse >> >> I would like to write more frequent newsletters, but it will be as >> time permits and inspiration hits. >> >> Weekly reports are extremely unlikely. >> >> --- >> Justin M. Keyes >> >> >> On Thu, Jan 5, 2017 at 7:51 PM, Madis Nõmme <madis.no...@gmail.com> wrote: >> > Thank you for the news update. I was just on the bountysource page >> > seeing >> > that it's almost 2.5k, so it could get you for 2 days. Just called out >> > all >> > my vim friends to give their support :) >> > >> > Neovim is working very well for me and I have complete faith in the core >> > team's capabilities and decisions. I like to regularly check back to the >> > project's page to see if something interesting has happened or been >> > added. >> > You know, like to use the newest features and regularly installing >> > neovim-head :) I think some other bountysource contributors regardless >> > of >> > their bounty size do the same. >> > >> > Do you think it would be possible to publish brief weekly updates >> > somewhere >> > on what has been happening and what's the plan for next week. I think it >> > would help the project's image and give a lot value and good feeling for >> > the >> > people interested. Bountysourcers would feel that their contribution >> > goes >> > for good :) >> > >> > Code mode! >> > Madis >> > >> > >> > On Tuesday, 29 April 2014 17:25:38 UTC+3, Thiago Arruda wrote: >> >> >> >> Hi >> >> >> >> I'm transfering some management roles to @justinmk. He will be in >> >> charge >> >> of the following: >> >> >> >> - Github administration(managing repositories, adding/removing members) >> >> - Bountysource administration(posting bounties, adding/removing >> >> members) >> >> - Merging/approval of pull requests that don't have direct impact on >> >> the >> >> features I'm working on >> >> >> >> Passing on these responsibilities will help me focus on implementing >> >> the >> >> features I promised in the fundraiser. @justinmk is a very early Neovim >> >> supporter sharing much of my vision/enthusiasm, so I'm sure he will >> >> make >> >> good decisions for the project. >> >> >> >> Another thing: For now on, tests can be written in lua or moonscript. >> >> Initially I have chosen moonscript because I find it very pleasing to >> >> read/write, while also taking care of some lua boilerplate, but it's >> >> clear >> >> that it bothers developers making important contributions to the >> >> project(@ZyX-I, @aktau...) and it has very bad error messages which >> >> make it >> >> hard for contributors to get started with writing tests. >> >> >> >> I have updated the wiki specifying that tests may be written in >> >> moonscript >> >> or lua, but if someone is interested, they can send PRs converting >> >> existing >> >> tests with 'moonc'(some manual tweaking/formatting may be required). If >> >> all >> >> tests are converted, we'll drop moonscript completely. >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups >> > "neovim" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> > an >> > email to neovim+unsubscr...@googlegroups.com. >> > For more options, visit https://groups.google.com/d/optout. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "neovim" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to neovim+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "neovim" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to neovim+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "neovim" group. To unsubscribe from this group and stop receiving emails from it, send an email to neovim+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
