[JBoss JIRA] (JBIDE-17162) Provide sha hashes for JBT/JBDS files on tools.jboss.org
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17162?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-17162:
----------------------------------
Assignee: Nick Boldt
> Provide sha hashes for JBT/JBDS files on tools.jboss.org
> --------------------------------------------------------
>
> Key: JBIDE-17162
> URL: https://issues.jboss.org/browse/JBIDE-17162
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: website
> Affects Versions: 4.2.0.Beta1
> Reporter: Marián Labuda
> Assignee: Nick Boldt
> Fix For: 4.2.0.Beta2
>
>
> We are providing md5s hashes for JBT and JBDS files (archives links under Update Site Zip). Bcs. it is long known about md5 security flaws (collisions) it is recommended to use sha hashes instead.
> Question is - do we provide md5 hashes only because of data integrity (if there are any missing bits after download) or we are trying to ensure security? In first case it's enough to use md5 (although there could be also hash collisions but it's unlikely). In second case there could be for example performed MITM attack (or any other...) and our files could be replaced by malformed/infected - there should be provided sha hashes instead of md5, but there still remains question if it would be enough without having not-secured web pages (without certificate) and sha links leading to sourceforge (I think that it would not be enough and hashes would have to be stored on tools.jboss.org domain).
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (TOOLSDOC-492) Create new docs landing page on new tools.jboss.org site (moving to asciidoc for docs in process)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-492?page=com.atlassian.jira.plug... ]
Nick Boldt edited comment on TOOLSDOC-492 at 5/5/14 2:14 AM:
-------------------------------------------------------------
PR to move content from where I had it to the new path, website/webcontent/userguide/. Also moved to lowercase files, and purges empty .adoc files + sample generated files (.pdf, .md, .epub., .html):
https://github.com/jbosstools/jbosstools-documentation/pull/255
[~mmurray] if you like this one, feel free to merge it in (and I can close PR # 254).
Live browseable content is here:
https://github.com/nickboldt/jbosstools-documentation/tree/TOOLSDOC-492_2...
was (Author: nickboldt):
PR to move content from where I had it to the new path, website/webcontent/userguide/. Also moved to lowercase files, and purges empty .adoc files + sample generated files (.pdf, .md, .epub., .html):
https://github.com/jbosstools/jbosstools-documentation/pull/255
[~mmurray] if you like this one, feel free to merge it in (and I can close PR # 254).
> Create new docs landing page on new tools.jboss.org site (moving to asciidoc for docs in process)
> -------------------------------------------------------------------------------------------------
>
> Key: TOOLSDOC-492
> URL: https://issues.jboss.org/browse/TOOLSDOC-492
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: User Guide
> Affects Versions: 4.2.0.Beta1
> Reporter: Nick Boldt
> Assignee: Michelle Murray
> Fix For: 4.2.0.Beta2
>
> Attachments: converted-adoc-asciidoc-css-not-github-css.png, converted-adoc-github-css-actual.png, converted-adoc-github-css.png, openshift-chapter-generated-epub.png, openshift-chapter-generated-pdf.png
>
>
> With the release of the new tools.jboss.org site, it's time to migrate the docs to the same skin / format / markup. Docbook is dead, long live Asciidoc!
> What [~mmurray] and I are thinking is that we would have a new landing page similar to one of these:
> http://tools.jboss.org/features/ (with icons that link to projects' latest doc)
> or
> http://tools.jboss.org/documentation/whatsnew/ (with the latest doc linked)
> And then under that landing page we'd have doc for each of projects' contributions to the User Guide, by milestone or Final release.
> Questions:
> a. [~maxandersen] [~burrsutter] [~mmusaji] Do we still need to provide 3 formats of doc - HTML, HTML-single, and PDF? Or can we replace that with this new content, PLUS include inline help doc within Eclipse? (That's another issue - see [~dgolovin] 's https://github.com/dgolovin/jbosstools-eclipse-docs/blob/master/docs/scen... for prototype)
> b. [~maxandersen] Should we include docs for "dead" projects like Freemarker, Portal, etc.? I'm guessing YES, even if the doc becomes out of date (ie., the doc for JBT 4.2 for Freemarker won't have changed much (or at all) since JBT 4.0/4.1).
> c. [~maxandersen] Should we convert old JBT 4.1.x (and/or 4.0.x, 3.3.x) doc to the new adoc format, or just start w/ the JBT 4.2.0.Beta1/2 doc? I'd be OK with 4.1 and maybe 4.0, but can we skip 3.3 since JBDS 5 is no longer fully supported?
> d. Will docbook2asciidoc [0] work for batch-converting docbook docs to adoc? @nick will try. If conversion works easily, then converting older User Guides is definitely more doable / less time consuming.
> [0] https://github.com/oreillymedia/docbook2asciidoc
> e. [~xcoulon] Is :page-component_version: still used, eg., in [1], or is the filename version itself used to categorize the content by milestone?
> [1] https://github.com/jbosstools/jbosstools-website/blob/master/documentatio...
> f. If we decide to continue to include other formats (eg., html-single, pdf) should we link to those from these places [2], [3]?
> [2] http://tools.jboss.org/downloads/overview.html
> [3] http://tools.jboss.org/downloads/jbosstools/luna/4.2.0.Beta1.html
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (TOOLSDOC-492) Create new docs landing page on new tools.jboss.org site (moving to asciidoc for docs in process)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-492?page=com.atlassian.jira.plug... ]
Nick Boldt commented on TOOLSDOC-492:
-------------------------------------
PR to move content from where I had it to the new path, website/webcontent/userguide/. Also moved to lowercase files, and purges empty .adoc files + sample generated files (.pdf, .md, .epub., .html):
https://github.com/jbosstools/jbosstools-documentation/pull/255
[~mmurray] if you like this one, feel free to merge it in (and I can close PR # 254).
> Create new docs landing page on new tools.jboss.org site (moving to asciidoc for docs in process)
> -------------------------------------------------------------------------------------------------
>
> Key: TOOLSDOC-492
> URL: https://issues.jboss.org/browse/TOOLSDOC-492
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: User Guide
> Affects Versions: 4.2.0.Beta1
> Reporter: Nick Boldt
> Assignee: Michelle Murray
> Fix For: 4.2.0.Beta2
>
> Attachments: converted-adoc-asciidoc-css-not-github-css.png, converted-adoc-github-css-actual.png, converted-adoc-github-css.png, openshift-chapter-generated-epub.png, openshift-chapter-generated-pdf.png
>
>
> With the release of the new tools.jboss.org site, it's time to migrate the docs to the same skin / format / markup. Docbook is dead, long live Asciidoc!
> What [~mmurray] and I are thinking is that we would have a new landing page similar to one of these:
> http://tools.jboss.org/features/ (with icons that link to projects' latest doc)
> or
> http://tools.jboss.org/documentation/whatsnew/ (with the latest doc linked)
> And then under that landing page we'd have doc for each of projects' contributions to the User Guide, by milestone or Final release.
> Questions:
> a. [~maxandersen] [~burrsutter] [~mmusaji] Do we still need to provide 3 formats of doc - HTML, HTML-single, and PDF? Or can we replace that with this new content, PLUS include inline help doc within Eclipse? (That's another issue - see [~dgolovin] 's https://github.com/dgolovin/jbosstools-eclipse-docs/blob/master/docs/scen... for prototype)
> b. [~maxandersen] Should we include docs for "dead" projects like Freemarker, Portal, etc.? I'm guessing YES, even if the doc becomes out of date (ie., the doc for JBT 4.2 for Freemarker won't have changed much (or at all) since JBT 4.0/4.1).
> c. [~maxandersen] Should we convert old JBT 4.1.x (and/or 4.0.x, 3.3.x) doc to the new adoc format, or just start w/ the JBT 4.2.0.Beta1/2 doc? I'd be OK with 4.1 and maybe 4.0, but can we skip 3.3 since JBDS 5 is no longer fully supported?
> d. Will docbook2asciidoc [0] work for batch-converting docbook docs to adoc? @nick will try. If conversion works easily, then converting older User Guides is definitely more doable / less time consuming.
> [0] https://github.com/oreillymedia/docbook2asciidoc
> e. [~xcoulon] Is :page-component_version: still used, eg., in [1], or is the filename version itself used to categorize the content by milestone?
> [1] https://github.com/jbosstools/jbosstools-website/blob/master/documentatio...
> f. If we decide to continue to include other formats (eg., html-single, pdf) should we link to those from these places [2], [3]?
> [2] http://tools.jboss.org/downloads/overview.html
> [3] http://tools.jboss.org/downloads/jbosstools/luna/4.2.0.Beta1.html
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBIDE-17125) Website: Text in banner/header should not contain "A"
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17125?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-17125:
---------------------------------------------
ah i see it worked locally - so yeah, thats weird and something to look at. maybe we got different version of css when running locally? [~xcoulon] ?
> Website: Text in banner/header should not contain "A"
> -----------------------------------------------------
>
> Key: JBIDE-17125
> URL: https://issues.jboss.org/browse/JBIDE-17125
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: website
> Affects Versions: 4.2.0.Beta1
> Reporter: Marián Labuda
> Assignee: Max Rydahl Andersen
> Priority: Minor
> Fix For: 4.2.0.Beta2
>
> Attachments: fixed-17125.png, header.png
>
>
> Banner / header or whatever it is called contain text "A JBoss Project". I think that "A" should not be here - it should be "JBoss Project". !header.png!
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBIDE-17125) Website: Text in banner/header should not contain "A"
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17125?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-17125:
---------------------------------------------
this issue goes against the guidelines/recommendation given from goldengate project and it can be seen on http://example.jboss.org/ that it really should have an "A" according to these.
Would be great if we didn't push commits to master if even when run locally it breaks too. I'm going to revert the commits to master.
> Website: Text in banner/header should not contain "A"
> -----------------------------------------------------
>
> Key: JBIDE-17125
> URL: https://issues.jboss.org/browse/JBIDE-17125
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: website
> Affects Versions: 4.2.0.Beta1
> Reporter: Marián Labuda
> Assignee: Max Rydahl Andersen
> Priority: Minor
> Fix For: 4.2.0.Beta2
>
> Attachments: fixed-17125.png, header.png
>
>
> Banner / header or whatever it is called contain text "A JBoss Project". I think that "A" should not be here - it should be "JBoss Project". !header.png!
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months