Great, thanks for the links and for working on the plan. I think the
community should align on the requirements of the new website as long as
it's still in development. We can then do an analysis in how far the
current state of the beta website differs from the requirements and make
that part of
What I have written doesn't directly align with the beta site. The site was
created by Mu, and several people have contributed to updating it with
content. The repo is here https://github.com/mli/new-docs
There's no architecture doc afaik.
I have docs for a redesign and new ux in the wiki:
I see. Would you mind linking the thread/doc where we discussed the
requirements for the new website?
-Marco
On Thu, Jul 18, 2019 at 9:49 PM Aaron Markham
wrote:
> I agree with you. I'd like the website to be fairly standard Jekyll and
> normal front end stuff, rather than a Sphinx template.
I agree with you. I'd like the website to be fairly standard Jekyll and
normal front end stuff, rather than a Sphinx template. Docs would be docs
built by doxygen, Sphinx, Scala, java, etc, based on their native docs
generation, and we'd get a microsite for each language binding. If one
breaks it
I'm not entirely sure about dropping docs for old versions to be honest.
The root cause in my opinion is the fact that the build is wy to
complicated. If it would have less dependencies and be more
straight-forward, it should be a matter of seconds. The key here could be
to separate the docs
I'd have it check signatures. Ssl is optional I think. China users seem to
have issues with SSL... That may have changed, but I think we might have to
work around that for background downloads for models.
With regard to the current links to dmlc.ml, I asked ivy to just get rid of
them with # if
While we are at it, we should maybe also take about SSL to avoid these
kinds of downloads in future.
-Marco
Aaron Markham schrieb am Mi., 17. Juli 2019,
01:20:
> Hi Hen,
> We still have all of the these models that are referenced in this
> issue:
Hi Hen,
We still have all of the these models that are referenced in this
issue: https://github.com/apache/incubator-mxnet/issues/15410
I think it's a pretty big security breach to have systems that do
automatic downloading point to a malware site. Anything that fetches
binary data should be well
Nice work :)
What other links does the project have that are outside Apache Infra
control and have this risk?
Outside of github.com/dmlc which is well known and iiuc in process for
resolving.
Hen
On Tue, Jul 9, 2019 at 4:46 PM Aaron Markham
wrote:
> The PR has passed CI. Please take a look.
The PR has passed CI. Please take a look.
https://github.com/apache/incubator-mxnet/pull/15454
We really need to get rid of those malware links, and this does that,
restores the Julia docs with a local build, has CI coverage, and a new
Ubuntu guide (since I had to figure out how to use Julia and
Hi,
I will add +1 to the micro-site approach.
Since I have tried to take the generated MD outputs from
Julia's doc system, but the syntax is incompatible with
the MD plugin of Sphinx.
Iblis Lin
林峻頤
On 7/4/19 12:12 PM, Aaron Markham wrote:
Hi dev@,
In case you missed the issues with the
Hi dev@,
In case you missed the issues with the dmlc.ml domain, it was let go
or sniped and now goes to a malware site. [1] Several assets like
models and the Julia documentation were hosted there.
I made some progress getting the Julia docs generated as part of the
regular website build flow.
12 matches
Mail list logo
