Loading...
 
Features / Usability

Features / Usability


Any Good?

posts: 2881 United Kingdom

Ok, Ive been thinking about this for a while and here it goes is this idea of any use to the Tiki Community?

On the style of a rentacoder site:

A Tiki user submits a feature request to the system. Tiki Developers or any coders then place a "bid" on the request. (bid = money) for which they will code the feature for. Then the submiter can choose out of the devs to the job who they wish to sponser.

I think it could work quite well and also aid development vastly.

Very little is needed in terms of coding to get it setup, we can use Trackers aka Forms to manage the "jobs" and "bids"

Anyway, theres the idea, so please everyone comment!

Damian

posts: 6 United States
It might be better to have the requester setup a bounty for a feature instead. Any coder or group of coders that completes the requirements of the feature request collects the bounty. I believe there is a site/organization that does arbitration of these things for open source projects.
posts: 6 United States

I mean kind of like the way gnome setup their bounties. The bounty system seems to be more efficient than the bid system because a handshake occurs only twice. The handshakes occur between the requester and the escrow service, and between the developer and the escrow. (The requester can always increase the bounty if no body responds for a while)

In your proposed bid system, the requester has to be active in checking what developers are willing to do it and for what price. The burden of making a successful handshake is moved from the developers to the requester.

I believe that the one with the money (ie the requester/customer) should have the advantage of convenience and not the developer. In a bounty system, every party knows exactly what they are getting and for what price.


posts: 6 United States

I mean kind of like the way gnome setup their bounties. The bounty system seems to be more efficient than the bid system because a handshake occurs only twice. The handshakes occur between the requester and the escrow service, and between the developer and the escrow. (The requester can always increase the bounty if no body responds for a while)

In your proposed bid system, the requester has to be active in checking what developers are willing to do it and for what price. The burden of making a successful handshake is moved from the developers to the requester.

I believe that the one with the money (ie the requester/customer) should have the advantage of convenience and not the developer. In a bounty system, every party knows exactly what they are getting and for what price.


Upcoming Events

1)  18 Apr 2024 14:00 GMT-0000
Tiki Roundtable Meeting
2)  16 May 2024 14:00 GMT-0000
Tiki Roundtable Meeting
3)  20 Jun 2024 14:00 GMT-0000
Tiki Roundtable Meeting
4)  18 Jul 2024 14:00 GMT-0000
Tiki Roundtable Meeting
5)  15 Aug 2024 14:00 GMT-0000
Tiki Roundtable Meeting
6)  19 Sep 2024 14:00 GMT-0000
Tiki Roundtable Meeting
7) 
Tiki birthday
8)  17 Oct 2024 14:00 GMT-0000
Tiki Roundtable Meeting
9)  21 Nov 2024 14:00 GMT-0000
Tiki Roundtable Meeting
10)  19 Dec 2024 14:00 GMT-0000
Tiki Roundtable Meeting