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

[Ferenc Kovacs < >]

On Sun, Jan 11, 2015 at 1:31 AM, Adam Jacob < " target="_blank"> > wrote:

You can report bugs at the chef-server repo.

thanks!

 

It's not on github because it is not open source

(it is on github, but in a private repo, under opscode/opscode-webui2),

yeah, I was aware that it isn't open source(only Chef Server core is licensed under the Apache license) but in it's current situation (where there seems to be no "secret" stuff in the repo) I thought it would make sense to have it in a public repo, and the replies I got it on irc was showing that the idea was at least considered before:

https://botbot.me/freenode/chef-hacking/2015-01-08/?msg=29060922&page=2

 

- 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.

of course, but does that mean that if I find an obvious bug I can't paste the diff for the fix to the github issue?

if that's ok, I fail to see why would it bad if it would be easier to report/fix bugs or just communicate about them (see https://github.com/opscode/opscode-omnibus/issues/535#issuecomment-58610366 or https://github.com/opscode/opscode-omnibus/issues/534#issuecomment-58129263 or https://tickets.opscode.com/browse/CHEF-5123?page=com.atlassian.jira.plugin.system.issuetabpanels:changehistory-tabpanel) where it is a PITA to follow the discussion for those without access to the repo.

but IANAL, and it is your decision, it was just something I wanted to ask!

--

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