<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Inline<br>
</p>
<br>
<div class="moz-cite-prefix">On 11/29/2017 02:14 PM, Summers Pittman
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAEQz2CuUbVBR99eHetJKFCrjdfB9zTF_S8Dv-PvfOZ0nbbF9kw@mail.gmail.com">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Nov 22, 2017 at 10:02 AM,
Wojciech Trocki <span dir="ltr"><<a
href="mailto:wtrocki@redhat.com" target="_blank"
moz-do-not-send="true">wtrocki@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div dir="ltr">Thanks for raising that question - I think
it's really important to talk about it. <br>
I think we had the similar conversation 6 months ago
when kickstarting RainCatcher docs.<br>
<br>
Personally I think is essential for every project to
have his own landing sub page (with documentation,demo
video etc.) that can be accessed easily from feedhenry,
aerogear main web pages.<br>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
Project? sync, push, raincatcher, digger - after that I'm not sure,
is each sdk a project or not?<br>
Do the users care what we consider to be a project? I'm thinking for
mobile.next, the end user might start by considering MCP, but then
later think about sync, then later think about the ios sdk. <br>
<br>
I think<a moz-do-not-send="true"
href="https://en.wikipedia.org/wiki/Lumpers_and_splitters"> this </a>needs
further exploration, but Raincatcher is a good example of things
working well.<br>
<br>
<blockquote type="cite"
cite="mid:CAEQz2CuUbVBR99eHetJKFCrjdfB9zTF_S8Dv-PvfOZ0nbbF9kw@mail.gmail.com">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div dir="ltr">In RainCatcher we went even further and
created separate web page (that is linked in <a
href="http://feedhenry.org" target="_blank"
moz-do-not-send="true">feedhenry.org</a>). <br>
This works pretty well as documentation, getting started
etc. is exposed directly on the main page.<br>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
Yea, I like that there's a feature associated with a set of repos,
and one doc repo to tie the functionality together. We could set the
homepage for all the associated repos to the published version of
the doc repo to tie them together.<br>
<blockquote type="cite"
cite="mid:CAEQz2CuUbVBR99eHetJKFCrjdfB9zTF_S8Dv-PvfOZ0nbbF9kw@mail.gmail.com">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div><br>
I think that <a href="http://feedhenry.org"
target="_blank" moz-do-not-send="true">feedhenry.org</a>
has really good layout itself when listing all
projects. We could just provide less information so
people looking for something specific will not need to
scroll too much. </div>
<div>Spring (any many other aggregating communities) do
the same. For example: <a
href="https://spring.io/docs/reference"
target="_blank" moz-do-not-send="true">https://spring.io/docs/<wbr>reference</a></div>
<div><br>
</div>
<div>We can apply similar list to aerogear website -
however I'm not aware of the impact or challenges in
that area)<br>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
Here's the big one:<br>
<br>
Would it help to redirect aerogear.org to feedhenry.org and host
everything there? I think that's been hinted at, but not asked
explicitly up to now. For me the advantages are:<br>
<br>
* one website is easier than two (process, tooling, communications,
etc)<br>
* addition is easier than subtraction, easier to add digger/push to
feedhenry.org, than to extract dead material from aerogear<br>
* not having to deal with jekyll/plugins ;)<br>
<br>
Paul<br>
<br>
<blockquote type="cite"
cite="mid:CAEQz2CuUbVBR99eHetJKFCrjdfB9zTF_S8Dv-PvfOZ0nbbF9kw@mail.gmail.com">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div class="gmail_extra"><br>
<div class="gmail_quote">
<div>
<div class="gmail-h5">On Wed, Nov 22, 2017 at 1:59
PM, Paul Wright <span dir="ltr"><<a
href="mailto:pwright@redhat.com"
target="_blank" moz-do-not-send="true">pwright@redhat.com</a>></span>
wrote:<br>
</div>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px
0px 0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div>
<div class="gmail-h5">
<div bgcolor="#FFFFFF">
<p>Hi AeroGear, FeedHenry<br>
<br>
As part of a review of Digger (Build Farm)
docs, I created a <a
href="https://github.com/aerogear/aerogear.org/pull/687"
target="_blank" moz-do-not-send="true">PR</a>
to attempt to improve user navigation of: <br>
</p>
<p><a href="https://aerogear.org/"
target="_blank" moz-do-not-send="true">https://aerogear.org/</a><br>
<br>
Feedback on that PR raised the question of
general navigation of this web site:<br>
<br>
* What should be in the Getting Started menu
to help me get started with digger? (I think
digger is more than a code snippet or
library)<br>
<br>
* If I'm interested in digger, should I
expect any digger info under module or
platform menu items?<br>
<br>
* I sometimes navigate to a page, but can't
remember how I navigated to it, then cannot
find the info again.<br>
<br>
These issues can be resolved, but will
require a lot of effort, but another
question is:<br>
<br>
* Will it provide us a platform to build the
community we want?</p>
<p> The web site looks great, and I learn a
lot from browsing it (eg I didn't know about
<a
class="gmail-m_-4556633413436706799m_-2638042873182333710m_-7459261403132971927moz-txt-link-freetext"
href="https://aerogear.org/sync/"
target="_blank" moz-do-not-send="true">https://aerogear.org/sync/</a>
until today), but I wonder if it is doing
the job we want it to do? and how do we keep
it up-to-date? (<a
class="gmail-m_-4556633413436706799m_-2638042873182333710m_-7459261403132971927moz-txt-link-freetext"
href="https://aerogear.org/docs/planning/"
target="_blank" moz-do-not-send="true">https://aerogear.org/docs/pla<wbr>nning/</a>)<br>
<br>
Meanwhile over at:<br>
<br>
<a href="http://feedhenry.org/docs/"
target="_blank" moz-do-not-send="true">http://feedhenry.org/docs/</a><br>
<br>
Not much there at the moment, but it will be
the location for mobile.next doc <br>
<br>
* Do we want users switching from MCP doc on
<a href="http://feedhenry.org"
target="_blank" moz-do-not-send="true">feedhenry.org</a>
over to digger doc on <a
href="http://aerogear.org" target="_blank"
moz-do-not-send="true">aerogear.org</a>
and back again for some fh.sync doc?<br>
<br>
These are difficult and challenging
questions, I don't expect them to be easy to
resolve and I'm happy to agree with whatever
the communities decide to do. All this mail
hopes to do is to raise the question of<br>
<br>
* How do we communicate the "mobile.next"
(i.e. feedhenry mcp and aerogear digger)
message as cleanly as possible?<br>
<br>
(The real challenge occurs after that,
convincing them to adopt mobile.next, but
users will never adopt if they can't find
answers they hit the first stumbling block)<br>
<br>
thanks,<br>
<br>
Paul</p>
</div>
<br>
</div>
</div>
______________________________<wbr>_________________<br>
feedhenry-dev mailing list<br>
<a href="mailto:feedhenry-dev@redhat.com"
target="_blank" moz-do-not-send="true">feedhenry-dev@redhat.com</a><br>
<a
href="https://www.redhat.com/mailman/listinfo/feedhenry-dev"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://www.redhat.com/mailman<wbr>/listinfo/feedhenry-dev</a><br>
<br>
</blockquote>
</div>
<span class="gmail-HOEnZb"><font color="#888888"><br>
</font></span></div>
</blockquote>
<div><br>
</div>
<div>Bumping this a bit.</div>
<div><br>
</div>
<div>Over the summer the community team put together a
backlog of items to update the feedhenry sdk page,
automate some documentation and blogging aggregation, and
begin to plan on how we would keep docs, demos, etc up to
date from a community perspective.</div>
<div><br>
</div>
<div><a
href="https://issues.jboss.org/secure/PortfolioPlanView.jspa?id=28&sid=30#backlog"
moz-do-not-send="true">https://issues.jboss.org/secure/PortfolioPlanView.jspa?id=28&sid=30#backlog</a>
(if that isn't working let me know).<br>
</div>
<div><br>
</div>
<div>While we didn't look at the aerogear community as we
were focusing on "feedhenry" it may be a good opportunity
to spin the team back up and bring Aerogear into its
fold. This will mean either maintaining two websites and
brands or combining them into a single landing page for
docs and community to feed into the mobile upstream. </div>
<div><br>
</div>
<div>MCP plays an important role in this because it is
pulling together a lot of the strings from AeroGear,
Wildfly, node.js, jboss, feedhenry, etc into a single
"launchpad".</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div class="gmail_extra"><span class="gmail-HOEnZb"><font
color="#888888"><br clear="all">
<div><br>
</div>
-- <br>
<div
class="gmail-m_-4556633413436706799gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div style="font-size:12.8px">
<p
style="color:rgb(0,0,0);font-family:overpass,sans-serif;font-weight:bold;margin:0px;padding:0px;font-size:14px;text-transform:uppercase"><span>WOJCIECH</span> <span>TROCKI</span></p>
<p
style="font-family:overpass,sans-serif;margin:0px;font-size:10px;color:rgb(153,153,153)"><a
href="https://www.redhat.com/"
style="color:rgb(0,136,206);margin:0px;text-decoration:none"
target="_blank"
moz-do-not-send="true">Red
Hat <span>Mobile</span></a></p>
<p
style="font-family:overpass,sans-serif;margin:0px
0px
6px;font-size:10px;color:rgb(153,153,153)"><span>IM: <span>wtrocki</span></span></p>
<table
style="color:rgb(0,0,0);font-family:overpass,sans-serif;font-size:medium"
border="0">
<tbody>
<tr>
<td width="100px"><a
href="https://red.ht/sig"
target="_blank"
moz-do-not-send="true"><img
src="https://www.redhat.com/files/brand/email/sig-redhat.png"
moz-do-not-send="true"
width="90"
height="auto"></a></td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</font></span></div>
<br>
______________________________<wbr>_________________<br>
feedhenry-dev mailing list<br>
<a href="mailto:feedhenry-dev@redhat.com"
moz-do-not-send="true">feedhenry-dev@redhat.com</a><br>
<a
href="https://www.redhat.com/mailman/listinfo/feedhenry-dev"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://www.redhat.com/<wbr>mailman/listinfo/feedhenry-dev</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
<br>
</body>
</html>