Re: [Wireshark-dev] Joint project with Git for outreachy

[Richard Sharpe]

On Sat, Sep 19, 2020 at 8:21 AM Jonathan Nieder  wrote:
>
> Hi wiresharkers,
>
> Outreachy  is a program similar to the
> Google Summer of Code, providing internships to work on open source
> projects.
>
> Emily (cc-ed) and I would be interested in mentoring an outreachy
> intern on adding support for the Git protocol to wireshark.  We think
> this would be helpful for documenting the spec better, for making
> debugging easier for future Git developers, and for helping people
> working on systems involving Git (e.g. CI systems) to understand the
> behavior of the systems they oversee.  We think that a co-mentor
> within wireshark would be helpful for making sure an intern is set up
> for success (helping them find pointers, making sure their approach is
> on the right track, etc).
>
> This would be a project under the Git umbrella
> .
>
> What do you think?  Does this sound interesting to you?

Replying again to all this time.

We welcome any one who wants to write a dissector or help out in any
area of Wireshark, as Ronnie said.

I am more than happy to offer advice and ideas and look at code to get
new Wireshark developers going.

-- 
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

[Wireshark-dev] Joint project with Git for outreachy

[Jonathan Nieder]

Hi wiresharkers,

Outreachy  is a program similar to the
Google Summer of Code, providing internships to work on open source
projects.

Emily (cc-ed) and I would be interested in mentoring an outreachy
intern on adding support for the Git protocol to wireshark.  We think
this would be helpful for documenting the spec better, for making
debugging easier for future Git developers, and for helping people
working on systems involving Git (e.g. CI systems) to understand the
behavior of the systems they oversee.  We think that a co-mentor
within wireshark would be helpful for making sure an intern is set up
for success (helping them find pointers, making sure their approach is
on the right track, etc).

This would be a project under the Git umbrella
.

What do you think?  Does this sound interesting to you?

Thanks,
Jonathan
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Joint project with Git for outreachy

[Richard Sharpe]

On Sat, Sep 19, 2020 at 2:13 AM ronnie sahlberg
 wrote:
>
> Hi Jonathan,
> Hi Emily
>
> Emily, you want to contribute to wireshark? That is awesome. I think I
> speak for everyone to send a HUGE welcome
> your way and hope your experience working on and with wireshark be excellent!
>
> I think a git dissector would be really awesome.
> We do have a packet-git.c already in wireshark, but looking at it it
> is very barebones (understatement of the year:-)
> but getting a real full blown git protocol implementation would be
> totally awesome.
>
> I am more than happy to provide feedback and advice for Emily. We do
> have pretty good development documentation so it should be pretty easy
> to get started and get a development environment up and running.

I agree. More than happy to help someone get up to speed with writing
dissectors, and I am sure many other developers are as well.

--
Regards
Richard Sharpe
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Managing Gitlab Issues

[Uli Heilmeier]

> I'm sorry I was unclear. I’m talking about the Status field of Bugzilla. Not 
> Gerrit labels. With Bugzilla a new bug had
> (normally) the status ‚Unconfirmed‘ at the beginning. When someone was able 
> to reproduce the issue the bug had the
> status ‚Confirmed‘. If something was missing (a capture file for example) the 
> status was ‚Incomplete‘. When someone was
> working on a fix the status was ‚In Progress‘.
> This is currently missing with Gitlab Issues. There is only ‚Open‘ and 
> ‚Closed‘.
> 
> Therefore I suggest we use labels to mark the status of an issue.
> 

I still prefer to have some status labels. However as there is no feedback it's 
seems I'm the only one. :-(

> 
> With Bugzilla I (as a normal contributor) was able to set the status of a bug 
> (not limited to my own created ones). Also
> I was able to correct the classification etc. At the moment I’m not able to 
> do this with Gitlab issues. When we can have
> a new group to edit/label issues I’m totally fine. 

I'm also not able to add a existing label (enhancement) to an issue created by 
myself. So it seems there is some setting
denying this.

>> * It would make sense to have templates for issues [3]. Has anyone 
>> already prepared this? Otherwise I will create
>> one and submit a MR?
>>
>>
>> This would help for sure. Please submit a MR for that.
> 
> Will do so.

Templates for FeatureRequest and Bug are active.


___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] Joint project with Git for outreachy

[ronnie sahlberg]

Hi Jonathan,
Hi Emily

Emily, you want to contribute to wireshark? That is awesome. I think I
speak for everyone to send a HUGE welcome
your way and hope your experience working on and with wireshark be excellent!

I think a git dissector would be really awesome.
We do have a packet-git.c already in wireshark, but looking at it it
is very barebones (understatement of the year:-)
but getting a real full blown git protocol implementation would be
totally awesome.

I am more than happy to provide feedback and advice for Emily. We do
have pretty good development documentation so it should be pretty easy
to get started and get a development environment up and running.


(
Jonathan, remember that smb2 client I was working on, libamb2?  I got
it to run on PlayStation2 now. It is totally awesome being able to use
SMB3.1.1 and full encryption to copy file between the PS2 memory card
and Azure cloud file server :-)
)

best regards
Ronnie Sahlberg




On Sat, Sep 19, 2020 at 8:21 AM Jonathan Nieder  wrote:
>
> Hi wiresharkers,
>
> Outreachy  is a program similar to the
> Google Summer of Code, providing internships to work on open source
> projects.
>
> Emily (cc-ed) and I would be interested in mentoring an outreachy
> intern on adding support for the Git protocol to wireshark.  We think
> this would be helpful for documenting the spec better, for making
> debugging easier for future Git developers, and for helping people
> working on systems involving Git (e.g. CI systems) to understand the
> behavior of the systems they oversee.  We think that a co-mentor
> within wireshark would be helpful for making sure an intern is set up
> for success (helping them find pointers, making sure their approach is
> on the right track, etc).
>
> This would be a project under the Git umbrella
> .
>
> What do you think?  Does this sound interesting to you?
>
> Thanks,
> Jonathan
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe