Re: Issue tracking

to GitHub Issues, and if so could be a good >> place to start looking into that process. >> >> Please let me know what you think. >> >> Thanks >> Justin >> >> On Jun 4, 2020, at 9:20 AM, Justin Obara wrote: >> >> Hi Everyone, >> &

Re: Issue tracking

4, 2020, at 9:20 AM, Justin Obara > <mailto:obara.jus...@gmail.com>> wrote: >> >> Hi Everyone, >> >> I haven’t heard any opposing views to my proposal below. I’m taking silence >> as consent and have moved forward with the first phase, which is to &

Re: Issue tracking

> Hi Everyone, > > I haven’t heard any opposing views to my proposal below. I’m taking > silence as consent and have moved forward with the first phase, which is to > catalogue the issue tracking for the public repos in the fluid-project > <https://github.com/fluid-project> and inc

Re: Issue tracking

rd any opposing views to my proposal below. I’m taking silence > as consent and have moved forward with the first phase, which is to catalogue > the issue tracking for the public repos in the fluid-project > <https://github.com/fluid-project> and inclusive-design > <https://git

Re: Issue tracking

Hi Everyone, I haven’t heard any opposing views to my proposal below. I’m taking silence as consent and have moved forward with the first phase, which is to catalogue the issue tracking for the public repos in the fluid-project <https://github.com/fluid-project> and inclusive-design

Issue tracking

Hi Everyone, This topic was touched upon in a recent "Enabling Github Issues for Infusion project ” Fluid-Work mailing-list thread. However, what I’m proposing here is slightly different from that part