Current project status

[prskr]

It seems that this project is currently not maintained at all even though there are lots of dependent projects (including some rather 'well known' companies like Uber, Weaveworks, Cilium, DataDog, Elastic...) and very interesting contributions like e.g. #911 and many more.

Also with Go 1.18 in place updates to at least Go 1.13 to improve error handling and such would make sense and most likely not break anything anymore.

So...what to do? It seems like @gconnell hasn't responded anymore to anything since ~1y and apparently nobody else has taken over so far ( @google-ospo-team anyone?). It would be a shame to have this project abandoned but having it orphaned and unmaintained could be even worse.

[domdom82]

this! I am basing another project on gopacket and am hesitant to put it into production without knowing the status of ownership / maintenance here. An update from @google-ospo-team would be highly appreciated.

[prskr]

Probably @google-admin ?

[google-ospo-team]

OSPO don't really handle maintaining projects on Github. Someone is welcome to take it over if they want, but the github-admin team isn't the team to do so. - Mike (OSPO github-admin@)

…

On Thu, Jun 2, 2022 at 3:24 AM 'Peter' via Google GitHub Admins < ***@***.***> wrote: Probably @google-admin <https://github.com/google-admin> ? — Reply to this email directly, view it on GitHub <#1016 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXSTVNH6JMOS3ZZCC7O6EUDVNBOTHANCNFSM5WRTZCFQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Mike Vanne

[domdom82]

@gconnell has recently opened a PR at google/btree#45 so at least he seems to be still working actively doing OSS at Google :-) not sure how to proceed here, though.

[gram-signal]

Hello! I am currently no longer at Google, and I am no longer actively maintaining this project. I would love it if someone wanted to take on maintenance of this project, but I'm unsure how that would work as I don't appear to have administrative rights to add admins to the project any longer. I was under the impression that that level of access would continue after I left Google, as my github account hasn't changed, but sadly that's not the case.

Writing this initially was a labor of love, and I'm super happy to see its use in the outside world. I'd happily bless any work to improve or maintain this, either via re-ownership of the project as it exists or some blessed, maintained fork.

Also, you'll note that my PR to google/btree is a pull request; I don't have the rights to push to that repo either anymore, just to request changes to those who do. :)

[google-ospo-team]

Google OSPO policy is fine with you having maintainer rights (which I think lets you do everything except make someone else admin?). Our policy is that users are removed when they leave Google, but are welcome to ask to be reinstated.

…

On Fri, Jun 3, 2022 at 1:04 PM 'gram-signal' via Google GitHub Admins < ***@***.***> wrote: Hello! I am currently no longer at Google, and I am no longer actively maintaining this project. I would love it if someone wanted to take on maintenance of this project, but I'm unsure how that would work as I don't appear to have administrative rights to add admins to the project any longer. I was under the impression that that level of access would continue after I left Google, as my github account hasn't changed, but sadly that's not the case. Writing this initially was a labor of love, and I'm super happy to see its use in the outside world. I'd happily bless any work to improve or maintain this, either via re-ownership of the project as it exists or some blessed, maintained fork. Also, you'll note that my PR to google/btree is a pull request; I don't have the rights to push to that repo either anymore, just to request changes to those who do. :) — Reply to this email directly, view it on GitHub <#1016 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXSTVNBYSKRBRQULRDK5J5TVNI3KNANCNFSM5WRTZCFQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Mike Vanne

[gram-signal]

Okay, awesome. Could I request that for my non-Signal account (@gconnell) for google/btree and google/gopacket? I can then work to find potential additional maintainers here to take on the longer-term maintenance.

[google-ospo-team]

Done.

…

On Fri, Jun 3, 2022 at 1:13 PM 'gram-signal' via Google GitHub Admins < ***@***.***> wrote: Okay, awesome. Could I request that for my non-Signal account ***@***.*** <https://github.com/gconnell>) for google/btree and google/gopacket? I can then work to find potential additional maintainers here to take on the longer-term maintenance. — Reply to this email directly, view it on GitHub <#1016 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXSTVNFP26YXXGQAYZCSQS3VNI4L7ANCNFSM5WRTZCFQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Mike Vanne

[gconnell]

Okay, I now have the power! The question is, does anyone want to take over as a maintainer?

[prskr]

These are great news! 🎉

Just for clarification: only (former) Google employees are allowed to take over as maintainer as long as the project remains within the Google organization?

Personally I'd love to contribute as much as my time allows and I'd be fine to review other's PRs but I think it would make sense to either find some developers at Google that are maintaining the project in the future with @gconnell or to move it to another organization (either another company or open source community) that is willing to take care to not rely on a single/few developer(s)?

[gconnell]

@google-ospo-team AFAIK, I appear to have been granted only Collaborator rights, not Maintainer, and thus I'm unable to add others as collaborators/maintainers. Could I be upgraded?

@baez90 If I can get to the maintainer level and find one or two maintainers that would like to keep the project going here, I don't see a problem with it staying in this location. However, if myself and future maintainers aren't allowed to add additional maintainers over time, I agree that moving is probably the best option.

[google-ospo-team]

I'm showing gconnell as having "Role: Maintain".

…

On Tue, Jun 7, 2022 at 1:24 AM 'Graeme Connell' via Google GitHub Admins < ***@***.***> wrote: @google-ospo-team <https://github.com/google-ospo-team> AFAIK, I appear to have been granted only Collaborator rights, not Maintainer, and thus I'm unable to add others as collaborators/maintainers. Could I be upgraded? @baez90 <https://github.com/baez90> If I can get to the maintainer level and find one or two maintainers that would like to keep the project going here, I don't see a problem with it staying in this location. However, if myself and future maintainers aren't allowed to add additional maintainers over time, I agree that moving is probably the best option. — Reply to this email directly, view it on GitHub <#1016 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXSTVNAVMS7BFHJ4NXXO7Z3VN3MH5ANCNFSM5WRTZCFQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Mike Vanne

[wader]

Adding SLL2 support #933 would useful as it seems to be used by modern version of tcpdump etc the-tcpdump-group/tcpdump#850 in some cases.

[mosajjal]

any updates to this thread? maybe someone should fork it and we start supporting it ourselves?