Fwd: Google Summer of Code 2016 is coming

[Roman Shaposhnik]

FYI.  Please make sure to follow Ulrich's instructions and label the ideas
in JIRA as he's askit to.

It is extremely important for us since GSOC has been a really great
way to grow (and retain!) new members of the community!

I would really encourage at least 2 volunteers from every podling
community to consider mentoring for GSoC. Please reply to me
personally (IN ADDITION TO FOLLOWING THE INSTRUCTIONS
BELLOW) if you are offering to be a mentor.

Really hoping for your help!

Thanks,
Roman.


-- Forwarded message --
From: Ulrich Stärk 
Date: Wed, Feb 10, 2016 at 12:16 PM
Subject: Google Summer of Code 2016 is coming
To: ment...@community.apache.org


Hello PMCs (incubator Mentors, please forward this email to your podlings),

Google Summer of Code [1] is a program sponsored by Google allowing
students to spend their summer
working on open source software. Students will receive stipends for
developing open source software
full-time for three months. Projects will provide mentoring and
project ideas, and in return have
the chance to get new code developed and - most importantly - to
identify and bring in new committers.

The ASF will apply as a participating organization meaning individual
projects don't have to apply
separately.

If you want to participate with your project we ask you to do the
following things as soon as
possible but by no later than 2016-02-19:

1. understand what it means to be a mentor [2].

2. record your project ideas.

Just create issues in JIRA, label them with gsoc2016, and they will
show up at [3]. Please be as
specific as possible when describing your idea. Include the
programming language, the tools and
skills required, but try not to scare potential students away. They
are supposed to learn what's
required before the program starts.

Use labels, e.g. for the programming language (java, c, c++, erlang,
python, brainfuck, ...) or
technology area (cloud, xml, web, foo, bar, ...) and record them at [5].

Please use the COMDEV JIRA project for recording your ideas if your
project doesn't use JIRA (e.g.
httpd, ooo). Contact d...@community.apache.org if you need assistance.

[4] contains some additional information (will be updated for 2016 shortly).

3. subscribe to ment...@community.apache.org; restricted to potential
mentors, meant to be used as a
private list - general discussions on the public
d...@community.apache.org list as much as possible
please). Use a recognized address when subscribing (@apache.org or one
of your alias addresses on
record).

Note that the ASF isn't accepted as a participating organization yet,
nevertheless you *have to*
start recording your ideas now or we will not get accepted.

Over the years we were able to complete hundreds of projects
successfully. Some of our prior
students are active contributors now! Let's make this year a success again!

Cheers,

Uli

P.S.: Except for the private parts (label spreadsheet mostly), this
email is free to be shared
publicly if you want to.

[1] https://summerofcode.withgoogle.com/
[2] http://community.apache.org/guide-to-being-a-mentor.html
[3] http://s.apache.org/gsoc2016ideas
[4] http://community.apache.org/gsoc.html
[5] http://s.apache.org/gsoclabels

Re: PRs submitted over public Github repo

[Colin P. McCabe]

I think it would be more appropriate to shadow the pull request to
JIRA, since in order to go in, all contributions need a JIRA + review
from committers.  Let's continue this discussion on INFRA-11298.

best,
Colin

On Fri, Feb 19, 2016 at 3:27 PM, Lewis John Mcgibbney
 wrote:
