Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tracecompass-dev] Vote for Committer status for Jean-Christian Kouame was started by Matthew Khouzam

Hi Alex

I agree with Genevieve that the nomination was bound to happen after all the contribution JC did since he has started working on the project as part of our development team at Ericsson.

The XML pattern analysis that was part of his master thesis is one of his biggest contribution so far. Beside that he contributed the XML Analysis manager, search capabilities in the Time Graph view as well as many bugfixes.

He'll continue working on Trace Compass full-time as part of our team.

All this and his proven commitment to the project, his nomination was more than deserved.

As a last note, for his nomination we applied the same standard that we applied when we nominated you as committer back in the Linux Tools project.

Best Regards
Bernd


On 04/22/2016 09:38 AM, Geneviève Bastien wrote:
Hi Alex,

This nomination doesn't come "out of the blue". The timing corresponds
to the submission of the last patch of his biggest contribution so far:
the XML pattern. We've all been there, our committership pending some
important contribution.

Also, JC's nomination in itself is no surprise. He has been working on
the project for many years, as intern, then master student and now
employee. It was just a matter of time. Most of us, except maybe you,
have been working closely with him in the last few months/weeks to
review his patches, so it is no big surprise.

It certainly could have been mentioned at the last meeting, given that
the submission of his patch was imminent. But unfortunately, it wasn't.
And here is the nomination. Do you really want to postpone it just so we
can discuss it?

But let it be guidelines for the next time a committer is nominated. We
should not take for granted any committer's vote, especially now that
there is 3 institutions involved: Ericsson, Poly and Efficios, we cannot
assume everyone knows what everyone else is doing.

Cheers,
Geneviève



On 04/21/2016 08:02 PM, Alexandre Montplaisir wrote:
Hi everyone,

Before anything, I want to make it clear that I have *no* doubts about
Jean-Christian's technical abilities and capabilities at being a
committer. In the proper circumstances I would gladly give him a +1.

However I am somewhat concerned by this "surprise" nomination. These
things should be discussed with everyone involved in the project
beforehand.

We had a project meeting just last Friday with almost all the
committers present. This would have been the perfect opportunity to
mention and present this nomination. Instead it just arrived out of
the blue on the mailing list, and with the voting deadline before the
next meeting.
The timing also does not seem ideal, with everyone working
relentlessly towards the feature freeze.

This situation is not ideal. If we can nominate anyone anytime without
prior discussions, then it means there is no real process at becoming
a comitter. Which greatly reduces the value of being a "committer" in
the first place.

What would you say if instead we postpone JC's nomination to after the
rush of the release? And after a proper introduction and discussion
during a project meeting.

Again, this is nothing against JC in particular. I am only arguing in
favor of a solid process, and a good timing for doing things.

What do you think?


Cheers,
Alexandre



On 2016-04-19 03:09 PM, portal on behalf of wrote:
tools.tracecompass Committers,
This automatically generated message signals that Matthew Khouzam has
nominated Jean-Christian Kouame as a Committer on the tools.tracecompass
project. The reason given is as follows:

It is a great honour to nominate Jean Christian Kouame as a committer
for
trace compass. He committed over 80 patches to the project already. He
actively reviews patches from colleagues, takes open source very
seriously
and make my office a much more pleasant place to work.

Here are some of his commits.

