We were talking about this in our team and wanted to give some feedback as we (RHMAP core team) are the ones who perhaps interact with AeroGear and FeedHenry communities/organizations more often than other people.

Wojciech, Paolo and their team has a spent a very good time on thinking about how to improve FeedHenry community and build/expand RainCatcher community.

I think moving things to FeedHenry and calling UPS "FH AG Push" sounds good. 

I won't go and do a full assessment of both communities/organizations but if we're doing this, we should definitely move these things from AeroGear to FeedHenry side and make sure they don't break in the future at least the current AeroGear things where things are working nicely:
* Stable processes (release, JIRA workflow, etc.)
* Open source first mentality (100% community releases, etc.)
* Somewhat active non Red Hat community members

One of the problems that I am having right now is finding people that should be the owners for AeroGear things, such as the website, aerogear.org. If we are going to do this merger, we should clarify the owners of components.

I would like to say that we, as RHMAP core/onprem team, are interested in owning the transition work (not any new components explicitly, but the transition work!) from AeroGear to FeedHenry collaborating with community leaders and members from the both side as well as MCP people.

RHMAP docs team is another group of people that interact with AG and FH quite often and they told me they're here for help whatever direction we go.


On Wed, Nov 29, 2017 at 5:14 PM, Summers Pittman <supittma@redhat.com> wrote:

On Wed, Nov 22, 2017 at 10:02 AM, Wojciech Trocki <wtrocki@redhat.com> wrote:
Thanks for raising that question - I think it's really important to talk about it. 
I think we had the similar conversation 6 months ago when kickstarting RainCatcher docs.

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.
In RainCatcher we went even further and created separate web page (that is linked in feedhenry.org). 
This works pretty well as documentation, getting started etc. is exposed directly on the main page.

I think that feedhenry.org 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. 
Spring (any many other aggregating communities) do the same. For example: https://spring.io/docs/reference

We can apply similar list to aerogear website - however I'm not aware of the impact or challenges in that area)

On Wed, Nov 22, 2017 at 1:59 PM, Paul Wright <pwright@redhat.com> wrote:

Hi AeroGear, FeedHenry

As part of a review of Digger (Build Farm) docs,  I created a PR to attempt to improve user navigation of:


Feedback on that PR raised the question of general navigation of this web site:

* 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)

* If I'm interested in digger, should I expect any digger info under module or platform menu items?

* I sometimes navigate to a page, but can't remember how I navigated to it, then cannot find the info again.

These issues can be resolved, but will require a lot of effort, but another question is:

* Will it provide us a platform to build the community we want?

The web site looks great, and I learn a lot from browsing it (eg I didn't know about https://aerogear.org/sync/ 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? (https://aerogear.org/docs/planning/)

Meanwhile over at:


Not much there at the moment, but it will be the location for mobile.next doc

* Do we want users switching from MCP doc on feedhenry.org over to digger doc on aerogear.org and back again for some fh.sync doc?

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

* How do we communicate the "mobile.next" (i.e. feedhenry mcp and aerogear digger) message as cleanly as possible?

(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)



feedhenry-dev mailing list

Bumping this a bit.

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.

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.  

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".



Red Hat Mobile

IM: wtrocki

feedhenry-dev mailing list

feedhenry-dev mailing list