> I am of the opinion that we should definitely have the PR's being shadowed
> to this list.
> It provides us with context about new contributions and more importantly
> new community members.
> Thanks Andrey for hitting the lists and letting us know about that.
> I filed https://issues.apache.org/jira/browse/INFRA-11298 to address this.
> Thanks
>
> On Fri, Feb 19, 2016 at 3:22 PM, <
> dev-digest-h...@htrace.incubator.apache.org> wrote:
>
>>
>> -- Forwarded message --
>> From: Andrey Redko 
>> To: dev@htrace.incubator.apache.org
>> Cc:
>> Date: Thu, 18 Feb 2016 07:47:50 -0500
>> Subject: PRs submitted over public Github repo
>> Hey Devs,
>>
>> I am wondering if anyone is watching the PRs submitted over public Github
>> repo  (http://github.com/apache/incubator-htrace/)?
>> Would be great to have some feedback on those.
>> Thank you.
>>
>> Best Regards,
>> Andriy Redko
>>
>>
>>

Re: HTrace 4.1 release candidate 2

[Colin P. McCabe]

Our compatibility policy (see
http://mail-archives.apache.org/mod_mbox/htrace-dev/201509.mbox/%3c55f8badc.4050...@oss.nttdata.co.jp%3E
) only covers the htrace-core4 API right now.  So we can guarantee
that any projects using htrace-core 4.0.1 can upgrade to htrace-core
4.1.0 without breaking anything.  (This is a more painful guarantee
than it sounds since it means we can't remove functions, only
deprecate them...  And so forth.)  But it's a very useful guarantee
for our downstream projects.

However, we don't support mixing and matching versions of the
SpanReceiver client and server components.  The admin has to roll out
a uniform version of those components-- for example, using htraced
4.0.1 with htrace-htraced.jar 4.1.0 is not supported.  The rationale
for this limitation is that tracing can simply be disabled for a brief
period during the rolling upgrade process.  Also, the different
SpanReceiver subprojects are at different levels of maturity, and
imposing heavy compatibility guarantees would slow down development
for no real gain.

best,
Colin


On Fri, Feb 19, 2016 at 4:32 PM, Stack  wrote:
> Can a 4.0.1 client talk to a 4.1.0 htrace? Has it been tested?
> St.Ack
>
> On Tue, Feb 9, 2016 at 7:00 PM, Colin P. McCabe  wrote:
>
>> Hi all,
>>
>> I've posted the second release candidate for HTrace 4.1 here:
>>
>> http://people.apache.org/~cmccabe/htrace/releases/4.1.0/rc2/
>>
>> The jars have been staged here:
>>
>> https://repository.apache.org/content/repositories/orgapachehtrace-1022
>>
>> Compared to rc1, this rc includes HTRACE-334 and HTRACE-342.
>>
>> HTrace 4.1 brings a lot of robustness improvements.  There were major
>> improvements to htraced and the web UI, as well as new metrics added.
>> There were numerous build fixups, and we added Docker support, to
>> ensure a repeatable build.
>>
>> Check it out.  The vote will run for 5 days.
>>
>> cheers,
>> Colin
>>
>>
>> Release Notes - HTrace - Version 4.1
>> ** Bug
>> * [HTRACE-114] - Fix compilation error of htrace-hbase against
>> hbase-1.0.0
>> * [HTRACE-238] - Change maven compiler source level to 1.7 to
>> match targetJdk
>> * [HTRACE-243] - Remove duplicate maven-assembly-plugin
>> configuration section in htrace-htraced/pom.xml
>> * [HTRACE-245] - NOTICE.txt: change "developed by The Apache
>> Software...” to "developed at The Apache Software...”
>> * [HTRACE-246] - HTrace WebApp not properly defined and therefore
>> not packaged into .war
>> * [HTRACE-248] - HTraced should gracefully shutdown if stopped
>> * [HTRACE-249] - Script and doc on how to publish website
>> * [HTRACE-251] - Fix "mvn clean" target
>> * [HTRACE-253] - Tracer loadSamplers and loadSpanReceivers logs
>> are too chatty
>> * [HTRACE-256] - Change the artifactId for htrace-core in branch
>> 4.0 to be htrace-core4
>> * [HTRACE-257] - htrace-htraced: add web symlink rather than
>> generating programmatically
>> * [HTRACE-262] - Temporarily suppress doclint for Java 8 to
>> prevent build failure
>> * [HTRACE-266] - Make the CLIENT_REST_MAX_SPANS_AT_A_TIME_KEY
>> config key more consistent with other configs
>> * [HTRACE-267] - Move owl logo licensing information from NOTICE to
>> LICENSE
>> * [HTRACE-268] - Remove Units and go-codec from LICENSE since they
>> are not contained in the source release
>> * [HTRACE-272] - TracerPool must not load multiple inscance of
>> same receiver class when a simple classname is given
>> * [HTRACE-279] - Fix issues where the HTracedSpanReceiver was
>> using the wrong JSON serialization for spans and add validation to
>> htraced REST ingest path
>> * [HTRACE-280] - htraced: add metrics about total spans added and
>> dropped per address
>> * [HTRACE-281] - htraced: add example/htraced-conf.xml
>> * [HTRACE-282] - htraced: reap spans which are older than a
>> configurable interval
>> * [HTRACE-283] - Heartbeater should wait for goroutine to finish on
>> close
>> * [HTRACE-284] - htrace-htraced, htrace-flume: do not treat the
>> shaded version of commons-logging as provided
>> * [HTRACE-285] - htraced tool: fix query parsing and add query_test
>> * [HTRACE-289] - Fix TraceEnabled, etc. logger methods for
>> conditional logging
>> * [HTRACE-294] - htraced: fix some metrics issues
>> * [HTRACE-297] - htraced: avoid serializing spans to json unless
>> TRACE logging is enabled
>> * [HTRACE-300] - Reaper should be initialized before shards are
>> activated
>> * [HTRACE-301] - htraced: fix unit tests that aren't waiting for
>> spans to be written, use semaphore for WrittenSpans
>> * [HTRACE-302] - htraced: Add admissions control to HRPC to limit
>> the number of incoming messages
>> * [HTRACE-304] - htraced: fix bug with GREATER_THAN queries
>> * [HTRACE-307] - htraced: queries sometimes return no results even
>> when many results exist due to confusion in iterator usage
>> * 

Re: PRs submitted over public Github repo

[Lewis John Mcgibbney]

I am of the opinion that we should definitely have the PR's being shadowed
to this list.
It provides us with context about new contributions and more importantly
new community members.
Thanks Andrey for hitting the lists and letting us know about that.
I filed https://issues.apache.org/jira/browse/INFRA-11298 to address this.
Thanks

On Fri, Feb 19, 2016 at 3:22 PM, <
dev-digest-h...@htrace.incubator.apache.org> wrote:

>
> -- Forwarded message --
> From: Andrey Redko 
> To: dev@htrace.incubator.apache.org
> Cc:
> Date: Thu, 18 Feb 2016 07:47:50 -0500
> Subject: PRs submitted over public Github repo
> Hey Devs,
>
> I am wondering if anyone is watching the PRs submitted over public Github
> repo  (http://github.com/apache/incubator-htrace/)?
> Would be great to have some feedback on those.
> Thank you.
>
> Best Regards,
> Andriy Redko
>
>
>

Re: HTrace 4.1 release candidate 2

[Lewis John Mcgibbney]

Hi Colin,

+1 from me. All my usual tests have passed and I am happy with this RC.
Apologies for late review. This one dropped off the TODO list of TODO's :)
Good job Colin and team. :)

On Tue, Feb 9, 2016 at 7:00 PM,  wrote:

>
> Subject: HTrace 4.1 release candidate 2
> Hi all,
>
> I've posted the second release candidate for HTrace 4.1 here:
>
> http://people.apache.org/~cmccabe/htrace/releases/4.1.0/rc2/
>
> The jars have been staged here:
>
> https://repository.apache.org/content/repositories/orgapachehtrace-1022
>
> Compared to rc1, this rc includes HTRACE-334 and HTRACE-342.
>
> HTrace 4.1 brings a lot of robustness improvements.  There were major
> improvements to htraced and the web UI, as well as new metrics added.
> There were numerous build fixups, and we added Docker support, to
> ensure a repeatable build.
>
> Check it out.  The vote will run for 5 days.
>
> cheers,
> Colin