Hi Jérôme, On Mon, Feb 25, 2019 at 2:19 PM Jérôme Martin <[email protected]> wrote:
> I'm currently working on different open source projects, and every one of > them features at least one or more #lang languages. > Some use s-expressions, some have their own syntax using the "brag" parser > generator. > Awesome! > The thing is, most of them don't show up in the results because I didn't > submitted them as Racket packages (I usually do that only with libraries) > or because there are no scribble docs written yet. > But I'm planning to make even more languages. Thanks to Racket, Language > Oriented Programming has become my tool of the trade for pretty much > everything. > > I guess I'll take some time to package some of them as standalone packages > so that they can show up there, but it's not my priority. > I'd suggest following the instructions in Tutorial: Creating a Package <https://blog.racket-lang.org/2017/10/tutorial-creating-a-package.html> by Stephen Chang ( https://blog.racket-lang.org/2017/10/tutorial-creating-a-package.html) > Do you folks think we should do some guide about "How to contribute > languages to the Racket ecosystem" which would go through all the nuts and > bolts of making a package "language-friendly" ? > Something along the lines of "Hey, you have a project using Racket on > Github, but you want it to show up in the Racket docs search? Here are the > steps to register your package. You have languages inside? Don't forget to > add this and that..." > I'd suggest A) including scribble file If you use `raco pkg new my-new-lang` it will also create a scribble file that you can just treat as a text file without worrying about formatting till you are ready. B) tagging as both 'lang' and 'language' on the racket package catalog at https://pkgs.racket-lang.org/ Create an account, add your package with the language and lang Stephen I know there already a lot of good documentation about that for people who > know what they want. But I feel it's more about getting Racket developers > aware that they can show up there in the first place (myself included, I > just realized most of my projects don't show up there). > Adding your package to the racket packet repository is absolutely essential! The How-to-get-started page on the GitHub wiki (at https://github.com/racket/racket/wiki/How-to-get-started) has a set of additional 'Getting started' links. > It could also be a small blog post showing up the good parts of the doc... > Or both. What do you think? (in fact, i'm definitely gonna write that blog > post anyways) > > maybe update https://github.com/racket/racket/wiki/How-to-get-started, or better still a Pull Request for the 'getting-started' <https://docs.racket-lang.org/getting-started/index.html> documentation:Source at https://github.com/racket/racket/blob/master/pkgs/racket-doc/scribblings/getting-started/getting-started.scrbl PS: scribble seems tricksy but you really can just dump plain text and it will work fine. Or you can do cool stuff e.g. https://gist.github.com/florence/b3fcc1df922008604e64362484dc1c28 OT: http://racket-news.com/2019/03/racket-news-issue-3.html Kind regards, Stephen > -- > You received this message because you are subscribed to the Google Groups > "Racket Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