3a5f73a tmf : Add pattern analysis behavior
93206da tmf : Move preconditions at the same level as states in the XML
file
206243f doc : Add user guide for time graph Find dialog
3629942 tmf : Add search dialog to timegraph views
0b563c2 tmf : Add parameters to XML core methods
5b901f9 tmf : Add latency statistics view for the pattern analysis
abda4cb analysis : Abstract the latency statistics analysis
0b9fc6d analysis : Remove checkNull() in Segment store statistic viewer
3b5dc74 tmf : Add latency density view for the pattern analysis
c8e5d00 tmf : Add latency scatter graph view for the pattern analysis
38fad53 tmf : Add latency table view for the pattern analysis
38e2a2e tmf : Introduce the modules for the XML pattern analysis
667601bf1 analysis : Introduce ISegmentListener
65a4afc analysis : Introduce buildAnalysisSegments() in Segment Store
analysis
5cca8ca doc : Remove documentation for 'Import XML analysis'
d570387 doc : Add documentation for XML analyses manager
f1c5294 statesystem : Add a default compareTo() for segments
73c74de analysis : Rename getResults() to getSegmentStore()
fa6e786 tmf : Move initialization steps of modules into analysisReady()
method
c81ffdf tmf : Make waitForInitialization() return a boolean
6537ccd tmf : add waitForInitialization() to
ITmfAnalysisModuleWithStateSystem
2fd6b08 tmf : Add test suite for the pattern segment builder
2e1183f tmf : Introduce pattern segment and pattern segment builder
cb11754 tmf : Fix potential null pointer dereference in XmlUtils
95a795f tmf : Remove import XML analysis command
f98e9db tmf : Add manager for XML analysis files
4af6758 tmf : Fix get analysis modules when executing analysis in
TmfTrace
74f8a7e tmf : Add a test to validate an XML pattern file
f038dfa tmf : Add the XML Schema Definition for the pattern matching
analysis
cbac1ac tmf : Improve toString() in TmfXmlStateValue and TmfXmlCondition
f0fd223 tmf : fix the 'Not' condition in TmfXmlCondition
8b6aede tmf : add of a range selection from other sources for the
tmfEventsTable
1010de5 tmf : Fix the xml condition multiple problem
900cbf8 tmf : Add test suite for the XML conditions
b39b8c5 tmf : Add comparison between two state values in the XML core
0a94b7d tmf : use of StringBuilder.append() instead of String operator +
7720848 tmf : remove occurrences of literals in
FilterTreeLabelProvider.java
cab535e tmf: Use prioritized List instead of Set in XmlStateProvider
c42ec90 tmf : Remove of unused import
89d0681 tmf : Use of Activator.logError() instead of
System.out.println()
651cbda tmf : Remove inefficient new String(String) constructor
f6c0ef7 lttng : Remove inefficient new String(String) constructor
a83a418 tmf : Avoid concatenating nonliterals in a StringBuilder
787117a lttng : Remove inefficient new String(String) constructor
41d89c0 tmf : Avoid concatenating nonliterals in a StringBuilder
560e259 tmf : Avoid concatenating nonliterals in a StringBuilder
1ff5d16 tmf : Use of Activator.logError() instead of
System.err.println()
0d57407 tmf : Avoid concatenating nonliterals in a StringBuffer
1124938 tmf : Remove inefficient new String(String) constructor
f1ee92f tmf : Use StringBuilder in TmfRawEventViewer
27a4031 tmf : Add constant modifier to fields in TimeGraphViewer
10957ea lttng : Remove  inefficient new String(String) constructor
5ea5357 analysis : Add constant modifier to a field
8e22bf2 tmf : Avoid concatenating nonliterals in StringBuilder
7cd2b0a lttng : Add constant modifier to a field
4237a64 tmf : Avoid concatenating nonliterals in a StringBuilder
5e1ee19 tmf : Avoid concatenating nonliterals in a StringBuilder
ab9ca7e tmf : Replace String() by an empty string "" in getHelpText
a194b17 tmf : Remove literals duplication in TmfXmlReadWriteStateValue
9922fcd tmf : Remove duplicate literals in TmfRawEventViewer
72f6827 tmf : Refactoring the comments in TmfRawEventViewer
058f8b3 tmf : Use Arrays.asList() instead of a loop
2b3be04 tmf : remove duplicated lines in TimeGraphScale.java
d88818e gdbtrace : remove occurrences of literals
2f4ad53 tmf : use of StringBuilder.append() instead of operator + for
strings
f8d9788 tmf : Change the order of modifiers of reinitializeCharts() in
TmfPieChartViewer
473d89d tmf : extract duplicate code into sortNodes() in GraphNode
a94e5ef tmf : use of the map values instead of keyset
7d8d08a tmf: Delete unused code in GraphNode
21c2ae8 tmf : Redefine CompareTo() in EventOccurrenceObject
42618bb tmf: Avoid duplicate literals in GraphNode
61d1a49 tmf.ui : Iterate in OffsetTraceHandler using the entryset
instead
of the keyset
22740f5 tmf.ui : use an entryset instead of a keyset in the GraphNode
7d59bbe tmf : add a mipmap section in the developer guide
95aa81e tmf : Update the histogram to handle lost events correctly
8d534d6 tmf : show environment variables of traces under Experiments
b73145e CTF : Handle traces with events without eventID
3b11ddc ctf: Move integer pretty-printing to IntegerDefinition
4962833 tmf: Show trace environment variables in the Properties view
ecce5d2 tmf : Fix binary search end time in InMemoryBackend
459f705 TMF : Bug 385217 - Display 64 unsigned integers correctly
029df6e TMF: change callsite action text


    * https://bugs.eclipse.org/bugs/show_bug.cgi?id=385217

The vote is being held via the MyFoundation portal: voters *must* use
the
portal for the votes to be properly recorded.  The voting will continue
until either all 7 existing Committers have voted or until they have
been
given enough time to vote, even if they do not do so (defined as at
least
one week). Jean-Christian Kouame must receive at least three +1s and
no -1s
for a successful election.

Eligible Committers must cast their votes through their My Foundation
portal page (do NOT just reply to this email; your vote will not be
correctly recorded unless you use the portal):

      http://portal.eclipse.org/

The project Committers eligible to vote are:

      Genevieve Bastien
      Francis Giraldeau
      Bernd Hufmann
      Matthew Khouzam
      Marc-Andre Laperle
      Alexandre Montplaisir
      Patrick Tasse

*NOTE*: Successful elections are left open for a maximum of 120 days to
allow for processing of paperwork.  After that time the election will be
expired, regardless of its current status.  Should papework
processing on
the part of the candidate take more time than allowed, a new election
will
have to be held.

If you have any questions, please do not hesitate to contact your
project
lead, PMC member, or the EMO <emo@xxxxxxxxxxx>

_______________________________________________
tracecompass-dev mailing list
tracecompass-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/tracecompass-dev
_______________________________________________
tracecompass-dev mailing list
tracecompass-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/tracecompass-dev

_______________________________________________
tracecompass-dev mailing list
tracecompass-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/tracecompass-dev




Back to the top