Hi Elric and all,
First, I look both ways before I cross the street.
Second, thank you (seriously) for considering my mental health :)
This is likely the most common (xkcd 2347!) issue in FOSS projects,
so... we're like everyone else.
Gary
On Sun, Jun 16, 2024 at 6:18 PM Elric V wrote:
>
> On
On 12/06/2024 15:45, Gary D. Gregory wrote:
## Community Health:
Regarding community health: please don't take this the wrong way, but it
feels like Gary is doing A LOT of the heavy lifting on all of the
commons projects. What happens if Gary is hit by a bus? Would the
commons community sti
Note that moving the dependabot PR emails to a different list (if it's
even possible) is only part of the problem.
Applying the PR generates a message to the commits list (which cannot
safely be dropped) as well as a message closing the PR.
On Sat, 15 Jun 2024 at 21:03, Phil Steitz wrote:
>
> On
On Sat, Jun 15, 2024 at 12:27 PM Gary Gregory
wrote:
> Hm, would using GitHub Issues instead of Jira make the trail following
> easier, harder, or the same?
>
Harder, because then you would have to search yet another place to
reconstruct history. But that would be less of an issue over time. I
Hm, would using GitHub Issues instead of Jira make the trail following
easier, harder, or the same?
Gary
On Sat, Jun 15, 2024, 2:58 PM Gary Gregory wrote:
> If we want to have everything recorded in one place, then we need to put
> up some roadblocks to PRs, the Wiki, and Jira like ... what? Ha
If we want to have everything recorded in one place, then we need to put up
some roadblocks to PRs, the Wiki, and Jira like ... what? Have a PR, wiki,
and Jira template/gate that says... you must discuss your issue/bug/feature
first on the mailing list? It does not feel workable.
I don't think thi
On Sat, Jun 15, 2024 at 10:19 AM Gary Gregory
wrote:
> Note that it is 1) awkward to say "Let's stop talking about this PR in
> this PR"
Funny we used to do that all the time in Jira comments. I guess times
change. FWIW, I think it is a step backward in discussion and ultimately
code and arch
Note that it is 1) awkward to say "Let's stop talking about this PR in
this PR" and 2) "You need to subscribe to a mailing to continue this
chat." It's just hard to find when to ask for a switch. Especially
when GH has a nice UI to make comments _about code_. Over at Log4j, we
now use GitHub issues
On Wed, Jun 12, 2024 at 10:58 AM Gary D. Gregory
wrote:
> On 2024/06/12 17:17:24 Phil Steitz wrote:
> > On Wed, Jun 12, 2024 at 7:27 AM sebb wrote:
> >
> > > On Wed, 12 Jun 2024 at 14:45, Gary D. Gregory
> wrote:
> > > >
> > > > Hello All,
> > > >
> > > > Here is the draft of our board report f
Thanks, Gary
Phil
On Wed, Jun 12, 2024 at 10:37 AM Gary D. Gregory
wrote:
> I've edited the sections commented on as:
>
> ## Project Activity:
> Many releases of our components:
> CONFIGURATION-2.11.0 was released on 2024-06-10.
> NET-3.11.1 was released on 2024-06-10.
> PARENT-71 w
On 2024/06/12 22:25:29 sebb wrote:
> On Wed, 12 Jun 2024 at 18:58, Gary D. Gregory wrote:
> >
> > On 2024/06/12 17:17:24 Phil Steitz wrote:
>
> > > +1
> > > I have had to filter out most of the messages and once I do that, there is
> > > almost no actual discussion on-list. I am worried that whe
On Wed, 12 Jun 2024 at 18:58, Gary D. Gregory wrote:
>
> On 2024/06/12 17:17:24 Phil Steitz wrote:
> > +1
> > I have had to filter out most of the messages and once I do that, there is
> > almost no actual discussion on-list. I am worried that when people do try
> > to start discussion, the mess
On 2024/06/12 17:17:24 Phil Steitz wrote:
> On Wed, Jun 12, 2024 at 7:27 AM sebb wrote:
>
> > On Wed, 12 Jun 2024 at 14:45, Gary D. Gregory wrote:
> > >
> > > Hello All,
> > >
> > > Here is the draft of our board report for June I plan on submitting in a
> > day or so, feedback is welcome.
> > >
On 2024/06/12 14:26:53 sebb wrote:
> On Wed, 12 Jun 2024 at 14:45, Gary D. Gregory wrote:
> >
> > Hello All,
> >
> > Here is the draft of our board report for June I plan on submitting in a
> > day or so, feedback is welcome.
> >
> > ## Description:
> > The mission of Apache Commons is the creati
I've edited the sections commented on as:
## Project Activity:
Many releases of our components:
CONFIGURATION-2.11.0 was released on 2024-06-10.
NET-3.11.1 was released on 2024-06-10.
PARENT-71 was released on 2024-06-10.
JEXL-3.4.0 was released on 2024-06-06.
NET-3.11.0 was re
On Wed, Jun 12, 2024 at 7:27 AM sebb wrote:
> On Wed, 12 Jun 2024 at 14:45, Gary D. Gregory wrote:
> >
> > Hello All,
> >
> > Here is the draft of our board report for June I plan on submitting in a
> day or so, feedback is welcome.
> >
> > ## Description:
> > The mission of Apache Commons is th
On Wed, 12 Jun 2024 at 14:45, Gary D. Gregory wrote:
>
> Hello All,
>
> Here is the draft of our board report for June I plan on submitting in a day
> or so, feedback is welcome.
>
> ## Description:
> The mission of Apache Commons is the creation and maintenance of Java focused
> reusable librari
Hi.
Le mer. 12 juin 2024 à 15:45, Gary D. Gregory a écrit :
>
> Hello All,
>
> Here is the draft of our board report for June I plan on submitting in a day
> or so, feedback is welcome.
>
> ## Description:
> The mission of Apache Commons is the creation and maintenance of Java focused
> reusable
Hello All,
Here is the draft of our board report for June I plan on submitting in a day or
so, feedback is welcome.
## Description:
The mission of Apache Commons is the creation and maintenance of Java focused
reusable libraries and components
## Project Status:
Current project status: Ongoing
19 matches
Mail list logo
