659029 - Private as default policy for new addon/library

Status: RESOLVED DUPLICATE of bug 659057

(addons.mozilla.org Graveyard :: Add-on Builder, defect)

Description

[arky [:arky]]

User-Agent:       Mozilla/5.0 (X11; Linux i686; rv:2.0.1) Gecko/20100101 Firefox/4.0.1
Build Identifier: Addon-on Builder preview

The latest addon listing on 'Browse Add-ons' are mostly empty and half finishing addons.

Perhaps setting the newly created addon/library permission to private would be one way of doing. Users can write, test and share the code for peer review/testing. 

Reproducible: Always

Steps to Reproduce:
1. Go to https://builder.addons.mozilla.org/ page and select 'Create an addon-on now'
2. Write some code 
3. Save your code
4. Go back to Your Account > Public Addon. You find the newly created add-on listed as public 

Actual Results:  
Newly created Addon/libraries are listed as public

Expected Results:  
Newly created Addon/libraries could be set as private

Comment 1

[Daniel Buchner [:dbuc]]

We will always set an add-on or library to Public by default, as that is consistent with our open source ideals.

The issue you identified regarding empty add-ons being displayed on the home page is something we are working on. We just implemented a new search service on the back-end, and will be switching to a query that will populated that section with a better result set that features more complete add-ons and libraries.

We're hoping to make the above change to the front page add-on query before the beta launch in late June :)