[LOOKING FOR VOLUNTEERS] Language consultants/advisers

[masatake]

The language consultants/advisers

• SystemVerilog

  • @antoinemadec

• JavaScript

  • @tristanHessell

• Vim (script)

  • @lacygoill

The recruitment

In #2076, we have been working on Cobol. In #1581, we have been working on Vue. In #2413, we have been working on SystemVerilog.

It is not possible for limited numbers of developers to support multiple languages. Do you know languages are updated like C++11, C++17, Java-1.8, Java-1.9,...? I didn't recognize this horrible fact when I make the first pull request to fishman-ctags, the origin of universal-ctags.

Ideally, we have a maintainer for each parser. However, I know well that people can't live on developing one's parser alone. I always wait for your pull request. However, you can help developing a parser for your favourite language without writing code for ctags.

I'm looking for a person who gives us advices about specified programming languages and tags output for the language.

We have to fix or improve parsers without enough knowledges about the target language, its convention, and community. Even a thing is so obvious for persons who use the language is not obvious for us. If you give me an advise, it is great help for us.

A typical question and advice:

• https://github.com/universal-ctags/ctags/issues/2489#issuecomment-609083640
• https://github.com/universal-ctags/ctags/issues/2489#issuecomment-609502181

Without this advice, I cannot merge my pull request though my code fixes the original issue.

If you are interested in being "language adviser", please put your name here. When we get a question about your language, we may contact with you. We expect you give a response in a week or so.

We expect a language advise reads ctags(1) man page. It means you know

• what is "kind",
• what is "field",
• what is "extra",
• what is "definition tag", and
• what is "reference tag" (especially what I wrote in #2428).

In addition we expect you that

• you know the concept "subparser" (see http://docs.ctags.io/en/latest/running-multi-parsers.html ),
• you understand the concept of open source software,
• you know Universal-ctags is distributed under the term of GPLv2 or later.

In addition I expect you that

• you are patient for my broken English,

If you are o.k., tell me:

• language(s) you know well
• frame work(s) or tool(s) written in the language you know well (if you have) e.g. Ruby-on-rails, moose (perl)... (see http://docs.ctags.io/en/latest/running-multi-parsers.html about the background of this question.)
• OS you are using
• a client tool you are using (e.g. vim+tagbar, emasc+xref, ...)
• skill of your English If you set this field "Good", I will ask you to review the changes for our documents. See #1038. In some cases, the changes are nothing to do is the language you know well.
• whether you know C language or not? (I wonder whether I can use the word of C language like "printf" and "strcmp" when asking a question to you.)
• How strongly you need the release of ctags-6.0. (Are you negotiator? See #1038.)

YOU CAN/SHOULD UNREGISTER yourself when you cannot find time for responding the question from us.

If advices for a question conflict between advisers, we will pick one of them without enough reason. In https://github.com/universal-ctags/ctags/pull/2459, two person help me for improving documents. It was very hard for me to reflect the reviews together.

We cannot promise improving or implementing the parser for the language you like. However, being a adviser may make a better result than say something to /dev/null (#1566).

[antoinemadec]

@masatake , I will be happy to help regarding systemverilog questions. I am about to be a dad in a month from now, so I might not be super responsive, but I will try my best.

[masatake]

@antoinemadec, thank you. Please, concentrate on your baby, and take care of your wife!

[tristanHessell]

@masatake I will be able to help with JavaScript questions. I am also a native language English speaker, so I am able to help with proofreading documents too.

[masatake]

@tristanHessell , thank you. I will revise my pull requests (#2005 and #2115). I will contact you at that time.

[lacygoill]

@masatake I think I can help regarding Vimscript questions. I will read the ctags manpage to better understand the concepts of extra and subparser.

[masatake]

@lacygoill, thank you.

[mttigg]

Super late to the party here, but as this is still open I will mention I can help out with either TypeScript or JavaScript where I can.

[masatake]

@mtti-g, thank you.