Thanks for clarifying this for us Alexey

_________________
Want to write for GNS3? Send me a message.

I contributed and my name does not appear to be listed.

For confidentially of those who contributed and didn't want their name in the software - we have made it so that you have to sign up through the members portal to get your name in the software. http://members.gns3.net/name-in-source-code/

If you have entered your name - then we are doing a final update at the end of Beta for all the remaining names.

Thanks

_________________
Want to write for GNS3? Send me a message.

@Pyzon


Sorry about this, unfortunately the list hasn't been updated with the last names we received. It will for sure in the next beta.

@adecisco


No you are very relevant and we are sorry if you name doesn't appear yet in the list.

@Technologov

I am sorry you feel that way but I don't think we have been disrespectful here. It is true we forgot to give credits in the about dialog but we were simply focused on building features. I apologize for this. However, this version of GNS3 is a complete rewrite and the number of people who have contributed to this version is limited.



Actually around 95% code of GNS3 itself is written by me. The software you mentioned are external tools/dependencies. To be more specific:

- Dynagen is not used at all in the new GNS3.
- Dynamips is a completely separate project, even if I agree we could never thanks Chris and the people who contribute to this project enough.
- Vboxwrapper is also an external dependency that I did not plan to use but did anyway because of the vboxapi/xpcom module not working with Python3.

The only pieces of code I have taken are from vboxwrapper (and are actually yours) and I have modified them a bit, you can have a look by yourself: https://github.com/GNS3/gns3-server/blo ... vm.py#L704





We will take these suggestions into consideration for the next release.

One last thing: relax! This is only beta ;)

Cheers,

_________________
Jeremy, GNS3 Programmer & Benevolent Dictator for Life.

The idea is that people who write portions of the code, should also include their name with a GIT push into the project. If they do not do that, this means they are not interested to see their name there.

For open-source projects which are incorporated into GNS3, which most probably are under GPL licenses, please just post a link to the project. And redistribute your software based on a compatible license. For example when you incorporate a MIT license, there is no reason to do anything.

We should look into this only from a Legal Perspective, otherwise there will be resources spent on tasks which are not important at all, like maintaining lists of names. And this will translate only to a lower quality of the final product.

As an example, please look at Wireshark, an amazing product: do they keep a list of names?

_________________

People written themselves in v0.8.x code, but suddenly got removed by v1.0.

Yes... to reiterate what Jeremy said...



GNS3 0.8.x (https://github.com/GNS3/gns3-legacy) is a COMPLETELY different codebase than that of GNS3 v1 (https://github.com/GNS3/gns3-gui, https://github.com/GNS3/gns3-server)

So those developers who contributed to GNS3 0.8.x the work isn't lost (see the legacy repo). As people contribute code to the new version, I am sure that Jeremy will not hesitate to give them credit where it is due.

As for things like Dynamips, VPCS etc... I don't feel there is a need to include all the developers of those in GNS3. They are seperate programs (and whilst they work hand in hand... they could/can/are used seperately). Recognition of work/contribution is a matter for each individual program.

_________________
Daniel
Forum Moderator & Debian Package Maintainer for GNS3, Dynamips & VPCS.
Standalone DEB Packages are available from http://gns3.serverb.co.uk - To be updated!