OPENCORES.ORG

Quite simply, what problem are you solving? The problem that was raised

Guy, I am not offering a solution to any problem. All I am presenting
is an idea, that allows the developer to control who accesses parts of
their codes.

Let me clarify, I am NOT for denying access to codes, what I have in
mind is a system where a developer can restric access to a PART of his
codes and show it  to only those individuals he chooses to.  These
people can be fellow contributors on OC, who could possibly provide
more help on the code and less negative communication. People willing
to work on verification etc can mail the author, who gives them access
to some files. Such restrictions could be applied on 'works in
progress' and beta releases. Once a stable copy is complete, the
developer releases it to the community, in its entirety.

In the end, it is upto the developer on how much access he chooses to
provide in the early stages.

Regards,
Abhijit

On 4/15/06, Guy Hutchison <ghutchis@g...> wrote:

> Quite simply, what problem are you solving?  The problem that was raised
> was, in my mind, that developers will be unwilling to release code for fear
> of negative communication received on the mailing list.
>
> If we restrict access to the cores, then it is true -- no one can see the
> code, so no one can complain.  But then what's the point of the site?  The
> idea of open source is to freely disseminate information.  Loading up code
> downloads with a bunch of restrictions would defeat that idea.
>
> The problem you appear to be solving is misuse of code and license
> violations by people who access the code.  I haven't heard that this has
> been a problem to date.
>
> - Guy
>
>
>
> _______________________________________________
> http://www.opencores.org/mailman/listinfo/cores
>
>