[Design-team] Re: Request about your contribution
I understand you very well.
Yes! I think the last meeting has set most of the tickets to the
fedora design team members.
Any meeting changes can also put on fedora design list if I don't online.
Most of the members follow the the rules fedora design and give some
help is not wrong.
Is one ticket has a legal issue with python logo and this will need to
fix by the design team - I don't remember the ticket, also any problem
can be put on table.
If you have some concern then you can loot to this ticket ( see:
https://fedorahosted.org/design-team/ticket/421 where for example is
one reference to: https://fedoraproject.org/wiki/Logo/UsageGuidelines
also some changes.
Yes. Summary of meeting can help us. - "the goal of understanding the
team's process for working on tasks."
You told me : "It creates confusion about who has taken the assignment."
Have you ? Do you see my ticket and what I need to do ? Can you help me?
https://fedorahosted.org/design-team/ticket/402
Any problem with my work can be solved by sending a mail to me and duffy.
Thank you for replay.
2016-08-18 21:56 GMT+03:00 Paul W. Frields <stickster(a)gmail.com>:
> Hi Catalin,
>
> I've been reviewing some of your recent contributions for Fedora
> Design, and I want to offer some suggestions.
>
> https://fedorahosted.org/design-team/ticket/447
> https://fedorahosted.org/design-team/ticket/468
>
> In these two examples, you interjected designs into a ticket that
> another designer was already working on. This is usually not a
> helpful approach for a community project. It creates confusion about
> who has taken the assignment.
>
> As I look at some of your other communication on the Design team's
> list, it also seems like people are having trouble understanding your
> language or intent. I realize English is not your native language, so
> the difficulty is understandable.
>
> I recommend that you try to listen to the design team meetings with
> the goal of understanding the team's process for working on tasks.
> Get familiar with how other designers provide input, and use that as a
> model for your own feedback. Once you have that understanding,
> request an assignment from the team. That way you will not step on
> other designers' toes, and it will be easier to contribute
> successfully.
>
> I hope this helps!
>
> --
> Paul W. Frields http://paul.frields.org/
> gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
> http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
> The open source story continues to grow: http://opensource.com