Thank you to everyone who’s been leaving comments and suggestions on the thread from yesterday, and keep adding to that thread, I’ll be bookmarking it for continual review. 🙂 Anyway, here’s an update on this project.
This week Ian Dunn and Scott Reilly have been cranking out code, testing, hunting for the bugs, re-testing, etc. Mel Choyce and I have had our heads together on design, and Andrea Middleton and Cami Kaos have been heads down with volunteers on backfilling the WordCamp.org data for speakers and organizers*. We plan to launch something today, but it will definitely be a v1, and I’m proposing we (being whoever wants to work on it moving forward, not necessarily this specific group of people) work on iterations in 2-week cycles moving forward so that improvements (even small ones) are continually making the profiles better.
The way I’m looking at profiles from a ux perspective is that for a visitor, the profile serves as someone’s WP resume, while for the profile owner, it serves as the dashboard for their involvement in the open source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. project. Based on that, here are the requirements for design:
- No one’s profile should look sad and lonely because they are new to the project or currently inactive.
- Seeing someone else’s profile should do the same thing as WordCamps, and help with the goal of our informal 3-word catchphrase (inspire*connect*contribute).
- The first look when you land on a page should give you a sense of who someone is, and what their involvement level is.
- It should be easy to see involvement by area/tasks, collections of things, activity in any part of wordpress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/. Including both a big-river activity stream and breakout views would be the base of this, with an infinitely extensible This is the ability to add additional functionality to the code. Plugins extend the WordPress core software. UI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. to allow for adding more areas of activity as we start to connect them to the central profile.
- Recognize contributors who are part of recognized contributor teams with a curated badge (vs pure quantity generating: imagine a forum volunteer and a spammy commenter/questioner both getting a badge saying they’re on the support team based on their activity numbers — yuck!). We’ll have to come up with a transparent metric for deciding what level/frequency of activity makes someone a ‘team member’ vs a contributor in that area. I’ll start checking in with each team and ask the team reps to help wrangle those decisions on a team-by-team basis.
So here’s the sketch I did yesterday for Ian to use as the starting point. Please take this in the spirit it’s offered; it’s just the working sketch/a set of ideas, and we’ll wind up with whatever we wind up with and then continue to iterate. So try not to get hung up on specifics yet. 🙂
