The discussion was kickstarted on October 9th with this discussion: <a href="../post/2503">https://polkadot.polkassembly.io/post/2503</a> and seeks to close the BD bounty - bounty 39 due to inaction and lack of structure and planning. <a href="https://polkadot.subsquare.io/treasury/bounties/39">https://polkadot.subsquare.io/treasury/bounties/39</a>
The main concern is the lack of activity and deliverables of this bounty. As expressed by the original discussion, this bounty was meant to be reactive to other external business development efforts but in 8 months it's had no activity.
Important comments like Ingo Rube an original member of the bounty suggesting that the bounty should be closed as it meant to be retroactive and high quality. Alternatives proposed by him were: centralized coordination from the W3F or bringing up teams with +2M USD deals closed i.e a heavy track record in order to reconsider such bounty again. <a href="../post/2503#q8Js8RZhd8npmgNsQJlN">https://polkadot.polkassembly.io/post/2503#q8Js8RZhd8npmgNsQJlN</a>
The rest of the comments focused mostly on the lack of activity and focus as the main reason for why this bounty should be closed, concerns we also share with respect with this bounty.
There is a counterparty referendum that is live concurrently that seeks to redesign the BD bounty with <a href="https://x.com/crisnguyen99">https://x.com/crisnguyen99</a> at the helm. We planned with to launch both referenda concurrently so that the closing bounty referenda would have a somewhat viable alternative.
The counterproposal seeks to change curators to: Vincent Chan, Cris Nguỵen, Thibault Perr&eacute;ard, Zachary &ldquo;Yung Beef&rdquo; Edwards, Albert Burgos, Technical Support: Luca Poggi. The link to the full counterproposal discussion with title: &ldquo;Propose to revamp Polkadot BD Bounty with New Curator Set and Structure&rdquo; <a href="../post/2559">https://polkadot.polkassembly.io/post/2559</a> Link to the referendum soon.
Link to the full counterparty proposal: <a href="https://docs.google.com/document/d/1gRc-jOHnNr646_9cXG8qZyz-jCmcCAh-lXwoXWDRvqY/edit?tab=t.0">https://docs.google.com/document/d/1gRc-jOHnNr646_9cXG8qZyz-jCmcCAh-lXwoXWDRvqY/edit?tab=t.0</a>
Saxemberg will be voting in favor of the closure of bounty 39 and against the counterproposal as we hold the view that BD is not well suited for such a bounty in the present and proposed conditions conditions and further work and deliveries have to be considered first.
A second point is that BD on Polkadot seems unfit to be managed by a single team as different DF, BD, dApp teams have a diverse set of skills, goals, locations/geographies and activities so a unification in this sense doesn&rsquo;t make sense at present.
Past efforts have had a variety degrees of success and the current alternative (counterproposal) doesn't guarantee a high degree of deliveries either.
&nbsp;
EDIT Nov 26th 2024.
<a href="https://x.com/saxemberg/status/1861025419140485318">https://x.com/saxemberg/status/1861025419140485318</a>
According to Cris Nguyen, they won't be pursuing a counterproposal that seeks to change curators and revisit B39. Instead they will attempt to create a new Business Development bounty sometime the future. Make sure to vote in that one too. Hopefully when that happens, referendum 1297 sets a precedent for BD operations and bounties.
&nbsp;

It seems like this bounty doesn't have neither proactive activity nor reactive activity as there is only one child bounty granted.
<a href="../bounty/39">https://polkadot.polkassembly.io/bounty/39</a>
<a href="../child_bounty/1445">https://polkadot.polkassembly.io/child_bounty/1445</a>
This bounty was meant to be reactive to other external business development efforts but in 8 months it's had no activity. We would like to hear if there are parties interested in the funds of these bounty because as of now all active BD efforts don't depend on it as they are working in parallel and with more specific goals. Otherwise, we'd like to hear if there are grounds for closing this bounty due to inactivity and lack of impact on BD efforts. A poll is included on this discussion, Voting AYE means closing the bounty NAY, means leaving it active but more than anything, we would like to hear the reasons why this bounty should or shouldn't be closed.
Let's kickstart the discussion.

Closing Bounty 39. BD (Business Development) Bounty?

General

Cancel a proposed or active bounty. All the funds will be sent to treasury and
the curator deposit will be unreserved if possible.

Only `T::RejectOrigin` is able to cancel a bounty.

- `bounty_id`: Bounty ID to cancel.

## Complexity
- O(1).

- **Problem Statement:** Lack of activity and structure in managing the BD bounty (bounty 39) on Polkadot.
- **Significance:** Concerns raised about the ineffectiveness of the current bounty in delivering results after 8 months.
- **Proposed Solution:** Close the current BD bounty and consider alternatives like centralized coordination from W3F or teams with a proven track record for future bounties.
- **Expected Outcomes:** Redesigning the BD bounty with new curators and structure to enhance effectiveness and deliverables.

#1297 Closing Bounty 39. BD (Business Development) Bounty.

No Active Proposals