Done. I believe you could've have just mention the mentors votes from
the dev@. IIRC it should be sufficient.
--
With regards,
Cos
On 2/17/23 00:42, Sergey Kamov wrote:
Dear mentors - can we please get you to vote on the release? Thanks!
Regards,
Sergey
-- Forwarded message
+1 [binding]
Checked the usual: checksums, README, binaries.
--
Thank you!,
Cos
On 2/6/23 00:50, Sergey Kamov wrote:
Dear mentors - can we please get you to vote on the release? Thanks!
Regards,
Sergey
On Sat, Feb 4, 2023 at 1:46 AM Sergey Makov wrote:
+1
Checked:
- mvn clean
Hello Richard!
Thanks for your interest in the project and welcome! As all the contribution
are voluntary please feel free to look at the Jira (or perhaps you have some
ideas on your own?).
Pick up what you like and start working on it. Others in this list will share
some points, I am sure.
On
+1
checked all usual stuff, everything seems to be in order. Thank you!
--
With regards,
Cos
On 13.07.2021 19:17, Ifropc wrote:
+1
Checked
- mvn clean verify
- signatures
Thanks,
Gleb.
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Monday, July 12th, 2021 at
I think this is a good idea, indeed! We need to make sure that all
back-references to the project and attributions are in place, and we
aren't violating the ASF trademark in any way.
As for the native speaker narration: I would disagree. It doesn't have
to be a native speaker, it is really
+1 [binding].
I checked licenses, binaries, signatures and checksums. Build is ok too.
--
With regards,
Cos
> On Thu, May 27, 2021 at 2:07 PM Sergey Makov wrote:
>
> +1
>
> Checked:
> - mvn clean package verify (MacOS)
> - signatures
>
> Regards,
> Sergey
>
> On Thu, May 27, 2021 at 6:55
My bad, I can see the report now. Signed off as well.
With regards,
Cos
On 11.03.2021 12:36, Paul King wrote:
I just signed the report - sorry if I missed any earlier notification
that it was ready for sign off.
As a general comment, with mentoring hat on, I'd normally expect at least
one
I don't see the report here
https://cwiki.apache.org/confluence/display/INCUBATOR/March2021#nlpcraft
Aren't we supposed to add it to the page manually?
With regards,
Cos
On 11.03.2021 11:03, Aaron Radzinski wrote:
Report was submitted last week. Is this about a mentor's sign off?
Thank
+1 [binding]
Usual checks:
- chechsums
- signatures
- absence of binary files
- RAT and licenses
- build and tests
Thank you!
With regards,
Cos
On 26.01.2021 17:34, Aaron Radzinski wrote:
NLPCraft-ers,
To start off 2021 we have prepared the latest 0.7.4 release.
This is a call for a vote
ium=email_source=link_campaign=sig-email_content=webmail>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Tue, Jan 12, 2021 at 9:26 AM Konstantin Boudnik wrote:
Sorr
Sorry, here's the link to [1]
https://lists.apache.org/thread.html/r580939d61273630a8987ae642c27242adbf71a811e499d8a13d149da%40%3Cdev.nlpcraft.apache.org%3E
With regards,
Cos
On 11.01.2021 18:25, Konstantin Boudnik wrote:
Mentors,
the release [VOTE] has been open for 11 days [1]. Can I ask
Mentors,
the release [VOTE] has been open for 11 days [1]. Can I ask you to take
a look at it?
To @dev : we still can close the [VOTE], but the mentors would need to
vote on the general@incubator rather than on dev@nlpcraft.
--
With regards,
Cos
+1 [binding]
Checked:
- RAT & files
- checksums and signatures
- ran verify (finally, the tests are running well in LXD container! Thank you!)
--
Cos
On Thu, Dec 31, 2020 at 02:41PM, Aaron Radzinski wrote:
> NLPCraft-ers,
> Happy New Year!
>
> To finish off the outgoing 2020 we have
+1 [binding]
License, checksums, signatures are checked out.
One thing: I stepped on this
Full command line: java -Xmx4G -Xms4G
--add-exports=java.base/jdk.internal.misc=ALL-UNNAMED
--add-exports=java.base/sun.nio.ch=ALL-UNNAMED
+1 [biding]
Checked all usual things, nothing overly suspicious. And I agree with Paul on
both counts - keeping KEYS in the version control is a bit unusual and doesn't
solve anything.
--
Cos
On Sat, Oct 24, 2020 at 12:19PM, Paul King wrote:
> One point I forgot - There is certainly mixed
It is test issue at best which ain't invalidating the release, in my
opinion. Which seems to be solid otherwise, IMO.
--
With regards,
Cos
On 2020-09-29 19:46, Nikita Ivanov wrote:
Furkan - is this still "-1" from you? Seems like an env issue. If indeed
necessary - team will re-cut the build
checked usual checksums, required and prohibited (binary) files.
Ran
% mvn clean package verify
and I see this error message:
[INFO] Starting process: server
[INFO] Using working directory for this process:
Paul,
I agree - we should switch to the normal quarterly cycle. I.e. next
would be in September, if I count it right.
--
With regards,
Cos
On 2020-07-06 18:33, Paul King wrote:
Hi Justin,
I was going to remind the project re below reporting requirement.
I was just wondering whether a
.
--
With regards,
Cos
On 2020-06-13 00:32, Aaron Radzinski wrote:
NLPCraft-ers,
The vote for Apache NLPCraft 0.6.1 release is closed now.
Vote result: The vote PASSES with 8 votes +1 and no -1.
+1 votes:
- Nikita Ivanov
- Aaron Radzinski
- Sergey Kamov
- Furkan KAMACI
- Sergey Makov
- Paul King
- Konstantin
ight after that?
Thanks,
--
Nikita Ivanov
On Mon, Jun 1, 2020 at 11:24 PM Konstantin Boudnik wrote:
Guys,
perhaps it would makes sense to start marking release candidates (RCs) to
vote
on as it makes it easier to distinguish them apart. Having a few RCs
aren't
that unusual as issues coul
,
Furkan KAMACI
On Tue, Jun 2, 2020 at 9:24 AM Konstantin Boudnik wrote:
Guys,
perhaps it would makes sense to start marking release candidates (RCs) to
vote
on as it makes it easier to distinguish them apart. Having a few RCs aren't
that unusual as issues could be found during the review/vote
Guys,
perhaps it would makes sense to start marking release candidates (RCs) to vote
on as it makes it easier to distinguish them apart. Having a few RCs aren't
that unusual as issues could be found during the review/vote process. However,
voting repeatedly on what seems like the same version
Yup, completely agree!
--
With regards,
Cos
On 2020-05-30 03:04, Furkan KAMACI wrote:
Hi,
Let me explain what to do for this kind of situations:
Lazy consensus is the most "proper" way for it and no need for a non-lazy
consensus voting. Lazy consensus is simply an announcement of 'silence
I don't think we need to have a vote on this. If the discussion has
produced a consensus for a technical matter - it is settled. If it
didn't - try to find a way to fix the contention points and keep finding
the consensus.
Voting only needs to a very specific cases, really [1]
[1]
for NodeJS, pip for Python, etc.) which don't mesh well with Java-based
projects.
NLPCraft committers can chime in as well.
Hope this makes it a bit clearer.
Best,
--
Nikita Ivanov
On Thu, May 21, 2020 at 7:51 AM Konstantin Boudnik wrote:
Perhaps a wrong thread for this, but why it seems like a
Perhaps a wrong thread for this, but why it seems like a good idea to have
separate releases for the client and for the NLPCraft proper you did a couple
of weeks ago? It is a bit confusing to me...
Thanks,
Cos
On Sat, May 16, 2020 at 06:10PM, Aaron Radzinski wrote:
> NLPCraft-ers,
> This is
Yup, officially the PPMC vote isn't binding - hence IPMC needs to cast
the votes (usual binding votes to make the release an official ASF one).
--
Cos
On 2020-04-21 13:24, Paul King wrote:
Actually, below is premature. Once dev vote has been handled, it needs the
second round of voting by
, Konstantin Boudnik
wrote:
While Dave is right about "PPMC Chair" (which is fictional,
because
PPMC
is a PMC with training wheels attached) what I experienced
worked
well
in
other podlings is a "training PPMC chair". Such a person would
effectively
play a role coordinatin
happening
on
ASF infra & using ASF way.
6. Initial committers have been added on February 13, 2020.
OFF: @Cos - do we need to kick off PPMC chair vote now?
--
Nikita Ivanov
On Thu, Mar 19, 2020 at 11:32 PM Konstantin Boudnik
wrote:
Well, fair enough, will prep the report then.
@nlpcraft tea
Well, fair enough, will prep the report then.
@nlpcraft team: I'd suggest the PPMC work on the initial draft of the
report in the next day or two so we can quickly polish it up on the list
and offer to IPMC for acceptance and feedback.
You can take a look at a good example of initial report
Justin,
I think I need to change the reporting period for the podling: I have
mistakenly put on March, etc. schedule, but clearly we have just moved
code and are wrapping up the infra setup.
I will update the projects' file accordingly, so we'll report in May
instead, if the community is ok
Cool. And once we start getting contributors to the project
(non-committers that is) - then what Evans said elsewhere.
--
Cos
On 2020-03-15 03:42, Aaron Radzinski wrote:
Got it to work.
Thank you,
--
Aaron Radzinski
On Fri, Mar 13, 2020 at 8:55 PM Konstantin Boudnik wrote:
Aaron
Aaron,
you need to add committers to a project role. Could you please check if
you can do it here
https://issues.apache.org/jira/plugins/servlet/project-config/NLPCRAFT/roles
I assigned you admin role, so you should be able to add everyone to PMC
group and that would solve the issue.
+1 for Dave's suggestion. There's no rush to delete the old ones. You
can add a large-font notice to the original repo, saying that the code
has been migrated to ASF and keep them until we don't need them for sure.
--
Cos
On 2020-03-11 22:36, Dave Fisher wrote:
Hi -
5. All original
Perhaps I am missing something, but why would you make a mess out of
'release' branch (although I am not sure what purpose it serves as I am
not aware what branching model you're using).
You can migrate your branches as is (at least those that you need) and
sort out any issues as you go.
Sorry, Aaron - it was on my list for a while ;(
I have added you, Nikita and Dave to PMC role - you should be able to do
whatever you need to. If you need more help with the project, you know
where to find me.
-
Cheers,
Cos
On 2020-03-10 05:27, Aaron Radzinski wrote:
Konstantine,
I'm
Nikita,
are we missing something? Most of the ticket's items were done through
self-service. DNS and LDAP are ready as far as I can tell.
I am not 100% sure about website, but I don't think it is INFRA thing to do.
Could you be clear what are you expecting from the ticket? Thanks.
--
Cos
Hey.
Do we need %subj% at all? If so, let's ask INFRA to setup.
--
Cos
There's RAT plugin (at least for Maven, but I believe for Gradle as
well) that does a number of necessary release checks on the source code.
I'd consider using it in the future.
--
Cos
On 2020-03-09 13:29, Aaron Radzinski wrote:
NLPCrafters,
All file headers have been updated in the
Just in case and for the future considerations.
--
Cos
Forwarded Message
Subject: [NOTICE] Structural changes to Apache downloads
Date: Wed, 4 Mar 2020 09:03:52 -0600
From: Daniel Gruno
Reply-To: priv...@groovy.apache.org
To: us...@infra.apache.org
Hello, Apache PMCs,
In
Good points Aaron.
I'd like to add one general motto of Apache: "if it didn't happen on
mailing list - it didn't happen". This is indeed very important because
emails are archived and easily accessible by people in different
timezone - remember that many projects are quite spread around the
And here we go
https://gitbox.apache.org/repos/asf#nlpcraft
One all new committers submit their ICLAs following by their accounts
creation I will make sure they have proper access rights.
--
Cos
42 matches
Mail list logo
