From omatskiv at redhat.com Tue Aug 2 12:00:18 2016 From: omatskiv at redhat.com (Oleg Matskiv) Date: Tue, 2 Aug 2016 14:00:18 +0200 Subject: [feedhenry-dev] Can anyone merge and publish new version of fh-dev-tools ? Message-ID: Hello guys, I fixed an issue in fh-dev-tools which prevented us from using it in openshift online. Would be great if someone with access rights could merge PR [1] and publish new version to NPM. Thanks ! [1] https://github.com/fheng/fh/pull/120 -- Oleg Matskiv Associate Quality Engineer Red Hat Mobile Application Platform omatskiv at redhat.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From mwessend at redhat.com Wed Aug 3 06:35:09 2016 From: mwessend at redhat.com (Matthias Wessendorf) Date: Wed, 3 Aug 2016 08:35:09 +0200 Subject: [feedhenry-dev] Community/Project Info on our Server SDKs / Github issues ? Message-ID: Hello, do folks like this format for our NPM modules ? https://github.com/feedhenry/fh-amqp-js/pull/6/files It gives some raw info about the project and its community e.g. this mailing list. Now since the main issue tracker is the FH JIRA instance, should we disable the Github issues on our Server SDK repos ? Disabling may help to avoid having two streams of issue trackers. Several Red Hat project do the same: defaulting to JIRA, having no GH issues. -Matthias -- Project lead AeroGear.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From jfrizell at redhat.com Wed Aug 3 07:37:03 2016 From: jfrizell at redhat.com (John Frizelle) Date: Wed, 3 Aug 2016 08:37:03 +0100 Subject: [feedhenry-dev] Community/Project Info on our Server SDKs / Github issues ? In-Reply-To: References: Message-ID: Big +1 for adding this info and disabling GH issues. -- 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 3 August 2016 at 07:35, Matthias Wessendorf wrote: > Hello, > > do folks like this format for our NPM modules ? > https://github.com/feedhenry/fh-amqp-js/pull/6/files > > It gives some raw info about the project and its community e.g. this > mailing list. > > > Now since the main issue tracker is the FH JIRA instance, should we > disable the Github issues on our Server SDK repos ? > > Disabling may help to avoid having two streams of issue trackers. Several > Red Hat project do the same: defaulting to JIRA, having no GH issues. > > -Matthias > > -- > 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 sblanc at redhat.com Wed Aug 3 09:16:06 2016 From: sblanc at redhat.com (Sebastien Blanc) Date: Wed, 3 Aug 2016 11:16:06 +0200 Subject: [feedhenry-dev] Community/Project Info on our Server SDKs / Github issues ? In-Reply-To: References: Message-ID: I was also thinking about the fh-automatron message on PRs, maybe for OSS projects we could have a "simplified" one ? On Wed, Aug 3, 2016 at 9:37 AM, John Frizelle wrote: > Big +1 for adding this info and disabling GH issues. > > > > -- > 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 3 August 2016 at 07:35, Matthias Wessendorf > wrote: > >> Hello, >> >> do folks like this format for our NPM modules ? >> https://github.com/feedhenry/fh-amqp-js/pull/6/files >> >> It gives some raw info about the project and its community e.g. this >> mailing list. >> >> >> Now since the main issue tracker is the FH JIRA instance, should we >> disable the Github issues on our Server SDK repos ? >> >> Disabling may help to avoid having two streams of issue trackers. Several >> Red Hat project do the same: defaulting to JIRA, having no GH issues. >> >> -Matthias >> >> -- >> 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 > > -------------- 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 gryan at redhat.com Wed Aug 3 09:57:33 2016 From: gryan at redhat.com (Gerard Ryan) Date: Wed, 03 Aug 2016 10:57:33 +0100 Subject: [feedhenry-dev] Community/Project Info on our Server SDKs / Github issues ? In-Reply-To: (Matthias Wessendorf's message of "Wed, 3 Aug 2016 08:35:09 +0200") References: Message-ID: <87r3a6uqcy.fsf@thinkpad.grdryn.redhat> Matthias Wessendorf writes: > Now since the main issue tracker is the FH JIRA instance, should we disable > the Github issues on our Server SDK repos ? > > Disabling may help to avoid having two streams of issue trackers. Several > Red Hat project do the same: defaulting to JIRA, having no GH issues. I like the idea of keeping the GH issues more than removing them. Of course, those of us who already have an account at jboss.org will create jira issues there, but I think it's an unnecessary hurdle for someone to open an issue if they don't already have an account there. If there are bugs, I'd like people to be able to tell us about them in the easiest way possible; instead of potentially never hearing about them because we made it more difficult to create them. If people inside Red Hat need to have a corresponding jira issue for some traceability or something, then they can create that issue and link to the GH one (and link to the jira one from the GH issue also, if that makes sense). Does anyone share my opinion? From mwessend at redhat.com Wed Aug 3 10:36:21 2016 From: mwessend at redhat.com (Matthias Wessendorf) Date: Wed, 3 Aug 2016 12:36:21 +0200 Subject: [feedhenry-dev] Community/Project Info on our Server SDKs / Github issues ? In-Reply-To: <87r3a6uqcy.fsf@thinkpad.grdryn.redhat> References: <87r3a6uqcy.fsf@thinkpad.grdryn.redhat> Message-ID: On Wed, Aug 3, 2016 at 11:57 AM, Gerard Ryan wrote: > Matthias Wessendorf writes: > > > Now since the main issue tracker is the FH JIRA instance, should we > disable > > the Github issues on our Server SDK repos ? > > > > Disabling may help to avoid having two streams of issue trackers. Several > > Red Hat project do the same: defaulting to JIRA, having no GH issues. > > I like the idea of keeping the GH issues more than removing them. Of > course, those of us who already have an account at jboss.org will create > jira issues there, but I think it's an unnecessary hurdle for someone to > open an issue if they don't already have an account there. > > If there are bugs, I'd like people to be able to tell us about them in > the easiest way possible; instead of potentially never hearing about > them because we made it more difficult to create them. > > If people inside Red Hat need to have a corresponding jira issue for > some traceability or something, then they can create that issue and link > to the GH one (and link to the jira one from the GH issue also, if that > makes sense). > > Does anyone share my opinion? > I see where you are coming from, but believe me, folks do abuse issues as a mailing list or forum. That's also the "easiest way" to 'ask' questions. These are reasons why lot's of Red Hat projects are not having them enabled. I think we can leave them enabled, and shut them down when it becomes more pain than use ? -M -- Project lead AeroGear.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From mwessend at redhat.com Wed Aug 3 10:44:06 2016 From: mwessend at redhat.com (Matthias Wessendorf) Date: Wed, 3 Aug 2016 12:44:06 +0200 Subject: [feedhenry-dev] Community/Project Info on our Server SDKs / Github issues ? In-Reply-To: References: Message-ID: I do agree that these are not really sounding that friendly :-) Also, lots of stuff can't be done by community contributors either that is recommended in the PR message, like fhcap-cli, or UART. Also, today we don't public contributing & code style guides as well. I think it's fair to have a more community friendly message, that for instance suggests paying attention to the builds (e.g. Travis/Jenkins) or any SonarQube issues with the PR. @Gerard: is this something that can be done for public feedhenry repos ? Thanks! Matthias On Wed, Aug 3, 2016 at 11:16 AM, Sebastien Blanc wrote: > I was also thinking about the fh-automatron message on PRs, maybe for OSS > projects we could have a "simplified" one ? > > On Wed, Aug 3, 2016 at 9:37 AM, John Frizelle wrote: > >> Big +1 for adding this info and disabling GH issues. >> >> >> >> -- >> 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 3 August 2016 at 07:35, Matthias Wessendorf >> wrote: >> >>> Hello, >>> >>> do folks like this format for our NPM modules ? >>> https://github.com/feedhenry/fh-amqp-js/pull/6/files >>> >>> It gives some raw info about the project and its community e.g. this >>> mailing list. >>> >>> >>> Now since the main issue tracker is the FH JIRA instance, should we >>> disable the Github issues on our Server SDK repos ? >>> >>> Disabling may help to avoid having two streams of issue trackers. >>> Several Red Hat project do the same: defaulting to JIRA, having no GH >>> issues. >>> >>> -Matthias >>> >>> -- >>> 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 >> >> > -- 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 gryan at redhat.com Thu Aug 4 08:26:57 2016 From: gryan at redhat.com (Gerard Ryan) Date: Thu, 04 Aug 2016 09:26:57 +0100 Subject: [feedhenry-dev] Community/Project Info on our Server SDKs / Github issues ? In-Reply-To: (Matthias Wessendorf's message of "Wed, 3 Aug 2016 12:36:21 +0200") References: <87r3a6uqcy.fsf@thinkpad.grdryn.redhat> Message-ID: <87twf16isu.fsf@thinkpad.grdryn.redhat> Matthias Wessendorf writes: > These are reasons why lot's of Red Hat projects are not having them > enabled. I think we can leave them enabled, and shut them down when it > becomes more pain than use ? Yes, that sounds better than eagerly disabling when we don't actually have a problem. Let's do that! :) From gryan at redhat.com Thu Aug 4 08:30:52 2016 From: gryan at redhat.com (Gerard Ryan) Date: Thu, 04 Aug 2016 09:30:52 +0100 Subject: [feedhenry-dev] Community/Project Info on our Server SDKs / Github issues ? In-Reply-To: (Matthias Wessendorf's message of "Wed, 3 Aug 2016 12:44:06 +0200") References: Message-ID: <87popp6imb.fsf@thinkpad.grdryn.redhat> Matthias Wessendorf writes: > @Gerard: is this something that can be done for public feedhenry repos ? > > On Wed, Aug 3, 2016 at 11:16 AM, Sebastien Blanc wrote: > >> I was also thinking about the fh-automatron message on PRs, maybe for OSS >> projects we could have a "simplified" one ? I'm sure it can! :) I'm not sure how straightforward it is right now, but it's all just software, so I'm sure we can bend it to our will. :)