Hi,
Here’s some other links that may help.
A worked example on how to assemble LICENSE and NOTICE:
https://github.com/justinmclean/ApacheWombat
https://vimeo.com/171210141
A previous incubator talk (from 2017):
https://www.youtube.com/watch?v=I0-lp1t9ee0
A talk I gave last year it currently
Hi,
Here’s the time line for the June report [1]
Wed June 05 -- Podling reports due by end of day
Sun June 09 -- Shepherd reviews due by end of day
Sun June 09 -- Summary due by end of day
Tue June 11 -- Mentor signoff due by end of day
Wed June 12 -- Report submitted to
I'd second Geertjan's comments about how helpful (even though it probably
seemed painful at the time) Justin's comments were for Apache Groovy during
our incubation.
Perhaps it is worth re-reading some of the reasons why The ASF values
highly the provenance behind all of the software in its
Hi,
> the fact people allow tools like apache RAT to rot, yet somehow can
> find glitches in dozens of repos tells me priorities are whacked.
If you’ve found an issue with Rat please raise an issue with that project.
Rat isn’t expected to be perfect, as it says:
Rat is really little more than a
HI,
> maybe you can open source the tools you use justin.
I spoken about it at many ApacheCons and provided "them" here on this list.
Calling them tools is probably an exaggeration, It’s nothing complex.
Here’s the tool I used:
search copyright | sort -u
(Where search is "find . -type f
Probably more than anyone in the world, I feel your pain. Tip: document
everything Justin identifies as a problem, focus on those items in addition
to everything you’re focusing on already, and each release will be less
painful than the one before.
Gj
On Sat, 18 May 2019 at 17:46, Adrian Cole
the fact people allow tools like apache RAT to rot, yet somehow can
find glitches in dozens of repos tells me priorities are whacked.
For example, the last release justin found a second header on a file
that said it was temporary (now deleted)
did he manually look at hundreds of files to see
In defence of Justin :-) I'm very sure NetBeans would not be as solid and
well placed in Apache right now, outside the Incubator, without Justin's
uncanny ability to find glitches. :-)
Gj
On Sat, May 18, 2019 at 4:59 PM Adrian Cole wrote:
> maybe you can open source the tools you use justin.
>
Hi
Look like the topic changed, somehow? Why?
This should a discussion about the possibility and recommendation about
**parallel vote**.
Let’s stay in that one, OK?
Back to the topic, as both IPMC and Zipkin mentor,
**parallel vote** is good to improve the slow progress about
maybe you can open source the tools you use justin.
you seem uncanny ability to find glitches, yet also have an ability to
ignore note in the vote request mentioning known issues.
start helping instead of finding faults. you are the reason incubator is
not something anyone wants to go through
Sorry Justin but this is you looking for “problems” that just are not there and
to me it comes across as you taking joy out of frustrating people. Nothing
about “nagging mentors privately to vote” holds any additional / relevant
information that needs disclosure to the public.
So something
Hi,
> I nagged our mentors privately to vote and mentioned that I would be
> trying a concurrent vote.
IMO that communication should be public, part of doing things at the ASF is
being open and tranparent. Again IMO that decision would of been better done
via consensus of the PPMC and not
Hi,
> But for Zipkin, there are lots of community releases which are built
> on top of auto tools, so I think it's much safer for us to start a
> parallel vote both PPMC and IPMC.
Given all release I’ve looked at had license (or other) issues why do you think
that the “auto tools” are doing
Yes, we (mentors of Zipkin) were informed about the vote in private mail.
I think it should be fine to ping mentor privately about the release
vote, as we cannot always monitor the dev mailing list.
Otherwise, it will some time for us to response the release vote.
Willem Jiang
Twitter:
As mentor is member of PPMC and IPMC, it could speed up the voting
process by getting the mentor involved at the earlier stage.
Normally we just wait for the PPMC to do the technical check then we
go through the License check in the IPMC vote.
But for Zipkin, there are lots of community releases
+1. (binding)
Here what I checked:
Signed key and hash code are OK
No binary in the source artifact
Notice and Disclaimer files are OK,
We need to polish the License file as Justin had mentioned in next release.
I also find a minor issue of License file
I cannot find the License information
> Can you point me to where the PPMC has a discussion about this?
I nagged our mentors privately to vote and mentioned that I would be
trying a concurrent vote.
Everyone in our PPMC is aware of the vote delay problem and this
thread. We have had numerous discussions about this topic since
Hi,
> I informed our mentors.
Can you point me to where the PPMC has a discussion about this?
Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail:
and I also said in the announcement that this was a concurrent vote.
On Sat, May 18, 2019, 7:55 AM Adrian Cole wrote:
> I informed our mentors.
>
> On Sat, May 18, 2019, 2:03 AM Justin Mclean
> wrote:
>
>> HI,
>>
>> Or better still if you want to try something new / not in line with
>> policy
19 matches
Mail list logo
