Re: [Inkscape-user] [Inkscape-docs] UX team?
Oh! (Copying over to dev and user lists.) There are so very many people interested in working on the UX (I seem to recall several people had been signed up -- it's hard to believe not one of them would volunteer for this simple task.
If "the team's business" means writing the intro, Team Details and Charter, I can do that. What other business might there be? (Even though I'm leading the Moderators Team, I suspect the "business" is probably different.)
If it requires a lot of work, let's put it up on the To-Do List page, to try to recruit someone. But what kind of business is it?
Thanks, brynn
-----Original Message----- From: Martin Owens Sent: Wednesday, September 20, 2017 7:25 AM To: brynn ; Inkscape-Docs Subject: Re: [Inkscape-docs] UX team?
On Wed, 2017-09-20 at 06:42 -0600, brynn wrote:
Hi Friends, I just noticed there is no UX team showing on the Teams page (https://inkscape.org/en/teams/). I could have sworn I saw one there, not too long ago (couple of months maybe). I think it had several members.
What happened with that?
The UI team is currently hidden as it's TODO introduction and lack of leadership made it hard to justify keeping it visible.
So what it needs is someone with a passion, preferably a UX person, who can say that even if it's just a team of one, that they will handle the team's business.
Best Regards, Martin Owens
On Wed, 2017-09-20 at 07:57 -0600, brynn wrote:
Oh! (Copying over to dev and user lists.) There are so very many people interested in working on the UX (I seem to recall several people had been signed up -- it's hard to believe not one of them would volunteer for this simple task.
If "the team's business" means writing the intro, Team Details and Charter, I can do that. What other business might there be? (Even though I'm leading the Moderators Team, I suspect the "business" is probably different.)
If it requires a lot of work, let's put it up on the To-Do List page, to try to recruit someone. But what kind of business is it?
The above, plus managing ux requests and making sure the team has a function that it can maintain. So if we have a discussion about a ux piece, there's a gitlab issues tracker or similar we can all go to.
But the actual setup is up to the leader and team tbh.
Best Regards, Martin Owens
On Wed, Sep 20, 2017 at 10:07:24AM -0400, Martin Owens wrote:
On Wed, 2017-09-20 at 07:57 -0600, brynn wrote:
Oh! (Copying over to dev and user lists.) There are so very many people interested in working on the UX (I seem to recall several people had been signed up -- it's hard to believe not one of them would volunteer for this simple task.
If "the team's business" means writing the intro, Team Details and Charter, I can do that. What other business might there be? (Even though I'm leading the Moderators Team, I suspect the "business" is probably different.)
If it requires a lot of work, let's put it up on the To-Do List page, to try to recruit someone. But what kind of business is it?
The above, plus managing ux requests and making sure the team has a function that it can maintain. So if we have a discussion about a ux piece, there's a gitlab issues tracker or similar we can all go to.
But the actual setup is up to the leader and team tbh.
"A function that it can maintain" is definitely true. A UX team would be notably different from, say, the Docs or Vectors team, in that it is (ideally) inward facing rather than outward facing. Documentation and marketing have essentially stand-alone output, with their input being into our development efforts. A UX team operates in the reverse direction, so will require setting up tighter coordination. So a principle goal for setting up a UX team would be working out a good strategy for getting development done on the changes they identify.
I have some further ideas here on how to relate the team to our development roadmap, and would be happy to brainstorm with anyone interested in getting this ux team up and running.
Bryce
I would propose we consider changing the "Development Team" to the "Product Team" and integrating UX, UI, Testing, and Programming into a more coordinated and cohesive group. Just my $0.02.
*Ryan Gorley* Managing Partner | Dijt https://dijt.co
On Wed, Sep 20, 2017 at 2:27 PM, Bryce Harrington <bryce@...983...
wrote:
On Wed, Sep 20, 2017 at 10:07:24AM -0400, Martin Owens wrote:
On Wed, 2017-09-20 at 07:57 -0600, brynn wrote:
Oh! (Copying over to dev and user lists.) There are so very many people interested in working on the UX (I seem to recall several people had been signed up -- it's hard to believe not one of them would volunteer for this simple task.
If "the team's business" means writing the intro, Team Details and Charter, I can do that. What other business might there be? (Even though I'm leading the Moderators Team, I suspect the "business" is probably different.)
If it requires a lot of work, let's put it up on the To-Do List page, to try to recruit someone. But what kind of business is it?
The above, plus managing ux requests and making sure the team has a function that it can maintain. So if we have a discussion about a ux piece, there's a gitlab issues tracker or similar we can all go to.
But the actual setup is up to the leader and team tbh.
"A function that it can maintain" is definitely true. A UX team would be notably different from, say, the Docs or Vectors team, in that it is (ideally) inward facing rather than outward facing. Documentation and marketing have essentially stand-alone output, with their input being into our development efforts. A UX team operates in the reverse direction, so will require setting up tighter coordination. So a principle goal for setting up a UX team would be working out a good strategy for getting development done on the changes they identify.
I have some further ideas here on how to relate the team to our development roadmap, and would be happy to brainstorm with anyone interested in getting this ux team up and running.
Bryce
Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Inkscape-user mailing list Inkscape-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-user
I would propose we consider changing the "Development Team" to the "Product Team" and integrating UX, UI, Testing, and Programming into a more coordinated and cohesive group. Just my $0.02.
+1 But I'd leave it as "Development" - people are more familiar with that term than the rather nebulous "Product Team"... which sounds almost like merchandising. :)
If UX is integrated into development, then it is part of development.
-C
*Ryan Gorley* Managing Partner | Dijt https://dijt.co
On Wed, Sep 20, 2017 at 2:27 PM, Bryce Harrington < bryce@...983...> wrote:
On Wed, Sep 20, 2017 at 10:07:24AM -0400, Martin Owens wrote:
On Wed, 2017-09-20 at 07:57 -0600, brynn wrote:
Oh! (Copying over to dev and user lists.) There are so very many people interested in working on the UX (I seem to recall several people had been signed up -- it's hard to believe not one of them would volunteer for this simple task.
If "the team's business" means writing the intro, Team Details and Charter, I can do that. What other business might there be? (Even though I'm leading the Moderators Team, I suspect the "business" is probably different.)
If it requires a lot of work, let's put it up on the To-Do List page, to try to recruit someone. But what kind of business is it?
The above, plus managing ux requests and making sure the team has a function that it can maintain. So if we have a discussion about a ux piece, there's a gitlab issues tracker or similar we can all go to.
But the actual setup is up to the leader and team tbh.
"A function that it can maintain" is definitely true. A UX team would be notably different from, say, the Docs or Vectors team, in that it is (ideally) inward facing rather than outward facing. Documentation and marketing have essentially stand-alone output, with their input being into our development efforts. A UX team operates in the reverse direction, so will require setting up tighter coordination. So a principle goal for setting up a UX team would be working out a good strategy for getting development done on the changes they identify.
I have some further ideas here on how to relate the team to our development roadmap, and would be happy to brainstorm with anyone interested in getting this ux team up and running.
Bryce
Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Inkscape-user mailing list Inkscape-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-user
Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Inkscape-user mailing list Inkscape-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-user
Aaahh. Well that is far more than I can handle.
I thought it was a more tangible team than apparently it really is. As a humble, not-so-technically inclined user, I would say that such a team is definitely needed.
It seems like I've seen relatively a lot of people offer to help with UI/UX. If all that's lacking is one or 2 people to take a leadership or organizational role, I wonder if adding it to the To-Do List page would help?
All best, brynn
-----Original Message----- From: Bryce Harrington Sent: Wednesday, September 20, 2017 2:27 PM To: Martin Owens Cc: brynn ; Inkscape-Docs ; Inkscape-Devel ; Inkscape User Community Subject: Re: [Inkscape-docs] UX team?
On Wed, Sep 20, 2017 at 10:07:24AM -0400, Martin Owens wrote:
On Wed, 2017-09-20 at 07:57 -0600, brynn wrote:
Oh! (Copying over to dev and user lists.) There are so very many people interested in working on the UX (I seem to recall several people had been signed up -- it's hard to believe not one of them would volunteer for this simple task.
If "the team's business" means writing the intro, Team Details and Charter, I can do that. What other business might there be? (Even though I'm leading the Moderators Team, I suspect the "business" is probably different.)
If it requires a lot of work, let's put it up on the To-Do List page, to try to recruit someone. But what kind of business is it?
The above, plus managing ux requests and making sure the team has a function that it can maintain. So if we have a discussion about a ux piece, there's a gitlab issues tracker or similar we can all go to.
But the actual setup is up to the leader and team tbh.
"A function that it can maintain" is definitely true. A UX team would be notably different from, say, the Docs or Vectors team, in that it is (ideally) inward facing rather than outward facing. Documentation and marketing have essentially stand-alone output, with their input being into our development efforts. A UX team operates in the reverse direction, so will require setting up tighter coordination. So a principle goal for setting up a UX team would be working out a good strategy for getting development done on the changes they identify.
I have some further ideas here on how to relate the team to our development roadmap, and would be happy to brainstorm with anyone interested in getting this ux team up and running.
Bryce
participants (5)
-
Bryce Harrington -
brynn -
C R -
Martin Owens -
Ryan Gorley