Le lun. 14 févr. 2022 à 16:11, Xeno Amess a écrit :
>
> > Code not actively developed does not attract newcomers.
> Well I have to say the reason for "codes not actively developed" is a
> strong lack of alive committers, or more detailed, reviewers.
In part, yes, but they are the consequence of
Hello.
Le lun. 14 févr. 2022 à 16:46, Xeno Amess a écrit :
>
> (sigh) Do you think make some public activities would help? Like helding
> some online summer camp or something?
Well, there is, at least, GSoC.
Yet, AFAIK, there is no prior thinking about how to respond to
such initiatives, not eve
(sigh) Do you think make some public activities would help? Like helding
some online summer camp or something?
> it is a request in a queue
And it is actually not a queue, but a mixture of stack and priority queue.
When we meet some very important prs like critical bug fix or safety
things, we will review them first.
But for normal prs, actually we treat prs like stack.
Two prs with the same importance, o
> Remember that creating a PR is not a guarantee of anything, it is a
request
in a queue, a queue managed by volunteers.
Yes, legally and mortally it is.
But if we get more reviewers I think it will help the repos be more popular.
The tough thing is I totally have no idea how to get us some more
Remember that creating a PR is not a guarantee of anything, it is a request
in a queue, a queue managed by volunteers.
Gary
On Mon, Feb 14, 2022, 10:12 Xeno Amess wrote:
> > Code not actively developed does not attract newcomers.
> Well I have to say the reason for "codes not actively develope
> Code not actively developed does not attract newcomers.
Well I have to say the reason for "codes not actively developed" is a
strong lack of alive committers, or more detailed, reviewers.
I have still 100+ unsolved prs in commons projects, some of which be 1 or 2
years ago, but it seems there ju
Le lun. 14 févr. 2022 à 14:34, Gary Gregory a écrit :
>
> My guess is that this is a combination of the maturity of the components
The "maturity" rationale is not an explanation; it is a cause.
Code not actively developed does not attract newcomers.
It is not an "opinion" anymore; it is backed by
My guess is that this is a combination of the maturity of the components
and people having moved on to jobs or hobbies that no longer requires these
components.
Gary
On Mon, Feb 14, 2022, 08:32 Xeno Amess wrote:
> > [2] Backed by the numbers provided the project's report to the ASF
> board (wh
> [2] Backed by the numbers provided the project's report to the ASF
board (where the number of "committers" is utterly misleading wrt
its actual effect on maintenance capacity).
I'm also interested in why there are so many committers while small
amounts of which really do commit during these yea
Hello.
Le lun. 14 févr. 2022 à 00:23, GitBox a écrit :
>
>
> nhojpatrick commented on pull request #104:
> URL: https://github.com/apache/commons-codec/pull/104#issuecomment-1038472244
>
>
>@garydgregory i agree it could be considered clutter. If all projects are
> kept active current it's n
Hello.
Le lun. 14 févr. 2022 à 08:03, Avijit Basak a écrit :
>
> Hi All
>
> Thanks for the review comments. Please find my comments below.
>
> (1)
> [...]
>
> (2)
> >The "GeneticException" class seems to mostly deal with "illegal"
> >arguments; hence it should be a subclass of the JDK's s
12 matches
Mail list logo
