search

Letractively / brewtoolz

Automatically exported from code.google.com/p/brewtoolz
GNU Lesser General Public License v3.0
0 stars 0 forks source link

Private Settings #89

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Feature Request:

Private recipes and brew logs. I would like to see recipes private by 
default, i like to spend some time developing them and they seem to go 
public the second they are created. Would like to be able to share once the 
recipe has been tweaked, brewed, or whatever, perhaps never shared.

Original issue reported on code.google.com by pete...@gmail.com on 6 May 2010 at 9:13

GoogleCodeExporter commented 8 years ago 
Possible solutions under consideration are:

- Apply some form of quality analysis across recipes before making them visible 

- Add some state that the user allows before a recipe is notes as completed.

- Allow user voting to put items into a "top 10 list"

- Allow moderator/admin users to choose recipes to put in this list.

The idea of never making a recipe visible is something users probably do want, 
but
how then does that attract other's to the site? 

Maybe we could do this on a very limited basis that must be selected every time 
a
user creates a recipe.

Possibly limit the number of recipes that where not visible?  Maybe give a time 
limit
etc?

Original comment by chris.ta...@gmail.com on 9 May 2010 at 12:48

GoogleCodeExporter commented 8 years ago

Original comment by chris.ta...@gmail.com on 9 May 2010 at 12:49

GoogleCodeExporter commented 8 years ago 
id probably just go with the quality analysis for now. seems the easiest. the 
others 
would be good for down the track.. though i do like the idea of the keeping 
them 
private for a length of time... (maximum 28 days or something). this way, if 
you were 
putting in a recipe you wanted to enter in to a competition, it wouldnt get 
revealed 
until after the comp

Original comment by pete...@gmail.com on 9 May 2010 at 9:48

GoogleCodeExporter commented 8 years ago 
After some initial design, think the most practical solution for the short term 
is to
mark a recipe as "Draft".

In this mode it will not appear in the recently added recipes list, and they 
will be
clearly marked as still Draft in the other lists.

Original comment by chris.ta...@gmail.com on 12 May 2010 at 10:12

GoogleCodeExporter commented 8 years ago

Original comment by chris.ta...@gmail.com on 13 May 2010 at 3:01

GoogleCodeExporter commented 8 years ago

Original comment by chris.ta...@gmail.com on 13 May 2010 at 4:12

GoogleCodeExporter commented 8 years ago 
Added functionality to mark a recipe as draft which goes some way to addressing 
the
above issues.

Original comment by chris.ta...@gmail.com on 13 May 2010 at 1:21