[chef-dev] Re: turning the opscode-webui2 repo from private to public

[Adam Jacob < >]

You can report bugs at the chef-server repo. It's not on github because it is not open source - the fact that you can see it within the (proprietary licensed) package doesn't mean you can fork,edit, compile, or even run it without submitting to our terms of use. 

Sent from my iPhone

On Jan 10, 2015, at 4:44 AM, Ferenc Kovacs < "> > wrote:

Hi,

I've asked this at the last irc meeting, but it wasn't on the agenda so I was asked to discuss it at a later time.

I was told that the webui2 repo is kept private mainly because it is a proprietary product. When asked how would turning the repo would make any difference when we already share the code publically as part of the opscode-manage plugin/package I was told that there are some _javascript_ files which are only available in minified form in the package.

Given how easy is to reformat js code if no other obfuscated method is used, I think that keeping the repo private doesn't really help with anything, but makes it harder to report bugs (as AFAIK the prefered method is to use github issues for reporting the bug to the appropriate repository) or to send pull request.

I would like to know if there are other reasons for keeping the repo private or if there is any chance or plans for turning it into public.

Thanks!

--

Ferenc Kovács
@Tyr43l - http://tyrael.hu