Community-Help for the core-team in deadline-times

Sebastian Sickelmann sebastian.sickelmann at
Tue Dec 1 11:27:07 UTC 2015

On 11/23/2015 10:03 PM, dalibor topic wrote:
> On 20.11.2015 14:57, Martijn Verburg wrote:
>> support.  What this group could perhaps do is split up the mailing lists
>> and have at least one of us watching all of the mailing list for new
>> contributors and making sure that their contributions don't get
>> lost/ignored.
> The most useful way to do that is to be sufficiently actively involved
> in a sufficient Project Role and technically educated in the
> development of the Project to be able to participate in the review &
> shepherding of incoming contributions directly.
That was more or less the idea. In times like those mentioned I would
read some mailing-list a little bit more actively than usual. Today I
read only those topics that seems to be relevant to what I want to do.
Or where the topics seems interesting to me. I am not a reviewer but I
can give contributors feedback what I can see in the suggested
contribution and I can help them find the right information of how to
contribute, ex. when the format is not in the right shape. In times
where deadlines are near I would widen my help to scan for messages that
are not answered for a long time and take a lock at them if I can
help(see above). If it is a new contributor (I can manually check the
census and the public available OCA list and markmail archives) i would
offer my help and make why I am answering the post. I do not want to
track someone personal and I do not want to blame any
My answer will contain some information about the adoption-discuss-list,
that i am nether an expert or an reviewer in this topic, but ....(what
ever I can see where I can help).

The only problem I have is to know when there is a deadline nearing.
Actually I only have the jdk9 schedule, but there may be other deadlines
i do not know.

> Without that, you would basically end up with a bunch of people not
> doing the actual work monitoring those who do.
> That's rarely very appreciated, and even less useful than it sounds,
> as there could be any reason why two minds don't meet. Most of those
> reasons are perfectly valid, and don't have to be explained or excused
> publicly.
>> We could set up a simple table in the Wiki with name vs mailing list and
>> have the results of the monitoring reported back here
> The trouble with coming up with surveillance infrastructure is that
> typically people being singled out for surveillance have not consented
> to it.
> In other words, don't create wiki pages that track what other people
> do, whether they are at a conference, or on vacation, submitted a
> patch and didn't reply or get a reply for $PERIOD, and so on.
> That would not be helpful.
I totally agree with you dalibor. And I hope that my suggestion(without
any monitoring, statistics, etc.) is not breaking any community matter
of course.
> cheers,
> dalibor topic

More information about the adoption-discuss mailing list