Re: GSoD approved technical writer - community bonding phase

[Peter Wu <peter () lekensteyn nl>]

Hi Alex,

Feel free to reach out in private to me and Tomasz, or the wireshark-dev list. We should probably set up an initial 
call using Jitsi or similar to discuss the initial planning and answer any questions you may have.

For communication, we have just moved to GitLab for issue tracking and code reviews. Someone from the community will 
likely pick up reviews as they pass by, but feel free to tag us specifically (I am @Lekensteyn, Tomasz is @desowin). We 
are also in the #wireshark IRC channel on Freenode.
There is also a GSoD Slack which we could potentially use if you prefer. There is definitely no shortage of 
communication channels... ;)

Kind regards,
Peter
https://lekensteyn.nl
(pardon my brevity, top-posting and formatting, sent from my phone)


On August 28, 2020 10:06:16 AM GMT+02:00, Alex Nik <rage.iz.me () gmail com> wrote:
> 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 () gmail com> wrote:
> >
> > Hi, Jaap
> >
> > > On 17 Aug 2020, at 19:08, Jaap Keuter <jaap.keuter () xs4all nl
> <mailto:jaap.keuter () xs4all nl>> wrote:
> > > > On 17 Aug 2020, at 16:07, Moshe Kaplan <mosheekaplan () gmail com
> <mailto:mosheekaplan () gmail com>> 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
> <https://gitlab.com/wireshark/wireshark/-/tree/master/docbook> .
> Information on submitting patches is available here:
> https://gitlab.com/wireshark/wireshark/-/wikis/Development/SubmittingPatches
> <https://gitlab.com/wireshark/wireshark/-/wikis/Development/SubmittingPatches>
> > > Correction, the manual as written in AsciiDoc, using the AsciiDoctor
> toolchain: https://asciidoctor.org <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 () wireshark org
> <mailto:wireshark-dev () wireshark org>>
> > > Archives:    https://www.wireshark.org/lists/wireshark-dev
> <https://www.wireshark.org/lists/wireshark-dev>
> > > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
> <https://www.wireshark.org/mailman/options/wireshark-dev>
> > >            
> mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
> <mailto:wireshark-dev-request () wireshark org?subject=unsubscribe>
> > Thanks,
> > Alex
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe