From supittma at redhat.com Wed Nov 9 18:06:42 2016 From: supittma at redhat.com (Summers Pittman) Date: Wed, 9 Nov 2016 13:06:42 -0500 Subject: [feedhenry-dev] Dogfooding for Developer Experience Message-ID: Y'all, Wojciech and I had a quick call to flesh out the discussion we were having on IRC about having a dogfooding exercise to better understand and discover what pain points developers have. As far as Jiraisms go, we have a few things to figure out before we can make a proper Epic out of it. Once we do, however, I hope that we can get things ready to start coding relatively quickly. 1) Do we want to greenfield an application or port an existing open source application to the platform? Greenfielding works great for learning specific parts of the platform (ex Auth) or answering certain questions (how do I get sync to do X, Y ,Z), but porting an existing application gives us the opportunity to see how our platform's assumptions mesh with the practices developers are currently using. 2) Do we want to focus on native (Windows + iOS + Android) or Cordova clients? Cordova apps will give us a better experience of challenges our current users have, but because there are so few native users in comparison a native focus may yield things which have been overlooked. 3) I'm sure that more will come from this so feel free to ask and answer your own questions here. Let's discuss in this thread today and Thursday and we can review it in our meeting Friday. Summers -------------- next part -------------- An HTML attachment was scrubbed... URL: From mwessend at redhat.com Thu Nov 10 09:15:39 2016 From: mwessend at redhat.com (Matthias Wessendorf) Date: Thu, 10 Nov 2016 10:15:39 +0100 Subject: [feedhenry-dev] Dogfooding for Developer Experience In-Reply-To: References: Message-ID: On Wed, Nov 9, 2016 at 7:06 PM, Summers Pittman wrote: > Y'all, > > Wojciech and I had a quick call to flesh out the discussion we were having > on IRC about having a dogfooding exercise to better understand and discover > what pain points developers have. > > As far as Jiraisms go, we have a few things to figure out before we can > make a proper Epic out of it. Once we do, however, I hope that we can get > things ready to start coding relatively quickly. > > 1) Do we want to greenfield an application or port an existing open source > application to the platform? Greenfielding works great for learning > specific parts of the platform (ex Auth) or answering certain questions > (how do I get sync to do X, Y ,Z), but porting an existing application > gives us the opportunity to see how our platform's assumptions mesh with > the practices developers are currently using. > I think we should to greenfield, as that might be a bit more fun. So if we figure out certain parts of the platform that are not fun to use, it's good feedback for improving. I think greenfield works a bit better here, because you are a bit more flexible on ideas and concepts @porting: A bit off-topic; But: Currently I am mentoring a student from Waterford. He works on a Node.js / Microservices version of AeroDoc (+adding Keycloak). At a later stage this might be even ported to an RHMAP template. So this might be related. bringing in existing code to the platform > > 2) Do we want to focus on native (Windows + iOS + Android) or Cordova > clients? Cordova apps will give us a better experience of challenges our > current users have, but because there are so few native users in comparison > a native focus may yield things which have been overlooked. > Hrm, not sure: both have benefits: native and cordova > > 3) I'm sure that more will come from this so feel free to ask and answer > your own questions here. > > Let's discuss in this thread today and Thursday and we can review it in > our meeting Friday. > > Summers > > _______________________________________________ > feedhenry-dev mailing list > feedhenry-dev at redhat.com > https://www.redhat.com/mailman/listinfo/feedhenry-dev > > -- Project lead AeroGear.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From cbrookes at redhat.com Thu Nov 10 16:02:34 2016 From: cbrookes at redhat.com (Craig Brookes) Date: Thu, 10 Nov 2016 16:02:34 +0000 Subject: [feedhenry-dev] Mongo Express Service - Manage your Mongo Database in RHMAP using Mongo Express In-Reply-To: References: Message-ID: This is pretty cool. I actually think having the data browser as an MBaaS service makes a lot of sense. For auth it seems you could create a piece of middleware that calls back to the platform to check a cookie or header value, if not there redirect to a login screen and proxy the credentials through to the platform. Craig On Thu, Nov 10, 2016 at 3:41 PM, Emilio Rodriguez Martinez < emrodrig at redhat.com> wrote: > Hey guys, > > based on consulting's feedback, we've been working to integrate Mongo > Express in RHMAP. The first step was integrate it as a platform service and > here you can find our findings: > > *Description* > Mongo Express Service is a RHMAP service which allows users to manage > their Mongo databases through a robust GUI. This interface includes several > pieces of functionality missing in the current Data Browser such as a > complex query runner or a database and collections statistics. > > Besides, Mongo Express is an ongoing Open Source project so we can benefit > from the community contribution. > > Here you can find a quick demo of Mongo Express working in RHMAP: > https://bluejeans.com/s/zTlgS/ > > *Current limitations* > - At the moment only the service's database is accessible automatically. > This means that the Cloud App's databases need to be manually configured to > be managed through this service. > > - This service needs to be public and therefore the database will be > exposed: anybody knowing the url would have access to the data. > > Note: both limitations can be workarounded. Depending on the feedback from > this service we will put more effort on this. > > *Installation and usage* > To use Mongo Express Service in RHMAP follow these steps: > 1. Provision the sample FeedHenry Service in RHMAP (Services & APIs > + > Provision MBaaS service > New MBaaS service) > 2. Make the new service public (Details > Make this Service Public to all > Projects and Services) > 3. Upgrade database (Data Browser > Upgrade Database) > 4. Replace code from the test service with the forked Mongo Express > Service fork: > - clone Mongo Express fork (git at github.com:emilioicai/mon > go-express-service.git) > - git remote add your services git url (Details > Git Url) > - git push --force origin master > 5. Deploy (using Node 4 as runtime) > 6. Mongo Express should be available through the Preview section in the > service view > > *Troubleshooting* > Most of the issues arise because of one of these settings: > - Service is not public > - Database was not upgraded before deploying > - Node 0.10 or Node 0.11 was used as runtime instead of Node 4 > In case of a problem re-provisioning and making sure those three settings > are properly configured. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jfrizell at redhat.com Thu Nov 10 18:59:37 2016 From: jfrizell at redhat.com (John Frizelle) Date: Thu, 10 Nov 2016 18:59:37 +0000 Subject: [feedhenry-dev] Dogfooding for Developer Experience In-Reply-To: References: Message-ID: I'm not really sure it makes that much of a difference. Typically, almost all development work is done locally - i.e. outside of the studio. The real interactions (and problems) with the product come after an app has been released as people are then fairly well locked into using the studio for management, monitoring, upgrades, debugging problems etc... So, if we really want to dogfood our product, we need to get something deployed and then go through the pain of trying to manage it through the platform... -- John Frizelle Platform Architect, Red Hat Mobile Consulting Engineering mobile: *+353 87 290 1644 * twitter:* @johnfriz* skype: *john_frizelle* mail: *jfrizell at redhat.com * On 10 November 2016 at 09:15, Matthias Wessendorf wrote: > > > On Wed, Nov 9, 2016 at 7:06 PM, Summers Pittman > wrote: > >> Y'all, >> >> Wojciech and I had a quick call to flesh out the discussion we were >> having on IRC about having a dogfooding exercise to better understand and >> discover what pain points developers have. >> >> As far as Jiraisms go, we have a few things to figure out before we can >> make a proper Epic out of it. Once we do, however, I hope that we can get >> things ready to start coding relatively quickly. >> >> 1) Do we want to greenfield an application or port an existing open >> source application to the platform? Greenfielding works great for learning >> specific parts of the platform (ex Auth) or answering certain questions >> (how do I get sync to do X, Y ,Z), but porting an existing application >> gives us the opportunity to see how our platform's assumptions mesh with >> the practices developers are currently using. >> > > I think we should to greenfield, as that might be a bit more fun. So if we > figure out certain parts of the platform that are not fun to use, it's good > feedback for improving. I think greenfield works a bit better here, because > you are a bit more flexible on ideas and concepts > > > @porting: > A bit off-topic; But: Currently I am mentoring a student from Waterford. > He works on a Node.js / Microservices version of AeroDoc (+adding > Keycloak). At a later stage this might be even ported to an RHMAP template. > So this might be related. bringing in existing code to the platform > > > >> >> 2) Do we want to focus on native (Windows + iOS + Android) or Cordova >> clients? Cordova apps will give us a better experience of challenges our >> current users have, but because there are so few native users in comparison >> a native focus may yield things which have been overlooked. >> > > Hrm, not sure: both have benefits: native and cordova > > > >> >> 3) I'm sure that more will come from this so feel free to ask and answer >> your own questions here. >> >> Let's discuss in this thread today and Thursday and we can review it in >> our meeting Friday. >> >> Summers >> >> _______________________________________________ >> feedhenry-dev mailing list >> feedhenry-dev at redhat.com >> https://www.redhat.com/mailman/listinfo/feedhenry-dev >> >> > > > -- > Project lead AeroGear.org > > _______________________________________________ > feedhenry-dev mailing list > feedhenry-dev at redhat.com > https://www.redhat.com/mailman/listinfo/feedhenry-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From wtrocki at redhat.com Fri Nov 11 10:25:22 2016 From: wtrocki at redhat.com (Wojciech Trocki) Date: Fri, 11 Nov 2016 10:25:22 +0000 Subject: [feedhenry-dev] Mongo Express Service - Manage your Mongo Database in RHMAP using Mongo Express In-Reply-To: References: Message-ID: Awesome work Emilio! What is also worth mentioning is that mongo-express has really good api that we may reuse when building data access service for RHMAP 5.0. On Thu, Nov 10, 2016 at 4:02 PM, Craig Brookes wrote: > This is pretty cool. I actually think having the data browser as an MBaaS > service makes a lot of sense. > For auth it seems you could create a piece of middleware that calls back > to the platform to check a cookie or header value, if not there redirect to > a login screen and proxy the credentials through to the platform. > > Craig > > On Thu, Nov 10, 2016 at 3:41 PM, Emilio Rodriguez Martinez < > emrodrig at redhat.com> wrote: > >> Hey guys, >> >> based on consulting's feedback, we've been working to integrate Mongo >> Express in RHMAP. The first step was integrate it as a platform service and >> here you can find our findings: >> >> *Description* >> Mongo Express Service is a RHMAP service which allows users to manage >> their Mongo databases through a robust GUI. This interface includes several >> pieces of functionality missing in the current Data Browser such as a >> complex query runner or a database and collections statistics. >> >> Besides, Mongo Express is an ongoing Open Source project so we can >> benefit from the community contribution. >> >> Here you can find a quick demo of Mongo Express working in RHMAP: >> https://bluejeans.com/s/zTlgS/ >> >> *Current limitations* >> - At the moment only the service's database is accessible automatically. >> This means that the Cloud App's databases need to be manually configured to >> be managed through this service. >> >> - This service needs to be public and therefore the database will be >> exposed: anybody knowing the url would have access to the data. >> >> Note: both limitations can be workarounded. Depending on the feedback >> from this service we will put more effort on this. >> >> *Installation and usage* >> To use Mongo Express Service in RHMAP follow these steps: >> 1. Provision the sample FeedHenry Service in RHMAP (Services & APIs > + >> Provision MBaaS service > New MBaaS service) >> 2. Make the new service public (Details > Make this Service Public to all >> Projects and Services) >> 3. Upgrade database (Data Browser > Upgrade Database) >> 4. Replace code from the test service with the forked Mongo Express >> Service fork: >> - clone Mongo Express fork (git at github.com:emilioicai/mon >> go-express-service.git) >> - git remote add your services git url (Details > Git Url) >> - git push --force origin master >> 5. Deploy (using Node 4 as runtime) >> 6. Mongo Express should be available through the Preview section in the >> service view >> >> *Troubleshooting* >> Most of the issues arise because of one of these settings: >> - Service is not public >> - Database was not upgraded before deploying >> - Node 0.10 or Node 0.11 was used as runtime instead of Node 4 >> In case of a problem re-provisioning and making sure those three settings >> are properly configured. >> > > -- Wojciech Trocki Software Engineer, Red Hat Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From coneill at redhat.com Fri Nov 11 10:28:41 2016 From: coneill at redhat.com (Conor O'Neill) Date: Fri, 11 Nov 2016 10:28:41 +0000 Subject: [feedhenry-dev] Mongo Express Service - Manage your Mongo Database in RHMAP using Mongo Express In-Reply-To: References: Message-ID: Great work on this. We've been seeing a lot of requests for Data Browser upgrades and this may be a better approach. Does it have bulk import/export? Conor On 10 November 2016 at 16:02, Craig Brookes wrote: > This is pretty cool. I actually think having the data browser as an MBaaS > service makes a lot of sense. > For auth it seems you could create a piece of middleware that calls back > to the platform to check a cookie or header value, if not there redirect to > a login screen and proxy the credentials through to the platform. > > Craig > > On Thu, Nov 10, 2016 at 3:41 PM, Emilio Rodriguez Martinez < > emrodrig at redhat.com> wrote: > >> Hey guys, >> >> based on consulting's feedback, we've been working to integrate Mongo >> Express in RHMAP. The first step was integrate it as a platform service and >> here you can find our findings: >> >> *Description* >> Mongo Express Service is a RHMAP service which allows users to manage >> their Mongo databases through a robust GUI. This interface includes several >> pieces of functionality missing in the current Data Browser such as a >> complex query runner or a database and collections statistics. >> >> Besides, Mongo Express is an ongoing Open Source project so we can >> benefit from the community contribution. >> >> Here you can find a quick demo of Mongo Express working in RHMAP: >> https://bluejeans.com/s/zTlgS/ >> >> *Current limitations* >> - At the moment only the service's database is accessible automatically. >> This means that the Cloud App's databases need to be manually configured to >> be managed through this service. >> >> - This service needs to be public and therefore the database will be >> exposed: anybody knowing the url would have access to the data. >> >> Note: both limitations can be workarounded. Depending on the feedback >> from this service we will put more effort on this. >> >> *Installation and usage* >> To use Mongo Express Service in RHMAP follow these steps: >> 1. Provision the sample FeedHenry Service in RHMAP (Services & APIs > + >> Provision MBaaS service > New MBaaS service) >> 2. Make the new service public (Details > Make this Service Public to all >> Projects and Services) >> 3. Upgrade database (Data Browser > Upgrade Database) >> 4. Replace code from the test service with the forked Mongo Express >> Service fork: >> - clone Mongo Express fork (git at github.com:emilioicai/mon >> go-express-service.git) >> - git remote add your services git url (Details > Git Url) >> - git push --force origin master >> 5. Deploy (using Node 4 as runtime) >> 6. Mongo Express should be available through the Preview section in the >> service view >> >> *Troubleshooting* >> Most of the issues arise because of one of these settings: >> - Service is not public >> - Database was not upgraded before deploying >> - Node 0.10 or Node 0.11 was used as runtime instead of Node 4 >> In case of a problem re-provisioning and making sure those three settings >> are properly configured. >> > > > _______________________________________________ > feedhenry-dev mailing list > feedhenry-dev at redhat.com > https://www.redhat.com/mailman/listinfo/feedhenry-dev > > -- Product Manager | Red Hat Mobile | Cell: +353-87-9790297 | Desk: +353-21-2303419 | Skype: cwjoneill | Location: Cork, Ireland | Timezone: GMT/BST -------------- next part -------------- An HTML attachment was scrubbed... URL: From weil at redhat.com Fri Nov 11 10:34:51 2016 From: weil at redhat.com (Wei Li) Date: Fri, 11 Nov 2016 10:34:51 +0000 Subject: [feedhenry-dev] Mongo Express Service - Manage your Mongo Database in RHMAP using Mongo Express In-Reply-To: References: Message-ID: It does. But it is using the same approach we are using at the moment with data browser, and it probably works fine with smaller dataset. It will not work very well with large dataset like we have in production environment. We are actually going to look at improving data browser start from the next sprint. But now it looks like we may have a better alternative. @Conor, do you think this can replace data browser in the studio? On Fri, Nov 11, 2016 at 10:28 AM, Conor O'Neill wrote: > Great work on this. We've been seeing a lot of requests for Data Browser > upgrades and this may be a better approach. Does it have bulk import/export? > > Conor > > > On 10 November 2016 at 16:02, Craig Brookes wrote: > >> This is pretty cool. I actually think having the data browser as an MBaaS >> service makes a lot of sense. >> For auth it seems you could create a piece of middleware that calls back >> to the platform to check a cookie or header value, if not there redirect to >> a login screen and proxy the credentials through to the platform. >> >> Craig >> >> On Thu, Nov 10, 2016 at 3:41 PM, Emilio Rodriguez Martinez < >> emrodrig at redhat.com> wrote: >> >>> Hey guys, >>> >>> based on consulting's feedback, we've been working to integrate Mongo >>> Express in RHMAP. The first step was integrate it as a platform service and >>> here you can find our findings: >>> >>> *Description* >>> Mongo Express Service is a RHMAP service which allows users to manage >>> their Mongo databases through a robust GUI. This interface includes several >>> pieces of functionality missing in the current Data Browser such as a >>> complex query runner or a database and collections statistics. >>> >>> Besides, Mongo Express is an ongoing Open Source project so we can >>> benefit from the community contribution. >>> >>> Here you can find a quick demo of Mongo Express working in RHMAP: >>> https://bluejeans.com/s/zTlgS/ >>> >>> *Current limitations* >>> - At the moment only the service's database is accessible automatically. >>> This means that the Cloud App's databases need to be manually configured to >>> be managed through this service. >>> >>> - This service needs to be public and therefore the database will be >>> exposed: anybody knowing the url would have access to the data. >>> >>> Note: both limitations can be workarounded. Depending on the feedback >>> from this service we will put more effort on this. >>> >>> *Installation and usage* >>> To use Mongo Express Service in RHMAP follow these steps: >>> 1. Provision the sample FeedHenry Service in RHMAP (Services & APIs > + >>> Provision MBaaS service > New MBaaS service) >>> 2. Make the new service public (Details > Make this Service Public to >>> all Projects and Services) >>> 3. Upgrade database (Data Browser > Upgrade Database) >>> 4. Replace code from the test service with the forked Mongo Express >>> Service fork: >>> - clone Mongo Express fork (git at github.com:emilioicai/mon >>> go-express-service.git) >>> - git remote add your services git url (Details > Git Url) >>> - git push --force origin master >>> 5. Deploy (using Node 4 as runtime) >>> 6. Mongo Express should be available through the Preview section in the >>> service view >>> >>> *Troubleshooting* >>> Most of the issues arise because of one of these settings: >>> - Service is not public >>> - Database was not upgraded before deploying >>> - Node 0.10 or Node 0.11 was used as runtime instead of Node 4 >>> In case of a problem re-provisioning and making sure those three >>> settings are properly configured. >>> >> >> >> _______________________________________________ >> feedhenry-dev mailing list >> feedhenry-dev at redhat.com >> https://www.redhat.com/mailman/listinfo/feedhenry-dev >> >> > > > -- > Product Manager | Red Hat Mobile | Cell: +353-87-9790297 | Desk: > +353-21-2303419 > | Skype: cwjoneill | Location: Cork, Ireland | Timezone: GMT/BST > -- Wei Li Red Hat email address: wei.li at redhat.com Senior Software Engineer -------------- next part -------------- An HTML attachment was scrubbed... URL: From jfrizell at redhat.com Fri Nov 11 10:43:27 2016 From: jfrizell at redhat.com (John Frizelle) Date: Fri, 11 Nov 2016 10:43:27 +0000 Subject: [feedhenry-dev] Mongo Express Service - Manage your Mongo Database in RHMAP using Mongo Express In-Reply-To: References: Message-ID: The conclusion from the document [1] that compared Data Browser with Mongo Express did not seem to indicate that we should replace Data Browser: *Mongo Express is more complete in number of features but lacks of some critical ones like multiple deletions or inline editing. Besides, its user interface is less intuitive than the one from Data Browser.* *If the stability of Data Browser is improved and some key features as complex querying are implemented, Data Browser could be a better alternative for most of the users. There are other features Mongo Express include which are targeted for more advanced users (like multiple database management) which could not be that important.* Let's make sure that we are in agreement on the way forward here. I'm not sure a knee-jerk rip and replace of Data Browser is the right answer - especially if mongo-express is only implemented as an MBaaS Service and is not a first class citizen of the Studio. I think we need to have a call to discuss this and make sure we are in agreement on the path forward. [1] https://docs.google.com/document/d/1ICBS4ieDkepNne1R_EVe1N9KyP3Ijjpmvc3GiJNrhmw/edit -- John Frizelle Platform Architect, Red Hat Mobile Consulting Engineering mobile: *+353 87 290 1644 * twitter:* @johnfriz* skype: *john_frizelle* mail: *jfrizell at redhat.com * On 11 November 2016 at 10:34, Wei Li wrote: > It does. But it is using the same approach we are using at the moment with > data browser, and it probably works fine with smaller dataset. It will not > work very well with large dataset like we have in production environment. > > We are actually going to look at improving data browser start from the > next sprint. But now it looks like we may have a better alternative. > @Conor, do you think this can replace data browser in the studio? > > On Fri, Nov 11, 2016 at 10:28 AM, Conor O'Neill > wrote: > >> Great work on this. We've been seeing a lot of requests for Data Browser >> upgrades and this may be a better approach. Does it have bulk import/export? >> >> Conor >> >> >> On 10 November 2016 at 16:02, Craig Brookes wrote: >> >>> This is pretty cool. I actually think having the data browser as an >>> MBaaS service makes a lot of sense. >>> For auth it seems you could create a piece of middleware that calls back >>> to the platform to check a cookie or header value, if not there redirect to >>> a login screen and proxy the credentials through to the platform. >>> >>> Craig >>> >>> On Thu, Nov 10, 2016 at 3:41 PM, Emilio Rodriguez Martinez < >>> emrodrig at redhat.com> wrote: >>> >>>> Hey guys, >>>> >>>> based on consulting's feedback, we've been working to integrate Mongo >>>> Express in RHMAP. The first step was integrate it as a platform service and >>>> here you can find our findings: >>>> >>>> *Description* >>>> Mongo Express Service is a RHMAP service which allows users to manage >>>> their Mongo databases through a robust GUI. This interface includes several >>>> pieces of functionality missing in the current Data Browser such as a >>>> complex query runner or a database and collections statistics. >>>> >>>> Besides, Mongo Express is an ongoing Open Source project so we can >>>> benefit from the community contribution. >>>> >>>> Here you can find a quick demo of Mongo Express working in RHMAP: >>>> https://bluejeans.com/s/zTlgS/ >>>> >>>> *Current limitations* >>>> - At the moment only the service's database is accessible >>>> automatically. This means that the Cloud App's databases need to be >>>> manually configured to be managed through this service. >>>> >>>> - This service needs to be public and therefore the database will be >>>> exposed: anybody knowing the url would have access to the data. >>>> >>>> Note: both limitations can be workarounded. Depending on the feedback >>>> from this service we will put more effort on this. >>>> >>>> *Installation and usage* >>>> To use Mongo Express Service in RHMAP follow these steps: >>>> 1. Provision the sample FeedHenry Service in RHMAP (Services & APIs > + >>>> Provision MBaaS service > New MBaaS service) >>>> 2. Make the new service public (Details > Make this Service Public to >>>> all Projects and Services) >>>> 3. Upgrade database (Data Browser > Upgrade Database) >>>> 4. Replace code from the test service with the forked Mongo Express >>>> Service fork: >>>> - clone Mongo Express fork (git at github.com:emilioicai/mon >>>> go-express-service.git) >>>> - git remote add your services git url (Details > Git Url) >>>> - git push --force origin master >>>> 5. Deploy (using Node 4 as runtime) >>>> 6. Mongo Express should be available through the Preview section in the >>>> service view >>>> >>>> *Troubleshooting* >>>> Most of the issues arise because of one of these settings: >>>> - Service is not public >>>> - Database was not upgraded before deploying >>>> - Node 0.10 or Node 0.11 was used as runtime instead of Node 4 >>>> In case of a problem re-provisioning and making sure those three >>>> settings are properly configured. >>>> >>> >>> >>> _______________________________________________ >>> feedhenry-dev mailing list >>> feedhenry-dev at redhat.com >>> https://www.redhat.com/mailman/listinfo/feedhenry-dev >>> >>> >> >> >> -- >> Product Manager | Red Hat Mobile | Cell: +353-87-9790297 | Desk: >> +353-21-2303419 >> | Skype: cwjoneill | Location: Cork, Ireland | Timezone: GMT/BST >> > > > > -- > Wei Li > Red Hat email address: wei.li at redhat.com > Senior Software Engineer > > _______________________________________________ > feedhenry-dev mailing list > feedhenry-dev at redhat.com > https://www.redhat.com/mailman/listinfo/feedhenry-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From coneill at redhat.com Fri Nov 11 10:55:31 2016 From: coneill at redhat.com (Conor O'Neill) Date: Fri, 11 Nov 2016 10:55:31 +0000 Subject: [feedhenry-dev] Mongo Express Service - Manage your Mongo Database in RHMAP using Mongo Express In-Reply-To: References: Message-ID: I think we're all in agreement here. My question was more of a mid/long term one, not a short term rip and replace. If we were to invest effort into mongo-express, I'd see both existing in parallel for quite a while. On 11 November 2016 at 10:52, David Martin wrote: > > Let's make sure that we are in agreement on the way forward here. I'm > not sure a knee-jerk rip and replace of Data Browser is the right answer - > especially if mongo-express is only implemented as an MBaaS Service and is > not a first class citizen of the Studio. > > Yes, agreed on this 100%. > I think there is much more to gain from improving the robustness of > databrowser as is than changing to mongo-express. > But I'd like to get consensus on how to move forward. > > I think this should be viewed as a mongo-express POC that shows how easy > it is for someone to use it themselves in their cloud app. (There's a big > problem to solve if we want to have it as a supported service i.e. allowing > a service to talk to a cloud app's db without hardcoding mong creds) > We shouldn't dismiss the findings from the initial report. > > > > > On 11 November 2016 at 10:43, John Frizelle wrote: > >> The conclusion from the document [1] that compared Data Browser with >> Mongo Express did not seem to indicate that we should replace Data Browser: >> >> *Mongo Express is more complete in number of features but lacks of some >> critical ones like multiple deletions or inline editing. Besides, its user >> interface is less intuitive than the one from Data Browser.* >> >> *If the stability of Data Browser is improved and some key features as >> complex querying are implemented, Data Browser could be a better >> alternative for most of the users. There are other features Mongo Express >> include which are targeted for more advanced users (like multiple database >> management) which could not be that important.* >> >> Let's make sure that we are in agreement on the way forward here. I'm not >> sure a knee-jerk rip and replace of Data Browser is the right answer - >> especially if mongo-express is only implemented as an MBaaS Service and is >> not a first class citizen of the Studio. >> >> I think we need to have a call to discuss this and make sure we are in >> agreement on the path forward. >> >> [1] https://docs.google.com/document/d/1ICBS4ieDkepNne1R_EVe >> 1N9KyP3Ijjpmvc3GiJNrhmw/edit >> >> -- >> John Frizelle >> Platform Architect, Red Hat Mobile >> Consulting Engineering >> >> mobile: *+353 87 290 1644 * >> twitter:* @johnfriz* >> skype: *john_frizelle* >> mail: *jfrizell at redhat.com * >> >> >> >> >> On 11 November 2016 at 10:34, Wei Li wrote: >> >>> It does. But it is using the same approach we are using at the moment >>> with data browser, and it probably works fine with smaller dataset. It will >>> not work very well with large dataset like we have in production >>> environment. >>> >>> We are actually going to look at improving data browser start from the >>> next sprint. But now it looks like we may have a better alternative. >>> @Conor, do you think this can replace data browser in the studio? >>> >>> On Fri, Nov 11, 2016 at 10:28 AM, Conor O'Neill >>> wrote: >>> >>>> Great work on this. We've been seeing a lot of requests for Data >>>> Browser upgrades and this may be a better approach. Does it have bulk >>>> import/export? >>>> >>>> Conor >>>> >>>> >>>> On 10 November 2016 at 16:02, Craig Brookes >>>> wrote: >>>> >>>>> This is pretty cool. I actually think having the data browser as an >>>>> MBaaS service makes a lot of sense. >>>>> For auth it seems you could create a piece of middleware that calls >>>>> back to the platform to check a cookie or header value, if not there >>>>> redirect to a login screen and proxy the credentials through to the >>>>> platform. >>>>> >>>>> Craig >>>>> >>>>> On Thu, Nov 10, 2016 at 3:41 PM, Emilio Rodriguez Martinez < >>>>> emrodrig at redhat.com> wrote: >>>>> >>>>>> Hey guys, >>>>>> >>>>>> based on consulting's feedback, we've been working to integrate Mongo >>>>>> Express in RHMAP. The first step was integrate it as a platform service and >>>>>> here you can find our findings: >>>>>> >>>>>> *Description* >>>>>> Mongo Express Service is a RHMAP service which allows users to manage >>>>>> their Mongo databases through a robust GUI. This interface includes several >>>>>> pieces of functionality missing in the current Data Browser such as a >>>>>> complex query runner or a database and collections statistics. >>>>>> >>>>>> Besides, Mongo Express is an ongoing Open Source project so we can >>>>>> benefit from the community contribution. >>>>>> >>>>>> Here you can find a quick demo of Mongo Express working in RHMAP: >>>>>> https://bluejeans.com/s/zTlgS/ >>>>>> >>>>>> *Current limitations* >>>>>> - At the moment only the service's database is accessible >>>>>> automatically. This means that the Cloud App's databases need to be >>>>>> manually configured to be managed through this service. >>>>>> >>>>>> - This service needs to be public and therefore the database will be >>>>>> exposed: anybody knowing the url would have access to the data. >>>>>> >>>>>> Note: both limitations can be workarounded. Depending on the feedback >>>>>> from this service we will put more effort on this. >>>>>> >>>>>> *Installation and usage* >>>>>> To use Mongo Express Service in RHMAP follow these steps: >>>>>> 1. Provision the sample FeedHenry Service in RHMAP (Services & APIs > >>>>>> + Provision MBaaS service > New MBaaS service) >>>>>> 2. Make the new service public (Details > Make this Service Public to >>>>>> all Projects and Services) >>>>>> 3. Upgrade database (Data Browser > Upgrade Database) >>>>>> 4. Replace code from the test service with the forked Mongo Express >>>>>> Service fork: >>>>>> - clone Mongo Express fork (git at github.com:emilioicai/mon >>>>>> go-express-service.git) >>>>>> - git remote add your services git url (Details > Git Url) >>>>>> - git push --force origin master >>>>>> 5. Deploy (using Node 4 as runtime) >>>>>> 6. Mongo Express should be available through the Preview section in >>>>>> the service view >>>>>> >>>>>> *Troubleshooting* >>>>>> Most of the issues arise because of one of these settings: >>>>>> - Service is not public >>>>>> - Database was not upgraded before deploying >>>>>> - Node 0.10 or Node 0.11 was used as runtime instead of Node 4 >>>>>> In case of a problem re-provisioning and making sure those three >>>>>> settings are properly configured. >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> feedhenry-dev mailing list >>>>> feedhenry-dev at redhat.com >>>>> https://www.redhat.com/mailman/listinfo/feedhenry-dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Product Manager | Red Hat Mobile | Cell: +353-87-9790297 | Desk: >>>> +353-21-2303419 >>>> | Skype: cwjoneill | Location: Cork, Ireland | Timezone: GMT/BST >>>> >>> >>> >>> >>> -- >>> Wei Li >>> Red Hat email address: wei.li at redhat.com >>> Senior Software Engineer >>> >>> _______________________________________________ >>> feedhenry-dev mailing list >>> feedhenry-dev at redhat.com >>> https://www.redhat.com/mailman/listinfo/feedhenry-dev >>> >>> >> > > > -- > David Martin > Red Hat Mobile > Twitter: @irldavem > IRC: @irldavem (feedhenry, mobile-internal) > -- Product Manager | Red Hat Mobile | Cell: +353-87-9790297 | Desk: +353-21-2303419 | Skype: cwjoneill | Location: Cork, Ireland | Timezone: GMT/BST -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From wtrocki at redhat.com Fri Nov 11 10:58:50 2016 From: wtrocki at redhat.com (Wojciech Trocki) Date: Fri, 11 Nov 2016 10:58:50 +0000 Subject: [feedhenry-dev] Mongo Express Service - Manage your Mongo Database in RHMAP using Mongo Express In-Reply-To: References: Message-ID: Mongo Express is just more powerful thanks to better APi. I we improve our fh.db api (provide v2 version for it) then we would be able to to do much more. UI for mongo express is not worth taking in because it would require significant amount of time to get similar result we have at the moment. We can just inspire on http mongo rest api it provides (is really solid) fh.db is very limited. If we enable users to type some custom mongodb queries as in command line that would be game changer for databrowser and probably entire product. On Fri, Nov 11, 2016 at 10:52 AM, David Martin wrote: > > Let's make sure that we are in agreement on the way forward here. I'm > not sure a knee-jerk rip and replace of Data Browser is the right answer - > especially if mongo-express is only implemented as an MBaaS Service and is > not a first class citizen of the Studio. > > Yes, agreed on this 100%. > I think there is much more to gain from improving the robustness of > databrowser as is than changing to mongo-express. > But I'd like to get consensus on how to move forward. > > I think this should be viewed as a mongo-express POC that shows how easy > it is for someone to use it themselves in their cloud app. (There's a big > problem to solve if we want to have it as a supported service i.e. allowing > a service to talk to a cloud app's db without hardcoding mong creds) > We shouldn't dismiss the findings from the initial report. > > > > > On 11 November 2016 at 10:43, John Frizelle wrote: > >> The conclusion from the document [1] that compared Data Browser with >> Mongo Express did not seem to indicate that we should replace Data Browser: >> >> *Mongo Express is more complete in number of features but lacks of some >> critical ones like multiple deletions or inline editing. Besides, its user >> interface is less intuitive than the one from Data Browser.* >> >> *If the stability of Data Browser is improved and some key features as >> complex querying are implemented, Data Browser could be a better >> alternative for most of the users. There are other features Mongo Express >> include which are targeted for more advanced users (like multiple database >> management) which could not be that important.* >> >> Let's make sure that we are in agreement on the way forward here. I'm not >> sure a knee-jerk rip and replace of Data Browser is the right answer - >> especially if mongo-express is only implemented as an MBaaS Service and is >> not a first class citizen of the Studio. >> >> I think we need to have a call to discuss this and make sure we are in >> agreement on the path forward. >> >> [1] https://docs.google.com/document/d/1ICBS4ieDkepNne1R_EVe >> 1N9KyP3Ijjpmvc3GiJNrhmw/edit >> >> -- >> John Frizelle >> Platform Architect, Red Hat Mobile >> Consulting Engineering >> >> mobile: *+353 87 290 1644 * >> twitter:* @johnfriz* >> skype: *john_frizelle* >> mail: *jfrizell at redhat.com * >> >> >> >> >> On 11 November 2016 at 10:34, Wei Li wrote: >> >>> It does. But it is using the same approach we are using at the moment >>> with data browser, and it probably works fine with smaller dataset. It will >>> not work very well with large dataset like we have in production >>> environment. >>> >>> We are actually going to look at improving data browser start from the >>> next sprint. But now it looks like we may have a better alternative. >>> @Conor, do you think this can replace data browser in the studio? >>> >>> On Fri, Nov 11, 2016 at 10:28 AM, Conor O'Neill >>> wrote: >>> >>>> Great work on this. We've been seeing a lot of requests for Data >>>> Browser upgrades and this may be a better approach. Does it have bulk >>>> import/export? >>>> >>>> Conor >>>> >>>> >>>> On 10 November 2016 at 16:02, Craig Brookes >>>> wrote: >>>> >>>>> This is pretty cool. I actually think having the data browser as an >>>>> MBaaS service makes a lot of sense. >>>>> For auth it seems you could create a piece of middleware that calls >>>>> back to the platform to check a cookie or header value, if not there >>>>> redirect to a login screen and proxy the credentials through to the >>>>> platform. >>>>> >>>>> Craig >>>>> >>>>> On Thu, Nov 10, 2016 at 3:41 PM, Emilio Rodriguez Martinez < >>>>> emrodrig at redhat.com> wrote: >>>>> >>>>>> Hey guys, >>>>>> >>>>>> based on consulting's feedback, we've been working to integrate Mongo >>>>>> Express in RHMAP. The first step was integrate it as a platform service and >>>>>> here you can find our findings: >>>>>> >>>>>> *Description* >>>>>> Mongo Express Service is a RHMAP service which allows users to manage >>>>>> their Mongo databases through a robust GUI. This interface includes several >>>>>> pieces of functionality missing in the current Data Browser such as a >>>>>> complex query runner or a database and collections statistics. >>>>>> >>>>>> Besides, Mongo Express is an ongoing Open Source project so we can >>>>>> benefit from the community contribution. >>>>>> >>>>>> Here you can find a quick demo of Mongo Express working in RHMAP: >>>>>> https://bluejeans.com/s/zTlgS/ >>>>>> >>>>>> *Current limitations* >>>>>> - At the moment only the service's database is accessible >>>>>> automatically. This means that the Cloud App's databases need to be >>>>>> manually configured to be managed through this service. >>>>>> >>>>>> - This service needs to be public and therefore the database will be >>>>>> exposed: anybody knowing the url would have access to the data. >>>>>> >>>>>> Note: both limitations can be workarounded. Depending on the feedback >>>>>> from this service we will put more effort on this. >>>>>> >>>>>> *Installation and usage* >>>>>> To use Mongo Express Service in RHMAP follow these steps: >>>>>> 1. Provision the sample FeedHenry Service in RHMAP (Services & APIs > >>>>>> + Provision MBaaS service > New MBaaS service) >>>>>> 2. Make the new service public (Details > Make this Service Public to >>>>>> all Projects and Services) >>>>>> 3. Upgrade database (Data Browser > Upgrade Database) >>>>>> 4. Replace code from the test service with the forked Mongo Express >>>>>> Service fork: >>>>>> - clone Mongo Express fork (git at github.com:emilioicai/mon >>>>>> go-express-service.git) >>>>>> - git remote add your services git url (Details > Git Url) >>>>>> - git push --force origin master >>>>>> 5. Deploy (using Node 4 as runtime) >>>>>> 6. Mongo Express should be available through the Preview section in >>>>>> the service view >>>>>> >>>>>> *Troubleshooting* >>>>>> Most of the issues arise because of one of these settings: >>>>>> - Service is not public >>>>>> - Database was not upgraded before deploying >>>>>> - Node 0.10 or Node 0.11 was used as runtime instead of Node 4 >>>>>> In case of a problem re-provisioning and making sure those three >>>>>> settings are properly configured. >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> feedhenry-dev mailing list >>>>> feedhenry-dev at redhat.com >>>>> https://www.redhat.com/mailman/listinfo/feedhenry-dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Product Manager | Red Hat Mobile | Cell: +353-87-9790297 | Desk: >>>> +353-21-2303419 >>>> | Skype: cwjoneill | Location: Cork, Ireland | Timezone: GMT/BST >>>> >>> >>> >>> >>> -- >>> Wei Li >>> Red Hat email address: wei.li at redhat.com >>> Senior Software Engineer >>> >>> _______________________________________________ >>> feedhenry-dev mailing list >>> feedhenry-dev at redhat.com >>> https://www.redhat.com/mailman/listinfo/feedhenry-dev >>> >>> >> > > > -- > David Martin > Red Hat Mobile > Twitter: @irldavem > IRC: @irldavem (feedhenry, mobile-internal) > -- Wojciech Trocki Software Engineer, Red Hat Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From weil at redhat.com Fri Nov 11 11:17:35 2016 From: weil at redhat.com (Wei Li) Date: Fri, 11 Nov 2016 11:17:35 +0000 Subject: [feedhenry-dev] Mongo Express Service - Manage your Mongo Database in RHMAP using Mongo Express In-Reply-To: References: Message-ID: I will setup a call to discuss this, and let's make a decision on it. Will send out the invitation shortly. On Fri, Nov 11, 2016 at 10:58 AM, Wojciech Trocki wrote: > Mongo Express is just more powerful thanks to better APi. I we improve our > fh.db api (provide v2 version for it) then we would be able to to do much > more. > UI for mongo express is not worth taking in because it would require > significant amount of time to get similar result we have at the moment. We > can just inspire on http mongo rest api it provides (is really solid) > fh.db is very limited. If we enable users to type some custom mongodb > queries as in command line that would be game changer for databrowser and > probably entire product. > > On Fri, Nov 11, 2016 at 10:52 AM, David Martin > wrote: > >> > Let's make sure that we are in agreement on the way forward here. I'm >> not sure a knee-jerk rip and replace of Data Browser is the right answer - >> especially if mongo-express is only implemented as an MBaaS Service and is >> not a first class citizen of the Studio. >> >> Yes, agreed on this 100%. >> I think there is much more to gain from improving the robustness of >> databrowser as is than changing to mongo-express. >> But I'd like to get consensus on how to move forward. >> >> I think this should be viewed as a mongo-express POC that shows how easy >> it is for someone to use it themselves in their cloud app. (There's a big >> problem to solve if we want to have it as a supported service i.e. allowing >> a service to talk to a cloud app's db without hardcoding mong creds) >> We shouldn't dismiss the findings from the initial report. >> >> >> >> >> On 11 November 2016 at 10:43, John Frizelle wrote: >> >>> The conclusion from the document [1] that compared Data Browser with >>> Mongo Express did not seem to indicate that we should replace Data Browser: >>> >>> *Mongo Express is more complete in number of features but lacks of some >>> critical ones like multiple deletions or inline editing. Besides, its user >>> interface is less intuitive than the one from Data Browser.* >>> >>> *If the stability of Data Browser is improved and some key features as >>> complex querying are implemented, Data Browser could be a better >>> alternative for most of the users. There are other features Mongo Express >>> include which are targeted for more advanced users (like multiple database >>> management) which could not be that important.* >>> >>> Let's make sure that we are in agreement on the way forward here. I'm >>> not sure a knee-jerk rip and replace of Data Browser is the right answer - >>> especially if mongo-express is only implemented as an MBaaS Service and is >>> not a first class citizen of the Studio. >>> >>> I think we need to have a call to discuss this and make sure we are in >>> agreement on the path forward. >>> >>> [1] https://docs.google.com/document/d/1ICBS4ieDkepNne1R_EVe >>> 1N9KyP3Ijjpmvc3GiJNrhmw/edit >>> >>> -- >>> John Frizelle >>> Platform Architect, Red Hat Mobile >>> Consulting Engineering >>> >>> mobile: *+353 87 290 1644 * >>> twitter:* @johnfriz* >>> skype: *john_frizelle* >>> mail: *jfrizell at redhat.com * >>> >>> >>> >>> >>> On 11 November 2016 at 10:34, Wei Li wrote: >>> >>>> It does. But it is using the same approach we are using at the moment >>>> with data browser, and it probably works fine with smaller dataset. It will >>>> not work very well with large dataset like we have in production >>>> environment. >>>> >>>> We are actually going to look at improving data browser start from the >>>> next sprint. But now it looks like we may have a better alternative. >>>> @Conor, do you think this can replace data browser in the studio? >>>> >>>> On Fri, Nov 11, 2016 at 10:28 AM, Conor O'Neill >>>> wrote: >>>> >>>>> Great work on this. We've been seeing a lot of requests for Data >>>>> Browser upgrades and this may be a better approach. Does it have bulk >>>>> import/export? >>>>> >>>>> Conor >>>>> >>>>> >>>>> On 10 November 2016 at 16:02, Craig Brookes >>>>> wrote: >>>>> >>>>>> This is pretty cool. I actually think having the data browser as an >>>>>> MBaaS service makes a lot of sense. >>>>>> For auth it seems you could create a piece of middleware that calls >>>>>> back to the platform to check a cookie or header value, if not there >>>>>> redirect to a login screen and proxy the credentials through to the >>>>>> platform. >>>>>> >>>>>> Craig >>>>>> >>>>>> On Thu, Nov 10, 2016 at 3:41 PM, Emilio Rodriguez Martinez < >>>>>> emrodrig at redhat.com> wrote: >>>>>> >>>>>>> Hey guys, >>>>>>> >>>>>>> based on consulting's feedback, we've been working to integrate >>>>>>> Mongo Express in RHMAP. The first step was integrate it as a platform >>>>>>> service and here you can find our findings: >>>>>>> >>>>>>> *Description* >>>>>>> Mongo Express Service is a RHMAP service which allows users to >>>>>>> manage their Mongo databases through a robust GUI. This interface includes >>>>>>> several pieces of functionality missing in the current Data Browser such as >>>>>>> a complex query runner or a database and collections statistics. >>>>>>> >>>>>>> Besides, Mongo Express is an ongoing Open Source project so we can >>>>>>> benefit from the community contribution. >>>>>>> >>>>>>> Here you can find a quick demo of Mongo Express working in RHMAP: >>>>>>> https://bluejeans.com/s/zTlgS/ >>>>>>> >>>>>>> *Current limitations* >>>>>>> - At the moment only the service's database is accessible >>>>>>> automatically. This means that the Cloud App's databases need to be >>>>>>> manually configured to be managed through this service. >>>>>>> >>>>>>> - This service needs to be public and therefore the database will be >>>>>>> exposed: anybody knowing the url would have access to the data. >>>>>>> >>>>>>> Note: both limitations can be workarounded. Depending on the >>>>>>> feedback from this service we will put more effort on this. >>>>>>> >>>>>>> *Installation and usage* >>>>>>> To use Mongo Express Service in RHMAP follow these steps: >>>>>>> 1. Provision the sample FeedHenry Service in RHMAP (Services & APIs >>>>>>> > + Provision MBaaS service > New MBaaS service) >>>>>>> 2. Make the new service public (Details > Make this Service Public >>>>>>> to all Projects and Services) >>>>>>> 3. Upgrade database (Data Browser > Upgrade Database) >>>>>>> 4. Replace code from the test service with the forked Mongo Express >>>>>>> Service fork: >>>>>>> - clone Mongo Express fork (git at github.com:emilioicai/mon >>>>>>> go-express-service.git) >>>>>>> - git remote add your services git url (Details > Git Url) >>>>>>> - git push --force origin master >>>>>>> 5. Deploy (using Node 4 as runtime) >>>>>>> 6. Mongo Express should be available through the Preview section in >>>>>>> the service view >>>>>>> >>>>>>> *Troubleshooting* >>>>>>> Most of the issues arise because of one of these settings: >>>>>>> - Service is not public >>>>>>> - Database was not upgraded before deploying >>>>>>> - Node 0.10 or Node 0.11 was used as runtime instead of Node 4 >>>>>>> In case of a problem re-provisioning and making sure those three >>>>>>> settings are properly configured. >>>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> feedhenry-dev mailing list >>>>>> feedhenry-dev at redhat.com >>>>>> https://www.redhat.com/mailman/listinfo/feedhenry-dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Product Manager | Red Hat Mobile | Cell: +353-87-9790297 | Desk: >>>>> +353-21-2303419 >>>>> | Skype: cwjoneill | Location: Cork, Ireland | Timezone: GMT/BST >>>>> >>>> >>>> >>>> >>>> -- >>>> Wei Li >>>> Red Hat email address: wei.li at redhat.com >>>> Senior Software Engineer >>>> >>>> _______________________________________________ >>>> feedhenry-dev mailing list >>>> feedhenry-dev at redhat.com >>>> https://www.redhat.com/mailman/listinfo/feedhenry-dev >>>> >>>> >>> >> >> >> -- >> David Martin >> Red Hat Mobile >> Twitter: @irldavem >> IRC: @irldavem (feedhenry, mobile-internal) >> > > > > -- > Wojciech Trocki > Software Engineer, Red Hat Mobile > > -- Wei Li Red Hat email address: wei.li at redhat.com Senior Software Engineer -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From wtrocki at redhat.com Mon Nov 14 12:55:14 2016 From: wtrocki at redhat.com (Wojciech Trocki) Date: Mon, 14 Nov 2016 12:55:14 +0000 Subject: [feedhenry-dev] Mongo Express Service - Manage your Mongo Database in RHMAP using Mongo Express In-Reply-To: References: Message-ID: @James How about exposing mongo connection url directly on SaaS platform (on prem users can connect to mongo using ssh tunnel)? >From technical point of view this would be possible since each cloud app is getting separate user and password so we would need to expose database to outside world on load balancer. This may be serious problem from legal and operational point of view. Just want to know your opinion on this one. On Fri, Nov 11, 2016 at 2:01 PM, James Mernin wrote: > Hi John, Emilio, Conor, > > This looks hugely promising (considering the shared pain we all know about > the Data Browser feature) and the the engineer in me agrees fully that > implementing this as an MBaaS Service is the right approach (and a neat use > of that part of the platform). > > However, it would be imperative that we also recognise the operational and > security risks in considering this, especially for the consulting team if > doing so on a customer app on SaaS (where they could be exposing Red Hat to > serious liability if it is not secured correctly). > > We could likely fail a lot of RFPs too if we exposed this as a standard > part of the platform. So if offered to customers, the risk of doing so > should be documented so that we're not liable for data breaches through lax > Mongo security. > > Regards, > > On 11 November 2016 at 10:43, John Frizelle wrote: > >> The conclusion from the document [1] that compared Data Browser with >> Mongo Express did not seem to indicate that we should replace Data Browser: >> >> *Mongo Express is more complete in number of features but lacks of some >> critical ones like multiple deletions or inline editing. Besides, its user >> interface is less intuitive than the one from Data Browser.* >> >> *If the stability of Data Browser is improved and some key features as >> complex querying are implemented, Data Browser could be a better >> alternative for most of the users. There are other features Mongo Express >> include which are targeted for more advanced users (like multiple database >> management) which could not be that important.* >> >> Let's make sure that we are in agreement on the way forward here. I'm not >> sure a knee-jerk rip and replace of Data Browser is the right answer - >> especially if mongo-express is only implemented as an MBaaS Service and is >> not a first class citizen of the Studio. >> >> I think we need to have a call to discuss this and make sure we are in >> agreement on the path forward. >> >> [1] https://docs.google.com/document/d/1ICBS4ieDkepNne1R_EVe >> 1N9KyP3Ijjpmvc3GiJNrhmw/edit >> >> -- >> John Frizelle >> Platform Architect, Red Hat Mobile >> Consulting Engineering >> >> mobile: *+353 87 290 1644 * >> twitter:* @johnfriz* >> skype: *john_frizelle* >> mail: *jfrizell at redhat.com * >> >> >> >> >> On 11 November 2016 at 10:34, Wei Li wrote: >> >>> It does. But it is using the same approach we are using at the moment >>> with data browser, and it probably works fine with smaller dataset. It will >>> not work very well with large dataset like we have in production >>> environment. >>> >>> We are actually going to look at improving data browser start from the >>> next sprint. But now it looks like we may have a better alternative. >>> @Conor, do you think this can replace data browser in the studio? >>> >>> On Fri, Nov 11, 2016 at 10:28 AM, Conor O'Neill >>> wrote: >>> >>>> Great work on this. We've been seeing a lot of requests for Data >>>> Browser upgrades and this may be a better approach. Does it have bulk >>>> import/export? >>>> >>>> Conor >>>> >>>> >>>> On 10 November 2016 at 16:02, Craig Brookes >>>> wrote: >>>> >>>>> This is pretty cool. I actually think having the data browser as an >>>>> MBaaS service makes a lot of sense. >>>>> For auth it seems you could create a piece of middleware that calls >>>>> back to the platform to check a cookie or header value, if not there >>>>> redirect to a login screen and proxy the credentials through to the >>>>> platform. >>>>> >>>>> Craig >>>>> >>>>> On Thu, Nov 10, 2016 at 3:41 PM, Emilio Rodriguez Martinez < >>>>> emrodrig at redhat.com> wrote: >>>>> >>>>>> Hey guys, >>>>>> >>>>>> based on consulting's feedback, we've been working to integrate Mongo >>>>>> Express in RHMAP. The first step was integrate it as a platform service and >>>>>> here you can find our findings: >>>>>> >>>>>> *Description* >>>>>> Mongo Express Service is a RHMAP service which allows users to manage >>>>>> their Mongo databases through a robust GUI. This interface includes several >>>>>> pieces of functionality missing in the current Data Browser such as a >>>>>> complex query runner or a database and collections statistics. >>>>>> >>>>>> Besides, Mongo Express is an ongoing Open Source project so we can >>>>>> benefit from the community contribution. >>>>>> >>>>>> Here you can find a quick demo of Mongo Express working in RHMAP: >>>>>> https://bluejeans.com/s/zTlgS/ >>>>>> >>>>>> *Current limitations* >>>>>> - At the moment only the service's database is accessible >>>>>> automatically. This means that the Cloud App's databases need to be >>>>>> manually configured to be managed through this service. >>>>>> >>>>>> - This service needs to be public and therefore the database will be >>>>>> exposed: anybody knowing the url would have access to the data. >>>>>> >>>>>> Note: both limitations can be workarounded. Depending on the feedback >>>>>> from this service we will put more effort on this. >>>>>> >>>>>> *Installation and usage* >>>>>> To use Mongo Express Service in RHMAP follow these steps: >>>>>> 1. Provision the sample FeedHenry Service in RHMAP (Services & APIs > >>>>>> + Provision MBaaS service > New MBaaS service) >>>>>> 2. Make the new service public (Details > Make this Service Public to >>>>>> all Projects and Services) >>>>>> 3. Upgrade database (Data Browser > Upgrade Database) >>>>>> 4. Replace code from the test service with the forked Mongo Express >>>>>> Service fork: >>>>>> - clone Mongo Express fork (git at github.com:emilioicai/mon >>>>>> go-express-service.git) >>>>>> - git remote add your services git url (Details > Git Url) >>>>>> - git push --force origin master >>>>>> 5. Deploy (using Node 4 as runtime) >>>>>> 6. Mongo Express should be available through the Preview section in >>>>>> the service view >>>>>> >>>>>> *Troubleshooting* >>>>>> Most of the issues arise because of one of these settings: >>>>>> - Service is not public >>>>>> - Database was not upgraded before deploying >>>>>> - Node 0.10 or Node 0.11 was used as runtime instead of Node 4 >>>>>> In case of a problem re-provisioning and making sure those three >>>>>> settings are properly configured. >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> feedhenry-dev mailing list >>>>> feedhenry-dev at redhat.com >>>>> https://www.redhat.com/mailman/listinfo/feedhenry-dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Product Manager | Red Hat Mobile | Cell: +353-87-9790297 | Desk: >>>> +353-21-2303419 >>>> | Skype: cwjoneill | Location: Cork, Ireland | Timezone: GMT/BST >>>> >>> >>> >>> >>> -- >>> Wei Li >>> Red Hat email address: wei.li at redhat.com >>> Senior Software Engineer >>> >>> _______________________________________________ >>> feedhenry-dev mailing list >>> feedhenry-dev at redhat.com >>> https://www.redhat.com/mailman/listinfo/feedhenry-dev >>> >>> >> > > > -- > James Mernin > Director of Cloud Operations > Red Hat Mobile > > Office: +353 51 810120 | Mobile: +353 87 9170808 > jmernin at redhat.com @mernin > http://www.redhat.com/mobile @redhatmobile > -- Wojciech Trocki Software Engineer, Red Hat Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From davmarti at redhat.com Mon Nov 14 17:29:25 2016 From: davmarti at redhat.com (David Martin) Date: Mon, 14 Nov 2016 17:29:25 +0000 Subject: [feedhenry-dev] Announcing the RHMAP Developer Experience Team Message-ID: Hello all, Starting today, the RHMAP 'Developer Experience' team is kicking off. So, what does this mean for you? Many things, depending on how you use RHMAP. Here's a handy TLDR of what the team goals are, and how we hope to help & communicate with each of the teams who are receiving this: Team Goals - Just one: "Be the driver of change in making RHMAP better for users" Mobile Consulting - Actively working with consulting to get feedback and driving actions out of that feedback - Helping out via rh-mobile-consulting slack channel wherever we can Solution Architects/Workshop trainers - Actively working with SA's and anyone who gives RHMAP workshops to get feedback and driving actions out of that feedback Engineering - Being the goto team for understanding how users are using the platform - Surfacing feedback with the teams, and helping to drive valuable changes Community (in general) - defaulting to feedhenry-dev mailing list & #feedhenry on irc for all team communication, planning etc.. - Having a public Jira board, with full visibility and insight into what the team is doing week to week: https://issues.jboss.org/secure/RapidBoard.jspa?rapidView=3758&view=planning.nodetail - Actively engaging in RHMAP open source projects on github Please don't hesitate to reach out to us as well if you have any questions about the above, or have feedback you'd like to share. The best place to give feedback is the feedhenry-dev mailing list -- David Martin Red Hat Mobile Twitter: @irldavem IRC: @irldavem (feedhenry, mobile-internal) -------------- next part -------------- An HTML attachment was scrubbed... URL: From coneill at redhat.com Tue Nov 15 09:57:27 2016 From: coneill at redhat.com (Conor O'Neill) Date: Tue, 15 Nov 2016 09:57:27 +0000 Subject: [feedhenry-dev] Announcing the RHMAP Developer Experience Team In-Reply-To: References: Message-ID: I'd just echo what James said. I'm really excited by this initiative. On 15 November 2016 at 09:39, James Mernin wrote: > Great email Dave, I'm so looking forward to see the fruits of your > collective labour, and seeing how we can help also. > > The very best of luck! > > On 14 November 2016 at 17:29, David Martin wrote: > >> Hello all, >> >> Starting today, the RHMAP 'Developer Experience' team is kicking off. >> So, what does this mean for you? >> Many things, depending on how you use RHMAP. >> >> Here's a handy TLDR of what the team goals are, and how we hope to help & >> communicate with each of the teams who are receiving this: >> >> Team Goals >> - Just one: "Be the driver of change in making RHMAP better for users" >> >> Mobile Consulting >> - Actively working with consulting to get feedback and driving actions >> out of that feedback >> - Helping out via rh-mobile-consulting slack channel wherever we can >> >> Solution Architects/Workshop trainers >> - Actively working with SA's and anyone who gives RHMAP workshops to get >> feedback and driving actions out of that feedback >> >> Engineering >> - Being the goto team for understanding how users are using the platform >> - Surfacing feedback with the teams, and helping to drive valuable changes >> >> Community (in general) >> - defaulting to feedhenry-dev mailing list & #feedhenry on irc for all >> team communication, planning etc.. >> - Having a public Jira board, with full visibility and insight into what >> the team is doing week to week: https://issues.jboss.org/secur >> e/RapidBoard.jspa?rapidView=3758&view=planning.nodetail >> - Actively engaging in RHMAP open source projects on github >> >> >> Please don't hesitate to reach out to us as well if you have any >> questions about the above, or have feedback you'd like to share. >> The best place to give feedback is the feedhenry-dev mailing list >> >> >> >> -- >> David Martin >> Red Hat Mobile >> Twitter: @irldavem >> IRC: @irldavem (feedhenry, mobile-internal) >> > > > > -- > James Mernin > Director of Cloud Operations > Red Hat Mobile > > Office: +353 51 810120 | Mobile: +353 87 9170808 > jmernin at redhat.com @mernin > http://www.redhat.com/mobile @redhatmobile > -- Product Manager | Red Hat Mobile | Cell: +353-87-9790297 | Desk: +353-21-2303419 | Skype: cwjoneill | Location: Cork, Ireland | Timezone: GMT/BST -------------- next part -------------- An HTML attachment was scrubbed... URL: From wtrocki at redhat.com Tue Nov 15 10:05:59 2016 From: wtrocki at redhat.com (Wojciech Trocki) Date: Tue, 15 Nov 2016 10:05:59 +0000 Subject: [feedhenry-dev] Announcing the RHMAP Developer Experience Team In-Reply-To: References: Message-ID: @Dave - WDYT about having some short blog post with some essential stuff from this email + info that all platform users can now submit their ideas? On Tue, Nov 15, 2016 at 9:57 AM, Conor O'Neill wrote: > I'd just echo what James said. I'm really excited by this initiative. > > > On 15 November 2016 at 09:39, James Mernin wrote: > >> Great email Dave, I'm so looking forward to see the fruits of your >> collective labour, and seeing how we can help also. >> >> The very best of luck! >> >> On 14 November 2016 at 17:29, David Martin wrote: >> >>> Hello all, >>> >>> Starting today, the RHMAP 'Developer Experience' team is kicking off. >>> So, what does this mean for you? >>> Many things, depending on how you use RHMAP. >>> >>> Here's a handy TLDR of what the team goals are, and how we hope to help >>> & communicate with each of the teams who are receiving this: >>> >>> Team Goals >>> - Just one: "Be the driver of change in making RHMAP better for users" >>> >>> Mobile Consulting >>> - Actively working with consulting to get feedback and driving actions >>> out of that feedback >>> - Helping out via rh-mobile-consulting slack channel wherever we can >>> >>> Solution Architects/Workshop trainers >>> - Actively working with SA's and anyone who gives RHMAP workshops to get >>> feedback and driving actions out of that feedback >>> >>> Engineering >>> - Being the goto team for understanding how users are using the platform >>> - Surfacing feedback with the teams, and helping to drive valuable >>> changes >>> >>> Community (in general) >>> - defaulting to feedhenry-dev mailing list & #feedhenry on irc for all >>> team communication, planning etc.. >>> - Having a public Jira board, with full visibility and insight into what >>> the team is doing week to week: https://issues.jboss.org/secur >>> e/RapidBoard.jspa?rapidView=3758&view=planning.nodetail >>> - Actively engaging in RHMAP open source projects on github >>> >>> >>> Please don't hesitate to reach out to us as well if you have any >>> questions about the above, or have feedback you'd like to share. >>> The best place to give feedback is the feedhenry-dev mailing list >>> >>> >>> >>> -- >>> David Martin >>> Red Hat Mobile >>> Twitter: @irldavem >>> IRC: @irldavem (feedhenry, mobile-internal) >>> >> >> >> >> -- >> James Mernin >> Director of Cloud Operations >> Red Hat Mobile >> >> Office: +353 51 810120 | Mobile: +353 87 9170808 >> jmernin at redhat.com @mernin >> http://www.redhat.com/mobile @redhatmobile >> > > > > -- > Product Manager | Red Hat Mobile | Cell: +353-87-9790297 | Desk: > +353-21-2303419 > | Skype: cwjoneill | Location: Cork, Ireland | Timezone: GMT/BST > -- Wojciech Trocki Software Engineer, Red Hat Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From wtrocki at redhat.com Tue Nov 15 10:24:26 2016 From: wtrocki at redhat.com (Wojciech Trocki) Date: Tue, 15 Nov 2016 10:24:26 +0000 Subject: [feedhenry-dev] Announcing the RHMAP Developer Experience Team In-Reply-To: References: Message-ID: Ticket created and landed into backlog: https://issues.jboss.org/browse/FH-2874 On Tue, Nov 15, 2016 at 10:14 AM, Leigh Griffin wrote: > Very best of luck to the team and really looking forward to seeing the > impact this will have. > > Great idea Wojciech, canvassing the community is going to be a core > element to how this team functions and the more blog posts we deliver the > better. > > On Tue, Nov 15, 2016 at 10:05 AM, Wojciech Trocki > wrote: > >> @Dave - WDYT about having some short blog post with some essential stuff >> from this email + info that all platform users can now submit their ideas? >> >> On Tue, Nov 15, 2016 at 9:57 AM, Conor O'Neill >> wrote: >> >>> I'd just echo what James said. I'm really excited by this initiative. >>> >>> >>> On 15 November 2016 at 09:39, James Mernin wrote: >>> >>>> Great email Dave, I'm so looking forward to see the fruits of your >>>> collective labour, and seeing how we can help also. >>>> >>>> The very best of luck! >>>> >>>> On 14 November 2016 at 17:29, David Martin wrote: >>>> >>>>> Hello all, >>>>> >>>>> Starting today, the RHMAP 'Developer Experience' team is kicking off. >>>>> So, what does this mean for you? >>>>> Many things, depending on how you use RHMAP. >>>>> >>>>> Here's a handy TLDR of what the team goals are, and how we hope to >>>>> help & communicate with each of the teams who are receiving this: >>>>> >>>>> Team Goals >>>>> - Just one: "Be the driver of change in making RHMAP better for users" >>>>> >>>>> Mobile Consulting >>>>> - Actively working with consulting to get feedback and driving actions >>>>> out of that feedback >>>>> - Helping out via rh-mobile-consulting slack channel wherever we can >>>>> >>>>> Solution Architects/Workshop trainers >>>>> - Actively working with SA's and anyone who gives RHMAP workshops to >>>>> get feedback and driving actions out of that feedback >>>>> >>>>> Engineering >>>>> - Being the goto team for understanding how users are using the >>>>> platform >>>>> - Surfacing feedback with the teams, and helping to drive valuable >>>>> changes >>>>> >>>>> Community (in general) >>>>> - defaulting to feedhenry-dev mailing list & #feedhenry on irc for all >>>>> team communication, planning etc.. >>>>> - Having a public Jira board, with full visibility and insight into >>>>> what the team is doing week to week: https://issues.jboss.org/secur >>>>> e/RapidBoard.jspa?rapidView=3758&view=planning.nodetail >>>>> - Actively engaging in RHMAP open source projects on github >>>>> >>>>> >>>>> Please don't hesitate to reach out to us as well if you have any >>>>> questions about the above, or have feedback you'd like to share. >>>>> The best place to give feedback is the feedhenry-dev mailing list >>>>> >>>>> >>>>> >>>>> -- >>>>> David Martin >>>>> Red Hat Mobile >>>>> Twitter: @irldavem >>>>> IRC: @irldavem (feedhenry, mobile-internal) >>>>> >>>> >>>> >>>> >>>> -- >>>> James Mernin >>>> Director of Cloud Operations >>>> Red Hat Mobile >>>> >>>> Office: +353 51 810120 | Mobile: +353 87 9170808 >>>> jmernin at redhat.com @mernin >>>> http://www.redhat.com/mobile @redhatmobile >>>> >>> >>> >>> >>> -- >>> Product Manager | Red Hat Mobile | Cell: +353-87-9790297 | Desk: >>> +353-21-2303419 >>> | Skype: cwjoneill | Location: Cork, Ireland | Timezone: GMT/BST >>> >> >> >> >> -- >> Wojciech Trocki >> Software Engineer, Red Hat Mobile >> >> > > > -- > Leigh Griffin > Engineering Manager, > Red Hat, > Waterford, > Ireland > -- Wojciech Trocki Software Engineer, Red Hat Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From kpiwko at redhat.com Tue Nov 15 12:50:03 2016 From: kpiwko at redhat.com (Karel Piwko) Date: Tue, 15 Nov 2016 13:50:03 +0100 Subject: [feedhenry-dev] Announcing the RHMAP Developer Experience Team In-Reply-To: References: Message-ID: +1 would not have said it better James. I'm looking forward to see QE being involved in this team as well, which is currently planned for start of January. Cheers, Karel On Tue, Nov 15, 2016 at 10:39 AM, James Mernin wrote: > Great email Dave, I'm so looking forward to see the fruits of your > collective labour, and seeing how we can help also. > > The very best of luck! > > On 14 November 2016 at 17:29, David Martin wrote: > >> Hello all, >> >> Starting today, the RHMAP 'Developer Experience' team is kicking off. >> So, what does this mean for you? >> Many things, depending on how you use RHMAP. >> >> Here's a handy TLDR of what the team goals are, and how we hope to help & >> communicate with each of the teams who are receiving this: >> >> Team Goals >> - Just one: "Be the driver of change in making RHMAP better for users" >> >> Mobile Consulting >> - Actively working with consulting to get feedback and driving actions >> out of that feedback >> - Helping out via rh-mobile-consulting slack channel wherever we can >> >> Solution Architects/Workshop trainers >> - Actively working with SA's and anyone who gives RHMAP workshops to get >> feedback and driving actions out of that feedback >> >> Engineering >> - Being the goto team for understanding how users are using the platform >> - Surfacing feedback with the teams, and helping to drive valuable changes >> >> Community (in general) >> - defaulting to feedhenry-dev mailing list & #feedhenry on irc for all >> team communication, planning etc.. >> - Having a public Jira board, with full visibility and insight into what >> the team is doing week to week: https://issues.jboss.org/secur >> e/RapidBoard.jspa?rapidView=3758&view=planning.nodetail >> - Actively engaging in RHMAP open source projects on github >> >> >> Please don't hesitate to reach out to us as well if you have any >> questions about the above, or have feedback you'd like to share. >> The best place to give feedback is the feedhenry-dev mailing list >> >> >> >> -- >> David Martin >> Red Hat Mobile >> Twitter: @irldavem >> IRC: @irldavem (feedhenry, mobile-internal) >> > > > > -- > James Mernin > Director of Cloud Operations > Red Hat Mobile > > Office: +353 51 810120 | Mobile: +353 87 9170808 > jmernin at redhat.com @mernin > http://www.redhat.com/mobile @redhatmobile > -------------- next part -------------- An HTML attachment was scrubbed... URL: From davmarti at redhat.com Wed Nov 16 10:24:31 2016 From: davmarti at redhat.com (David Martin) Date: Wed, 16 Nov 2016 10:24:31 +0000 Subject: [feedhenry-dev] Dogfooding for Developer Experience In-Reply-To: References: Message-ID: Here's a practical use case for dogfooding that could really benefit the team. I'm currently trying to get info about how our templates are used. However, this is a tricky thing that can currently only yield limited factual info from querying the platform db. How about the 'RHMAP Developer Experience Feedback App' - a forms app - each form is a VERY short 'survey' (because I'd imagine most people hate filling in surveys) - inital form would have 2 things -- loads of checkboxes for selecting which templates you have/do use (so 1 checkbox per template) -- how do you use the templates? (checkboxes for 'Solutions', 'Training', 'Demos') Future forms/surveys could be: - Which of these templates/samples would you potential use? (radio for various templates/samples ideas we have) - Which of these databrowser features would you most like to see? (radio for things like 'shell access', or 'complex queries via UI' or 'export based on a complex query' I was planning on putting together a POC to see if could work. On 10 November 2016 at 18:59, John Frizelle wrote: > I'm not really sure it makes that much of a difference. > > Typically, almost all development work is done locally - i.e. outside of > the studio. > > The real interactions (and problems) with the product come after an app > has been released as people are then fairly well locked into using the > studio for management, monitoring, upgrades, debugging problems etc... > > So, if we really want to dogfood our product, we need to get something > deployed and then go through the pain of trying to manage it through the > platform... > > > -- > John Frizelle > Platform Architect, Red Hat Mobile > Consulting Engineering > > mobile: *+353 87 290 1644 * > twitter:* @johnfriz* > skype: *john_frizelle* > mail: *jfrizell at redhat.com * > > > > > On 10 November 2016 at 09:15, Matthias Wessendorf > wrote: > >> >> >> On Wed, Nov 9, 2016 at 7:06 PM, Summers Pittman >> wrote: >> >>> Y'all, >>> >>> Wojciech and I had a quick call to flesh out the discussion we were >>> having on IRC about having a dogfooding exercise to better understand and >>> discover what pain points developers have. >>> >>> As far as Jiraisms go, we have a few things to figure out before we can >>> make a proper Epic out of it. Once we do, however, I hope that we can get >>> things ready to start coding relatively quickly. >>> >>> 1) Do we want to greenfield an application or port an existing open >>> source application to the platform? Greenfielding works great for learning >>> specific parts of the platform (ex Auth) or answering certain questions >>> (how do I get sync to do X, Y ,Z), but porting an existing application >>> gives us the opportunity to see how our platform's assumptions mesh with >>> the practices developers are currently using. >>> >> >> I think we should to greenfield, as that might be a bit more fun. So if >> we figure out certain parts of the platform that are not fun to use, it's >> good feedback for improving. I think greenfield works a bit better here, >> because you are a bit more flexible on ideas and concepts >> >> >> @porting: >> A bit off-topic; But: Currently I am mentoring a student from Waterford. >> He works on a Node.js / Microservices version of AeroDoc (+adding >> Keycloak). At a later stage this might be even ported to an RHMAP template. >> So this might be related. bringing in existing code to the platform >> >> >> >>> >>> 2) Do we want to focus on native (Windows + iOS + Android) or Cordova >>> clients? Cordova apps will give us a better experience of challenges our >>> current users have, but because there are so few native users in comparison >>> a native focus may yield things which have been overlooked. >>> >> >> Hrm, not sure: both have benefits: native and cordova >> >> >> >>> >>> 3) I'm sure that more will come from this so feel free to ask and answer >>> your own questions here. >>> >>> Let's discuss in this thread today and Thursday and we can review it in >>> our meeting Friday. >>> >>> Summers >>> >>> _______________________________________________ >>> feedhenry-dev mailing list >>> feedhenry-dev at redhat.com >>> https://www.redhat.com/mailman/listinfo/feedhenry-dev >>> >>> >> >> >> -- >> Project lead AeroGear.org >> >> _______________________________________________ >> feedhenry-dev mailing list >> feedhenry-dev at redhat.com >> https://www.redhat.com/mailman/listinfo/feedhenry-dev >> >> > > _______________________________________________ > feedhenry-dev mailing list > feedhenry-dev at redhat.com > https://www.redhat.com/mailman/listinfo/feedhenry-dev > > -- David Martin Red Hat Mobile Twitter: @irldavem IRC: @irldavem (feedhenry, mobile-internal) -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From supittma at redhat.com Wed Nov 16 12:57:35 2016 From: supittma at redhat.com (Summers Pittman) Date: Wed, 16 Nov 2016 07:57:35 -0500 Subject: [feedhenry-dev] Dogfooding for Developer Experience In-Reply-To: References: Message-ID: On Wed, Nov 16, 2016 at 5:24 AM, David Martin wrote: > Here's a practical use case for dogfooding that could really benefit the > team. > I'm currently trying to get info about how our templates are used. > However, this is a tricky thing that can currently only yield limited > factual info from querying the platform db. > > How about the 'RHMAP Developer Experience Feedback App' > - a forms app > - each form is a VERY short 'survey' (because I'd imagine most people hate > filling in surveys) > - inital form would have 2 things > -- loads of checkboxes for selecting which templates you have/do use (so 1 > checkbox per template) > -- how do you use the templates? (checkboxes for 'Solutions', 'Training', > 'Demos') > > Future forms/surveys could be: > - Which of these templates/samples would you potential use? (radio for > various templates/samples ideas we have) > - Which of these databrowser features would you most like to see? (radio > for things like 'shell access', or 'complex queries via UI' or 'export > based on a complex query' > > I was planning on putting together a POC to see if could work. > > +1. Forms for me has always been a "that's this thing over there I've never touched" so getting more first hand reports on it would be nice. Also IIRC it is a big selling feature. > On 10 November 2016 at 18:59, John Frizelle wrote: > >> I'm not really sure it makes that much of a difference. >> >> Typically, almost all development work is done locally - i.e. outside of >> the studio. >> >> The real interactions (and problems) with the product come after an app >> has been released as people are then fairly well locked into using the >> studio for management, monitoring, upgrades, debugging problems etc... >> >> So, if we really want to dogfood our product, we need to get something >> deployed and then go through the pain of trying to manage it through the >> platform... >> >> >> -- >> John Frizelle >> Platform Architect, Red Hat Mobile >> Consulting Engineering >> >> mobile: *+353 87 290 1644 * >> twitter:* @johnfriz* >> skype: *john_frizelle* >> mail: *jfrizell at redhat.com * >> >> >> >> >> On 10 November 2016 at 09:15, Matthias Wessendorf >> wrote: >> >>> >>> >>> On Wed, Nov 9, 2016 at 7:06 PM, Summers Pittman >>> wrote: >>> >>>> Y'all, >>>> >>>> Wojciech and I had a quick call to flesh out the discussion we were >>>> having on IRC about having a dogfooding exercise to better understand and >>>> discover what pain points developers have. >>>> >>>> As far as Jiraisms go, we have a few things to figure out before we can >>>> make a proper Epic out of it. Once we do, however, I hope that we can get >>>> things ready to start coding relatively quickly. >>>> >>>> 1) Do we want to greenfield an application or port an existing open >>>> source application to the platform? Greenfielding works great for learning >>>> specific parts of the platform (ex Auth) or answering certain questions >>>> (how do I get sync to do X, Y ,Z), but porting an existing application >>>> gives us the opportunity to see how our platform's assumptions mesh with >>>> the practices developers are currently using. >>>> >>> >>> I think we should to greenfield, as that might be a bit more fun. So if >>> we figure out certain parts of the platform that are not fun to use, it's >>> good feedback for improving. I think greenfield works a bit better here, >>> because you are a bit more flexible on ideas and concepts >>> >>> >>> @porting: >>> A bit off-topic; But: Currently I am mentoring a student from Waterford. >>> He works on a Node.js / Microservices version of AeroDoc (+adding >>> Keycloak). At a later stage this might be even ported to an RHMAP template. >>> So this might be related. bringing in existing code to the platform >>> >>> >>> >>>> >>>> 2) Do we want to focus on native (Windows + iOS + Android) or Cordova >>>> clients? Cordova apps will give us a better experience of challenges our >>>> current users have, but because there are so few native users in comparison >>>> a native focus may yield things which have been overlooked. >>>> >>> >>> Hrm, not sure: both have benefits: native and cordova >>> >>> >>> >>>> >>>> 3) I'm sure that more will come from this so feel free to ask and >>>> answer your own questions here. >>>> >>>> Let's discuss in this thread today and Thursday and we can review it in >>>> our meeting Friday. >>>> >>>> Summers >>>> >>>> _______________________________________________ >>>> feedhenry-dev mailing list >>>> feedhenry-dev at redhat.com >>>> https://www.redhat.com/mailman/listinfo/feedhenry-dev >>>> >>>> >>> >>> >>> -- >>> Project lead AeroGear.org >>> >>> _______________________________________________ >>> feedhenry-dev mailing list >>> feedhenry-dev at redhat.com >>> https://www.redhat.com/mailman/listinfo/feedhenry-dev >>> >>> >> >> _______________________________________________ >> feedhenry-dev mailing list >> feedhenry-dev at redhat.com >> https://www.redhat.com/mailman/listinfo/feedhenry-dev >> >> > > > -- > David Martin > Red Hat Mobile > Twitter: @irldavem > IRC: @irldavem (feedhenry, mobile-internal) > > _______________________________________________ > feedhenry-dev mailing list > feedhenry-dev at redhat.com > https://www.redhat.com/mailman/listinfo/feedhenry-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From wtrocki at redhat.com Wed Nov 16 12:58:37 2016 From: wtrocki at redhat.com (Wojciech Trocki) Date: Wed, 16 Nov 2016 12:58:37 +0000 Subject: [feedhenry-dev] Dogfooding for Developer Experience In-Reply-To: References: Message-ID: +1 for having Drag and Drop app. On Wed, Nov 16, 2016 at 12:57 PM, Summers Pittman wrote: > > > On Wed, Nov 16, 2016 at 5:24 AM, David Martin wrote: > >> Here's a practical use case for dogfooding that could really benefit the >> team. >> I'm currently trying to get info about how our templates are used. >> However, this is a tricky thing that can currently only yield limited >> factual info from querying the platform db. >> >> How about the 'RHMAP Developer Experience Feedback App' >> - a forms app >> - each form is a VERY short 'survey' (because I'd imagine most people >> hate filling in surveys) >> - inital form would have 2 things >> -- loads of checkboxes for selecting which templates you have/do use (so >> 1 checkbox per template) >> -- how do you use the templates? (checkboxes for 'Solutions', 'Training', >> 'Demos') >> >> Future forms/surveys could be: >> - Which of these templates/samples would you potential use? (radio for >> various templates/samples ideas we have) >> - Which of these databrowser features would you most like to see? (radio >> for things like 'shell access', or 'complex queries via UI' or 'export >> based on a complex query' >> >> I was planning on putting together a POC to see if could work. >> >> > +1. Forms for me has always been a "that's this thing over there I've > never touched" so getting more first hand reports on it would be nice. > Also IIRC it is a big selling feature. > > >> On 10 November 2016 at 18:59, John Frizelle wrote: >> >>> I'm not really sure it makes that much of a difference. >>> >>> Typically, almost all development work is done locally - i.e. outside of >>> the studio. >>> >>> The real interactions (and problems) with the product come after an app >>> has been released as people are then fairly well locked into using the >>> studio for management, monitoring, upgrades, debugging problems etc... >>> >>> So, if we really want to dogfood our product, we need to get something >>> deployed and then go through the pain of trying to manage it through the >>> platform... >>> >>> >>> -- >>> John Frizelle >>> Platform Architect, Red Hat Mobile >>> Consulting Engineering >>> >>> mobile: *+353 87 290 1644 * >>> twitter:* @johnfriz* >>> skype: *john_frizelle* >>> mail: *jfrizell at redhat.com * >>> >>> >>> >>> >>> On 10 November 2016 at 09:15, Matthias Wessendorf >>> wrote: >>> >>>> >>>> >>>> On Wed, Nov 9, 2016 at 7:06 PM, Summers Pittman >>>> wrote: >>>> >>>>> Y'all, >>>>> >>>>> Wojciech and I had a quick call to flesh out the discussion we were >>>>> having on IRC about having a dogfooding exercise to better understand and >>>>> discover what pain points developers have. >>>>> >>>>> As far as Jiraisms go, we have a few things to figure out before we >>>>> can make a proper Epic out of it. Once we do, however, I hope that we can >>>>> get things ready to start coding relatively quickly. >>>>> >>>>> 1) Do we want to greenfield an application or port an existing open >>>>> source application to the platform? Greenfielding works great for learning >>>>> specific parts of the platform (ex Auth) or answering certain questions >>>>> (how do I get sync to do X, Y ,Z), but porting an existing application >>>>> gives us the opportunity to see how our platform's assumptions mesh with >>>>> the practices developers are currently using. >>>>> >>>> >>>> I think we should to greenfield, as that might be a bit more fun. So if >>>> we figure out certain parts of the platform that are not fun to use, it's >>>> good feedback for improving. I think greenfield works a bit better here, >>>> because you are a bit more flexible on ideas and concepts >>>> >>>> >>>> @porting: >>>> A bit off-topic; But: Currently I am mentoring a student from >>>> Waterford. He works on a Node.js / Microservices version of AeroDoc >>>> (+adding Keycloak). At a later stage this might be even ported to an RHMAP >>>> template. So this might be related. bringing in existing code to the >>>> platform >>>> >>>> >>>> >>>>> >>>>> 2) Do we want to focus on native (Windows + iOS + Android) or Cordova >>>>> clients? Cordova apps will give us a better experience of challenges our >>>>> current users have, but because there are so few native users in comparison >>>>> a native focus may yield things which have been overlooked. >>>>> >>>> >>>> Hrm, not sure: both have benefits: native and cordova >>>> >>>> >>>> >>>>> >>>>> 3) I'm sure that more will come from this so feel free to ask and >>>>> answer your own questions here. >>>>> >>>>> Let's discuss in this thread today and Thursday and we can review it >>>>> in our meeting Friday. >>>>> >>>>> Summers >>>>> >>>>> _______________________________________________ >>>>> feedhenry-dev mailing list >>>>> feedhenry-dev at redhat.com >>>>> https://www.redhat.com/mailman/listinfo/feedhenry-dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Project lead AeroGear.org >>>> >>>> _______________________________________________ >>>> feedhenry-dev mailing list >>>> feedhenry-dev at redhat.com >>>> https://www.redhat.com/mailman/listinfo/feedhenry-dev >>>> >>>> >>> >>> _______________________________________________ >>> feedhenry-dev mailing list >>> feedhenry-dev at redhat.com >>> https://www.redhat.com/mailman/listinfo/feedhenry-dev >>> >>> >> >> >> -- >> David Martin >> Red Hat Mobile >> Twitter: @irldavem >> IRC: @irldavem (feedhenry, mobile-internal) >> >> _______________________________________________ >> feedhenry-dev mailing list >> feedhenry-dev at redhat.com >> https://www.redhat.com/mailman/listinfo/feedhenry-dev >> >> > > _______________________________________________ > feedhenry-dev mailing list > feedhenry-dev at redhat.com > https://www.redhat.com/mailman/listinfo/feedhenry-dev > > -- Wojciech Trocki Software Engineer, Red Hat Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From mmurphy at redhat.com Thu Nov 17 19:23:15 2016 From: mmurphy at redhat.com (Martin Murphy) Date: Thu, 17 Nov 2016 19:23:15 +0000 Subject: [feedhenry-dev] How are PRs to open source repos reviewed? Message-ID: How are PRs to open source repos reviewed? e.g. if someone submits a PR for fh-fhc, is that enough to get a review? Or do they have to ping someone/someplace? Cheers, M. From dpassos at redhat.com Thu Nov 17 19:44:28 2016 From: dpassos at redhat.com (Daniel Passos) Date: Thu, 17 Nov 2016 17:44:28 -0200 Subject: [feedhenry-dev] How are PRs to open source repos reviewed? In-Reply-To: References: Message-ID: What we have been doing on AeroGear is: 1) If the PR came from the community? * Check is there is a Jira for this one, if not create one and link the PR * Ping someone with more knowledgement about the project to review this one Example: https://github.com/aerogear/aerogear-ios-http/pull/73 https://github.com/aerogear/aerogear-ios-oauth2/pull/61 2) If the PR came from the team * Add the Jira about the PR in the PR * Ping someone with more knowledge about the project to review this one Example: https://github.com/aerogear/aerogear-android-auth/pull/37 Bonus point to comment using reaction gifts[1] [1] http://www.reactiongifs.com/ On Thu, Nov 17, 2016 at 5:23 PM, Martin Murphy wrote: > How are PRs to open source repos reviewed? > e.g. if someone submits a PR for fh-fhc, is that enough to get a review? > Or do they have to ping someone/someplace? > > Cheers, > M. > > _______________________________________________ > feedhenry-dev mailing list > feedhenry-dev at redhat.com > https://www.redhat.com/mailman/listinfo/feedhenry-dev > -- -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: From mmurphy at redhat.com Thu Nov 17 20:05:24 2016 From: mmurphy at redhat.com (Martin Murphy) Date: Thu, 17 Nov 2016 20:05:24 +0000 Subject: [feedhenry-dev] How are PRs to open source repos reviewed? In-Reply-To: References: Message-ID: Thanks Passos. That would mean that someone on the team would have to be looking out for PRs to the open source repos. Do you know if we have that in place for all our open source repos? Cheers, M. On 17 November 2016 at 19:44, Daniel Passos wrote: > What we have been doing on AeroGear is: > > 1) If the PR came from the community? > > * Check is there is a Jira for this one, if not create one and link the PR > * Ping someone with more knowledgement about the project to review this one > > Example: https://github.com/aerogear/aerogear-ios-http/pull/73 > https://github.com/aerogear/aerogear-ios-oauth2/pull/61 > > > 2) If the PR came from the team > > * Add the Jira about the PR in the PR > * Ping someone with more knowledge about the project to review this one > > Example: https://github.com/aerogear/aerogear-android-auth/pull/37 > > Bonus point to comment using reaction gifts[1] > > [1] http://www.reactiongifs.com/ > > > On Thu, Nov 17, 2016 at 5:23 PM, Martin Murphy wrote: >> >> How are PRs to open source repos reviewed? >> e.g. if someone submits a PR for fh-fhc, is that enough to get a review? >> Or do they have to ping someone/someplace? >> >> Cheers, >> M. >> >> _______________________________________________ >> feedhenry-dev mailing list >> feedhenry-dev at redhat.com >> https://www.redhat.com/mailman/listinfo/feedhenry-dev > > > > > -- > -- Passos From dpassos at redhat.com Thu Nov 17 20:11:04 2016 From: dpassos at redhat.com (Daniel Passos) Date: Thu, 17 Nov 2016 18:11:04 -0200 Subject: [feedhenry-dev] How are PRs to open source repos reviewed? In-Reply-To: References: Message-ID: There is an option on Github to receive an email for every new PR. I think you can configure it for all repo or only for the repos you want. On Thu, Nov 17, 2016 at 6:05 PM, Martin Murphy wrote: > Thanks Passos. > > That would mean that someone on the team would have to be looking out > for PRs to the open source repos. > Do you know if we have that in place for all our open source repos? > > Cheers, > M. > > > On 17 November 2016 at 19:44, Daniel Passos wrote: > > What we have been doing on AeroGear is: > > > > 1) If the PR came from the community? > > > > * Check is there is a Jira for this one, if not create one and link the > PR > > * Ping someone with more knowledgement about the project to review this > one > > > > Example: https://github.com/aerogear/aerogear-ios-http/pull/73 > > https://github.com/aerogear/aerogear-ios-oauth2/pull/61 > > > > > > 2) If the PR came from the team > > > > * Add the Jira about the PR in the PR > > * Ping someone with more knowledge about the project to review this one > > > > Example: https://github.com/aerogear/aerogear-android-auth/pull/37 > > > > Bonus point to comment using reaction gifts[1] > > > > [1] http://www.reactiongifs.com/ > > > > > > On Thu, Nov 17, 2016 at 5:23 PM, Martin Murphy > wrote: > >> > >> How are PRs to open source repos reviewed? > >> e.g. if someone submits a PR for fh-fhc, is that enough to get a review? > >> Or do they have to ping someone/someplace? > >> > >> Cheers, > >> M. > >> > >> _______________________________________________ > >> feedhenry-dev mailing list > >> feedhenry-dev at redhat.com > >> https://www.redhat.com/mailman/listinfo/feedhenry-dev > > > > > > > > > > -- > > -- Passos > -- -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: From wtrocki at redhat.com Fri Nov 18 16:35:02 2016 From: wtrocki at redhat.com (Wojciech Trocki) Date: Fri, 18 Nov 2016 16:35:02 +0000 Subject: [feedhenry-dev] How are PRs to open source repos reviewed? In-Reply-To: References: Message-ID: We do not have any guide at the moment but.. I'm trying to address this problem with this PR in help repo: https://github.com/fheng/help/pull/261 Feel free to add some comments and your suggestions. Regards Wojtek T. On Thu, Nov 17, 2016 at 8:11 PM, Daniel Passos wrote: > There is an option on Github to receive an email for every new PR. I think > you can configure it for all repo or only for the repos you want. > > On Thu, Nov 17, 2016 at 6:05 PM, Martin Murphy wrote: > >> Thanks Passos. >> >> That would mean that someone on the team would have to be looking out >> for PRs to the open source repos. >> Do you know if we have that in place for all our open source repos? >> >> Cheers, >> M. >> >> >> On 17 November 2016 at 19:44, Daniel Passos wrote: >> > What we have been doing on AeroGear is: >> > >> > 1) If the PR came from the community? >> > >> > * Check is there is a Jira for this one, if not create one and link the >> PR >> > * Ping someone with more knowledgement about the project to review this >> one >> > >> > Example: https://github.com/aerogear/aerogear-ios-http/pull/73 >> > https://github.com/aerogear/aerogear-ios-oauth2/pull/61 >> > >> > >> > 2) If the PR came from the team >> > >> > * Add the Jira about the PR in the PR >> > * Ping someone with more knowledge about the project to review this one >> > >> > Example: https://github.com/aerogear/aerogear-android-auth/pull/37 >> > >> > Bonus point to comment using reaction gifts[1] >> > >> > [1] http://www.reactiongifs.com/ >> > >> > >> > On Thu, Nov 17, 2016 at 5:23 PM, Martin Murphy >> wrote: >> >> >> >> How are PRs to open source repos reviewed? >> >> e.g. if someone submits a PR for fh-fhc, is that enough to get a >> review? >> >> Or do they have to ping someone/someplace? >> >> >> >> Cheers, >> >> M. >> >> >> >> _______________________________________________ >> >> feedhenry-dev mailing list >> >> feedhenry-dev at redhat.com >> >> https://www.redhat.com/mailman/listinfo/feedhenry-dev >> > >> > >> > >> > >> > -- >> > -- Passos >> > > > > -- > -- Passos > > _______________________________________________ > feedhenry-dev mailing list > feedhenry-dev at redhat.com > https://www.redhat.com/mailman/listinfo/feedhenry-dev > > -- Wojciech Trocki Software Engineer, Red Hat Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From emrodrig at redhat.com Thu Nov 10 15:41:29 2016 From: emrodrig at redhat.com (Emilio Rodriguez Martinez) Date: Thu, 10 Nov 2016 16:41:29 +0100 Subject: [feedhenry-dev] Mongo Express Service - Manage your Mongo Database in RHMAP using Mongo Express Message-ID: Hey guys, based on consulting's feedback, we've been working to integrate Mongo Express in RHMAP. The first step was integrate it as a platform service and here you can find our findings: *Description* Mongo Express Service is a RHMAP service which allows users to manage their Mongo databases through a robust GUI. This interface includes several pieces of functionality missing in the current Data Browser such as a complex query runner or a database and collections statistics. Besides, Mongo Express is an ongoing Open Source project so we can benefit from the community contribution. Here you can find a quick demo of Mongo Express working in RHMAP: https://bluejeans.com/s/zTlgS/ *Current limitations* - At the moment only the service's database is accessible automatically. This means that the Cloud App's databases need to be manually configured to be managed through this service. - This service needs to be public and therefore the database will be exposed: anybody knowing the url would have access to the data. Note: both limitations can be workarounded. Depending on the feedback from this service we will put more effort on this. *Installation and usage* To use Mongo Express Service in RHMAP follow these steps: 1. Provision the sample FeedHenry Service in RHMAP (Services & APIs > + Provision MBaaS service > New MBaaS service) 2. Make the new service public (Details > Make this Service Public to all Projects and Services) 3. Upgrade database (Data Browser > Upgrade Database) 4. Replace code from the test service with the forked Mongo Express Service fork: - clone Mongo Express fork (git at github.com:emilioicai/ mongo-express-service.git) - git remote add your services git url (Details > Git Url) - git push --force origin master 5. Deploy (using Node 4 as runtime) 6. Mongo Express should be available through the Preview section in the service view *Troubleshooting* Most of the issues arise because of one of these settings: - Service is not public - Database was not upgraded before deploying - Node 0.10 or Node 0.11 was used as runtime instead of Node 4 In case of a problem re-provisioning and making sure those three settings are properly configured. -------------- next part -------------- An HTML attachment was scrubbed... URL: From davmarti at redhat.com Fri Nov 11 10:52:22 2016 From: davmarti at redhat.com (David Martin) Date: Fri, 11 Nov 2016 10:52:22 +0000 Subject: [feedhenry-dev] Mongo Express Service - Manage your Mongo Database in RHMAP using Mongo Express In-Reply-To: References: Message-ID: > Let's make sure that we are in agreement on the way forward here. I'm not sure a knee-jerk rip and replace of Data Browser is the right answer - especially if mongo-express is only implemented as an MBaaS Service and is not a first class citizen of the Studio. Yes, agreed on this 100%. I think there is much more to gain from improving the robustness of databrowser as is than changing to mongo-express. But I'd like to get consensus on how to move forward. I think this should be viewed as a mongo-express POC that shows how easy it is for someone to use it themselves in their cloud app. (There's a big problem to solve if we want to have it as a supported service i.e. allowing a service to talk to a cloud app's db without hardcoding mong creds) We shouldn't dismiss the findings from the initial report. On 11 November 2016 at 10:43, John Frizelle wrote: > The conclusion from the document [1] that compared Data Browser with Mongo > Express did not seem to indicate that we should replace Data Browser: > > *Mongo Express is more complete in number of features but lacks of some > critical ones like multiple deletions or inline editing. Besides, its user > interface is less intuitive than the one from Data Browser.* > > *If the stability of Data Browser is improved and some key features as > complex querying are implemented, Data Browser could be a better > alternative for most of the users. There are other features Mongo Express > include which are targeted for more advanced users (like multiple database > management) which could not be that important.* > > Let's make sure that we are in agreement on the way forward here. I'm not > sure a knee-jerk rip and replace of Data Browser is the right answer - > especially if mongo-express is only implemented as an MBaaS Service and is > not a first class citizen of the Studio. > > I think we need to have a call to discuss this and make sure we are in > agreement on the path forward. > > [1] https://docs.google.com/document/d/1ICBS4ieDkepNne1R_ > EVe1N9KyP3Ijjpmvc3GiJNrhmw/edit > > -- > John Frizelle > Platform Architect, Red Hat Mobile > Consulting Engineering > > mobile: *+353 87 290 1644 * > twitter:* @johnfriz* > skype: *john_frizelle* > mail: *jfrizell at redhat.com * > > > > > On 11 November 2016 at 10:34, Wei Li wrote: > >> It does. But it is using the same approach we are using at the moment >> with data browser, and it probably works fine with smaller dataset. It will >> not work very well with large dataset like we have in production >> environment. >> >> We are actually going to look at improving data browser start from the >> next sprint. But now it looks like we may have a better alternative. >> @Conor, do you think this can replace data browser in the studio? >> >> On Fri, Nov 11, 2016 at 10:28 AM, Conor O'Neill >> wrote: >> >>> Great work on this. We've been seeing a lot of requests for Data Browser >>> upgrades and this may be a better approach. Does it have bulk import/export? >>> >>> Conor >>> >>> >>> On 10 November 2016 at 16:02, Craig Brookes wrote: >>> >>>> This is pretty cool. I actually think having the data browser as an >>>> MBaaS service makes a lot of sense. >>>> For auth it seems you could create a piece of middleware that calls >>>> back to the platform to check a cookie or header value, if not there >>>> redirect to a login screen and proxy the credentials through to the >>>> platform. >>>> >>>> Craig >>>> >>>> On Thu, Nov 10, 2016 at 3:41 PM, Emilio Rodriguez Martinez < >>>> emrodrig at redhat.com> wrote: >>>> >>>>> Hey guys, >>>>> >>>>> based on consulting's feedback, we've been working to integrate Mongo >>>>> Express in RHMAP. The first step was integrate it as a platform service and >>>>> here you can find our findings: >>>>> >>>>> *Description* >>>>> Mongo Express Service is a RHMAP service which allows users to manage >>>>> their Mongo databases through a robust GUI. This interface includes several >>>>> pieces of functionality missing in the current Data Browser such as a >>>>> complex query runner or a database and collections statistics. >>>>> >>>>> Besides, Mongo Express is an ongoing Open Source project so we can >>>>> benefit from the community contribution. >>>>> >>>>> Here you can find a quick demo of Mongo Express working in RHMAP: >>>>> https://bluejeans.com/s/zTlgS/ >>>>> >>>>> *Current limitations* >>>>> - At the moment only the service's database is accessible >>>>> automatically. This means that the Cloud App's databases need to be >>>>> manually configured to be managed through this service. >>>>> >>>>> - This service needs to be public and therefore the database will be >>>>> exposed: anybody knowing the url would have access to the data. >>>>> >>>>> Note: both limitations can be workarounded. Depending on the feedback >>>>> from this service we will put more effort on this. >>>>> >>>>> *Installation and usage* >>>>> To use Mongo Express Service in RHMAP follow these steps: >>>>> 1. Provision the sample FeedHenry Service in RHMAP (Services & APIs > >>>>> + Provision MBaaS service > New MBaaS service) >>>>> 2. Make the new service public (Details > Make this Service Public to >>>>> all Projects and Services) >>>>> 3. Upgrade database (Data Browser > Upgrade Database) >>>>> 4. Replace code from the test service with the forked Mongo Express >>>>> Service fork: >>>>> - clone Mongo Express fork (git at github.com:emilioicai/mon >>>>> go-express-service.git) >>>>> - git remote add your services git url (Details > Git Url) >>>>> - git push --force origin master >>>>> 5. Deploy (using Node 4 as runtime) >>>>> 6. Mongo Express should be available through the Preview section in >>>>> the service view >>>>> >>>>> *Troubleshooting* >>>>> Most of the issues arise because of one of these settings: >>>>> - Service is not public >>>>> - Database was not upgraded before deploying >>>>> - Node 0.10 or Node 0.11 was used as runtime instead of Node 4 >>>>> In case of a problem re-provisioning and making sure those three >>>>> settings are properly configured. >>>>> >>>> >>>> >>>> _______________________________________________ >>>> feedhenry-dev mailing list >>>> feedhenry-dev at redhat.com >>>> https://www.redhat.com/mailman/listinfo/feedhenry-dev >>>> >>>> >>> >>> >>> -- >>> Product Manager | Red Hat Mobile | Cell: +353-87-9790297 | Desk: >>> +353-21-2303419 >>> | Skype: cwjoneill | Location: Cork, Ireland | Timezone: GMT/BST >>> >> >> >> >> -- >> Wei Li >> Red Hat email address: wei.li at redhat.com >> Senior Software Engineer >> >> _______________________________________________ >> feedhenry-dev mailing list >> feedhenry-dev at redhat.com >> https://www.redhat.com/mailman/listinfo/feedhenry-dev >> >> > -- David Martin Red Hat Mobile Twitter: @irldavem IRC: @irldavem (feedhenry, mobile-internal) -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From jmernin at redhat.com Fri Nov 11 14:01:12 2016 From: jmernin at redhat.com (James Mernin) Date: Fri, 11 Nov 2016 14:01:12 +0000 Subject: [feedhenry-dev] Mongo Express Service - Manage your Mongo Database in RHMAP using Mongo Express In-Reply-To: References: Message-ID: Hi John, Emilio, Conor, This looks hugely promising (considering the shared pain we all know about the Data Browser feature) and the the engineer in me agrees fully that implementing this as an MBaaS Service is the right approach (and a neat use of that part of the platform). However, it would be imperative that we also recognise the operational and security risks in considering this, especially for the consulting team if doing so on a customer app on SaaS (where they could be exposing Red Hat to serious liability if it is not secured correctly). We could likely fail a lot of RFPs too if we exposed this as a standard part of the platform. So if offered to customers, the risk of doing so should be documented so that we're not liable for data breaches through lax Mongo security. Regards, On 11 November 2016 at 10:43, John Frizelle wrote: > The conclusion from the document [1] that compared Data Browser with Mongo > Express did not seem to indicate that we should replace Data Browser: > > *Mongo Express is more complete in number of features but lacks of some > critical ones like multiple deletions or inline editing. Besides, its user > interface is less intuitive than the one from Data Browser.* > > *If the stability of Data Browser is improved and some key features as > complex querying are implemented, Data Browser could be a better > alternative for most of the users. There are other features Mongo Express > include which are targeted for more advanced users (like multiple database > management) which could not be that important.* > > Let's make sure that we are in agreement on the way forward here. I'm not > sure a knee-jerk rip and replace of Data Browser is the right answer - > especially if mongo-express is only implemented as an MBaaS Service and is > not a first class citizen of the Studio. > > I think we need to have a call to discuss this and make sure we are in > agreement on the path forward. > > [1] https://docs.google.com/document/d/1ICBS4ieDkepNne1R_ > EVe1N9KyP3Ijjpmvc3GiJNrhmw/edit > > -- > John Frizelle > Platform Architect, Red Hat Mobile > Consulting Engineering > > mobile: *+353 87 290 1644 * > twitter:* @johnfriz* > skype: *john_frizelle* > mail: *jfrizell at redhat.com * > > > > > On 11 November 2016 at 10:34, Wei Li wrote: > >> It does. But it is using the same approach we are using at the moment >> with data browser, and it probably works fine with smaller dataset. It will >> not work very well with large dataset like we have in production >> environment. >> >> We are actually going to look at improving data browser start from the >> next sprint. But now it looks like we may have a better alternative. >> @Conor, do you think this can replace data browser in the studio? >> >> On Fri, Nov 11, 2016 at 10:28 AM, Conor O'Neill >> wrote: >> >>> Great work on this. We've been seeing a lot of requests for Data Browser >>> upgrades and this may be a better approach. Does it have bulk import/export? >>> >>> Conor >>> >>> >>> On 10 November 2016 at 16:02, Craig Brookes wrote: >>> >>>> This is pretty cool. I actually think having the data browser as an >>>> MBaaS service makes a lot of sense. >>>> For auth it seems you could create a piece of middleware that calls >>>> back to the platform to check a cookie or header value, if not there >>>> redirect to a login screen and proxy the credentials through to the >>>> platform. >>>> >>>> Craig >>>> >>>> On Thu, Nov 10, 2016 at 3:41 PM, Emilio Rodriguez Martinez < >>>> emrodrig at redhat.com> wrote: >>>> >>>>> Hey guys, >>>>> >>>>> based on consulting's feedback, we've been working to integrate Mongo >>>>> Express in RHMAP. The first step was integrate it as a platform service and >>>>> here you can find our findings: >>>>> >>>>> *Description* >>>>> Mongo Express Service is a RHMAP service which allows users to manage >>>>> their Mongo databases through a robust GUI. This interface includes several >>>>> pieces of functionality missing in the current Data Browser such as a >>>>> complex query runner or a database and collections statistics. >>>>> >>>>> Besides, Mongo Express is an ongoing Open Source project so we can >>>>> benefit from the community contribution. >>>>> >>>>> Here you can find a quick demo of Mongo Express working in RHMAP: >>>>> https://bluejeans.com/s/zTlgS/ >>>>> >>>>> *Current limitations* >>>>> - At the moment only the service's database is accessible >>>>> automatically. This means that the Cloud App's databases need to be >>>>> manually configured to be managed through this service. >>>>> >>>>> - This service needs to be public and therefore the database will be >>>>> exposed: anybody knowing the url would have access to the data. >>>>> >>>>> Note: both limitations can be workarounded. Depending on the feedback >>>>> from this service we will put more effort on this. >>>>> >>>>> *Installation and usage* >>>>> To use Mongo Express Service in RHMAP follow these steps: >>>>> 1. Provision the sample FeedHenry Service in RHMAP (Services & APIs > >>>>> + Provision MBaaS service > New MBaaS service) >>>>> 2. Make the new service public (Details > Make this Service Public to >>>>> all Projects and Services) >>>>> 3. Upgrade database (Data Browser > Upgrade Database) >>>>> 4. Replace code from the test service with the forked Mongo Express >>>>> Service fork: >>>>> - clone Mongo Express fork (git at github.com:emilioicai/mon >>>>> go-express-service.git) >>>>> - git remote add your services git url (Details > Git Url) >>>>> - git push --force origin master >>>>> 5. Deploy (using Node 4 as runtime) >>>>> 6. Mongo Express should be available through the Preview section in >>>>> the service view >>>>> >>>>> *Troubleshooting* >>>>> Most of the issues arise because of one of these settings: >>>>> - Service is not public >>>>> - Database was not upgraded before deploying >>>>> - Node 0.10 or Node 0.11 was used as runtime instead of Node 4 >>>>> In case of a problem re-provisioning and making sure those three >>>>> settings are properly configured. >>>>> >>>> >>>> >>>> _______________________________________________ >>>> feedhenry-dev mailing list >>>> feedhenry-dev at redhat.com >>>> https://www.redhat.com/mailman/listinfo/feedhenry-dev >>>> >>>> >>> >>> >>> -- >>> Product Manager | Red Hat Mobile | Cell: +353-87-9790297 | Desk: >>> +353-21-2303419 >>> | Skype: cwjoneill | Location: Cork, Ireland | Timezone: GMT/BST >>> >> >> >> >> -- >> Wei Li >> Red Hat email address: wei.li at redhat.com >> Senior Software Engineer >> >> _______________________________________________ >> feedhenry-dev mailing list >> feedhenry-dev at redhat.com >> https://www.redhat.com/mailman/listinfo/feedhenry-dev >> >> > -- James Mernin Director of Cloud Operations Red Hat Mobile Office: +353 51 810120 | Mobile: +353 87 9170808 jmernin at redhat.com @mernin http://www.redhat.com/mobile @redhatmobile -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From jmernin at redhat.com Mon Nov 14 14:37:14 2016 From: jmernin at redhat.com (James Mernin) Date: Mon, 14 Nov 2016 14:37:14 +0000 Subject: [feedhenry-dev] Mongo Express Service - Manage your Mongo Database in RHMAP using Mongo Express In-Reply-To: References: Message-ID: As per my previous reply, the the legal and operational points that you make at the end are the main reasons this is not currently supported. That, plus the fact that so many customers ask very specific questions in this area during pre-sales stage, that we believe doing this could lose those sales. On 14 November 2016 at 12:55, Wojciech Trocki wrote: > @James > How about exposing mongo connection url directly on SaaS platform (on prem > users can connect to mongo using ssh tunnel)? > From technical point of view this would be possible since each cloud app > is getting separate user and password so we would need to expose database > to outside world on load balancer. > This may be serious problem from legal and operational point of view. Just > want to know your opinion on this one. > > On Fri, Nov 11, 2016 at 2:01 PM, James Mernin wrote: > >> Hi John, Emilio, Conor, >> >> This looks hugely promising (considering the shared pain we all know >> about the Data Browser feature) and the the engineer in me agrees fully >> that implementing this as an MBaaS Service is the right approach (and a >> neat use of that part of the platform). >> >> However, it would be imperative that we also recognise the operational >> and security risks in considering this, especially for the consulting team >> if doing so on a customer app on SaaS (where they could be exposing Red Hat >> to serious liability if it is not secured correctly). >> >> We could likely fail a lot of RFPs too if we exposed this as a standard >> part of the platform. So if offered to customers, the risk of doing so >> should be documented so that we're not liable for data breaches through lax >> Mongo security. >> >> Regards, >> >> On 11 November 2016 at 10:43, John Frizelle wrote: >> >>> The conclusion from the document [1] that compared Data Browser with >>> Mongo Express did not seem to indicate that we should replace Data Browser: >>> >>> *Mongo Express is more complete in number of features but lacks of some >>> critical ones like multiple deletions or inline editing. Besides, its user >>> interface is less intuitive than the one from Data Browser.* >>> >>> *If the stability of Data Browser is improved and some key features as >>> complex querying are implemented, Data Browser could be a better >>> alternative for most of the users. There are other features Mongo Express >>> include which are targeted for more advanced users (like multiple database >>> management) which could not be that important.* >>> >>> Let's make sure that we are in agreement on the way forward here. I'm >>> not sure a knee-jerk rip and replace of Data Browser is the right answer - >>> especially if mongo-express is only implemented as an MBaaS Service and is >>> not a first class citizen of the Studio. >>> >>> I think we need to have a call to discuss this and make sure we are in >>> agreement on the path forward. >>> >>> [1] https://docs.google.com/document/d/1ICBS4ieDkepNne1R_EVe >>> 1N9KyP3Ijjpmvc3GiJNrhmw/edit >>> >>> -- >>> John Frizelle >>> Platform Architect, Red Hat Mobile >>> Consulting Engineering >>> >>> mobile: *+353 87 290 1644 * >>> twitter:* @johnfriz* >>> skype: *john_frizelle* >>> mail: *jfrizell at redhat.com * >>> >>> >>> >>> >>> On 11 November 2016 at 10:34, Wei Li wrote: >>> >>>> It does. But it is using the same approach we are using at the moment >>>> with data browser, and it probably works fine with smaller dataset. It will >>>> not work very well with large dataset like we have in production >>>> environment. >>>> >>>> We are actually going to look at improving data browser start from the >>>> next sprint. But now it looks like we may have a better alternative. >>>> @Conor, do you think this can replace data browser in the studio? >>>> >>>> On Fri, Nov 11, 2016 at 10:28 AM, Conor O'Neill >>>> wrote: >>>> >>>>> Great work on this. We've been seeing a lot of requests for Data >>>>> Browser upgrades and this may be a better approach. Does it have bulk >>>>> import/export? >>>>> >>>>> Conor >>>>> >>>>> >>>>> On 10 November 2016 at 16:02, Craig Brookes >>>>> wrote: >>>>> >>>>>> This is pretty cool. I actually think having the data browser as an >>>>>> MBaaS service makes a lot of sense. >>>>>> For auth it seems you could create a piece of middleware that calls >>>>>> back to the platform to check a cookie or header value, if not there >>>>>> redirect to a login screen and proxy the credentials through to the >>>>>> platform. >>>>>> >>>>>> Craig >>>>>> >>>>>> On Thu, Nov 10, 2016 at 3:41 PM, Emilio Rodriguez Martinez < >>>>>> emrodrig at redhat.com> wrote: >>>>>> >>>>>>> Hey guys, >>>>>>> >>>>>>> based on consulting's feedback, we've been working to integrate >>>>>>> Mongo Express in RHMAP. The first step was integrate it as a platform >>>>>>> service and here you can find our findings: >>>>>>> >>>>>>> *Description* >>>>>>> Mongo Express Service is a RHMAP service which allows users to >>>>>>> manage their Mongo databases through a robust GUI. This interface includes >>>>>>> several pieces of functionality missing in the current Data Browser such as >>>>>>> a complex query runner or a database and collections statistics. >>>>>>> >>>>>>> Besides, Mongo Express is an ongoing Open Source project so we can >>>>>>> benefit from the community contribution. >>>>>>> >>>>>>> Here you can find a quick demo of Mongo Express working in RHMAP: >>>>>>> https://bluejeans.com/s/zTlgS/ >>>>>>> >>>>>>> *Current limitations* >>>>>>> - At the moment only the service's database is accessible >>>>>>> automatically. This means that the Cloud App's databases need to be >>>>>>> manually configured to be managed through this service. >>>>>>> >>>>>>> - This service needs to be public and therefore the database will be >>>>>>> exposed: anybody knowing the url would have access to the data. >>>>>>> >>>>>>> Note: both limitations can be workarounded. Depending on the >>>>>>> feedback from this service we will put more effort on this. >>>>>>> >>>>>>> *Installation and usage* >>>>>>> To use Mongo Express Service in RHMAP follow these steps: >>>>>>> 1. Provision the sample FeedHenry Service in RHMAP (Services & APIs >>>>>>> > + Provision MBaaS service > New MBaaS service) >>>>>>> 2. Make the new service public (Details > Make this Service Public >>>>>>> to all Projects and Services) >>>>>>> 3. Upgrade database (Data Browser > Upgrade Database) >>>>>>> 4. Replace code from the test service with the forked Mongo Express >>>>>>> Service fork: >>>>>>> - clone Mongo Express fork (git at github.com:emilioicai/mon >>>>>>> go-express-service.git) >>>>>>> - git remote add your services git url (Details > Git Url) >>>>>>> - git push --force origin master >>>>>>> 5. Deploy (using Node 4 as runtime) >>>>>>> 6. Mongo Express should be available through the Preview section in >>>>>>> the service view >>>>>>> >>>>>>> *Troubleshooting* >>>>>>> Most of the issues arise because of one of these settings: >>>>>>> - Service is not public >>>>>>> - Database was not upgraded before deploying >>>>>>> - Node 0.10 or Node 0.11 was used as runtime instead of Node 4 >>>>>>> In case of a problem re-provisioning and making sure those three >>>>>>> settings are properly configured. >>>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> feedhenry-dev mailing list >>>>>> feedhenry-dev at redhat.com >>>>>> https://www.redhat.com/mailman/listinfo/feedhenry-dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Product Manager | Red Hat Mobile | Cell: +353-87-9790297 | Desk: >>>>> +353-21-2303419 >>>>> | Skype: cwjoneill | Location: Cork, Ireland | Timezone: GMT/BST >>>>> >>>> >>>> >>>> >>>> -- >>>> Wei Li >>>> Red Hat email address: wei.li at redhat.com >>>> Senior Software Engineer >>>> >>>> _______________________________________________ >>>> feedhenry-dev mailing list >>>> feedhenry-dev at redhat.com >>>> https://www.redhat.com/mailman/listinfo/feedhenry-dev >>>> >>>> >>> >> >> >> -- >> James Mernin >> Director of Cloud Operations >> Red Hat Mobile >> >> Office: +353 51 810120 | Mobile: +353 87 9170808 >> jmernin at redhat.com @mernin >> http://www.redhat.com/mobile @redhatmobile >> > > > > -- > Wojciech Trocki > Software Engineer, Red Hat Mobile > > -- James Mernin Director of Cloud Operations Red Hat Mobile Office: +353 51 810120 | Mobile: +353 87 9170808 jmernin at redhat.com @mernin http://www.redhat.com/mobile @redhatmobile -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From jmernin at redhat.com Tue Nov 15 09:39:15 2016 From: jmernin at redhat.com (James Mernin) Date: Tue, 15 Nov 2016 09:39:15 +0000 Subject: [feedhenry-dev] Announcing the RHMAP Developer Experience Team In-Reply-To: References: Message-ID: Great email Dave, I'm so looking forward to see the fruits of your collective labour, and seeing how we can help also. The very best of luck! On 14 November 2016 at 17:29, David Martin wrote: > Hello all, > > Starting today, the RHMAP 'Developer Experience' team is kicking off. > So, what does this mean for you? > Many things, depending on how you use RHMAP. > > Here's a handy TLDR of what the team goals are, and how we hope to help & > communicate with each of the teams who are receiving this: > > Team Goals > - Just one: "Be the driver of change in making RHMAP better for users" > > Mobile Consulting > - Actively working with consulting to get feedback and driving actions out > of that feedback > - Helping out via rh-mobile-consulting slack channel wherever we can > > Solution Architects/Workshop trainers > - Actively working with SA's and anyone who gives RHMAP workshops to get > feedback and driving actions out of that feedback > > Engineering > - Being the goto team for understanding how users are using the platform > - Surfacing feedback with the teams, and helping to drive valuable changes > > Community (in general) > - defaulting to feedhenry-dev mailing list & #feedhenry on irc for all > team communication, planning etc.. > - Having a public Jira board, with full visibility and insight into what > the team is doing week to week: https://issues.jboss.org/ > secure/RapidBoard.jspa?rapidView=3758&view=planning.nodetail > - Actively engaging in RHMAP open source projects on github > > > Please don't hesitate to reach out to us as well if you have any questions > about the above, or have feedback you'd like to share. > The best place to give feedback is the feedhenry-dev mailing list > > > > -- > David Martin > Red Hat Mobile > Twitter: @irldavem > IRC: @irldavem (feedhenry, mobile-internal) > -- James Mernin Director of Cloud Operations Red Hat Mobile Office: +353 51 810120 | Mobile: +353 87 9170808 jmernin at redhat.com @mernin http://www.redhat.com/mobile @redhatmobile -------------- next part -------------- An HTML attachment was scrubbed... URL: From lgriffin at redhat.com Tue Nov 15 10:14:26 2016 From: lgriffin at redhat.com (Leigh Griffin) Date: Tue, 15 Nov 2016 10:14:26 +0000 Subject: [feedhenry-dev] Announcing the RHMAP Developer Experience Team In-Reply-To: References: Message-ID: Very best of luck to the team and really looking forward to seeing the impact this will have. Great idea Wojciech, canvassing the community is going to be a core element to how this team functions and the more blog posts we deliver the better. On Tue, Nov 15, 2016 at 10:05 AM, Wojciech Trocki wrote: > @Dave - WDYT about having some short blog post with some essential stuff > from this email + info that all platform users can now submit their ideas? > > On Tue, Nov 15, 2016 at 9:57 AM, Conor O'Neill wrote: > >> I'd just echo what James said. I'm really excited by this initiative. >> >> >> On 15 November 2016 at 09:39, James Mernin wrote: >> >>> Great email Dave, I'm so looking forward to see the fruits of your >>> collective labour, and seeing how we can help also. >>> >>> The very best of luck! >>> >>> On 14 November 2016 at 17:29, David Martin wrote: >>> >>>> Hello all, >>>> >>>> Starting today, the RHMAP 'Developer Experience' team is kicking off. >>>> So, what does this mean for you? >>>> Many things, depending on how you use RHMAP. >>>> >>>> Here's a handy TLDR of what the team goals are, and how we hope to help >>>> & communicate with each of the teams who are receiving this: >>>> >>>> Team Goals >>>> - Just one: "Be the driver of change in making RHMAP better for users" >>>> >>>> Mobile Consulting >>>> - Actively working with consulting to get feedback and driving actions >>>> out of that feedback >>>> - Helping out via rh-mobile-consulting slack channel wherever we can >>>> >>>> Solution Architects/Workshop trainers >>>> - Actively working with SA's and anyone who gives RHMAP workshops to >>>> get feedback and driving actions out of that feedback >>>> >>>> Engineering >>>> - Being the goto team for understanding how users are using the platform >>>> - Surfacing feedback with the teams, and helping to drive valuable >>>> changes >>>> >>>> Community (in general) >>>> - defaulting to feedhenry-dev mailing list & #feedhenry on irc for all >>>> team communication, planning etc.. >>>> - Having a public Jira board, with full visibility and insight into >>>> what the team is doing week to week: https://issues.jboss.org/secur >>>> e/RapidBoard.jspa?rapidView=3758&view=planning.nodetail >>>> - Actively engaging in RHMAP open source projects on github >>>> >>>> >>>> Please don't hesitate to reach out to us as well if you have any >>>> questions about the above, or have feedback you'd like to share. >>>> The best place to give feedback is the feedhenry-dev mailing list >>>> >>>> >>>> >>>> -- >>>> David Martin >>>> Red Hat Mobile >>>> Twitter: @irldavem >>>> IRC: @irldavem (feedhenry, mobile-internal) >>>> >>> >>> >>> >>> -- >>> James Mernin >>> Director of Cloud Operations >>> Red Hat Mobile >>> >>> Office: +353 51 810120 | Mobile: +353 87 9170808 >>> jmernin at redhat.com @mernin >>> http://www.redhat.com/mobile @redhatmobile >>> >> >> >> >> -- >> Product Manager | Red Hat Mobile | Cell: +353-87-9790297 | Desk: >> +353-21-2303419 >> | Skype: cwjoneill | Location: Cork, Ireland | Timezone: GMT/BST >> > > > > -- > Wojciech Trocki > Software Engineer, Red Hat Mobile > > -- Leigh Griffin Engineering Manager, Red Hat, Waterford, Ireland -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From ckrych at redhat.com Tue Nov 15 12:57:38 2016 From: ckrych at redhat.com (Corinne Krych) Date: Tue, 15 Nov 2016 13:57:38 +0100 Subject: [feedhenry-dev] Announcing the RHMAP Developer Experience Team In-Reply-To: References: Message-ID: Congratulations and welcome to DevX team (such a cool name)! ++ Corinne On Tue, Nov 15, 2016 at 1:50 PM, Karel Piwko wrote: > +1 would not have said it better James. I'm looking forward to see QE > being involved in this team as well, which is currently planned for start > of January. > > Cheers, > > Karel > > On Tue, Nov 15, 2016 at 10:39 AM, James Mernin wrote: > >> Great email Dave, I'm so looking forward to see the fruits of your >> collective labour, and seeing how we can help also. >> >> The very best of luck! >> >> On 14 November 2016 at 17:29, David Martin wrote: >> >>> Hello all, >>> >>> Starting today, the RHMAP 'Developer Experience' team is kicking off. >>> So, what does this mean for you? >>> Many things, depending on how you use RHMAP. >>> >>> Here's a handy TLDR of what the team goals are, and how we hope to help >>> & communicate with each of the teams who are receiving this: >>> >>> Team Goals >>> - Just one: "Be the driver of change in making RHMAP better for users" >>> >>> Mobile Consulting >>> - Actively working with consulting to get feedback and driving actions >>> out of that feedback >>> - Helping out via rh-mobile-consulting slack channel wherever we can >>> >>> Solution Architects/Workshop trainers >>> - Actively working with SA's and anyone who gives RHMAP workshops to get >>> feedback and driving actions out of that feedback >>> >>> Engineering >>> - Being the goto team for understanding how users are using the platform >>> - Surfacing feedback with the teams, and helping to drive valuable >>> changes >>> >>> Community (in general) >>> - defaulting to feedhenry-dev mailing list & #feedhenry on irc for all >>> team communication, planning etc.. >>> - Having a public Jira board, with full visibility and insight into what >>> the team is doing week to week: https://issues.jboss.org/secur >>> e/RapidBoard.jspa?rapidView=3758&view=planning.nodetail >>> - Actively engaging in RHMAP open source projects on github >>> >>> >>> Please don't hesitate to reach out to us as well if you have any >>> questions about the above, or have feedback you'd like to share. >>> The best place to give feedback is the feedhenry-dev mailing list >>> >>> >>> >>> -- >>> David Martin >>> Red Hat Mobile >>> Twitter: @irldavem >>> IRC: @irldavem (feedhenry, mobile-internal) >>> >> >> >> >> -- >> James Mernin >> Director of Cloud Operations >> Red Hat Mobile >> >> Office: +353 51 810120 | Mobile: +353 87 9170808 >> jmernin at redhat.com @mernin >> http://www.redhat.com/mobile @redhatmobile >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wtrocki at redhat.com Mon Nov 21 16:18:36 2016 From: wtrocki at redhat.com (Wojciech Trocki) Date: Mon, 21 Nov 2016 16:18:36 +0000 Subject: [feedhenry-dev] Using mailing list as main source of new functionalities Message-ID: Hi Everyone We want to keep our backlog consistent and clean from ideas that may not be addressed in near future. To provide some collaboration space we created new trello board. Why duplication over jira? This matches some agile approach: "When backlog has some tickets that would not be part of roadmap for the next 6 months then they should be removed from backlog :] ". I would like to ask all interesting parties about opinion on using Trello vs Mailing List Why we created trello and decided to not use mailing list (IMHO) *Positive parts:* - Simplicity - Defaulting to one source (email) - Easy to contribute - just sent email. *Negative parts:* - No overview and visibility for our roadmap - just bunch of emails. - No way to retrieve emails before signed to group - No way to stage and label issues for customers and better visibility - Mixed content - feature request can be mixed with other non related email threads like this one. - Interface from the last century: http://www.redhat.com/archives/feedhenry-dev/2016-November/msg00000.html Regards -- Wojciech Trocki Software Engineer, Red Hat Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From wtrocki at redhat.com Mon Nov 21 16:22:48 2016 From: wtrocki at redhat.com (Wojciech Trocki) Date: Mon, 21 Nov 2016 16:22:48 +0000 Subject: [feedhenry-dev] [Feature request] Allow to create project with mongo database that is already migrated. Message-ID: *TL;DR - New cloud apps and services should use direct mongo db access. Migration should be used only for legacy projects.* We require database migrations for the new apps mostly because of historical reasons. We should enable creation of service and cloud app with direct access to the mongo database. Creating ditch type database doesn't make any sense at the moment because in most of the guides and services we require database to be migrated straightaway. That's would improve our guides and would mean way less hassle for customers. Conor mentioned this numerous times in some of high level requirements documents. This functionality was also confirmed to be really useful for consulting. Sometimes developers forgot to migrate database and fh-ditch is used in production which is causing some performance and access problems and involve painful database migration. This feature may be also mentioned in various tickets and different contexts. Purpose of this emails is to determine some blockers (do we still have to use ditch by default) and provide some general actions. Regards -- Wojciech Trocki Software Engineer, Red Hat Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From wtrocki at redhat.com Mon Nov 21 16:27:56 2016 From: wtrocki at redhat.com (Wojciech Trocki) Date: Mon, 21 Nov 2016 16:27:56 +0000 Subject: [feedhenry-dev] Using mailing list as main source of new functionalities In-Reply-To: References: Message-ID: Url to our public trello board: https://trello.com/b/olSlTR9m/rhmap-developer-experience-feedback On Mon, Nov 21, 2016 at 4:18 PM, Wojciech Trocki wrote: > Hi Everyone > > We want to keep our backlog consistent and clean from ideas that may not > be addressed in near future. To provide some collaboration space we created > new trello board. > Why duplication over jira? This matches some agile approach: "When backlog > has some tickets that would not be part of roadmap for the next 6 months > then they should be removed from backlog :] ". > > I would like to ask all interesting parties about opinion on using Trello > vs Mailing List > > Why we created trello and decided to not use mailing list (IMHO) > > *Positive parts:* > > - Simplicity > - Defaulting to one source (email) > - Easy to contribute - just sent email. > > *Negative parts:* > > - No overview and visibility for our roadmap - just bunch of emails. > - No way to retrieve emails before signed to group > - No way to stage and label issues for customers and better visibility > - Mixed content - feature request can be mixed with other non related > email threads like this one. > - Interface from the last century: > http://www.redhat.com/archives/feedhenry-dev/2016-November/msg00000.html > > > Regards > > -- > Wojciech Trocki > Software Engineer, Red Hat Mobile > > -- Wojciech Trocki Software Engineer, Red Hat Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From jfrizell at redhat.com Mon Nov 21 16:39:50 2016 From: jfrizell at redhat.com (John Frizelle) Date: Mon, 21 Nov 2016 16:39:50 +0000 Subject: [feedhenry-dev] [Feature request] Allow to create project with mongo database that is already migrated. In-Reply-To: References: Message-ID: I added some comments to the trello ticket - copying them here for visibility... The problem with this approach (and the reason we have historically used shared DB) is that a new empty DB in MongoDB 2.x requires ~300MB of disk space - that's a HUGE overhead for every single app created (especially considering that a large % of apps created are hello world style apps that do not require dedicated DB). In MongoDB 3.x, there is pretty much a 0 overhead on creating a new DB - i.e. it does not pre-allocate 100's of MB of disk space. So, I think we either need to wait until we have 3.X MongoDB or be able to indicate in the project/app/service template if it requires a dedicated DB and only create the dedicated DB for those templates that need it. -- John Frizelle Platform Architect, Red Hat Mobile Consulting Engineering mobile: *+353 87 290 1644 * twitter:* @johnfriz* skype: *john_frizelle* mail: *jfrizell at redhat.com * On 21 November 2016 at 16:22, Wojciech Trocki wrote: > *TL;DR - New cloud apps and services should use direct mongo db access. > Migration should be used only for legacy projects.* > > We require database migrations for the new apps mostly because of > historical reasons. We should enable creation of service and cloud app with > direct access to the mongo database. Creating ditch type database doesn't > make any sense at the moment because in most of the guides and services we > require database to be migrated straightaway. > > That's would improve our guides and would mean way less hassle for > customers. Conor mentioned this numerous times in some of high level > requirements documents. This functionality was also confirmed to be really > useful for consulting. Sometimes developers forgot to migrate database and > fh-ditch is used in production which is causing some performance and access > problems and involve painful database migration. > > This feature may be also mentioned in various tickets and different > contexts. > Purpose of this emails is to determine some blockers (do we still have to > use ditch by default) and provide some general actions. > > Regards > -- > Wojciech Trocki > Software Engineer, Red Hat Mobile > > > _______________________________________________ > feedhenry-dev mailing list > feedhenry-dev at redhat.com > https://www.redhat.com/mailman/listinfo/feedhenry-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From davmarti at redhat.com Mon Nov 21 18:03:20 2016 From: davmarti at redhat.com (David Martin) Date: Mon, 21 Nov 2016 18:03:20 +0000 Subject: [feedhenry-dev] Using mailing list as main source of new functionalities In-Reply-To: References: Message-ID: I initially created the trello board as a landing ground and discussion area for features requests and enhancements. A way for users to give their feedback and make sure their voice was heard before an action was taken ('action was taken' meaning something was added to the Jira backlog) The mailing list didn't even come into mind as the place for that to happen. Thanks to Summers for bringing it up with me, I think using trello for this is probably not the best way forward. The mailing list makes so much sense, and I really should have thought of it. Where I think we're lacking, and some other teams have found it useful, is having the team roadmap view visible. All our backlog is ultimately in Jira. The roadmap is hidden away in our Jira backlog in the form of issues & Epics. Is there a way to better visualise the backlog at the 'roadmap' level? Is that something people would find useful? On 21 November 2016 at 16:27, Wojciech Trocki wrote: > Url to our public trello board: https://trello.com/b/ > olSlTR9m/rhmap-developer-experience-feedback > > On Mon, Nov 21, 2016 at 4:18 PM, Wojciech Trocki > wrote: > >> Hi Everyone >> >> We want to keep our backlog consistent and clean from ideas that may not >> be addressed in near future. To provide some collaboration space we created >> new trello board. >> Why duplication over jira? This matches some agile approach: "When >> backlog has some tickets that would not be part of roadmap for the next 6 >> months then they should be removed from backlog :] ". >> >> I would like to ask all interesting parties about opinion on using Trello >> vs Mailing List >> >> Why we created trello and decided to not use mailing list (IMHO) >> >> *Positive parts:* >> >> - Simplicity >> - Defaulting to one source (email) >> - Easy to contribute - just sent email. >> >> *Negative parts:* >> >> - No overview and visibility for our roadmap - just bunch of emails. >> - No way to retrieve emails before signed to group >> - No way to stage and label issues for customers and better visibility >> - Mixed content - feature request can be mixed with other non related >> email threads like this one. >> - Interface from the last century: >> http://www.redhat.com/archives/feedhenry-dev/2016-November/msg00000.html >> >> >> Regards >> >> -- >> Wojciech Trocki >> Software Engineer, Red Hat Mobile >> >> > > > -- > Wojciech Trocki > Software Engineer, Red Hat Mobile > > > _______________________________________________ > feedhenry-dev mailing list > feedhenry-dev at redhat.com > https://www.redhat.com/mailman/listinfo/feedhenry-dev > > -- David Martin Red Hat Mobile Twitter: @irldavem IRC: @irldavem (feedhenry, mobile-internal) -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From wtrocki at redhat.com Mon Nov 21 18:16:49 2016 From: wtrocki at redhat.com (Wojciech Trocki) Date: Mon, 21 Nov 2016 18:16:49 +0000 Subject: [feedhenry-dev] Using mailing list as main source of new functionalities In-Reply-To: References: Message-ID: We have already installed agile road plugin that is using some variation of gantt chart. Example here: https://issues.jboss.org/secure/PortfolioPlan.jspa?id=12#backlog I think that trello would be good solution for exposing roadmap. On Mon, Nov 21, 2016 at 6:03 PM, David Martin wrote: > I initially created the trello board as a landing ground and discussion > area for features requests and enhancements. > A way for users to give their feedback and make sure their voice was heard > before an action was taken ('action was taken' meaning something was added > to the Jira backlog) > The mailing list didn't even come into mind as the place for that to > happen. > > Thanks to Summers for bringing it up with me, I think using trello for > this is probably not the best way forward. > The mailing list makes so much sense, and I really should have thought of > it. > > Where I think we're lacking, and some other teams have found it useful, is > having the team roadmap view visible. > All our backlog is ultimately in Jira. > The roadmap is hidden away in our Jira backlog in the form of issues & > Epics. > Is there a way to better visualise the backlog at the 'roadmap' level? > Is that something people would find useful? > > > > On 21 November 2016 at 16:27, Wojciech Trocki wrote: > >> Url to our public trello board: https://trello.com/b/ol >> SlTR9m/rhmap-developer-experience-feedback >> >> On Mon, Nov 21, 2016 at 4:18 PM, Wojciech Trocki >> wrote: >> >>> Hi Everyone >>> >>> We want to keep our backlog consistent and clean from ideas that may not >>> be addressed in near future. To provide some collaboration space we created >>> new trello board. >>> Why duplication over jira? This matches some agile approach: "When >>> backlog has some tickets that would not be part of roadmap for the next 6 >>> months then they should be removed from backlog :] ". >>> >>> I would like to ask all interesting parties about opinion on using >>> Trello vs Mailing List >>> >>> Why we created trello and decided to not use mailing list (IMHO) >>> >>> *Positive parts:* >>> >>> - Simplicity >>> - Defaulting to one source (email) >>> - Easy to contribute - just sent email. >>> >>> *Negative parts:* >>> >>> - No overview and visibility for our roadmap - just bunch of emails. >>> - No way to retrieve emails before signed to group >>> - No way to stage and label issues for customers and better visibility >>> - Mixed content - feature request can be mixed with other non related >>> email threads like this one. >>> - Interface from the last century: >>> http://www.redhat.com/archives/feedhenry-dev/2016-November/msg00000.html >>> >>> >>> Regards >>> >>> -- >>> Wojciech Trocki >>> Software Engineer, Red Hat Mobile >>> >>> >> >> >> -- >> Wojciech Trocki >> Software Engineer, Red Hat Mobile >> >> >> _______________________________________________ >> feedhenry-dev mailing list >> feedhenry-dev at redhat.com >> https://www.redhat.com/mailman/listinfo/feedhenry-dev >> >> > > > -- > David Martin > Red Hat Mobile > Twitter: @irldavem > IRC: @irldavem (feedhenry, mobile-internal) > -- Wojciech Trocki Software Engineer, Red Hat Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From jfrizell at redhat.com Mon Nov 21 22:34:59 2016 From: jfrizell at redhat.com (John Frizelle) Date: Mon, 21 Nov 2016 22:34:59 +0000 Subject: [feedhenry-dev] Using mailing list as main source of new functionalities In-Reply-To: References: Message-ID: JIRA portfolios may also be an option. I know Leigh has been looking into this a bit so might be able to shed some more light on it's potential fit here. -- John Frizelle Platform Architect, Red Hat Mobile Consulting Engineering mobile: *+353 87 290 1644 * twitter:* @johnfriz* skype: *john_frizelle* mail: *jfrizell at redhat.com * On 21 November 2016 at 18:16, Wojciech Trocki wrote: > We have already installed agile road plugin that is using some variation > of gantt chart. > Example here: https://issues.jboss.org/secure/PortfolioPlan.jspa? > id=12#backlog > > I think that trello would be good solution for exposing roadmap. > > On Mon, Nov 21, 2016 at 6:03 PM, David Martin wrote: > >> I initially created the trello board as a landing ground and discussion >> area for features requests and enhancements. >> A way for users to give their feedback and make sure their voice was >> heard before an action was taken ('action was taken' meaning something was >> added to the Jira backlog) >> The mailing list didn't even come into mind as the place for that to >> happen. >> >> Thanks to Summers for bringing it up with me, I think using trello for >> this is probably not the best way forward. >> The mailing list makes so much sense, and I really should have thought of >> it. >> >> Where I think we're lacking, and some other teams have found it useful, >> is having the team roadmap view visible. >> All our backlog is ultimately in Jira. >> The roadmap is hidden away in our Jira backlog in the form of issues & >> Epics. >> Is there a way to better visualise the backlog at the 'roadmap' level? >> Is that something people would find useful? >> >> >> >> On 21 November 2016 at 16:27, Wojciech Trocki wrote: >> >>> Url to our public trello board: https://trello.com/b/ol >>> SlTR9m/rhmap-developer-experience-feedback >>> >>> On Mon, Nov 21, 2016 at 4:18 PM, Wojciech Trocki >>> wrote: >>> >>>> Hi Everyone >>>> >>>> We want to keep our backlog consistent and clean from ideas that may >>>> not be addressed in near future. To provide some collaboration space we >>>> created new trello board. >>>> Why duplication over jira? This matches some agile approach: "When >>>> backlog has some tickets that would not be part of roadmap for the next 6 >>>> months then they should be removed from backlog :] ". >>>> >>>> I would like to ask all interesting parties about opinion on using >>>> Trello vs Mailing List >>>> >>>> Why we created trello and decided to not use mailing list (IMHO) >>>> >>>> *Positive parts:* >>>> >>>> - Simplicity >>>> - Defaulting to one source (email) >>>> - Easy to contribute - just sent email. >>>> >>>> *Negative parts:* >>>> >>>> - No overview and visibility for our roadmap - just bunch of emails. >>>> - No way to retrieve emails before signed to group >>>> - No way to stage and label issues for customers and better visibility >>>> - Mixed content - feature request can be mixed with other non related >>>> email threads like this one. >>>> - Interface from the last century: >>>> http://www.redhat.com/archives/feedhenry-dev/2016-November/m >>>> sg00000.html >>>> >>>> >>>> Regards >>>> >>>> -- >>>> Wojciech Trocki >>>> Software Engineer, Red Hat Mobile >>>> >>>> >>> >>> >>> -- >>> Wojciech Trocki >>> Software Engineer, Red Hat Mobile >>> >>> >>> _______________________________________________ >>> feedhenry-dev mailing list >>> feedhenry-dev at redhat.com >>> https://www.redhat.com/mailman/listinfo/feedhenry-dev >>> >>> >> >> >> -- >> David Martin >> Red Hat Mobile >> Twitter: @irldavem >> IRC: @irldavem (feedhenry, mobile-internal) >> > > > > -- > Wojciech Trocki > Software Engineer, Red Hat Mobile > > > _______________________________________________ > feedhenry-dev mailing list > feedhenry-dev at redhat.com > https://www.redhat.com/mailman/listinfo/feedhenry-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From lgriffin at redhat.com Tue Nov 22 09:50:45 2016 From: lgriffin at redhat.com (Leigh Griffin) Date: Tue, 22 Nov 2016 09:50:45 +0000 Subject: [feedhenry-dev] Using mailing list as main source of new functionalities In-Reply-To: References: Message-ID: I think Portfolios fit this perfectly as they can allow you create Initiatives which can have multiple Epics wrapped around them. See this link: https://radiantminds.atlassian.net/wiki/display/GUIDE/Initiatives Check out Portfolios in this video, good 18 minute overview: https://www.youtube.com/watch?v=LexaHkZls3g I'm not happy with the performance of Portfolios on the last version of JIRA, it was grinding to a halt. A large part of that was the volume of tickets we had not just on the RHMAP project but interconnected projects. The performance issue was related to the huge number of release versions that we carry across all projects and as a forward roadmapping tool it was struggling. However I'm happy to try it with DevX which is on a separate board and only drawing from a subset of 2 projects and 3 epics. I just created the Portfolio for you now and performance looks to be decent. I added Wojciech and Dave as people with write access (and John & Jason & I). I don't want to open write access to a lot of people initially because this is *fully integrated *into JIRA and you can push metadata to tickets. So don't sync anything unless you know what you are doing. Watch the video, reach out to me and I can jump on a quick call with you and lets see how it goes. https://issues.jboss.org/secure/PortfolioPlanView.jspa?id=18#backlog Mobile Team have view permissions just to check it out. Leigh. On Mon, Nov 21, 2016 at 10:34 PM, John Frizelle wrote: > JIRA portfolios may also be an option. > > I know Leigh has been looking into this a bit so might be able to shed > some more light on it's potential fit here. > > -- > John Frizelle > Platform Architect, Red Hat Mobile > Consulting Engineering > > mobile: *+353 87 290 1644 * > twitter:* @johnfriz* > skype: *john_frizelle* > mail: *jfrizell at redhat.com * > > > > > On 21 November 2016 at 18:16, Wojciech Trocki wrote: > >> We have already installed agile road plugin that is using some variation >> of gantt chart. >> Example here: https://issues.jboss.org/secure/PortfolioPlan.jspa?id= >> 12#backlog >> >> I think that trello would be good solution for exposing roadmap. >> >> On Mon, Nov 21, 2016 at 6:03 PM, David Martin >> wrote: >> >>> I initially created the trello board as a landing ground and discussion >>> area for features requests and enhancements. >>> A way for users to give their feedback and make sure their voice was >>> heard before an action was taken ('action was taken' meaning something was >>> added to the Jira backlog) >>> The mailing list didn't even come into mind as the place for that to >>> happen. >>> >>> Thanks to Summers for bringing it up with me, I think using trello for >>> this is probably not the best way forward. >>> The mailing list makes so much sense, and I really should have thought >>> of it. >>> >>> Where I think we're lacking, and some other teams have found it useful, >>> is having the team roadmap view visible. >>> All our backlog is ultimately in Jira. >>> The roadmap is hidden away in our Jira backlog in the form of issues & >>> Epics. >>> Is there a way to better visualise the backlog at the 'roadmap' level? >>> Is that something people would find useful? >>> >>> >>> >>> On 21 November 2016 at 16:27, Wojciech Trocki >>> wrote: >>> >>>> Url to our public trello board: https://trello.com/b/ol >>>> SlTR9m/rhmap-developer-experience-feedback >>>> >>>> On Mon, Nov 21, 2016 at 4:18 PM, Wojciech Trocki >>>> wrote: >>>> >>>>> Hi Everyone >>>>> >>>>> We want to keep our backlog consistent and clean from ideas that may >>>>> not be addressed in near future. To provide some collaboration space we >>>>> created new trello board. >>>>> Why duplication over jira? This matches some agile approach: "When >>>>> backlog has some tickets that would not be part of roadmap for the next 6 >>>>> months then they should be removed from backlog :] ". >>>>> >>>>> I would like to ask all interesting parties about opinion on using >>>>> Trello vs Mailing List >>>>> >>>>> Why we created trello and decided to not use mailing list (IMHO) >>>>> >>>>> *Positive parts:* >>>>> >>>>> - Simplicity >>>>> - Defaulting to one source (email) >>>>> - Easy to contribute - just sent email. >>>>> >>>>> *Negative parts:* >>>>> >>>>> - No overview and visibility for our roadmap - just bunch of emails. >>>>> - No way to retrieve emails before signed to group >>>>> - No way to stage and label issues for customers and better visibility >>>>> - Mixed content - feature request can be mixed with other non related >>>>> email threads like this one. >>>>> - Interface from the last century: >>>>> http://www.redhat.com/archives/feedhenry-dev/2016-November/m >>>>> sg00000.html >>>>> >>>>> >>>>> Regards >>>>> >>>>> -- >>>>> Wojciech Trocki >>>>> Software Engineer, Red Hat Mobile >>>>> >>>>> >>>> >>>> >>>> -- >>>> Wojciech Trocki >>>> Software Engineer, Red Hat Mobile >>>> >>>> >>>> _______________________________________________ >>>> feedhenry-dev mailing list >>>> feedhenry-dev at redhat.com >>>> https://www.redhat.com/mailman/listinfo/feedhenry-dev >>>> >>>> >>> >>> >>> -- >>> David Martin >>> Red Hat Mobile >>> Twitter: @irldavem >>> IRC: @irldavem (feedhenry, mobile-internal) >>> >> >> >> >> -- >> Wojciech Trocki >> Software Engineer, Red Hat Mobile >> >> >> _______________________________________________ >> feedhenry-dev mailing list >> feedhenry-dev at redhat.com >> https://www.redhat.com/mailman/listinfo/feedhenry-dev >> >> > > _______________________________________________ > feedhenry-dev mailing list > feedhenry-dev at redhat.com > https://www.redhat.com/mailman/listinfo/feedhenry-dev > > -- Leigh Griffin Engineering Manager, Red Hat, Waterford, Ireland -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From davmarti at redhat.com Tue Nov 22 14:55:03 2016 From: davmarti at redhat.com (David Martin) Date: Tue, 22 Nov 2016 14:55:03 +0000 Subject: [feedhenry-dev] Using 'sort' with fh.db API Message-ID: Picked this up on slack, but thought others might find it useful (Thanks Evan, Philip & Chad) An example of how to sort fh.db results: var options = { "act": "list", "type": collectionName, "sort" : {lastName: 1} // sort JSON results by lastName (ascending). Use -1 for descending }; Probably something worth adding to the docs, so i added https://issues.jboss.org/browse/FH-2894 Evan mentioned that "this might only work if you've upgraded the db since it appears to follow the mongodb syntax/format" Has anyone tried it without an 'upgraded' db? -- David Martin Red Hat Mobile Twitter: @irldavem IRC: @irldavem (feedhenry, mobile-internal) -------------- next part -------------- An HTML attachment was scrubbed... URL: From wtrocki at redhat.com Tue Nov 22 15:10:34 2016 From: wtrocki at redhat.com (Wojciech Trocki) Date: Tue, 22 Nov 2016 15:10:34 +0000 Subject: [feedhenry-dev] Using 'sort' with fh.db API In-Reply-To: References: Message-ID: Thanks for posting that. Sorting works fine in DataBrowser without database migration. Additionally we would need to describe limitations of the query api (impossible to do logical operations etc.) Adding this info to the ticket. On Tue, Nov 22, 2016 at 2:55 PM, David Martin wrote: > Picked this up on slack, but thought others might find it useful (Thanks > Evan, Philip & Chad) > > An example of how to sort fh.db results: > > > var options = { > "act": "list", > "type": collectionName, > "sort" : {lastName: 1} // sort JSON results by lastName > (ascending). Use -1 for descending > }; > > > Probably something worth adding to the docs, so i added > https://issues.jboss.org/browse/FH-2894 > > Evan mentioned that "this might only work if you've upgraded the db since > it appears to follow the mongodb syntax/format" > Has anyone tried it without an 'upgraded' db? > > -- > David Martin > Red Hat Mobile > Twitter: @irldavem > IRC: @irldavem (feedhenry, mobile-internal) > > _______________________________________________ > feedhenry-dev mailing list > feedhenry-dev at redhat.com > https://www.redhat.com/mailman/listinfo/feedhenry-dev > > -- Wojciech Trocki Software Engineer, Red Hat Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From mmurphy at redhat.com Tue Nov 22 15:53:06 2016 From: mmurphy at redhat.com (Martin Murphy) Date: Tue, 22 Nov 2016 15:53:06 +0000 Subject: [feedhenry-dev] How are PRs to open source repos reviewed? In-Reply-To: References: Message-ID: Thanks Wojtek, There are probably a few changes that I would suggest, I'll put them in a PR. Since there's no-one monitoring for PRs, an email to this list might make sense when looking for a review. Cheers, M. On 18 November 2016 at 16:35, Wojciech Trocki wrote: > We do not have any guide at the moment but.. > I'm trying to address this problem with this PR in help repo: > > https://github.com/fheng/help/pull/261 > > Feel free to add some comments and your suggestions. > > Regards > > Wojtek T. > > On Thu, Nov 17, 2016 at 8:11 PM, Daniel Passos wrote: > >> There is an option on Github to receive an email for every new PR. I >> think you can configure it for all repo or only for the repos you want. >> >> On Thu, Nov 17, 2016 at 6:05 PM, Martin Murphy >> wrote: >> >>> Thanks Passos. >>> >>> That would mean that someone on the team would have to be looking out >>> for PRs to the open source repos. >>> Do you know if we have that in place for all our open source repos? >>> >>> Cheers, >>> M. >>> >>> >>> On 17 November 2016 at 19:44, Daniel Passos wrote: >>> > What we have been doing on AeroGear is: >>> > >>> > 1) If the PR came from the community? >>> > >>> > * Check is there is a Jira for this one, if not create one and link >>> the PR >>> > * Ping someone with more knowledgement about the project to review >>> this one >>> > >>> > Example: https://github.com/aerogear/aerogear-ios-http/pull/73 >>> > https://github.com/aerogear/a >>> erogear-ios-oauth2/pull/61 >>> > >>> > >>> > 2) If the PR came from the team >>> > >>> > * Add the Jira about the PR in the PR >>> > * Ping someone with more knowledge about the project to review this one >>> > >>> > Example: https://github.com/aerogear/aerogear-android-auth/pull/37 >>> > >>> > Bonus point to comment using reaction gifts[1] >>> > >>> > [1] http://www.reactiongifs.com/ >>> > >>> > >>> > On Thu, Nov 17, 2016 at 5:23 PM, Martin Murphy >>> wrote: >>> >> >>> >> How are PRs to open source repos reviewed? >>> >> e.g. if someone submits a PR for fh-fhc, is that enough to get a >>> review? >>> >> Or do they have to ping someone/someplace? >>> >> >>> >> Cheers, >>> >> M. >>> >> >>> >> _______________________________________________ >>> >> feedhenry-dev mailing list >>> >> feedhenry-dev at redhat.com >>> >> https://www.redhat.com/mailman/listinfo/feedhenry-dev >>> > >>> > >>> > >>> > >>> > -- >>> > -- Passos >>> >> >> >> >> -- >> -- Passos >> >> _______________________________________________ >> feedhenry-dev mailing list >> feedhenry-dev at redhat.com >> https://www.redhat.com/mailman/listinfo/feedhenry-dev >> >> > > > -- > Wojciech Trocki > Software Engineer, Red Hat Mobile > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From mmurphy at redhat.com Tue Nov 22 17:27:55 2016 From: mmurphy at redhat.com (Martin Murphy) Date: Tue, 22 Nov 2016 17:27:55 +0000 Subject: [feedhenry-dev] Review request for fh-fhc PR Message-ID: Hi folks, is anyone able to review a PR to fh-fhc? [1] It fixes HHTP Proxy server support - FH-2856 [2] Cheers, M. [1] https://github.com/feedhenry/fh-fhc/pull/268 [2] https://issues.jboss.org/browse/FH-2856 From wtrocki at redhat.com Tue Nov 22 18:30:18 2016 From: wtrocki at redhat.com (Wojciech Trocki) Date: Tue, 22 Nov 2016 18:30:18 +0000 Subject: [feedhenry-dev] Review request for fh-fhc PR In-Reply-To: References: Message-ID: Thanks for contribution. It's reviewed now. On Tue, Nov 22, 2016 at 5:27 PM, Martin Murphy wrote: > Hi folks, > is anyone able to review a PR to fh-fhc? [1] > It fixes HHTP Proxy server support - FH-2856 [2] > > Cheers, > M. > > > [1] https://github.com/feedhenry/fh-fhc/pull/268 > [2] https://issues.jboss.org/browse/FH-2856 > > _______________________________________________ > feedhenry-dev mailing list > feedhenry-dev at redhat.com > https://www.redhat.com/mailman/listinfo/feedhenry-dev > -- Wojciech Trocki Software Engineer, Red Hat Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From wtrocki at redhat.com Tue Nov 22 21:11:55 2016 From: wtrocki at redhat.com (Wojciech Trocki) Date: Tue, 22 Nov 2016 21:11:55 +0000 Subject: [feedhenry-dev] Using mailing list as main source of new functionalities In-Reply-To: References: Message-ID: @John/@Leigh - I checked video and plugin documentation. Portfolio (agile roadmap plugin) seems to be really good solution for project planning. We trying now to reorganize our backlog into more smaller and detailed epics and then we would need to evaluate this option. I think that it would fit to the main purpose and we can make this public so customers can see when interesting stuff would be completed. Thanks for inspiration! On Tue, Nov 22, 2016 at 9:50 AM, Leigh Griffin wrote: > I think Portfolios fit this perfectly as they can allow you create > Initiatives which can have multiple Epics wrapped around them. See this > link: > https://radiantminds.atlassian.net/wiki/display/GUIDE/Initiatives > > Check out Portfolios in this video, good 18 minute overview: > https://www.youtube.com/watch?v=LexaHkZls3g > > I'm not happy with the performance of Portfolios on the last version of > JIRA, it was grinding to a halt. A large part of that was the volume of > tickets we had not just on the RHMAP project but interconnected projects. > The performance issue was related to the huge number of release versions > that we carry across all projects and as a forward roadmapping tool it was > struggling. > > However I'm happy to try it with DevX which is on a separate board and > only drawing from a subset of 2 projects and 3 epics. I just created the > Portfolio for you now and performance looks to be decent. I added Wojciech > and Dave as people with write access (and John & Jason & I). I don't want > to open write access to a lot of people initially because this is *fully > integrated *into JIRA and you can push metadata to tickets. So don't sync > anything unless you know what you are doing. Watch the video, reach out to > me and I can jump on a quick call with you and lets see how it goes. > > https://issues.jboss.org/secure/PortfolioPlanView.jspa?id=18#backlog > > Mobile Team have view permissions just to check it out. > > Leigh. > > On Mon, Nov 21, 2016 at 10:34 PM, John Frizelle > wrote: > >> JIRA portfolios may also be an option. >> >> I know Leigh has been looking into this a bit so might be able to shed >> some more light on it's potential fit here. >> >> -- >> John Frizelle >> Platform Architect, Red Hat Mobile >> Consulting Engineering >> >> mobile: *+353 87 290 1644 * >> twitter:* @johnfriz* >> skype: *john_frizelle* >> mail: *jfrizell at redhat.com * >> >> >> >> >> On 21 November 2016 at 18:16, Wojciech Trocki wrote: >> >>> We have already installed agile road plugin that is using some variation >>> of gantt chart. >>> Example here: https://issues.jboss.org/secure/PortfolioPlan.jspa?id= >>> 12#backlog >>> >>> I think that trello would be good solution for exposing roadmap. >>> >>> On Mon, Nov 21, 2016 at 6:03 PM, David Martin >>> wrote: >>> >>>> I initially created the trello board as a landing ground and discussion >>>> area for features requests and enhancements. >>>> A way for users to give their feedback and make sure their voice was >>>> heard before an action was taken ('action was taken' meaning something was >>>> added to the Jira backlog) >>>> The mailing list didn't even come into mind as the place for that to >>>> happen. >>>> >>>> Thanks to Summers for bringing it up with me, I think using trello for >>>> this is probably not the best way forward. >>>> The mailing list makes so much sense, and I really should have thought >>>> of it. >>>> >>>> Where I think we're lacking, and some other teams have found it useful, >>>> is having the team roadmap view visible. >>>> All our backlog is ultimately in Jira. >>>> The roadmap is hidden away in our Jira backlog in the form of issues & >>>> Epics. >>>> Is there a way to better visualise the backlog at the 'roadmap' level? >>>> Is that something people would find useful? >>>> >>>> >>>> >>>> On 21 November 2016 at 16:27, Wojciech Trocki >>>> wrote: >>>> >>>>> Url to our public trello board: https://trello.com/b/ol >>>>> SlTR9m/rhmap-developer-experience-feedback >>>>> >>>>> On Mon, Nov 21, 2016 at 4:18 PM, Wojciech Trocki >>>>> wrote: >>>>> >>>>>> Hi Everyone >>>>>> >>>>>> We want to keep our backlog consistent and clean from ideas that may >>>>>> not be addressed in near future. To provide some collaboration space we >>>>>> created new trello board. >>>>>> Why duplication over jira? This matches some agile approach: "When >>>>>> backlog has some tickets that would not be part of roadmap for the next 6 >>>>>> months then they should be removed from backlog :] ". >>>>>> >>>>>> I would like to ask all interesting parties about opinion on using >>>>>> Trello vs Mailing List >>>>>> >>>>>> Why we created trello and decided to not use mailing list (IMHO) >>>>>> >>>>>> *Positive parts:* >>>>>> >>>>>> - Simplicity >>>>>> - Defaulting to one source (email) >>>>>> - Easy to contribute - just sent email. >>>>>> >>>>>> *Negative parts:* >>>>>> >>>>>> - No overview and visibility for our roadmap - just bunch of emails. >>>>>> - No way to retrieve emails before signed to group >>>>>> - No way to stage and label issues for customers and better >>>>>> visibility >>>>>> - Mixed content - feature request can be mixed with other non related >>>>>> email threads like this one. >>>>>> - Interface from the last century: >>>>>> http://www.redhat.com/archives/feedhenry-dev/2016-November/m >>>>>> sg00000.html >>>>>> >>>>>> >>>>>> Regards >>>>>> >>>>>> -- >>>>>> Wojciech Trocki >>>>>> Software Engineer, Red Hat Mobile >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Wojciech Trocki >>>>> Software Engineer, Red Hat Mobile >>>>> >>>>> >>>>> _______________________________________________ >>>>> feedhenry-dev mailing list >>>>> feedhenry-dev at redhat.com >>>>> https://www.redhat.com/mailman/listinfo/feedhenry-dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> David Martin >>>> Red Hat Mobile >>>> Twitter: @irldavem >>>> IRC: @irldavem (feedhenry, mobile-internal) >>>> >>> >>> >>> >>> -- >>> Wojciech Trocki >>> Software Engineer, Red Hat Mobile >>> >>> >>> _______________________________________________ >>> feedhenry-dev mailing list >>> feedhenry-dev at redhat.com >>> https://www.redhat.com/mailman/listinfo/feedhenry-dev >>> >>> >> >> _______________________________________________ >> feedhenry-dev mailing list >> feedhenry-dev at redhat.com >> https://www.redhat.com/mailman/listinfo/feedhenry-dev >> >> > > > -- > Leigh Griffin > Engineering Manager, > Red Hat, > Waterford, > Ireland > -- Wojciech Trocki Software Engineer, Red Hat Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From lgriffin at redhat.com Wed Nov 23 09:49:48 2016 From: lgriffin at redhat.com (Leigh Griffin) Date: Wed, 23 Nov 2016 09:49:48 +0000 Subject: [feedhenry-dev] Using mailing list as main source of new functionalities In-Reply-To: References: Message-ID: Happy to jump in on a call to share what I know about it, I think it's going to be very powerful for teams, stakeholders and public information sharing. I'm hoping that it works for DevX which has a smaller footprint than our huge RHMAP project and the complexity of the boards there. It will help me make the necessary changes to get this working for all teams. Leigh On Tue, Nov 22, 2016 at 9:11 PM, Wojciech Trocki wrote: > @John/@Leigh - I checked video and plugin documentation. > Portfolio (agile roadmap plugin) seems to be really good solution for > project planning. We trying now to reorganize our backlog into more smaller > and detailed epics and then we would need to evaluate this option. I think > that it would fit to the main purpose and we can make this public so > customers can see when interesting stuff would be completed. Thanks for > inspiration! > > > On Tue, Nov 22, 2016 at 9:50 AM, Leigh Griffin > wrote: > >> I think Portfolios fit this perfectly as they can allow you create >> Initiatives which can have multiple Epics wrapped around them. See this >> link: >> https://radiantminds.atlassian.net/wiki/display/GUIDE/Initiatives >> >> Check out Portfolios in this video, good 18 minute overview: >> https://www.youtube.com/watch?v=LexaHkZls3g >> >> I'm not happy with the performance of Portfolios on the last version of >> JIRA, it was grinding to a halt. A large part of that was the volume of >> tickets we had not just on the RHMAP project but interconnected projects. >> The performance issue was related to the huge number of release versions >> that we carry across all projects and as a forward roadmapping tool it was >> struggling. >> >> However I'm happy to try it with DevX which is on a separate board and >> only drawing from a subset of 2 projects and 3 epics. I just created the >> Portfolio for you now and performance looks to be decent. I added Wojciech >> and Dave as people with write access (and John & Jason & I). I don't want >> to open write access to a lot of people initially because this is *fully >> integrated *into JIRA and you can push metadata to tickets. So don't >> sync anything unless you know what you are doing. Watch the video, reach >> out to me and I can jump on a quick call with you and lets see how it goes. >> >> https://issues.jboss.org/secure/PortfolioPlanView.jspa?id=18#backlog >> >> Mobile Team have view permissions just to check it out. >> >> Leigh. >> >> On Mon, Nov 21, 2016 at 10:34 PM, John Frizelle >> wrote: >> >>> JIRA portfolios may also be an option. >>> >>> I know Leigh has been looking into this a bit so might be able to shed >>> some more light on it's potential fit here. >>> >>> -- >>> John Frizelle >>> Platform Architect, Red Hat Mobile >>> Consulting Engineering >>> >>> mobile: *+353 87 290 1644 * >>> twitter:* @johnfriz* >>> skype: *john_frizelle* >>> mail: *jfrizell at redhat.com * >>> >>> >>> >>> >>> On 21 November 2016 at 18:16, Wojciech Trocki >>> wrote: >>> >>>> We have already installed agile road plugin that is using some >>>> variation of gantt chart. >>>> Example here: https://issues.jboss.org/secure/PortfolioPlan.jspa?id= >>>> 12#backlog >>>> >>>> I think that trello would be good solution for exposing roadmap. >>>> >>>> On Mon, Nov 21, 2016 at 6:03 PM, David Martin >>>> wrote: >>>> >>>>> I initially created the trello board as a landing ground and >>>>> discussion area for features requests and enhancements. >>>>> A way for users to give their feedback and make sure their voice was >>>>> heard before an action was taken ('action was taken' meaning something was >>>>> added to the Jira backlog) >>>>> The mailing list didn't even come into mind as the place for that to >>>>> happen. >>>>> >>>>> Thanks to Summers for bringing it up with me, I think using trello for >>>>> this is probably not the best way forward. >>>>> The mailing list makes so much sense, and I really should have thought >>>>> of it. >>>>> >>>>> Where I think we're lacking, and some other teams have found it >>>>> useful, is having the team roadmap view visible. >>>>> All our backlog is ultimately in Jira. >>>>> The roadmap is hidden away in our Jira backlog in the form of issues & >>>>> Epics. >>>>> Is there a way to better visualise the backlog at the 'roadmap' level? >>>>> Is that something people would find useful? >>>>> >>>>> >>>>> >>>>> On 21 November 2016 at 16:27, Wojciech Trocki >>>>> wrote: >>>>> >>>>>> Url to our public trello board: https://trello.com/b/ol >>>>>> SlTR9m/rhmap-developer-experience-feedback >>>>>> >>>>>> On Mon, Nov 21, 2016 at 4:18 PM, Wojciech Trocki >>>>>> wrote: >>>>>> >>>>>>> Hi Everyone >>>>>>> >>>>>>> We want to keep our backlog consistent and clean from ideas that may >>>>>>> not be addressed in near future. To provide some collaboration space we >>>>>>> created new trello board. >>>>>>> Why duplication over jira? This matches some agile approach: "When >>>>>>> backlog has some tickets that would not be part of roadmap for the next 6 >>>>>>> months then they should be removed from backlog :] ". >>>>>>> >>>>>>> I would like to ask all interesting parties about opinion on using >>>>>>> Trello vs Mailing List >>>>>>> >>>>>>> Why we created trello and decided to not use mailing list (IMHO) >>>>>>> >>>>>>> *Positive parts:* >>>>>>> >>>>>>> - Simplicity >>>>>>> - Defaulting to one source (email) >>>>>>> - Easy to contribute - just sent email. >>>>>>> >>>>>>> *Negative parts:* >>>>>>> >>>>>>> - No overview and visibility for our roadmap - just bunch of emails. >>>>>>> - No way to retrieve emails before signed to group >>>>>>> - No way to stage and label issues for customers and better >>>>>>> visibility >>>>>>> - Mixed content - feature request can be mixed with other non >>>>>>> related email threads like this one. >>>>>>> - Interface from the last century: >>>>>>> http://www.redhat.com/archives/feedhenry-dev/2016-November/m >>>>>>> sg00000.html >>>>>>> >>>>>>> >>>>>>> Regards >>>>>>> >>>>>>> -- >>>>>>> Wojciech Trocki >>>>>>> Software Engineer, Red Hat Mobile >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Wojciech Trocki >>>>>> Software Engineer, Red Hat Mobile >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> feedhenry-dev mailing list >>>>>> feedhenry-dev at redhat.com >>>>>> https://www.redhat.com/mailman/listinfo/feedhenry-dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> David Martin >>>>> Red Hat Mobile >>>>> Twitter: @irldavem >>>>> IRC: @irldavem (feedhenry, mobile-internal) >>>>> >>>> >>>> >>>> >>>> -- >>>> Wojciech Trocki >>>> Software Engineer, Red Hat Mobile >>>> >>>> >>>> _______________________________________________ >>>> feedhenry-dev mailing list >>>> feedhenry-dev at redhat.com >>>> https://www.redhat.com/mailman/listinfo/feedhenry-dev >>>> >>>> >>> >>> _______________________________________________ >>> feedhenry-dev mailing list >>> feedhenry-dev at redhat.com >>> https://www.redhat.com/mailman/listinfo/feedhenry-dev >>> >>> >> >> >> -- >> Leigh Griffin >> Engineering Manager, >> Red Hat, >> Waterford, >> Ireland >> > > > > -- > Wojciech Trocki > Software Engineer, Red Hat Mobile > > -- Leigh Griffin Engineering Manager, Red Hat, Waterford, Ireland -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From mmurphy at redhat.com Wed Nov 23 13:50:37 2016 From: mmurphy at redhat.com (Martin Murphy) Date: Wed, 23 Nov 2016 13:50:37 +0000 Subject: [feedhenry-dev] Review request for fh-fhc PR In-Reply-To: References: Message-ID: Thanks Wojtek, In the "Reviewing changes" section of the help repo, it says: > Note: if you have write access to the repository, do not directly merge > pull requests. Let another team member review your pull request and approve > it. Can you merge it also? Cheers, M. On 22 November 2016 at 18:30, Wojciech Trocki wrote: > Thanks for contribution. It's reviewed now. > > On Tue, Nov 22, 2016 at 5:27 PM, Martin Murphy wrote: > >> Hi folks, >> is anyone able to review a PR to fh-fhc? [1] >> It fixes HHTP Proxy server support - FH-2856 [2] >> >> Cheers, >> M. >> >> >> [1] https://github.com/feedhenry/fh-fhc/pull/268 >> [2] https://issues.jboss.org/browse/FH-2856 >> >> _______________________________________________ >> feedhenry-dev mailing list >> feedhenry-dev at redhat.com >> https://www.redhat.com/mailman/listinfo/feedhenry-dev >> > > > > -- > Wojciech Trocki > Software Engineer, Red Hat Mobile > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From wtrocki at redhat.com Wed Nov 23 18:28:16 2016 From: wtrocki at redhat.com (Wojciech Trocki) Date: Wed, 23 Nov 2016 18:28:16 +0000 Subject: [feedhenry-dev] Using mailing list as main source of new functionalities In-Reply-To: References: Message-ID: Big thanks for Leigh for huge inspiration. Tool looks awesome and can help us to reorganize epics: https://issues.jboss.org/secure/PortfolioPlanView.jspa?id=18#reporting What I particularly like is reports section where we can see how we following our main roadmap :] Regards On Wed, Nov 23, 2016 at 9:49 AM, Leigh Griffin wrote: > Happy to jump in on a call to share what I know about it, I think it's > going to be very powerful for teams, stakeholders and public information > sharing. I'm hoping that it works for DevX which has a smaller footprint > than our huge RHMAP project and the complexity of the boards there. It will > help me make the necessary changes to get this working for all teams. > > Leigh > > On Tue, Nov 22, 2016 at 9:11 PM, Wojciech Trocki > wrote: > >> @John/@Leigh - I checked video and plugin documentation. >> Portfolio (agile roadmap plugin) seems to be really good solution for >> project planning. We trying now to reorganize our backlog into more smaller >> and detailed epics and then we would need to evaluate this option. I think >> that it would fit to the main purpose and we can make this public so >> customers can see when interesting stuff would be completed. Thanks for >> inspiration! >> >> >> On Tue, Nov 22, 2016 at 9:50 AM, Leigh Griffin >> wrote: >> >>> I think Portfolios fit this perfectly as they can allow you create >>> Initiatives which can have multiple Epics wrapped around them. See this >>> link: >>> https://radiantminds.atlassian.net/wiki/display/GUIDE/Initiatives >>> >>> Check out Portfolios in this video, good 18 minute overview: >>> https://www.youtube.com/watch?v=LexaHkZls3g >>> >>> I'm not happy with the performance of Portfolios on the last version of >>> JIRA, it was grinding to a halt. A large part of that was the volume of >>> tickets we had not just on the RHMAP project but interconnected projects. >>> The performance issue was related to the huge number of release versions >>> that we carry across all projects and as a forward roadmapping tool it was >>> struggling. >>> >>> However I'm happy to try it with DevX which is on a separate board and >>> only drawing from a subset of 2 projects and 3 epics. I just created the >>> Portfolio for you now and performance looks to be decent. I added Wojciech >>> and Dave as people with write access (and John & Jason & I). I don't want >>> to open write access to a lot of people initially because this is *fully >>> integrated *into JIRA and you can push metadata to tickets. So don't >>> sync anything unless you know what you are doing. Watch the video, reach >>> out to me and I can jump on a quick call with you and lets see how it goes. >>> >>> https://issues.jboss.org/secure/PortfolioPlanView.jspa?id=18#backlog >>> >>> Mobile Team have view permissions just to check it out. >>> >>> Leigh. >>> >>> On Mon, Nov 21, 2016 at 10:34 PM, John Frizelle >>> wrote: >>> >>>> JIRA portfolios may also be an option. >>>> >>>> I know Leigh has been looking into this a bit so might be able to shed >>>> some more light on it's potential fit here. >>>> >>>> -- >>>> John Frizelle >>>> Platform Architect, Red Hat Mobile >>>> Consulting Engineering >>>> >>>> mobile: *+353 87 290 1644 * >>>> twitter:* @johnfriz* >>>> skype: *john_frizelle* >>>> mail: *jfrizell at redhat.com * >>>> >>>> >>>> >>>> >>>> On 21 November 2016 at 18:16, Wojciech Trocki >>>> wrote: >>>> >>>>> We have already installed agile road plugin that is using some >>>>> variation of gantt chart. >>>>> Example here: https://issues.jboss.org/secure/PortfolioPlan.jspa?id= >>>>> 12#backlog >>>>> >>>>> I think that trello would be good solution for exposing roadmap. >>>>> >>>>> On Mon, Nov 21, 2016 at 6:03 PM, David Martin >>>>> wrote: >>>>> >>>>>> I initially created the trello board as a landing ground and >>>>>> discussion area for features requests and enhancements. >>>>>> A way for users to give their feedback and make sure their voice was >>>>>> heard before an action was taken ('action was taken' meaning something was >>>>>> added to the Jira backlog) >>>>>> The mailing list didn't even come into mind as the place for that to >>>>>> happen. >>>>>> >>>>>> Thanks to Summers for bringing it up with me, I think using trello >>>>>> for this is probably not the best way forward. >>>>>> The mailing list makes so much sense, and I really should have >>>>>> thought of it. >>>>>> >>>>>> Where I think we're lacking, and some other teams have found it >>>>>> useful, is having the team roadmap view visible. >>>>>> All our backlog is ultimately in Jira. >>>>>> The roadmap is hidden away in our Jira backlog in the form of issues >>>>>> & Epics. >>>>>> Is there a way to better visualise the backlog at the 'roadmap' level? >>>>>> Is that something people would find useful? >>>>>> >>>>>> >>>>>> >>>>>> On 21 November 2016 at 16:27, Wojciech Trocki >>>>>> wrote: >>>>>> >>>>>>> Url to our public trello board: https://trello.com/b/ol >>>>>>> SlTR9m/rhmap-developer-experience-feedback >>>>>>> >>>>>>> On Mon, Nov 21, 2016 at 4:18 PM, Wojciech Trocki >>>>>> > wrote: >>>>>>> >>>>>>>> Hi Everyone >>>>>>>> >>>>>>>> We want to keep our backlog consistent and clean from ideas that >>>>>>>> may not be addressed in near future. To provide some collaboration space we >>>>>>>> created new trello board. >>>>>>>> Why duplication over jira? This matches some agile approach: "When >>>>>>>> backlog has some tickets that would not be part of roadmap for the next 6 >>>>>>>> months then they should be removed from backlog :] ". >>>>>>>> >>>>>>>> I would like to ask all interesting parties about opinion on using >>>>>>>> Trello vs Mailing List >>>>>>>> >>>>>>>> Why we created trello and decided to not use mailing list (IMHO) >>>>>>>> >>>>>>>> *Positive parts:* >>>>>>>> >>>>>>>> - Simplicity >>>>>>>> - Defaulting to one source (email) >>>>>>>> - Easy to contribute - just sent email. >>>>>>>> >>>>>>>> *Negative parts:* >>>>>>>> >>>>>>>> - No overview and visibility for our roadmap - just bunch of emails. >>>>>>>> - No way to retrieve emails before signed to group >>>>>>>> - No way to stage and label issues for customers and better >>>>>>>> visibility >>>>>>>> - Mixed content - feature request can be mixed with other non >>>>>>>> related email threads like this one. >>>>>>>> - Interface from the last century: >>>>>>>> http://www.redhat.com/archives/feedhenry-dev/2016-November/m >>>>>>>> sg00000.html >>>>>>>> >>>>>>>> >>>>>>>> Regards >>>>>>>> >>>>>>>> -- >>>>>>>> Wojciech Trocki >>>>>>>> Software Engineer, Red Hat Mobile >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Wojciech Trocki >>>>>>> Software Engineer, Red Hat Mobile >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> feedhenry-dev mailing list >>>>>>> feedhenry-dev at redhat.com >>>>>>> https://www.redhat.com/mailman/listinfo/feedhenry-dev >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> David Martin >>>>>> Red Hat Mobile >>>>>> Twitter: @irldavem >>>>>> IRC: @irldavem (feedhenry, mobile-internal) >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Wojciech Trocki >>>>> Software Engineer, Red Hat Mobile >>>>> >>>>> >>>>> _______________________________________________ >>>>> feedhenry-dev mailing list >>>>> feedhenry-dev at redhat.com >>>>> https://www.redhat.com/mailman/listinfo/feedhenry-dev >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> feedhenry-dev mailing list >>>> feedhenry-dev at redhat.com >>>> https://www.redhat.com/mailman/listinfo/feedhenry-dev >>>> >>>> >>> >>> >>> -- >>> Leigh Griffin >>> Engineering Manager, >>> Red Hat, >>> Waterford, >>> Ireland >>> >> >> >> >> -- >> Wojciech Trocki >> Software Engineer, Red Hat Mobile >> >> > > > -- > Leigh Griffin > Engineering Manager, > Red Hat, > Waterford, > Ireland > -- Wojciech Trocki Software Engineer, Red Hat Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From mmurphy at redhat.com Thu Nov 24 12:42:41 2016 From: mmurphy at redhat.com (Martin Murphy) Date: Thu, 24 Nov 2016 12:42:41 +0000 Subject: [feedhenry-dev] Review request for fh-fhc PR In-Reply-To: References: Message-ID: Hi folks, The PR has been reviewed, who can merge it, before it needs to be rebased again? Cheers, M. On 23 November 2016 at 13:50, Martin Murphy wrote: > Thanks Wojtek, > In the "Reviewing changes" section of the help repo, it says: > >> Note: if you have write access to the repository, do not directly merge >> pull requests. Let another team member review your pull request and approve >> it. > > > Can you merge it also? > > Cheers, > M. > > > On 22 November 2016 at 18:30, Wojciech Trocki wrote: > >> Thanks for contribution. It's reviewed now. >> >> On Tue, Nov 22, 2016 at 5:27 PM, Martin Murphy >> wrote: >> >>> Hi folks, >>> is anyone able to review a PR to fh-fhc? [1] >>> It fixes HHTP Proxy server support - FH-2856 [2] >>> >>> Cheers, >>> M. >>> >>> >>> [1] https://github.com/feedhenry/fh-fhc/pull/268 >>> [2] https://issues.jboss.org/browse/FH-2856 >>> >>> _______________________________________________ >>> feedhenry-dev mailing list >>> feedhenry-dev at redhat.com >>> https://www.redhat.com/mailman/listinfo/feedhenry-dev >>> >> >> >> >> -- >> Wojciech Trocki >> Software Engineer, Red Hat Mobile >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From wtrocki at redhat.com Thu Nov 24 12:50:40 2016 From: wtrocki at redhat.com (Wojciech Trocki) Date: Thu, 24 Nov 2016 12:50:40 +0000 Subject: [feedhenry-dev] Review request for fh-fhc PR In-Reply-To: References: Message-ID: Going to check and merge this now. On Thu, Nov 24, 2016 at 12:42 PM, Martin Murphy wrote: > Hi folks, > The PR has been reviewed, who can merge it, before it needs to be rebased > again? > > Cheers, > M. > > On 23 November 2016 at 13:50, Martin Murphy wrote: > >> Thanks Wojtek, >> In the "Reviewing changes" section of the help repo, it says: >> >>> Note: if you have write access to the repository, do not directly merge >>> pull requests. Let another team member review your pull request and approve >>> it. >> >> >> Can you merge it also? >> >> Cheers, >> M. >> >> >> On 22 November 2016 at 18:30, Wojciech Trocki wrote: >> >>> Thanks for contribution. It's reviewed now. >>> >>> On Tue, Nov 22, 2016 at 5:27 PM, Martin Murphy >>> wrote: >>> >>>> Hi folks, >>>> is anyone able to review a PR to fh-fhc? [1] >>>> It fixes HHTP Proxy server support - FH-2856 [2] >>>> >>>> Cheers, >>>> M. >>>> >>>> >>>> [1] https://github.com/feedhenry/fh-fhc/pull/268 >>>> [2] https://issues.jboss.org/browse/FH-2856 >>>> >>>> _______________________________________________ >>>> feedhenry-dev mailing list >>>> feedhenry-dev at redhat.com >>>> https://www.redhat.com/mailman/listinfo/feedhenry-dev >>>> >>> >>> >>> >>> -- >>> Wojciech Trocki >>> Software Engineer, Red Hat Mobile >>> >>> >> > -- Wojciech Trocki Software Engineer, Red Hat Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From pdarrow at redhat.com Thu Nov 24 20:35:25 2016 From: pdarrow at redhat.com (Peter Darrow) Date: Thu, 24 Nov 2016 16:35:25 -0400 Subject: [feedhenry-dev] Improving feedhenry.org Message-ID: Hi all, When I visit http://feedhenry.org/, it's hard for me to tell what the FeedHenry project is or what it can do for me. I'm currently shown a large ad for Raincatcher, and mentions of Mobile SDKs and templates, but there's no high level outline of what FeedHenry does. Below the fold in the "Develop, Deploy, Manage and Monitor" section there are a few sentences that sort of give a summary, but I think we could do a little better. Correct me if I'm wrong, but isn't Raincatcher an application built with FeedHenry and not the platform itself? What are your thoughts on creating a more focused landing page with clearly outlined features? One project I've contributed to does a great job of this: http://locust.io/. Are we waiting until the entire platform is open-sourced before highlighting it like this? Cheers, Peter -------------- next part -------------- An HTML attachment was scrubbed... URL: From jfrizell at redhat.com Thu Nov 24 20:47:02 2016 From: jfrizell at redhat.com (John Frizelle) Date: Thu, 24 Nov 2016 20:47:02 +0000 Subject: [feedhenry-dev] Improving feedhenry.org In-Reply-To: References: Message-ID: Hi Peter, I'd love to see some additions and improvements to feedhenry.org - especially with the open sourcing of the Build Farm and MBaaS on the way. Up to now, we had been trying to restrict what we talked about to be just the current OSS components, but perhaps we should give a broader overview of the whole solution and then detail which parts are already OSS (lit up links) and which parts are yet to come (greyed out with no links) -- just an example of how we might achieve it. Please feel free to circulate any ideas / suggestions / concepts or even Github branches (the code is hosted here: https://github.com/feedhenry/feedhenry.github.com) Cheers, John. -- John Frizelle Platform Architect, Red Hat Mobile Consulting Engineering mobile: *+353 87 290 1644 * twitter:* @johnfriz* skype: *john_frizelle* mail: *jfrizell at redhat.com * On 24 November 2016 at 20:35, Peter Darrow wrote: > Hi all, > > When I visit http://feedhenry.org/, it's hard for me to tell what the > FeedHenry project is or what it can do for me. I'm currently shown a large > ad for Raincatcher, and mentions of Mobile SDKs and templates, but there's > no high level outline of what FeedHenry does. Below the fold in the > "Develop, Deploy, Manage and Monitor" section there are a few sentences > that sort of give a summary, but I think we could do a little better. > > Correct me if I'm wrong, but isn't Raincatcher an application built with > FeedHenry and not the platform itself? What are your thoughts on creating a > more focused landing page with clearly outlined features? One project I've > contributed to does a great job of this: http://locust.io/. Are we > waiting until the entire platform is open-sourced before highlighting it > like this? > > Cheers, > Peter > > _______________________________________________ > feedhenry-dev mailing list > feedhenry-dev at redhat.com > https://www.redhat.com/mailman/listinfo/feedhenry-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From pdarrow at redhat.com Thu Nov 24 21:09:24 2016 From: pdarrow at redhat.com (Peter Darrow) Date: Thu, 24 Nov 2016 17:09:24 -0400 Subject: [feedhenry-dev] Improving feedhenry.org In-Reply-To: References: Message-ID: Thanks for the background John, I kind of expected that was the case. I wouldn't really call myself a web designer or marketer, so while I can try to provide input, I'm not sure it will be the best. I would simply try to mimic other open source project pages that I think do a good job. Do we have any designers within Red Hat that would be able to help with something like this? Just a thought! On Thu, Nov 24, 2016 at 4:47 PM, John Frizelle wrote: > Hi Peter, > > I'd love to see some additions and improvements to feedhenry.org - > especially with the open sourcing of the Build Farm and MBaaS on the way. > > Up to now, we had been trying to restrict what we talked about to be just > the current OSS components, but perhaps we should give a broader overview > of the whole solution and then detail which parts are already OSS (lit up > links) and which parts are yet to come (greyed out with no links) -- just > an example of how we might achieve it. > > Please feel free to circulate any ideas / suggestions / concepts or even > Github branches (the code is hosted here: https://github.com/ > feedhenry/feedhenry.github.com) > > Cheers, > John. > > -- > John Frizelle > Platform Architect, Red Hat Mobile > Consulting Engineering > > mobile: *+353 87 290 1644 * > twitter:* @johnfriz* > skype: *john_frizelle* > mail: *jfrizell at redhat.com * > > > > > On 24 November 2016 at 20:35, Peter Darrow wrote: > >> Hi all, >> >> When I visit http://feedhenry.org/, it's hard for me to tell what the >> FeedHenry project is or what it can do for me. I'm currently shown a large >> ad for Raincatcher, and mentions of Mobile SDKs and templates, but there's >> no high level outline of what FeedHenry does. Below the fold in the >> "Develop, Deploy, Manage and Monitor" section there are a few sentences >> that sort of give a summary, but I think we could do a little better. >> >> Correct me if I'm wrong, but isn't Raincatcher an application built with >> FeedHenry and not the platform itself? What are your thoughts on creating a >> more focused landing page with clearly outlined features? One project I've >> contributed to does a great job of this: http://locust.io/. Are we >> waiting until the entire platform is open-sourced before highlighting it >> like this? >> >> Cheers, >> Peter >> >> _______________________________________________ >> feedhenry-dev mailing list >> feedhenry-dev at redhat.com >> https://www.redhat.com/mailman/listinfo/feedhenry-dev >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From davmarti at redhat.com Fri Nov 25 09:56:53 2016 From: davmarti at redhat.com (David Martin) Date: Fri, 25 Nov 2016 09:56:53 +0000 Subject: [feedhenry-dev] Improving feedhenry.org In-Reply-To: References: Message-ID: Any thoughts on adding a 'community libraries' section to feedhenry.org? I'm thinking just a list of modules users have created to help using or developing on the platform. e.g. - fhlog https://github.com/evanshortiss/fhlog JavaScript log library for client and cloud with a great API. Logs are timestamped, and can be saved and uploaded to a server. - fh-rest-sync-proxy https://github.com/feedhenry-staff/fh-rest-sync-proxy Proxy $fh.sync calls from a client to an MBaaS Service that exposes a RESTful API - rhmap-auth https://github.com/Keyang/rhmap-auth A library to validate RHMAP platform credentials - rhmap-stats https://www.npmjs.com/package/rhmap-stats RedHat Mobile Application system monitoring and stats lib (probably lots more) Also, I don't see fhc mentioned on the site. Probably one that deserves its own section? On 24 November 2016 at 21:09, Peter Darrow wrote: > Thanks for the background John, I kind of expected that was the case. I > wouldn't really call myself a web designer or marketer, so while I can try > to provide input, I'm not sure it will be the best. I would simply try to > mimic other open source project pages that I think do a good job. > > Do we have any designers within Red Hat that would be able to help with > something like this? Just a thought! > > On Thu, Nov 24, 2016 at 4:47 PM, John Frizelle > wrote: > >> Hi Peter, >> >> I'd love to see some additions and improvements to feedhenry.org - >> especially with the open sourcing of the Build Farm and MBaaS on the way. >> >> Up to now, we had been trying to restrict what we talked about to be just >> the current OSS components, but perhaps we should give a broader overview >> of the whole solution and then detail which parts are already OSS (lit up >> links) and which parts are yet to come (greyed out with no links) -- just >> an example of how we might achieve it. >> >> Please feel free to circulate any ideas / suggestions / concepts or even >> Github branches (the code is hosted here: https://github.com/feedh >> enry/feedhenry.github.com) >> >> Cheers, >> John. >> >> -- >> John Frizelle >> Platform Architect, Red Hat Mobile >> Consulting Engineering >> >> mobile: *+353 87 290 1644 * >> twitter:* @johnfriz* >> skype: *john_frizelle* >> mail: *jfrizell at redhat.com * >> >> >> >> >> On 24 November 2016 at 20:35, Peter Darrow wrote: >> >>> Hi all, >>> >>> When I visit http://feedhenry.org/, it's hard for me to tell what the >>> FeedHenry project is or what it can do for me. I'm currently shown a large >>> ad for Raincatcher, and mentions of Mobile SDKs and templates, but there's >>> no high level outline of what FeedHenry does. Below the fold in the >>> "Develop, Deploy, Manage and Monitor" section there are a few sentences >>> that sort of give a summary, but I think we could do a little better. >>> >>> Correct me if I'm wrong, but isn't Raincatcher an application built with >>> FeedHenry and not the platform itself? What are your thoughts on creating a >>> more focused landing page with clearly outlined features? One project I've >>> contributed to does a great job of this: http://locust.io/. Are we >>> waiting until the entire platform is open-sourced before highlighting it >>> like this? >>> >>> Cheers, >>> Peter >>> >>> _______________________________________________ >>> feedhenry-dev mailing list >>> feedhenry-dev at redhat.com >>> https://www.redhat.com/mailman/listinfo/feedhenry-dev >>> >>> >> > > _______________________________________________ > feedhenry-dev mailing list > feedhenry-dev at redhat.com > https://www.redhat.com/mailman/listinfo/feedhenry-dev > > -- David Martin Red Hat Mobile Twitter: @irldavem IRC: @irldavem (feedhenry, mobile-internal) -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From mwessend at redhat.com Fri Nov 25 10:02:49 2016 From: mwessend at redhat.com (Matthias Wessendorf) Date: Fri, 25 Nov 2016 11:02:49 +0100 Subject: [feedhenry-dev] Improving feedhenry.org In-Reply-To: References: Message-ID: On Thu, Nov 24, 2016 at 10:09 PM, Peter Darrow wrote: > Thanks for the background John, I kind of expected that was the case. I > wouldn't really call myself a web designer or marketer, so while I can try > to provide input, I'm not sure it will be the best. I would simply try to > mimic other open source project pages that I think do a good job. > > Do we have any designers within Red Hat that would be able to help with > something like this? Just a thought! > the team from Catherine Robson would be the one to contact for these kind of things -M > > On Thu, Nov 24, 2016 at 4:47 PM, John Frizelle > wrote: > >> Hi Peter, >> >> I'd love to see some additions and improvements to feedhenry.org - >> especially with the open sourcing of the Build Farm and MBaaS on the way. >> >> Up to now, we had been trying to restrict what we talked about to be just >> the current OSS components, but perhaps we should give a broader overview >> of the whole solution and then detail which parts are already OSS (lit up >> links) and which parts are yet to come (greyed out with no links) -- just >> an example of how we might achieve it. >> >> Please feel free to circulate any ideas / suggestions / concepts or even >> Github branches (the code is hosted here: https://github.com/feedh >> enry/feedhenry.github.com) >> >> Cheers, >> John. >> >> -- >> John Frizelle >> Platform Architect, Red Hat Mobile >> Consulting Engineering >> >> mobile: *+353 87 290 1644 * >> twitter:* @johnfriz* >> skype: *john_frizelle* >> mail: *jfrizell at redhat.com * >> >> >> >> >> On 24 November 2016 at 20:35, Peter Darrow wrote: >> >>> Hi all, >>> >>> When I visit http://feedhenry.org/, it's hard for me to tell what the >>> FeedHenry project is or what it can do for me. I'm currently shown a large >>> ad for Raincatcher, and mentions of Mobile SDKs and templates, but there's >>> no high level outline of what FeedHenry does. Below the fold in the >>> "Develop, Deploy, Manage and Monitor" section there are a few sentences >>> that sort of give a summary, but I think we could do a little better. >>> >>> Correct me if I'm wrong, but isn't Raincatcher an application built with >>> FeedHenry and not the platform itself? What are your thoughts on creating a >>> more focused landing page with clearly outlined features? One project I've >>> contributed to does a great job of this: http://locust.io/. Are we >>> waiting until the entire platform is open-sourced before highlighting it >>> like this? >>> >>> Cheers, >>> Peter >>> >>> _______________________________________________ >>> feedhenry-dev mailing list >>> feedhenry-dev at redhat.com >>> https://www.redhat.com/mailman/listinfo/feedhenry-dev >>> >>> >> > > _______________________________________________ > feedhenry-dev mailing list > feedhenry-dev at redhat.com > https://www.redhat.com/mailman/listinfo/feedhenry-dev > > -- Project lead AeroGear.org -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From mwessend at redhat.com Fri Nov 25 10:03:45 2016 From: mwessend at redhat.com (Matthias Wessendorf) Date: Fri, 25 Nov 2016 11:03:45 +0100 Subject: [feedhenry-dev] Improving feedhenry.org In-Reply-To: References: Message-ID: On Fri, Nov 25, 2016 at 10:56 AM, David Martin wrote: > Any thoughts on adding a 'community libraries' section to feedhenry.org? > > I'm thinking just a list of modules users have created to help using or > developing on the platform. > > e.g. > - fhlog https://github.com/evanshortiss/fhlog JavaScript log library for > client and cloud with a great API. Logs are timestamped, and can be saved > and uploaded to a server. > - fh-rest-sync-proxy https://github.com/feedhenry-staff/fh-rest-sync-proxy > Proxy $fh.sync calls from a client to an MBaaS Service that exposes a > RESTful API > - rhmap-auth https://github.com/Keyang/rhmap-auth A library to validate > RHMAP platform credentials > - rhmap-stats https://www.npmjs.com/package/rhmap-stats RedHat Mobile > Application system monitoring and stats lib > > (probably lots more) > hard to update, and keep in sync. I'd recommend linking to a wiki (A list of community powered FeedHenry projects). Were folks can just dump their repos > > Also, I don't see fhc mentioned on the site. Probably one that deserves > its own section? > > > On 24 November 2016 at 21:09, Peter Darrow wrote: > >> Thanks for the background John, I kind of expected that was the case. I >> wouldn't really call myself a web designer or marketer, so while I can try >> to provide input, I'm not sure it will be the best. I would simply try to >> mimic other open source project pages that I think do a good job. >> >> Do we have any designers within Red Hat that would be able to help with >> something like this? Just a thought! >> >> On Thu, Nov 24, 2016 at 4:47 PM, John Frizelle >> wrote: >> >>> Hi Peter, >>> >>> I'd love to see some additions and improvements to feedhenry.org - >>> especially with the open sourcing of the Build Farm and MBaaS on the way. >>> >>> Up to now, we had been trying to restrict what we talked about to be >>> just the current OSS components, but perhaps we should give a broader >>> overview of the whole solution and then detail which parts are already OSS >>> (lit up links) and which parts are yet to come (greyed out with no links) >>> -- just an example of how we might achieve it. >>> >>> Please feel free to circulate any ideas / suggestions / concepts or even >>> Github branches (the code is hosted here: https://github.com/feedh >>> enry/feedhenry.github.com) >>> >>> Cheers, >>> John. >>> >>> -- >>> John Frizelle >>> Platform Architect, Red Hat Mobile >>> Consulting Engineering >>> >>> mobile: *+353 87 290 1644 * >>> twitter:* @johnfriz* >>> skype: *john_frizelle* >>> mail: *jfrizell at redhat.com * >>> >>> >>> >>> >>> On 24 November 2016 at 20:35, Peter Darrow wrote: >>> >>>> Hi all, >>>> >>>> When I visit http://feedhenry.org/, it's hard for me to tell what the >>>> FeedHenry project is or what it can do for me. I'm currently shown a large >>>> ad for Raincatcher, and mentions of Mobile SDKs and templates, but there's >>>> no high level outline of what FeedHenry does. Below the fold in the >>>> "Develop, Deploy, Manage and Monitor" section there are a few sentences >>>> that sort of give a summary, but I think we could do a little better. >>>> >>>> Correct me if I'm wrong, but isn't Raincatcher an application built >>>> with FeedHenry and not the platform itself? What are your thoughts on >>>> creating a more focused landing page with clearly outlined features? One >>>> project I've contributed to does a great job of this: http://locust.io/. >>>> Are we waiting until the entire platform is open-sourced before >>>> highlighting it like this? >>>> >>>> Cheers, >>>> Peter >>>> >>>> _______________________________________________ >>>> feedhenry-dev mailing list >>>> feedhenry-dev at redhat.com >>>> https://www.redhat.com/mailman/listinfo/feedhenry-dev >>>> >>>> >>> >> >> _______________________________________________ >> feedhenry-dev mailing list >> feedhenry-dev at redhat.com >> https://www.redhat.com/mailman/listinfo/feedhenry-dev >> >> > > > -- > David Martin > Red Hat Mobile > Twitter: @irldavem > IRC: @irldavem (feedhenry, mobile-internal) > > _______________________________________________ > feedhenry-dev mailing list > feedhenry-dev at redhat.com > https://www.redhat.com/mailman/listinfo/feedhenry-dev > > -- Project lead AeroGear.org -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From kxiang at redhat.com Tue Nov 22 12:45:29 2016 From: kxiang at redhat.com (Keyang Xiang) Date: Tue, 22 Nov 2016 12:45:29 +0000 Subject: [feedhenry-dev] Any idea of support file storage in Dyno Message-ID: As subject, in RHMAP Dyno, if an app dependency needs to store files to filesystem (most likely config, user data, session data) while it is not possible to port to mongodb, is there a stable place to persist those files? ~Keyang -------------- next part -------------- An HTML attachment was scrubbed... URL: From wtrocki at redhat.com Fri Nov 25 17:10:56 2016 From: wtrocki at redhat.com (Wojciech Trocki) Date: Fri, 25 Nov 2016 17:10:56 +0000 Subject: [feedhenry-dev] Developer Experience Sprint Report Message-ID: Hi everyone, *In this sprint DevExp tam were mainly focusing on:* - Making "Mongo Express" production ready (expect awesome blog post soon) - Kickstarting community actions - Collecting feedback from various groups including RHMAP consulting - Improvements around UX/UI - especially around project creation screen. *For the next sprint we going to focus on:* - Documenting and sharing ideas future of our fh-fhc toolbox (improving our cmd tooling) - Improving UI/UX around projects area - Improving community guidelines and open-source projects - .. or whatever community would tell us to do *Recognition* I would like to personally thank *Emilio for finishing our Mongo Express feature.* Huge thanks for* Peter for starting various conversations about UI/UX improvements in studio and improving community interactions. *Great job guys! *Scrum report:* https://issues.jboss.org/secure/RapidBoard.jspa?rapidView=3758&view=reporting&chart=burndownChart&sprint=5466 *Retrospective report:* We decided to document our retrospectives in one google document to have quick look into previous goals. Document shared here: *https://docs.google.com/document/d/1TOWN2jFxT6mZ8KfscDPFc-PUx2eQ0OnirB1ncwBpq88/edit# * Thanks, -- Wojciech Trocki Software Engineer, Red Hat Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: From wtrocki at redhat.com Fri Nov 25 17:35:34 2016 From: wtrocki at redhat.com (Wojciech Trocki) Date: Fri, 25 Nov 2016 17:35:34 +0000 Subject: [feedhenry-dev] Any idea of support file storage in Dyno In-Reply-To: References: Message-ID: Currently platform supports 4 types of storage engines ( correct me if I'm wrong): - Mongodb - GridFS (mongo based) - Cache (Redis) - Temp local file storage (wiped on deploy) All engines may be used to hold config, user data, session data At the moment all files stored on local filesystem from node.js app would be removed with the next deploy. Even storing them outside application source folder would not help because running container can be killed anytime without backup etc. First idea I have in mind where DevExp team can help is to build *DataStore service for RHMAP platform that would allow to load/store any file* without worrying where is stored and how it's backed up by platform. This would allow developers to spin up service within project. Stored data would be available to all cloud apps and services. DataStore service can use underlying GridFS storage with help of Redis as cache. Another step would be to provide service client that would allow you to interact with files using CRUD operations. As we can imagine there may be so many usages for this storage so we definitely do not want to provide something that would not be covered by backups or would be forgotten when moving clusters. WDYT? Regards On Tue, Nov 22, 2016 at 12:45 PM, Keyang Xiang wrote: > As subject, in RHMAP Dyno, if an app dependency needs to store files to > filesystem (most likely config, user data, session data) while it is not > possible to port to mongodb, is there a stable place to persist those files? > > ~Keyang > > _______________________________________________ > feedhenry-dev mailing list > feedhenry-dev at redhat.com > https://www.redhat.com/mailman/listinfo/feedhenry-dev > > -- Wojciech Trocki Software Engineer, Red Hat Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 11472 bytes Desc: not available URL: