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

["Scott M. Likens" < >]

My 10c,

If nothing else they could create an empty public repo just for
reporting bugs.  I admit CoreOS made me fond of this idea as it helps
with triage.

https://github.com/coreos/bugs/issues

On 1/10/15 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
> !DSPAM:54b11ea3231786337816477!

Attachment: signature.asc
Description: OpenPGP digital signature