launchpad-dev team mailing list archive

[Chris Johnston <chrisjohnston@xxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/01/2012 12:35 PM, Deryck Hodge wrote:
> On Mon, Oct 1, 2012 at 11:30 AM, Chris Johnston
> <chrisjohnston@xxxxxxxxxx> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 09/28/2012 11:29 AM, Francis J. Lacoste wrote:
>>> Better Privacy check-point 2012-09-26
>>> =====================================
>>>
>>> Summary -------
>>>
>>> * OEM/HWE still migrating en masse to Sharing * Private blueprints
>>> are in beta * On track for Oct 8th private project milestone
>>>
>>> Blueprints privacy ------------------
>>>
>>> * Get the sprints blueprints query sorted out
>>>
>>
>> Greetings,
>>
>> So after having a small side conversation to be brought up to speed as
>> to what was meant by "Get the sprints blueprints query sorted out" I
>> have a question to raise. My understanding from Francis is that a
>> private blueprint will still be allowed to be proposed to a sprint,
>> just nothing will happen as it will not show up on the sprint query.
>> This seems like it would lead to a confusing UI by telling the user
>> that they can do something, but then the user not receiving the
>> expected result. Am I misunderstanding how this is planned to work, or
>> it my understanding fairly accurate? If my understanding is accurate,
>> has anything been thought of to combat this confusing UI that is being
>> introduced?
>>
>
> A private blueprint will show up for people who can view it. This
> works like any other private object on Launchpad. If you have
> permission to view the object, then it will show up in your view of
> the list, but if I do not, then it will not show up in my view.
>
> Cheers,
> deryck
>
Deryck,

One of the points of something being on a sprint is for Summit to create
a meeting out of the blueprint. So this still seems to lead the same
question. Summit doesn't have permission to see it, so the expected
result of "add blueprint to UDS sprint to create meeting" still fails
unless I am missing something.

cJ

- -- 
Respectfully,

Chris Johnston - cjohnston
Ubuntu Member
chrisjohnston@xxxxxxxxxx
www.chrisjohnston.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAlBpxwUACgkQyDxSNf9BQVy08QCePI/HiSn03rvA6rEazl8jk1us
VYMAoJp9JgcOvXEGwRNeuP4vgBZfJVJ5
=KkWo
-----END PGP SIGNATURE-----