<div dir="ltr">Hi Paul,<div><br></div><div>lot's of content on the AeroGear website is out of date, due to lack of work in the past two years (see the planing page).</div><div><br></div><div>Note: the sync was a prototype, for real-time sync; based on different algorithms and papers in that area, but never went really anywere... </div><div>I guess it's dead now.</div><div><br></div><div>Over the past two years we did work a bit on the AeroGear Push server, and their libraries (e.g. mobile client-side lib and server-side integrations for node/java).</div><div><br></div><div>Regarding Digger - it's a standalone project, under the aerogear realm - like push. Both bits can be used completely independent. </div><div><br></div><div><br></div><div>I think some content (e.g. sync) needs to be removed (while we can still keep the repos), but we should be perhaps focusing on AeroGear UPS and digger, for community offerings.</div><div><br></div><div><a href="http://ag.org/push">ag.org/push</a> (like is)</div><div><a href="http://ag.org/digger">ag.org/digger</a> (with backgrounds motivations, Laura's videos etc)</div><div><br></div><div><br></div><div>Regarding feedhenry / mcp , just one comment: it does integrate w/ AG features, such as push or digger, and will IMO offer the integration parts (e.g. APBs etc)</div><div><br></div><div><br></div><div>-Matthias</div><div><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Nov 22, 2017 at 2:59 PM, Paul Wright <span dir="ltr"><<a href="mailto:pwright@redhat.com" target="_blank">pwright@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<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">PR</a> to attempt to improve user navigation of:
<br>
</p>
<p><a href="https://aerogear.org/" target="_blank">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="m_2607500947793605963m_-7459261403132971927moz-txt-link-freetext" href="https://aerogear.org/sync/" target="_blank">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="m_2607500947793605963m_-7459261403132971927moz-txt-link-freetext" href="https://aerogear.org/docs/planning/" target="_blank">https://aerogear.org/docs/pla<wbr>nning/</a>)<br>
<br>
Meanwhile over at:<br>
<br>
<a href="http://feedhenry.org/docs/" target="_blank">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">feedhenry.org</a>
over to digger doc on <a href="http://aerogear.org" target="_blank">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>______________________________<wbr>_________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/aerogear-dev</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a></div></div></div>
</div></div>