Hey Paul,

On Wed, Jan 3, 2018 at 8:13 AM, Paul Wright <pwright@redhat.com> wrote:

Hi Daniel,

I like the idea (I think this is how the docs organization should be driven), how about:

As a developer or contributor, I'd like to know what repos are associated with the feature/platform I'm planning to develop for.

I think this was the original intention behind the 'Modules' pulldown on aerogear.org which, for example, links to https://aerogear.org/sync/. Unfortunately, the repos link doesn't work as expected for me. (and I'm not sure if changing the link to https://github.com/search?q=org%3Aaerogear+sync is a good solution)

q instead of search in your query string. Here is an example:

You should use https://github.com/aerogear?q=sync

As I've said earlier [1], I find aerogear.org difficult to maintain (it's now a mishmash of html/markdown/asciidoc, with dependencies I seem to have difficulty following [2].

I totally agree with you, I know that pain. There is a lot of history behind of this mess. I also don't like this.

If there isn't an appetite for changing to asciibinder, I can still help reorganize, update and publish documentation, and this seems as good an issue as any to start with. How about doing this collation on the wiki (using asciidoc):

https://github.com/aerogear/aerogear.org/wiki

I'm not a big fan of Asciidoctor, I usually prefer to use Markdown, because it is more simple and more community driven, but I'm not against to use any other thing, just wanna use only *one* thing :)

I don't know that is the best approach to solve it. Not sure if a wiki in the aerogear.org or if we should move the documentation for wiki in each repo. I only know docs is a little outdated and maintain it is a hell.

Anyway, whatever decision we made count me in to help to update/organize the docs.

WDYT?

Paul

[1] https://www.redhat.com/archives/feedhenry-dev/2017-December/msg00091.html

[2] https://github.com/aerogear/aerogear.org/pull/714
On 01/02/2018 10:08 PM, Daniel Passos wrote:
I was thinking about have a project to group the repos with the same feature/platform, but that is not the GH idea.

I thought project will give us something like https://github.com/aerogear/projects/sync and this link will list all sync repos

As I sad, nevermind!
On Tue, Jan 2, 2018 at 7:22 PM, Wei Li <weil@redhat.com> wrote:
You can have GH project per org - https://github.com/orgs/aerogear/projects. But I don't know why we need it given that we already have Trello & Jira?
On Tue, Jan 2, 2018 at 5:47 PM, Daniel Passos <dpassos@redhat.com> wrote:
Hi Paul,

Nevermind,

I'd like to create a project to group repos, like:

Project X

aerogear-android-x

aerogear-ios-x

But, GH do it in a different way. Just realized GH project is per repo not per org

My mistake. Sorry about that.
On Tue, Jan 2, 2018 at 3:40 PM, Paul Wright <pwright@redhat.com> wrote:
Hi Daniel,

can you outline why you think it will help?

If there are projects for all platforms and features, won't we end up wrangling projects as well as repos?

Note: I'm saying this with true ignorance, I have no idea whether that's true or not ;)

Paul

On 01/02/2018 05:16 PM, Daniel Passos wrote:
Hi

I wanna create some Github projects to help us to organize repos on AeroGear organization. Wdyt?

I was thinking about create 2 types of projects:

Platforms

Features

Some examples in my mind:

Platforms

Android
iOS
JS
Xamarin
Cordova

Feature

Website
Core
Http
Push
OAuth2
Database
Security
Sync

PS: A repo can be in more than one project.

--

-- Passos
_______________________________________________
feedhenry-dev mailing list
feedhenry-dev@redhat.com
https://www.redhat.com/mailman/listinfo/feedhenry-dev
-- Paul Wright Mobile Docs (github: finp)
--

-- Passos
_______________________________________________
feedhenry-dev mailing list
feedhenry-dev@redhat.com
https://www.redhat.com/mailman/listinfo/feedhenry-dev
--
WEI LI

SENIOR SOFTWARE ENGINEER

Red Hat Mobile

weil@redhat.com M: +353862393272
--

-- Passos
-- 
Paul Wright
Mobile Docs (github: finp)

-- Passos