Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

is this repo still alive? #112

Closed
lyonsdpy opened this issue May 26, 2022 · 4 comments
Closed

is this repo still alive? #112

lyonsdpy opened this issue May 26, 2022 · 4 comments
Labels

Comments

@lyonsdpy
Copy link

No description provided.

@nemith
Copy link
Collaborator

nemith commented Jul 22, 2022

This was my first Project in Go back when i worked at Juniper. I have moved onto many different companies since then and have a need for go-netconf again. I think this project is need of a v2 rewrite and I have started that however it may take some time for the API and the features to stabilize.

I will be working on it mostly here: https://github.com/nemith/go-netconf/tree/v2 and tracking it this in #24

Is there anything in particular you are looking for?

@hellt
Copy link

hellt commented Jul 22, 2022

I know this may sound like unsolicited advice, but why don't we, as a community, try to make a single package strong enough?
There is already a solid foundation made by @carlmontanari in https://github.com/scrapli/scrapligo with netconf support lacking just some RPCs.

@nemith
Copy link
Collaborator

nemith commented Jul 22, 2022

@hellt Scrapligo seems like it is trying to be more than just a netconf library. This is trying to be low-level as possible and stick to the RFCs and then be able to be extended by other libraries to add additional functionality. Scrapligo could use the rewrite if they wanted but seems like it's goals are a bit different.

There are some fundamental differences as well. I am not a fan of regexp for matching xml and so there may be some differences in approach which is perfectly fine.

@nemith
Copy link
Collaborator

nemith commented Jul 22, 2022

So i am going to answer "Yes". I am trying to revive some some life into this library which has been stale for too long. And I am going to close this issue for now.

@nemith nemith closed this as completed Jul 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants