[aerogear-dev] GH Issues vs JIRA
Kris Borchers
kris at redhat.com
Fri Aug 2 21:53:07 EDT 2013
On Aug 2, 2013, at 8:21 PM, Douglas Campos <qmx at qmx.me> wrote:
> On Fri, Aug 02, 2013 at 07:31:53PM -0500, Kris Borchers wrote:
>> So today I absentmindedly created a GH issue to rename a repo instead
>> of a JIRA. This actually demonstrated a problem we might have. If we
>> don't want to deal with people filing issues on GH and just want
>> JIRAs, we may want to consider turning off issues. I know if I was
>> trying to file a bug and someone asked me to file it again somewhere
>> else, I would be annoyed.
> All our repos should have github issues turned off - if this is not the
> case please file JIRAs for me.
>>
>> That said, I think we need to be very careful with this. If we turn
>> off GH issues, we would need very prominent links to our contributing
>> guides near the top of every repo's README so people can easily see
>> where they can file issues.
> Good idea, what about filing a handful of JIRAS for updating
> CONTRIBUTING.markdown? This can be a good low-hanging fruit for new
> contributors…
Updating those files is fine but I would still like something in all READMEs since those are what people look at. I know I never look for a contributing file and since we're removing issues, they won't get the GH prompt unless they file a PR and that's not what someone trying to file a bug is doing necessarily.
>
> --
> qmx
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
More information about the aerogear-dev
mailing list