elementary-dev-community team mailing list archive

[Jaap Broekhuizen <jaapz.b@xxxxxxxxx>]

I think the best and easiest way would be just to use the tagging system,
like Sergey said, if that does what i think it does :)
I don't think it's a good idea to have one person everyone has to go to to
ask if he maybe could assign the bug to elementary-design, such a process
will take far longer than just tagging a bug, and also depending on one
person for something like this is always a bit tricky on the open source
community :)

I also think asking anyone (not just one person) from the elementery-design
team to mark a bug for designer input by elementary-design would still be a
tedious process, because you still have the second person who needs to do
some actions. It would be far easier to just tag the bug by the person who
thinks the bug needs designer input.

Met vriendelijke groet,

Jaap Broekhuizen

Aquamarijnstraat 273
9743 PG  Groningen

jaap.broekhuizen.nu
jaapz.b@xxxxxxxxx
06 - 39 81 36 97


On Thu, Jun 28, 2012 at 1:20 AM, Andrea Basso <voluntatefaber@xxxxxxxxx>wrote:

> There are not many alternatives, I guess. Well, we could add some trusted
> guy to ~elementary-design and it'll be up to them mark those bugs as
> requiring designers' input.
>
> PROS:
>  - for everyone else, everything stays as it is now
>
> CONS:
>  - there are non-designer people in ~elementary-design (and thus they
> receive mails who're not addressed to them)
>  - only some trusted guys can mark bugs as requiring designers' input
>
> I don't really know which one is better...
>
> Regards,
> Andrea Basso
>
>
> On Wed, 27 Jun 2012 13:54:09 +0200, Сергей Давыдов <shnatsel@xxxxxxxxx>
> wrote:
>
>  Hey guys,
>>
>> as you have probably noticed, Launchpad no longer allows assigning a
>> team of which you are not a member of to bug reports, so we can no
>> longer use the established way of summoning designers upon bug
>> reports.
>>
>> The current convention served two things: first, it generated an extra
>> email to the thread asking designers to have a look at the bug.
>> Second, it provided an overview of bugs requiring designer input at
>> https://bugs.launchpad.net/~**elementary-design<https://bugs.launchpad.net/~elementary-design>
>>
>> As for a new convention, I guess bug tags will come in handy for
>> generating a list, and since they also generate an email about the tag
>> change (unless you disable it somewhere in LP settings), designers can
>> set up mail filters to separate those reports.
>>
>> Any other ideas for a new convention?
>>
>> --
>> Sergey "Shnatsel" Davidoff
>>
>
> --
> Mailing list: https://launchpad.net/~**elementary-dev-community<https://launchpad.net/~elementary-dev-community>
> Post to     : elementary-dev-community@**lists.launchpad.net<elementary-dev-community@xxxxxxxxxxxxxxxxxxx>
> Unsubscribe : https://launchpad.net/~**elementary-dev-community<https://launchpad.net/~elementary-dev-community>
> More help   : https://help.launchpad.net/**ListHelp<https://help.launchpad.net/ListHelp>
>