Andrew,
I understand your frustration as I think you do ours. As users of a
free product, we definitely shouldn't be making any demands (ever!), but
nothing wrong with complaints/feedback, we just cant demand those
changes, etc. I think a lot of people are just venting right now out of
disappointment since we love this app so much and in all honesty,
nothing comes even close to the feature set, quality, and the great
support you do give us.
Like I have said before, I think the biggest hurdle to getting more
contributors to the project is that the application is mainly
used/installed by system administrators and python is not typically one
of those languages that they are strong at. Add a couple frameworks on
top of that and it reduces the possible number of contributors by even
more. Something like php or perl would have open the doors a bit wider
to possible contributors.
I will add though that hen we find bugs, design flaws, make
suggestions, etc, that IS actually contributing in a small way though as
it makes your solution better for yourself, but also for your paying
clients which I am sure you use the software for. Especially if you are
offering a SaaS solution on the side.
Anyway, thanks again for your efforts and hard work. Please do not get
any criticism get you down as I know thats the last thing that is going
to motivate you to do more for us.
Regards,
Mark
On 2012-10-10 07:59, Andrew Colin Kissa wrote:
You clearly failed in understanding the gist of the issue so i will
respond to the issues you have raised.
On 10 Oct 2012, at 2:14 PM, Anis Jendoubi wrote:
- you're the only boss of your project, which is ok in initial
processes but not at this stage of the project.
I could not agree more.
- you keep the baruwa under your own control and not letting anyone
join the one person team, and you know well what I mean by that ;)
I frankly do not know what you mean by i do not let anyone join. The
door is open this is a meritocracy, you contribute
code, documentation, translations or help out other users and you are
in. I have never turned away anyone who wants
to join the "team"
- you made the project opensource that we thank you for that (the
proof is that you got a lot of thanks for the nice project on this
mailing list), however it feels like you're not building the community
well (bringing additional developpers on board).
How do you suggest i do that, i have done everything open source
projects do short of dragging contributors to contribute
i cannot do more.
- there are thousands of opensource projects that were ripped and
made benefit for others without bringing benefits to the original
developpers (as a simple example you can take snort which was overused
commercially through other known businesses before it showed that all
their products were based on the opensource snort engine), so IMHO you
can't opensource something if you start think that everyone will use
it and benefit from it, that's not the "opensource" approach if you
know what I mean, just don't opensource it and that's it.
You clearly do not get it, the people who use snort actually make an
effort to make it better, write code, write documentation
integrate it with other products etc, they do not expect the original
developers to do all that while the seat back and spend
their time enjoying the finer things in life.
The point am trying to make is the open source echo system must be
symbiotic not one sided.
To be blank, For example i use Exim am not going to spend my sunday
writing postfix plugins just to look cool coz i have no
use for them that is where the open source approach kicks in, someone
who uses postfix must write that to solve his own
problem.
Until someone actively participates in making the project better, i
will not listen to their grand standing. Like Linus always
says show me the code.
- Andrew
--
www.baruwa.org
_______________________________________________
Keep Baruwa FREE - http://pledgie.com/campaigns/12056
_______________________________________________
Keep Baruwa FREE - http://pledgie.com/campaigns/12056
