← Back to team overview

launchpad-dev team mailing list archive

Re: visibility vs. information_type for Products

 

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

On 12-09-18 11:03 AM, Curtis Hovey wrote:
> There are groups of people interacting with a project and they use 
> different information types.
> 
> * Project Creators use Public, Proprietary, and Embargoed for
> planning. * Project Community uses Public, Private (user), Private
> Security

I don't understand this distinction.  It seems like "creator" actually
means "owner" or "planner", since people who had no role in the
creation of the project could wind up filing proprietary bugs later.

I think you're describing three categories
Project Community, Project Creators who are not planning, who behave
the same, and Project Creators who are planning, who use different
types.  (I split Project Creators into planning and non-planning to
reconcile with your later statement "The creators also work with
[Public, Private (user), Private Security].")

I don't think this is accurate, because some projects will use
Proprietary and Embargoed regardless of whether they are planning.

Perhaps you meant:
 * Project Creators use Public, Proprietary,
   and Embargoed for planning, and all available types when not
   planning.
 * Project Community uses Public, Private (user), Private Security

Is that it?  It seems to disagree with this next statement, which
implies that creators do not create Private (user) or Private Security.

> Project, teams, and blueprints originate from the creators, so they
> can only be Public, Proprietary, and Embargoed

It's certainly *possible* for a blueprint to be security-related.
Similarly, it can contain private user data.  I think the reason we
exclude those information types from Specifications is because we
don't think it's common enough to support.  I don't think it's because
they originate from planning creators.  Also, we don't prevent
non-creators from creating blueprints.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlBYnvcACgkQ0F+nu1YWqI3TmwCfWd/3gOlLSM0+/GFnNHE+rh6O
Ul0AnRkwbRiPY6jsfYizJ7N5UtcEyj9x
=uNei
-----END PGP SIGNATURE-----


Follow ups

References