Ever since Linux Foundation started pushing the COC gags into ASF
projects I kept wondering if people won't behave in civil manner - just
like Paul has alluded to - unless they are explicitly told how to be
good boys and girls?
Let me ask a perhaps naive but a very honest question: why do we r
I think it is a great idea, thanks MG!
I've been doing Perl/Bash for decades, however more and more I am
employing Groovy to do my sysadmin chores. I learned to live with an
extra second or two to bring up a JVM. However, having this dependency
gone would make things easier and faster for sure
I don't think I was calling his email this way ;) but rather reaffirming
his point of view.
--
With regards,
Cos
On 2020-06-15 18:26, Remko Popma wrote:
On Mon, Jun 15, 2020 at 2:12 PM Konstantin Boudnik <mailto:c...@apache.org>> wrote:
Precisely, MG!
This
Precisely, MG!
This is what these discussions are swaying us into: to forget that we
are first and foremost came here to enjoy this great Groovy language
which many of us are using day in and day out (thanks for the team that
has made this possible!).
We aren't just a bunch of marginalized g
hat more guests
stay and become part of our community.
Remko.
On Sun, Jun 14, 2020 at 4:12 PM Konstantin Boudnik mailto:c...@apache.org>> wrote:
Thanks for kind words Remko. But I am not trying to blame myself
for anything.
I am perfectly aware about my
or in IT in
> general.
> We can only try to be aware of the biases that we inevitably have, and make
> our projects and interactions as welcoming as possible.
> I joined this project fairly recently, so I wasn't there when you were
> mentoring, but I am sure you did a great job.
>
Thank you for chiming in, Jenn.
As you mention "problems our community faces with inclusivity" - would
you mind mention a case of such a problem in the past? I was one of the
mentors of this project (as in was a part of it from its early days in
ASF), so I guess I am missing something in this
Well said!
> If we're doing this to "be on the right side"
Or "there are some groups projecting their own inner guilt and trying to
convince the rest of us they are on a moral high ground aka right side".
But because of their record of implementing poly-logism and moral
relativism arguments
to be totally neutral, this proposal does seem to
provide terms that many would find more neutral, so having that option
seems like a good thing from my point of view.
Cheers, Paul.
On Fri, Jun 12, 2020 at 1:15 AM Konstantin Boudnik <mailto:c...@apache.org>> wrote:
Hey fellas!
Hey fellas!
Wearing my hat of a software developer, using Groovy quite extensively
for the last decade, I'd like to understand the ramifications of the
initiative:
- at some point I would have to go back and comb through my code and
change/recompile everything that would be affected by the pr
t;
> Sent from my primitive Tricorder
>
>> On 22 Jul 2018, at 17:33, Konstantin Boudnik wrote:
>>
>> +1 There was APL once ;)
>> --
>> With regards,
>> Konstantin (Cos) Boudnik
>> 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
>>
>> Di
+1 There was APL once ;)
--
With regards,
Konstantin (Cos) Boudnik
2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
Disclaimer: Opinions expressed in this email are those of the author,
and do not necessarily represent the views of any company the author
might be affiliated with at the moment
Yup,
Apache mailing lists do not accept attachments.
--
With regards,
Konstantin (Cos) Boudnik
2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
Disclaimer: Opinions expressed in this email are those of the author,
and do not necessarily represent the views of any company the author
might be a
>needing the extra download. Perhaps that should be a section in our
>next
>board report?
>
>Anyway, we should get those changes for the next prepared releases.
>
>Cheers, Paul.
>
>
>On Tue, Nov 14, 2017 at 4:18 AM, Konstantin Boudnik
>wrote:
>
>> Current r
Current release includes a binary file (gradle/wrapper/*jar), which
isn't compatible with Apache release policy (ie source-only releases).
In all honestly, this isn't the first release with the same issue. I
was talking about it for too long and I am sorry I didn't address this
issue earlier.
Here
u wrote:
> Remind me how many of those problems would have been avoided if the Gradle
> wrapper was blessed by the Foundation?
>
>
> 2017-09-01 13:00 GMT+02:00 Paul King :
>
> >
> >
> > On Fri, Sep 1, 2017 at 3:50 AM, Konstantin Boudnik wrote:
> >
>
+1 [binding]
- Signature is ok
- Checksum is ok (although the file is formatted so that it prevent automatic
validation via -c option)
- RAT is ok
Perhaps a note on the requirement for Gradle 3.5.1 needs to be added to the
release notes? 'cause the build is failing with the latest version as well
It's painfully close to the elvis operator, isn't it?
On Tue, Nov 22, 2016 at 07:14AM, Daniel Sun wrote:
> Hi all,
>
> Marcin Erdmann proposed the new operator ?=, e.g. a ?= "foo" is
> equivalent of a = a ?: "foo".
>
> I like his idea, what do you think about it?
>
> Cheers,
> Danie
Maven has a way of signing artifacts and publishing checksums. In fact, it is
one of the requirement we stick to in Apache Bigtop (see [1])
Maven has verify plugin for this purpose [2].
[1]
https://repo.maven.apache.org/maven2/org/apache/bigtop/itest/itest-common/1.1.0/
[2] https://maven.apache.
+1 [binding]
signature is ok
sha1 is ok
rat is ok
builds and produces functional binaries
One small note: sha1 and md5 aren't considered secure, it'd make sense to
switch into gpg generated checksums, perhaps. I can work on that in the next a
couple of days, I guess
Thanks!
COs
On Fri, Jun 0
We are no longer PPMC, so it is ok to say it as it is - PMC ;)
We'll cast my vote later today.
Cos
On Fri, Jun 03, 2016 at 07:20PM, Cédric Champeau wrote:
> Dear community,
>
> I am happy to start the VOTE thread for the long awaited Apache Groovy
> 2.4.7!
> This release includes numerous bugf
Hello Alvaro.
Thanks for reaching out. We have the groovy packaging both for deb and rpm.
Here's the RPM spec
https://github.com/apache/bigtop/tree/master/bigtop-packages/src/rpm/bigtop-groovy/SPECS
currently, we're at 2.4.4, so I guess updating to 2.4.6 might make sense,
unless 2.5 is getti
On Mon, Feb 29, 2016 at 06:40PM, Cédric Champeau wrote:
> 2016-02-29 18:37 GMT+01:00 Konstantin Boudnik :
>
> > Sorry for a delay in the answer...
> >
> > On Mon, Feb 29, 2016 at 12:01PM, Jochen Theodorou wrote:
> > >
> > > On 27.02.2016 05:26, Aseem
Sorry for a delay in the answer...
On Mon, Feb 29, 2016 at 12:01PM, Jochen Theodorou wrote:
>
> On 27.02.2016 05:26, Aseem Bansal wrote:
> >Hi Konstantin Boudnik
> >
> >Are the things on groovy-lang not considered originating from Apache
> >premises?
Where the
There's another concern: docs of an Apache project has to originate, as the
source code, from Apache premises (Infra, etc.) While linking doesn't exactly
violates this, it is still looks like "Ok, here's our documentation, but for
this little piece you'd need to go and check somewhere else". There'
nless suggested
otherwise.
Regards,
Cos
On Thu, Feb 25, 2016 at 05:12PM, Konstantin Boudnik wrote:
> Hi Pascal.
>
> The logs are gone, but I will attempt to rerun the tests and share the
> stacktraces via JIRA.
>
> Cheers,
> Cos
>
> On Sun, Feb 21, 2016 at 01:25PM,
Hi Pascal.
The logs are gone, but I will attempt to rerun the tests and share the
stacktraces via JIRA.
Cheers,
Cos
On Sun, Feb 21, 2016 at 01:25PM, Pascal Schumacher wrote:
> Hi Konstantin,
>
> thanks for the in-depth check. :)
>
> Am 19.02.2016 um 08:49 schrieb Kon
+1 [binding]
- source code checksum [1] and signature are ok
- binary zip checksum/signature is ok
- gradle.properties is missing the ASL header and breaking the rat check. I
figure this alone doesn't warrant a respin, but the header needs to be added
or the file needs to be excluded from the
Second that!
Another thing we can do if there's enough interest is to put together a
pow-wow session for Apache Groovy. Basically, grab a room, get together and
chat about anything that seems important. Face to face is always more
productive than any e-comms out there. I would be happy to help to
As one of the people who helped Groovy with the incubation, I don't see such
statement as anything even vaguely resembling the situation. What I see is a
tremendous growth in the community, project popularity, and very active
development. Considering that this "simple explanation" doesn't seem to b
Great! Mind spreading the secret knowledge around ?
Cos
On Sun, Jan 17, 2016 at 10:57PM, Roman Shaposhnik wrote:
> Done!
>
> On Thu, Jan 14, 2016 at 1:15 PM, Pascal Schumacher
> wrote:
> > Hi Roman,
> >
> > any updates?
> >
> > https://projects.apache.org/project.html?groovy now shows the DOAP
On Fri, Jan 15, 2016 at 07:20PM, Russel Winder wrote:
> On Fri, 2016-01-15 at 19:57 +0100, Pascal Schumacher wrote:
> > Hello everybody,
> >
> > should the line endings of all source files in git be normalized to
> > "\n"?
> >
> > see the discussion at https://github.com/apache/groovy/pull/236
>
Second what Pascal said. Many time I've seen when people are hesitant to take
on task because the ticket is assigned to someone. One way around it is to
educate the community to simply grab anything that hasn't been updated for a
while, which is a good sign that ticket isn't getting worked on. But
33 matches
Mail list logo
