Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [nattable-dev] Committer status
Hi,

I just wanted to ping on this request. If I don't get further response till the end of this week, I will start cleaning up our committers.

Greez,
Dirk

P.S. To repeat my statements: That doesn't mean anybody gets banned forever, just removed until you are able to be more active.


On Fri, Nov 22, 2013 at 2:28 PM, Dirk Fauth <dirk.fauth@xxxxxxxxx> wrote:
Hi,

if I remove the committer state from inactive users, it only means that contributions can not be committed without previous checks. Edwin and I did a lot in stabilizing NatTable 1.x, but there is still some code that should be banned IMHO (like opening a new Thread in the SummaryRowLayer for every summary value, and that by using new Thread() for example). Sometimes little things, sometimes big issues, and I don't know how much of that stuff the inactive committers noticed or are aware of.

So removing inactive users simply means to remove the rights to modify the build process or push directly into the repository.
- if you like to contribute, please go ahead :)
- if you want to step up as active committer at a later time, you're welcome

I'm also thinking about using Gerrit for contributions to make it easier for everyone to contribute and validate.

For me removing inactive users means:
- showing the community that there are not 7 but only 3 active committers (from which 2 are also not very active ATM)
- ensure that there is no code change pushed that is not verified before (my wrong commits are bad enough)

Greez,
Dirk


On Fri, Nov 22, 2013 at 2:16 PM, Matt Biggs <zebbedi@xxxxxxxxx> wrote:
Hi,

Sorry we haven't really been in touch. We do very much still use NatTable, but we just haven't had the time to be able to contribute anything back, and really don't know when we will get more time. We are still interested in contributing, but if you wish to remove inactive users, then we will have to maybe re-apply at a later date?

Cheers
Matt


On 22 November 2013 10:54, Dirk Fauth <dirk.fauth@xxxxxxxxx> wrote:
Hi everybody,

with the current happenings and plannings for NatTable it is time to clean up the project structure.

As a short update:
  1. We want to release a NatTable 1.1 version soon, no concrete date, but only a few things should be finished till then
  2. We are planning to freeze the NatTable 1.x branch after releasing 1.1. This is because we noticed that the current architecture has reached it's limits and every new feature, enhancement or even bugfix is quite a pain since NatTable has grown the way it is now

With the freeze I also want to clean up. Seeing 7 listed committers feels strange when looking at the diagram that shows only 3 active ones. Also we haven't heard from the others for more than a year now. Edwin said that he wanted to get in touch with them, but as Edwin seems to be not able to work on NatTable for a while, I'll take the part until he's back (and hopefully this doesn't take too long!).

So with this mail I ask all of the listed committers to respond about their status. Are you still interested in working on NatTable or do you have new jobs and are not able to work on NatTable anymore?

Greez,

Dirk


_______________________________________________
nattable-dev mailing list
nattable-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/nattable-dev



_______________________________________________
nattable-dev mailing list
nattable-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/nattable-dev



Back to the top