You are not logged in.
Hi,
I have a couple of questions
1) Your terms says the following:
"Portions of the Epic Browser are available in source code form under the terms of the BSD License at http://www.chromium.org. Nothing in this Agreement will be construed to limit any rights granted under the Open Source Licenses. Subject to the foregoing, the Epic Browser, for itself and on behalf of its licensors, hereby reserves all intellectual property rights in the Product, except for the rights expressly granted in this Agreement. "
and
"U.S. GOVERNMENT END-USERS. The Product is a "commercial item," as that term is defined in 48 C.F.R. 2.101, consisting of "commercial computer software" and "commercial computer software documentation," as such terms are used in 48 C.F.R. 12.212 (Sept. 1995) and 48 C.F.R. 227.7202 (June 1995). Consistent with 48 C.F.R. 12.212, 48 C.F.R. 27.405(b)(2) (June 1998) and 48 C.F.R. 227.7202, all U.S. Government End Users acquire the Product with only those rights as set forth herein."
The question is is epic really an open source project? Do you plan to release the full source code along with build instructions just like firefox or chromium? or are you planning to just release portions of the project?
2) What is the timeline for the official source code release?
3) Will you use a public source repository where developers can submit patches, etc?
Offline
Sorry about the TOU, we need to edit that, you're right - we didn't review that properly!! Good catch!
We're working on at least 2 major updates...so will probably take a few weeks for an official full release...plan to be a public repository. Btw, again write us for any files or anything you need - a few users have asked for some files and that was great. We haven't gotten any patches back yet (!), but if you or anyone would like to start working on Epic, we're more than happy to send you files, get anyone started.
We intend to release virtually all source code (I say almost all because certain things we may not be able to release like a list of IPs for a proxy bank or anything sensitive (but even that stuff we'll allow some third parties to view)). Not sure about how detailed our build instructions will be, etc., mainly because we're a really small team & chromium is huge and not that easy to work with!
Sorry for the delay - given its size, will take some time, and our project is a little different. We'd love help & do need contributors. Please write us to join us immediately.
Offline