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.

Sign up for GitHub

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

Jump to bottom

Discuss how code improvements should be published #3

Open
cesarsouza opened this issue Jan 2, 2015 · 1 comment
Open

Discuss how code improvements should be published #3

cesarsouza opened this issue Jan 2, 2015 · 1 comment

Comments

@cesarsouza
Copy link
Member

After #1, #2 and other issues are done, it would be needed to discuss how those features could be made available to the world.
@cesarsouza
Copy link
Member Author

Since some of the features were needed right now for use in Accord.NET (and one personal project that uses Accord/AForge), I incorporated some of them directly in Accord.NET (of course keeping all the previous copyrights, licensing schemes, etc). However, I kept them as internal classes while we see how the publishing could be done.

The point is that I wasn't planning on incorporating those classes directly in Accord, but rather keep AForge.NET around. The problem is that I can't publish those modifications under the AForge.NET name, for example, in NuGet.

@cesarsouza cesarsouza mentioned this issue Apr 4, 2015
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cesarsouza