Lets make Concrete5 Better: Bugs Bounty
Permalink
I just have an idea
How about make the February is the Bug Bounty Month.
We try to give rewards to developer (concrete5 or outside developer) which can solve the concrete 5.5.1 bugs.
The criteria we need to discuss it:
Developer with most solve the bugs, or maybe by point system.
Performance improvements can be also counted if significant.
we need some committee:
some from Concrete5 team.
some from outside developer (with minimum x badges/ we can vote)
I will donate between $ 100 (if less than 20 bugs solved)- $ 200 (if more than 20 bugs solved) to this even.
Time: 1-29 February 2012
You can contribute also, even though it is only few $ or thousands $$$$. Just imagine if 10, 100 or more people donate this will be interesting.
What do you think ?
Just my 2c
How about make the February is the Bug Bounty Month.
We try to give rewards to developer (concrete5 or outside developer) which can solve the concrete 5.5.1 bugs.
The criteria we need to discuss it:
Developer with most solve the bugs, or maybe by point system.
Performance improvements can be also counted if significant.
we need some committee:
some from Concrete5 team.
some from outside developer (with minimum x badges/ we can vote)
I will donate between $ 100 (if less than 20 bugs solved)- $ 200 (if more than 20 bugs solved) to this even.
Time: 1-29 February 2012
You can contribute also, even though it is only few $ or thousands $$$$. Just imagine if 10, 100 or more people donate this will be interesting.
What do you think ?
Just my 2c
Lets try something different. where the rewards is $$$
I hope it attract some developer and can make Concrete5 better
I hope it attract some developer and can make Concrete5 better
While $$$ is always nice, one must consider the negative repercussions of using monetary rewards for work, especially in an open source community.
The people that work on making Concrete5 better are not necessarily driven by money. Many appreciate that a lot of work has gone into a platform that makes it easier to earn a living and contribute time (or code) to help others along. Others, spend time or money on development for key pieces and decide to share with the community for a variety of reasons. Others help answer questions in the forums or write how-to's as a way of paying things forward.
As for implementing a system of tracking and prioritizing bugs, I think most will get fixed within a reasonable amount of time as the most active people have a need to fix them as they complete work for their clients. Let's not forget that earlier versions are still available and work pretty damn good.
By rewarding the amount of bugs fixed, you risk rewarding those who fix a large number of trivial bugs poorly instead of rewarding those who fix a low number of important bugs well (in a way that scales and doesn't mess with future releases). Quantity rewards usually end up with the low hanging fruit being picked clean and coming back to haunt everyone later.
Those with talent and skill will undertake the fixing of important bugs with skill and care as external projects require it. They will make robust fixes that take the past and the future into account and will not cause them money in rework for a paying client if it can be avoided. Paying for bugs now will see a few good fixes, but will generally be paid for with everyone's time in the future.
Lastly, you can't gather enough money to make it worthwhile. Developers will fix things for a client and share with the community, but receiving $10 for a seemingly simple bug that takes 20 hours to properly fix is simply insulting to someone with the talent to fix it properly.
I like that there are ideas flowing to 'normalize' the latest release and get back to building sites, but IMHO, bringing money into the equation won't help. There are a lot of people that spend a lot of time on making Concrete5 better and I think they do a hell of a job, (Special thanks to all of you!). This release, while not perfect, has been fairly well communicated and fairly smooth for a major release.
The people that work on making Concrete5 better are not necessarily driven by money. Many appreciate that a lot of work has gone into a platform that makes it easier to earn a living and contribute time (or code) to help others along. Others, spend time or money on development for key pieces and decide to share with the community for a variety of reasons. Others help answer questions in the forums or write how-to's as a way of paying things forward.
As for implementing a system of tracking and prioritizing bugs, I think most will get fixed within a reasonable amount of time as the most active people have a need to fix them as they complete work for their clients. Let's not forget that earlier versions are still available and work pretty damn good.
By rewarding the amount of bugs fixed, you risk rewarding those who fix a large number of trivial bugs poorly instead of rewarding those who fix a low number of important bugs well (in a way that scales and doesn't mess with future releases). Quantity rewards usually end up with the low hanging fruit being picked clean and coming back to haunt everyone later.
Those with talent and skill will undertake the fixing of important bugs with skill and care as external projects require it. They will make robust fixes that take the past and the future into account and will not cause them money in rework for a paying client if it can be avoided. Paying for bugs now will see a few good fixes, but will generally be paid for with everyone's time in the future.
Lastly, you can't gather enough money to make it worthwhile. Developers will fix things for a client and share with the community, but receiving $10 for a seemingly simple bug that takes 20 hours to properly fix is simply insulting to someone with the talent to fix it properly.
I like that there are ideas flowing to 'normalize' the latest release and get back to building sites, but IMHO, bringing money into the equation won't help. There are a lot of people that spend a lot of time on making Concrete5 better and I think they do a hell of a job, (Special thanks to all of you!). This release, while not perfect, has been fairly well communicated and fairly smooth for a major release.
Thanks for the comments.
Lets wait for others opinion.
Lets wait for others opinion.
I'm not sure we're solving problems we actually have. I look at the
bug tracker and I only see too bugs with any confirmations that
haven't been resolved. If you've got a few minutes to donate go ahead
and confirm another bug. We'll fix it.
best wishes
Franz Maruna
CEO - concrete5.org
http://about.me/frz
bug tracker and I only see too bugs with any confirmations that
haven't been resolved. If you've got a few minutes to donate go ahead
and confirm another bug. We'll fix it.
best wishes
Franz Maruna
CEO - concrete5.org
http://about.me/frz
+1
5.5.0 bugs which still exist on 5.5.1
http://www.concrete5.org/developers/bugs/5-5-0/base_url-no-longer-s...
Hhhm any other idea to make more developer interesting to help concrete5 ?
5.5.0 bugs which still exist on 5.5.1
http://www.concrete5.org/developers/bugs/5-5-0/base_url-no-longer-s...
Hhhm any other idea to make more developer interesting to help concrete5 ?
As described, that isn't a bug. That's why it was left off the 5.5.1 list.
There's an entry in 5.5.1 that we're working on for this issue which isn't that BASE_URL and DIR_REL don't appear on config/site.php – it's that concrete5 doesn't handle SSL correctly when they don't.
There's an entry in 5.5.1 that we're working on for this issue which isn't that BASE_URL and DIR_REL don't appear on config/site.php – it's that concrete5 doesn't handle SSL correctly when they don't.
Mike