Thanks! Is adriancole also authorized now?
On Tuesday, April 16, 2013, Marvin Humphrey wrote:
> On Tue, Apr 16, 2013 at 12:13 PM, Matt Stephenson
> >
> wrote:
> > I'm helping out with the jclouds incubation. My username is
> MattStephenson
>
> Done.
>
> Marvin Humphrey
>
> -
Thanks!
On Tuesday, April 16, 2013, Christian Grobmeier wrote:
> On Tue, Apr 16, 2013 at 9:26 PM, Adrian Cole
> >
> wrote:
> > Thanks! Is adriancole also authorized now?
>
> I just added you
>
> Cheers
>
>
>
> > On Tuesday, April 16, 2013, Marvin Hum
Thanks for the offers to mentor, folks. I've noticed there's a new
"Volunteer" section below, so feel free to add in there :)
http://wiki.apache.org/incubator/jcloudsProposal
Thanks for the support and hope we get accepted!
-A
On Tue, Apr 16, 2013 at 12:27 PM, Mohammad Nour El-Din <
nour.moham
k together on the Apache Cloud ecosystem.
-A
On Tue, Apr 16, 2013 at 2:51 PM, Adrian Cole wrote:
> Thanks for the offers to mentor, folks. I've noticed there's a new
> "Volunteer" section below, so feel free to add in there :)
>
> http://wiki.apache.org/in
Tomaz and Olivier (and David)
You guys are awesome to offer help. I thought maybe 5 was the number of
mentors we needed, but I heard a sentiment of "the more the merrier" So,
I'm adding any apache member with experience with incubation that offers to
help us. Seems a better problem to have more
board as mentor or on this list).
>
> Cheers,
> Suresh
>
> On Apr 16, 2013, at 7:51 PM, Adrian Cole wrote:
>
> > Tomaz and Olivier (and David)
> >
> > You guys are awesome to offer help. I thought maybe 5 was the number of
> > mentors we needed, but I hea
it.
>
> Cheers,
> Suresh
>
> >
> > I really like our proposal, but I'm biased. Obviously we wanna be a part
> > of Apache, so this kind of acceptance by the community is amazingly great
> > news!
> >
> >
> > Matt
> >
> &g
Thanks, Carlos, both for the code bidd as well offering to be our 10th
mentor :) Now, I promised mattstep that if we got to 10 mentors, we'd
start creating mentor titles. I was thinking Eternal mentor, Supreme
mentor, but quickly ran out of ideas. Can you take this on?
:D
On Tue, Apr 16, 2013
+1
/* using maven, ran denominator live regression tests on route53,
dynect, ultradns-ws, and rackspace-clouddns with no problems. */
On Tue, Jun 18, 2013 at 5:38 AM, Jim Jagielski wrote:
>
> On Jun 16, 2013, at 10:04 PM, Andrew Bayer wrote:
>
>>
>> [ ] +1
>> [ ] 0
>> [ ] -1 (explain why)
>>
>
+1
checked out tag and ran the following tests successfully
cassandra, aws-ec2 (verified it used t1.micro type)
zookeeper, cloudservers-us (verified it used the 512m flavor)
hbase, cloudservers-us (verified it used the 1024m flavor)
all tests bootstrapped with the cloud-specific user, but execute
+1 I spot tested cassandra on aws-ec2 and zookeeper on
cloudservers-us from the tag. a-ok
-Adrian
On Thu, Mar 24, 2011 at 3:26 PM, Patrick Hunt wrote:
> +1. md5/sha1/gpg all look good. apache-rat:check is clean, and I was
> able to stand up a ZK cluster, use it, then destroy.
>
> Patrick
>
> O
Hi, all.
Mind adding my user AdrianCole with edit rights to
https://wiki.apache.org/incubator/ZipkinProposal? I'd like to help
finalize the proposal.
Best,
-A
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
Fo
nity members through the ASF.
=== Reliance on Salaried Developers ===
Zipkin has one full time salaried developer, Adrian Cole. Though some
of the developers are paid by their employer to contribute to Zipkin,
many Zipkin developers contribute code and documentation on their own
time and have do
ote more time on this project.
>
> [1] https://github.com/openzipkin/openzipkin.github.io/issues/51
> [2] https://github.com/apache/incubator-servicecomb-saga
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Fri, Aug 17, 2018 at 5:29 PM, Adrian Cole
> wr
omogenous Developers ===
> At the time of the writing, OpenZipkin's core 12 developers all work at
> different companies around the globe. Most operate their own tracing sites,
> but some no longer operate sites at all: staying for the community we've
> built. Our ASF champion, M
There was a process involved at Twitter when we first moved it to the
openzipkin organization. It was 100% clear that this was an act for
the community to control the code. Senior management were involved
https://groups.google.com/d/msg/zipkin-user/fbOgEZpuQx4/bWH1-__EmCoJ
After that, all the rep
elow.
>
> Thoughts?
>
> John
>
> [1]: https://github.com/openzipkin/zipkin/graphs/contributors
>
> On Tue, Sep 18, 2018 at 9:25 PM Adrian Cole wrote:
>
> > There was a process involved at Twitter when we first moved it to the
> > openzipkin organ
> Hi,
>
> Is OpenZipkin a formal entity?
>
> What about Lookout who also had a fork (according to the references)?
>
> At Twitter you might try Remy DeCausemaker.
>
> Regards,
> Dave
>
> Sent from my iPhone
>
> > On Sep 18, 2018, at 6:59 PM, Adrian Cole wrote:
with minor
> > contributions as long as we were confident their contributions were under
> > ALv2.
> >
> > Once the community has approved the move to the ASF, any copyright holder
> > or an agent can replace the headers with the ASF header.
> >
> > O
smaller works came from quite a few folks all with the noted
CONTRIBUTORS guidance.
Does this framing help at all with next steps?
Best,
-A
On Thu, 27 Sep 2018, 17:28 Adrian Cole, wrote:
> Hi, all.
>
> Assuming the primary provenance concern is Twitter, I'm looping in
> Ravi who
Thanks tons. I am now watching INFRA-16989 and will follow-up there.
On Thu, Sep 27, 2018 at 5:59 PM Bertrand Delacretaz
wrote:
>
> Hi,
>
> On Thu, Sep 27, 2018 at 5:29 PM Adrian Cole wrote:
> > ...basically I'm sure many of us would like to know where the
> > co
>
> > On Sep 27, 2018, at 2:59 PM, Bertrand Delacretaz
> > wrote:
> >
> > Hi,
> >
> > On Thu, Sep 27, 2018 at 5:29 PM Adrian Cole wrote:
> >> ...basically I'm sure many of us would like to know where the
> >> concerns are and how
Great to see SkyWalking reach this stage. A good example for others!
Good luck for the graduation and will be watching!
Best,
-Adrian
On Tue, Oct 30, 2018 at 4:21 PM Mick Semb Wever wrote:
>
> After discussion in the podling's community on the dev ML
> https://lists.apache.org/thread.html/4ee889
Hello All,
This is a call for vote to release Apache Zipkin Brave Karaf
(Incubating) version 0.1.2
The Apache Zipkin community has voted on and approved a proposal to
release Apache Zipkin Brave Karaf (Incubating) version 0.1.2.
We now kindly request the Incubator PMC members review and vote on
thanks justin. I missed this part about the jar and know there are options
to it.
the license warnings were already resolved for the next release.
On the NOTICE, the headers originally said copyright "The OpenZipkin
Authors" I can put that into a pull request prior to re-cutting.
As recutting, r
> The product name is a problem.
>
> Please explain how this release relates to Apache Karaf? We can give you
> branding guidance once you do.
Sure thing. Zipkin is a tracing system and Brave is the original name
of the tracing libary, and the most widely used one. We currently file
"Brave" under
> Re NOTICE did you project come to the ASF in 2016? Who did it come from, and
> if the headers were changed to ASF ones then they should be mentioned in
> NOTICE.
I've not seen any example of a project noting prior headers like this,
so I winged a pull request. Feedback welcome!
https://github.c
> See [1][2] on policy and many many projects do it except those that were
> developed solely at the ASF.
In practice, you can find many, many that have stock files and were
not developed solely at the ASF.
Considering our statement was "The OpenZipkin Authors", I have not
seen any file at all li
I suspect this has gone around in some incarnations, but I wanted to
bring the topic to the front.
One of the main problems solved in Gradle was environment consistency
through "wrapper scripts". Wrappers lock the version of the tool and
incidental dependencies in order to stabilize the build. Thi
To help others participate, here is the original thread:
https://lists.apache.org/thread.html/8e9b5ec9b8fcc14427bee4dc64f4db7692b787e6349ed348b983d914@%3Cgeneral.incubator.apache.org%3E
Here is the part about the file in question:
> Should this file have an ASF header? [2] Where did it originally
>
> Did the Zipkin project file an SGA? If no, the contribution is all ICLA
> based and you are correct.
> If yes, then AFAIK Justin is correct, but there may be other edge cases.
>
There was no SGA. This particular codebase was also primarily authored by
iCLA signers. In Zipkin, we did an odd th
> Does it help, that I wrote that file and submitted it in a pull request to
> eliminate the binary jar needed prior to my change? ... Guess that's also
> an additional reason why there's an Apache header on it :-)
imho it helps in so far as the work itself (thanks!) and also a subject
matter exp
> But in the end ... if we actually do include code by takari isn't if fair
> to mention it?
>
this is where I am trying to get at actually. is it an intention to change
the NOTICE files
After all it's not just the Java code the wrapper scripts themselves should
> count too.
> And in the end it's
FYI I've asked takari to donate the wrapper to the ASF. It is
important but tiny
https://github.com/takari/takari-maven-plugin/issues/18
Meanwhile, we will remove the wrapper from the source distribution as
putting it in the NOTICE file is something off-putting to a few of our
contributors. We can
We would really prefer us to not have to add a non standard and explicit
line in the NOTICE file about "The OpenZipkin Authors" as it doesnt exist
as a legal entity and even if it did, it didn't sign an SGA.
We would like that to not only be a non-blocker for this release, but also
subsequent ones
are with replies.)
>
> Thanks for your patience regarding the branding issue I mentioned.
>
> > On Feb 14, 2019, at 4:29 AM, Adrian Cole
> wrote:
>
>
>
> > Finally, there was an unresolved question about branding of the repo. I
> > dont think we sh
e/MNG-5937?focusedCommentId=16771456&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16771456
On Thu, Feb 14, 2019 at 4:18 PM Adrian Cole wrote:
>
> FYI I've asked takari to donate the wrapper to the ASF. It is
> important but tiny
> https://github
This vote failed due to binaries in the distribution. Will send a new
vote shortly.
Thanks for the input, all.
-A
On Fri, Feb 15, 2019 at 7:56 AM Adrian Cole wrote:
>
> Perfectly fine naming suggestion. thanks, Dave.
>
> "Apache Zipkin Brave (incubating) for Apache Karaf&quo
Hello All,
This is a call for vote to release Apache Zipkin Brave (incubating)
for Apache Karaf version 0.1.2
The Apache Zipkin community has voted on and approved a proposal to
release Apache Zipkin Brave (incubating) for Apache Karaf version
0.1.2.
We now kindly request the Incubator PMC membe
Thanks to everyone that participated. The vote to release Apache
Zipkin Brave (incubating) for Apache Karaf version 0.1.2 is now
closed. It passed with 6 (+1 binding) votes and no 0 or -1 votes.
Results:
6 (+1 binding) from 姜宁 Willem Jiang, 吴晟 Sheng Wu, Andriy Redko,
Olivier Lamy, John D. Ament, J
Hi, all.
Problems getting subscribed to mailing lists can be crippling. For
example, we have someone stuck in workflow steps where they are
supposed to formally reply to a private@ invitation to join the PPMC.
We've had several people with and without moderator access try to
help. It is really dis
> The infra team is on slack and they are very responsive to sos type of
> questions...
Great! didn't realise that. Thanks
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: genera
for closure. here's the slack info
https://www.apache.org/dev/infra-volunteer#slack
On Wed, Mar 6, 2019 at 10:24 PM Adrian Cole wrote:
>
> > The infra team is on slack and they are very responsive to sos type of
> > questions...
>
> Great! d
Drive by opinion here, since one of the topics is about expiring "merit"
On one hand, you want to encourage participation and people being one
of NNN where NNN are inactive is demotivating
On one hand, you want to immortalize merit, but is an incubator wiki
pile-on indicative of merit?
On one hand
> The standard response to this would be a question in return. Instead of
> "remove inactive members and add new ones" why not just "add new ones".
wires crossed and not IPMC (yet), but I agree with this rationale.
Avoid the loaded topic. focus on the important one.
--
+1 not binding
On Wed, Mar 20, 2019 at 10:38 AM juan pan wrote:
>
> +1 no binding
>
> Best Regards!
>
> -
> Juan Pan (Trista)
> Apache ShardingSphere
>
> On 2019/03/19 05:21:41, "Mick Semb Wever" wrote:
> >
> >
> > After the latest discussion amongst this dev comm
The Apache Zipkin community has voted on and approved a proposal to
release Apache Zipkin Brave (incubating) for Apache Cassandra version
0.10.2. The voting thread can be found here:
https://lists.apache.org/thread.html/c2c55a0e347f90bcb07032b4fa79e34a6832742e7284d7f327583b23@%3Cdev.zipkin.apache.o
Thanks to everyone that participated. The vote to release Apache
Zipkin Brave (incubating) for Apache Cassandra version 0.10.2 is now
closed. It PASSED with 3 (+1 binding) votes and no 0 or -1 votes:
+1 Andriy Redko (binding)
+1 Willem Jiang (binding)
+1 Mick Semb Wever (binding)
Vote thread:
htt
I agree please email the author of the cat photo or find another cat.
This topic is boring and probably there are actual important things we
are defocused from when focusing so massively on this photo.
On Sun, Mar 31, 2019 at 10:51 AM Davor Bonaci wrote:
>
> The issue at hand is simply called the
tabpanels%3Acomment-tabpanel#comment-16805839
I'm excited about netbeans becoming an apache TLP, and also interested
in learning if there are things in that process (beyond the photo
snatching) other podlings like the one I am should be careful of.
Cheers,
-A
On Sun, Mar 31, 2019 at 12:35
I have a related question. In Zipkin (incubating) last release of one of
our projects, we had 3 IPMC +1 votes prior to the formal verification vote.
Then we basically just waited 72hrs anyway with no additional votes but it
didn't matter as we had what we needed (another came later but still) [1]
Directly on this proposal, I agree. In Zipkin (incubating) we are lucky
that mentors are already active.
However, we should not take this for granted and certainly it would be
harder and more fragile if our mentors were not looking carefully and
voting.
-A
On Mon, Apr 1, 2019, 10:30 AM Craig Rus
one part that may not be obvious is the bookkeeping overhead on projects
with many repositories and also the load on the IPMC.
For example in zipkin, we are migrating several repositories. You can
imagine a surge of release verification votes which if people here want to
take the burden of respond
o be doing a bad job at the later vote too.
On Tue, Apr 2, 2019, 9:42 AM Adrian Cole wrote:
> one part that may not be obvious is the bookkeeping overhead on projects
> with many repositories and also the load on the IPMC.
>
> For example in zipkin, we are migrating several repositorie
Parallel would solve our problem of delayed bookkeeping as well. good idea.
It is not so much about about the initial 72 hours, rather the pause
then another 72hrs that someone having to remember. Podlings have a
stateful experience during a release.. they have to know which are in
what stage. vot
is doesn't preclude SO like solutions in our own space, just thinking
aloud.
On Sat, Apr 6, 2019, 7:22 AM Adrian Cole wrote:
> I think we should get legal clarity if folks disagree, but providing
> content under CC license does not stop you from also licensing it under ASL.
>
>
I think we should get legal clarity if folks disagree, but providing
content under CC license does not stop you from also licensing it under ASL.
IOTW, I can give an answer, license that answer simultaneously to two
parties.
Agree that we cant lift other people's content from SO based on its lice
This one had 1 vote cast on the dev list: a +1 from Mick Semb Wever.
Cheers,
-Adrian
On Mon, Apr 29, 2019, 7:23 PM Justin Mclean
wrote:
> Hi,
>
> Out of interest how many mentor / IPMC votes do get on the dev list?
>
> Thanks,
> Justin
>
> ---
d
has the right commands, pasted for convenience to others
(gpg --list-sigs 'Adrian Cole' && gpg --armor --export 'Adrian Cole') >> KEYS
I corrected mine and will help others correct.
-
To
Adrian Cole wrote:
>
> Thanks, Justin. there was a problem in our license header
> configuration that updated that vendored subdirectory. I will revert
> that part (and move the text in the wrong spot) in the next release
> which will be next week.
> https://github.com/apache/incub
Thanks, Justin. there was a problem in our license header
configuration that updated that vendored subdirectory. I will revert
that part (and move the text in the wrong spot) in the next release
which will be next week.
https://github.com/apache/incubator-zipkin/issues/2567
Please let us know if t
FYI there was another binding +1 vote on the other thread from Ignasi Barrera
https://lists.apache.org/thread.html/fcc730ad01eb55293f7a174a3b5301f4a277b6222c7bb821d33faf2e@%3Cdev.zipkin.apache.org%3E
On 2019/05/07 14:25:42, Raja Sundaram Ganesan wrote:
> Hello IPMC
> The Apache Zipkin community
Hi, all.
During a release vote, it can be tempting to tack on feedback about
things not being voted on, but pertain to the eventual graduation of a
project. For example, some glitch about content on a website. In
projects with only one or few codebases, it can maybe make sense to
conflate things r
Hello IPMC
The Apache Zipkin community has voted on and approved a proposal to release
Apache Zipkin (incubating) version 2.14.0. The voting thread can be found here:
https://lists.apache.org/thread.html/03b215cc4a6e10a7092fe39b6ce87d3a964f35b6e181e12da4d45432@%3Cdev.zipkin.apache.org%3E
This vo
Thanks justin. Opened an issue to polish this eventhough these files
won't survive graduation.
https://github.com/apache/incubator-zipkin/issues/2602
On Fri, May 17, 2019 at 10:04 AM Justin Mclean wrote:
>
> Hi,
>
> +1 (binding) but there some improvements that can be made.
>
> I checked:
> - inc
FWIW I tried this just recently and was requested to not do it again. Worth
knowing
https://lists.apache.org/thread.html/0571e9dd1b7711c588a38d8a664378ce7df31c72592edcbe8ab8a72b@%3Cgeneral.incubator.apache.org%3E
On 2019/04/02 09:30:10, Geertjan Wielenga
wrote:
> Maybe the PPMC and IPMC vote
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
> at least discuss it with the IPMC first and give them a heads up that you
> are doing so.
>
> Thanks,
> Justin
> -
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
> 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
incubat
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
On
Beans 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.
&
Thanks to everyone that participated. The vote to release Release
Apache Zipkin (incubating) version 2.14.0 is now closed. It PASSED
with 5 (+1 binding) votes and no 0 or -1 votes:
+1 Willem Ning Jiang (binding)
+1 Sheng Wu (binding)
+1 Andriy Redko (binding)
+1 Michael Semb Wever (binding)
+1 Jus
Hello Community,
The Apache Zipkin (incubating) team is pleased to announce that Zipkin
2.14.0 has just been released.
Apache Zipkin (incubating) is a distributed tracing system. It helps
gather timing data needed to troubleshoot latency problems in
microservice architectures. It manages both the
Hi, all.
We tripped on some bugs related to maven projects generating the file
DEPENDENCIES which includes information about runtime dependencies. We
marked this as a graduation blocker assuming that is required.
Later, we noticed a certain lack of clarity on how to handle this for
javascript.. T
Thanks, Justin. Crystal clear!
On Sun, Jun 2, 2019 at 3:58 PM Justin Mclean wrote:
>
> Hi,
>
> > Can someone clarify if packaging a file named DEPENDENCIES is required
> > or a nice-to-have?
>
> It’s a nice to have. You’re releases do need to have no Category X licence
> (e.g. GPL) dependancies.
wouldnt it be fair to keep the incubator benefit adjectives away from words
like reliable and production ready?
If I am not mistaken, almost all of the efforts are around ceremony around
the code, not whether it works. In fact the slowing of the community hurts
production ness as it is far slower
> > As others have mentioned, such release bugs would be labelled as blocking
> > for graduation. Ideally the bug ticket numbers would be listed in a
> > disclaimer file within the release.
>
> Interesting idea, that list would need to be kept up to date in there. It
> might be easier to just tag
Hi, all.
Through Zipkin's incubation, I noticed that knowledge of state of the
art is not equally distributed. Some voting approaches already in use
aren't known. Also what you can use to automate isn't known. As
podlings don't always know the right questions to ask, it might be
beneficial for fut
> If the mentors on the project list have voted +1, then the vote can be
> continued in parallel? Shouldn't this help reduce both the time votes take
> but not waste the limited IPMC bandwidth?
That's exactly what we tried and were given grief about. We waited
until 3 binding +1 votes, which is
Hi, all
I just noticed that all states in the diagram are under the assumption
that the only way a project stops is by the IPMC making a decision for
the project, saying they have no community etc.
https://incubator.apache.org/policy/process.html#termination_or_retirement
A route not listed is t
as there was little progress inside incubator, the far easiest on
everyone is to resume our old "io.zipkin" group ids. We have no plans
to use any apache namespaces as it represents one release of several
out of many projects. Least surprising and distracting is a
straightforward revert.
-A
On Mo
on the maven topic:
for almost all cases there will be no classpath problem. the most common
entry point into maven was the package for "brave" which was never released
under an apache group id. the underlying libraries had very few call sites
in comparison. the "bom" most commonly used was also n
community as I do I would rate the other
packages released as a super high priority concern these are low level or
niche libraries. it would have been a problem if we released brave but we
didn't luckily.
On Tue, Jun 18, 2019, 5:33 PM sebb wrote:
> On Tue, 18 Jun 2019 at 00:40, Adr
of course I meant "packages released as a *not* super high priority concern"
On Tue, Jun 18, 2019, 5:37 PM Adrian Cole wrote:
> if you would like to do, this feel free. this type of concern seems more
> like a github issue vs an incubator discussion. we have changed group i
84 matches
Mail list logo
