You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@fineract.apache.org by Awasum Yannick <aw...@apache.org> on 2019/04/26 11:51:10 UTC

Merge Fineract Issues list into Dev List?

Hi All,

I noticed very few people(just 16) are subscribed to the issues list it can
be difficult for new contributors or even old ones to help or have
visibility when issues are created.

It will make sense to join the Issues list with the Dev list so all new
issues, comments and PRs can go directly to the Dev list which has more
Developers. looks like it more of switching issues notification list to dev
list and disabling the issues list.

My reasoning is that the higher the number of people looking at new issues
and comments, the faster the response time will be. This could even help
end users get comfortable with reporting bugs and reading bugs as they will
get notifications.

Also some people are not even ware that we have an issues list or know
where the bug tracker is located. This could help in this aspect.

What do you all think?

Re: Merge Fineract Issues list into Dev List?

Posted by Babajide Apata <ap...@gmail.com>.
This is a great Idea awasum, as some of us are not even aware of the issues
mailing list.

On Fri, 26 Apr 2019, 12:51 Awasum Yannick, <aw...@apache.org> wrote:

> Hi All,
>
> I noticed very few people(just 16) are subscribed to the issues list it
> can be difficult for new contributors or even old ones to help or have
> visibility when issues are created.
>
> It will make sense to join the Issues list with the Dev list so all new
> issues, comments and PRs can go directly to the Dev list which has more
> Developers. looks like it more of switching issues notification list to dev
> list and disabling the issues list.
>
> My reasoning is that the higher the number of people looking at new issues
> and comments, the faster the response time will be. This could even help
> end users get comfortable with reporting bugs and reading bugs as they will
> get notifications.
>
> Also some people are not even ware that we have an issues list or know
> where the bug tracker is located. This could help in this aspect.
>
> What do you all think?
>

Re: Merge Fineract Issues list into Dev List?

Posted by Mexina Daniel <me...@singo.africa>.
Hello Awasum

I support this.

Regards

> On April 26, 2019 at 5:21 PM Awasum Yannick <aw...@apache.org> wrote:
> 
>     Hi All,
> 
>     I noticed very few people(just 16) are subscribed to the issues list it can be difficult for new contributors or even old ones to help or have visibility when issues are created.
> 
>     It will make sense to join the Issues list with the Dev list so all new issues, comments and PRs can go directly to the Dev list which has more Developers. looks like it more of switching issues notification list to dev list and disabling the issues list.
> 
>     My reasoning is that the higher the number of people looking at new issues and comments, the faster the response time will be. This could even help end users get comfortable with reporting bugs and reading bugs as they will get notifications.
> 
>     Also some people are not even ware that we have an issues list or know where the bug tracker is located. This could help in this aspect.
> 
>     What do you all think?
> 


Mexina Daniel

Singo Africa Limited

Mbezi Beach "B"  | Mwai Kibaki Road | 6 Wasafi Str.
P.O BOX 78908 | 14121 Dar es salaam

+255 71 211 0791 | +255 22 261 8511

amala.co.tz https://amala.co.tz/  | singo.africa https://singo.africa

         

Re: Merge Fineract Issues list into Dev List?

Posted by Nic <so...@mail.com>.
^^ OK

On April 26, 2019 7:51:10 PM GMT+08:00, Awasum Yannick <aw...@apache.org> wrote:
>Hi All,
>
>I noticed very few people(just 16) are subscribed to the issues list it
>can
>be difficult for new contributors or even old ones to help or have
>visibility when issues are created.
>
>It will make sense to join the Issues list with the Dev list so all new
>issues, comments and PRs can go directly to the Dev list which has more
>Developers. looks like it more of switching issues notification list to
>dev
>list and disabling the issues list.
>
>My reasoning is that the higher the number of people looking at new
>issues
>and comments, the faster the response time will be. This could even
>help
>end users get comfortable with reporting bugs and reading bugs as they
>will
>get notifications.
>
>Also some people are not even ware that we have an issues list or know
>where the bug tracker is located. This could help in this aspect.
>
>What do you all think?

-- 
Sent from my p≡p for Android.