Page MenuHomePhabricator

Define good practices to start working on project concepts privately
Closed, ResolvedPublic

Description

While Wikimedia Foundation projects requesting prioritization and resources should have their concepts publicly available (T118231), and while drafting concepts publicly should be the default recommendation, there might be situations where starting to work on a concept privately will bring some advantages.

In this task we aim to define when private drafting is useful and what are the criteria that would define the appropriate time to go public.

https://www.mediawiki.org/wiki/User:Keegan_(WMF)/PDP/Private_planning

Related Objects

StatusAssignedTask
DuplicateQgil
ResolvedQgil
ResolvedQgil
DuplicateNone
DuplicateNone
DuplicateQgil
ResolvedElitre
ResolvedElitre
DeclinedNone
OpenNone
OpenNone
InvalidKeegan
DeclinedKeegan
DeclinedNone
ResolvedElitre
ResolvedQuiddity
ResolvedKeegan
ResolvedKeegan

Event Timeline

Qgil created this task.Jan 14 2016, 7:09 AM
Qgil raised the priority of this task from to Normal.
Qgil updated the task description. (Show Details)
Qgil added subscribers: Ironholds_backup, Krenair, Quiddity and 10 others.
Whatamidoing-WMF added a comment.EditedJan 23 2016, 7:34 AM

Here's a few, to start brainstorming. Some ideas here are not appropriate for every circumstance.

  • Draft in private if you truly don't know what you're talking about yet. "Something or another about, I dunno, it should just be easier for people to find stuff" isn't a very useful entry point for collaboration. Post when you're past the point of doodling in the margins of your notes and can explain what you're thinking about in reasonably concrete terms.
  • Draft in private when your idea changes every day, or every hour. Post when you've stuck with the same iteration for a week.
  • Draft in private when you don't want help. Post when you do.
  • Draft in private if you're talking about real people. Post after you've turned "WhatamIdoing is incredibly annoying and stubborn" into something like "She's tenacious and passionate about her community".
  • Draft in private when you have an idea that needs careful thought. Post after you've determined things like whether Legal will break out in a bad rash, or when you have a reasonably clear explanation of how your potentially good idea differs from a closely related bad idea (or whatever else prompts the need for careful thought).
  • Consider drafting in private when you know that an idea will be popular with core community members, but you're not sure that it's feasible. Post when there's a chance that it could really happen. Nobody likes to have longed-for treats dangled in front of them, only to have them snatched away with "Ha ha, only kidding! It turns out that this isn't feasible after all!"

How many more ideas can we come up with?

Qgil added a subscriber: Keegan.

Thank you @Whatamidoing-WMF , this is very useful. @Keegan, since this task is related to community engagement + Concept stage, I think we need to schedule it for Liaisons-February-2016.

Begin in private when there is a security or privacy issue which needs to be worked out prior to discussing publicly.

But ask publicly when there is a security or privacy problem to work out which could privately use community input, use cases and expertise

Met with some CLs and PMs for discussion and review. All-in-all there is a general agreement that when you're past brainstorming/thinking/ideation what have you and you start scheduling meetings and writing things down, you're probably at the Understand stage and it's time to work in public.

There was also a general agreement to stick to a high-level, narrative format instead of a scenario or FAQ-type page, those can live on the talk page for now.

Thus, the text in the page is ready: https://www.mediawiki.org/wiki/User:Keegan_(WMF)/PDP/Private_planning

It needs:

  1. A new title
  2. A home
  3. Integration

To-do tomorrow (Thurs, Mar 3).

Qgil added a subscriber: Jseddon.Mar 3 2016, 10:26 AM

Great!

One area where good practices need to be clear are proposals for restricted grants. There has been a lot of discussion about this in the past months. Is there already WMF documentation or guidelines about how to handle transparency and confidentiality in restricted grants requests? Is there any requirement for confidentiality from the organizations we apply for grants?

Keegan added a comment.Mar 3 2016, 7:28 PM

Great!
One area where good practices need to be clear are proposals for restricted grants. There has been a lot of discussion about this in the past months. Is there already WMF documentation or guidelines about how to handle transparency and confidentiality in restricted grants requests? Is there any requirement for confidentiality from the organizations we apply for grants?

@Jseddon Thoughts?

I'm pretty sure this documentation lives somewhere, though I'm not sure how up-to-date it is.

I'll park this somewhere in the meantime, we can work in applications to other parts of the org as they arise.

DStrine removed a subscriber: DStrine.Mar 31 2016, 9:16 PM
Keegan added a comment.Apr 4 2016, 7:45 PM

Just needs plugged into the forthcoming Guidelines on Community Engagement, not closing until then, otherwise this is done.

Keegan changed the task status from Open to Stalled.Apr 5 2016, 7:53 PM
Qgil updated the task description. (Show Details)May 30 2016, 9:38 AM
Qgil awarded a token.