[Alex Nik <rage.iz.me@xxxxxxxxx>]

Hi, guys.

I checked the gitlab and cloned the repo. I grepped the {missing} items and got the list to work with. According to phase 1 I need to contact mentors and start working on the planning. I still have some questions about the organised process for the writers (like: who would review the docs? Do we have a list of the subject matter experts for the technical opinions? Any other method of the communication besides the mail? etc). Please, contact me!

Thanks in advance.

Alex

On 17 Aug 2020, at 19:22, Alex Nik <rage.iz.me@xxxxxxxxx> wrote:

Hi, Jaap

On 17 Aug 2020, at 19:08, Jaap Keuter <jaap.keuter@xxxxxxxxx> wrote:

On 17 Aug 2020, at 16:07, Moshe Kaplan <mosheekaplan@xxxxxxxxx> wrote:

1. The Wireshark manuals are written with docbook. The text is in the wsug_src directory here: https://gitlab.com/wireshark/wireshark/-/tree/master/docbook . Information on submitting patches is available here: https://gitlab.com/wireshark/wireshark/-/wikis/Development/SubmittingPatches

Correction, the manual as written in AsciiDoc, using the AsciiDoctor toolchain: https://asciidoctor.org

The development process is entering a state of flux, due to the pending move from Gerrit to GitLab. Thing will change in the coming time. There’s changes in the descriptions incoming, but it may be a bit turbulent at times.

That’s a good news! I’m pretty much familiar with the asciidoc! I saw the familiar *.adoc files in the repo :D

Thanks,

Jaap

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
            mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe

Thanks,

Alex