-
Notifications
You must be signed in to change notification settings - Fork 70
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
Congratulation #1
Comments
hi Thomas First I want to thank you! we wrote this project in 2011 within Cisco as an internal project, and at that time I reference your yes, I can change the daemon name from And the same issue happened in So if I want to keep the package name as openbgp or openbmp in github and pypi, is there any problem in future? I am not familiar with open source policy, please help me. BR, Peng Xiao |
Hi Peng, You can not always avoid name clashes as there is not policy. But having a name similar to an existing project with cause you a few issues:
Overall it is confusing for the user, hence why it is preferable, nothing more. Sincerely, Thomas |
thanks, I will think about a new name for our project |
For a first release, the code is clean and quite easy to read. I wish you all the best with openbgp.
It is just unfortunate that a popular open source daemon called "openbgpd" already exists ( http://www.openbgpd.org/ ). You may want to consider another name for your project ( it is not too late ) or at least make sure the daemon is not called the same as openbsd's one.
Oh, and do not do my mistake and use str for anything: like you did with "construct", use a different function to generate string representation of BGP objects.
Best of luck.
The text was updated successfully, but these errors were encountered: