[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pfsense-dev
Subject:    [pfS-Dev] the reality of community contributions
From:       Franco Fichtner <slashy83 () gmail ! com>
Date:       2014-03-30 8:51:36
Message-ID: 15CD9B29-CE84-47B6-9E66-E29242CF1B23 () gmail ! com
[Download RAW message or body]

Hi Jim,
hi Chris,
hi Ermal,
hi everybody,

so it has happened again.  I really like the project; I really like contributing.
What I don't like is that numerous pull requests linger unattended, uncommented.  And then
it happens that pfSense developers go ahead and commit the changes themselves, like this
one:

https://github.com/pfsense/pfsense/commit/1b60c644c9c64a27386d0506fc5e7e557060a2c2

There has been a pull request to do just that and a little bit more:

https://github.com/pfsense/pfsense/pull/1032/files

What's worse is that this is not the first time this happened.  I've had similar pull
requests in the tools repository that weren't attended to only to have them show up
three months later as official commits.  I can't prove this since the tools repo is
gone, but then again I don't really have to.  There's a gap between the accusation that
companies don't contribute and the whole "we are an active open source community" vibe
that has been promoted lately. I think most people here on the list already know that.

If you want sustainable community support, then you ought to step up your game.  And if
you want to be picky about what goes in and what not then at least say so.  It's just
that this current way of doing things isn't working very well for pfSense in the long
run.


Cheers,
Franco
_______________________________________________
Dev mailing list
Dev@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/dev
[prev in list] [next in list] [prev in thread] [next in thread]