Closed tgeorgeux closed 2 years ago
Hello everyone! My name is Daniel Lau and I’ll be the product manager for this endeavor. My background is in front end development and user experience design. I currently work as a UX Designer at Intuitive Surgical, where we make the Da Vinci surgical robot. I’m currently located in the San Francisco Bay Area. In my spare time, I enjoy eating at new restaurants, traveling to new countries, and spending time with friends and family. My favorite country I’ve recently visited is Japan.
I can’t wait to pick up where Tim left off and dive deep into researching Jupyter. This community is incredibly diverse and vibrant. Our team will focus on understanding Jupyter and developing a product that will make this community proud.
Hi everyone! My name is Joseph Hornig and I will be serving as the content strategist and assisting with UX research and design. It’s an honor to be working with Jupyter on this project and I’m looking forward to learning from you all as we go along.
I’m originally from the East Coast—I grew up in Baltimore, Maryland and then spent eight years in Washington, DC—but I love my new home in southern California. I’ve recently been hired as a UX Writer for Kaiser Permanente, and in my previous role I lead the website redesign for UCI’s Office of Admissions.
The HCI and Design master’s program has been an incredible experience so far, and I’m really excited to be partnering with Jupyter on this project. We’re hitting the ground running, so be on the lookout for updates from us soon!
Hi everyone! I'm Christina Bui, the lead researcher for this project. My background is in human-centered design research, from UC Berkeley's Design Innovation and UC Irvine's HCI programs. I'm currently signed on as a UI/UX & product marketing intern at Zuora, where my focus is on user research and market research. I was born and raised in southern California, but have spent the last 7 years in the San Francisco bay area. Having used Jupyter's products before, I've found the open source community inspiring in so many ways.
Thank you so much for the opportunity to contribute to this endeavor. We aim to drive Tim's project to fruition while bringing you all along in the spirit of openness and inclusion. Your feedback is crucial in steering our direction, so we look forward to hearing from you all!
Hi all - looking forward to engaging with you in the coming weeks 👋
Also, I'd recommend reaching out on the Discourse page, which has a lot more eyeballs than this repository :-)
Hello team! I am Omar Filippelli the lead UX Designer for the project. I have 10+ years’ experience in UX design and usability research. Currently leading cloud development efforts for Panduit, one of the leading providers of Data Center hardware and software. I am excited with the opportunity to be part of Jupyter’s community and contribute to the success of this open-source product. This will be a great collaborative effort with your feedback, support, and contributions. Something personal about me, I love watching and playing soccer.
Happy to learn about the community, tool, and anything else related to Jupyter. Please feel free to reach out.
@choldgraf Thanks for the heads up
Good point @choldgraf I've started a discourse thread in the meta section.
https://discourse.jupyter.org/t/wip-re-design-of-jupyter-org-website/691/4
Hello everyone. My name is Ana and I'm the Director of Jupyter work at Cal Poly in San Luis Obispo (I work with Tim). I look forward to seeing this work progress and to your contributions! I would encourage this group to engage/update the wider community of contributors as much as possible. One channel to keep in mind for big announcements to the larger community is Twitter which has a little over 40,000 followers. If you'd like to take advantage of this feel free to send me suggested content as you would like it published.
Thank you @choldgraf and @Ruv7 , we're excited to work with you all. Our initial research report is going to be posted in a few days, and we will definitely take you up on your offer to announce our updates as we release them.
Actually we are conducting 1-on-1 interviews for the next 2 weeks and would love to invite you to participate as contributors and steering council members. We have gathered a number of interviewees who are less active in the community, but we would like more perspectives from core members like yourselves. If you are or someone you know would be interested, feel free to get in touch with us through Tim!
Sure - is the week of the 22nd an option? Next week for me is pretty full with meetings. Send me a few times that work for you. Also if you pull together a 2 paragraph description I can send out a call for participation to the steering council. I would suggest 1 paragraph on who you are and your project, 1 paragraph on what you're looking for in the interview and the parameters. These are busy people so knowing the details of the ask will be important to determine whether or not they'll be able to participate. Note these folks are all over the world so definitely think about time zones when you're proposing meeting slots. :)
Thanks so much @Ruv7! The week of the 22nd should be fine, Tues/Wed/Thurs eves after 5:00 p.m. PST generally work best for us, but we're flexible. And if you wouldn't mind sharing the below invite with the Steering Council members, that would be great! Thanks so much for all of your help!
We are a group of Human-Computer Interaction graduate students at the University of California, Irvine who have partnered with Project Jupyter to help maximize the effectiveness of the jupyter.org website as part of our six-month capstone project. We are working directly with Tim George, Jupyter’s lead UI/UX designer, and have already begun some preliminary UX research.
To help learn as much as we can about Jupyter and its users, we would like to conduct a few one-on-one interviews with some members of the Steering Council. These interviews will allow us to have a more free-flowing conversation and dive deeper into certain topics as we go. Generally, we will want to know about how you got involved in Jupyter, why you use it, what you love about it, and what improvements you’d like to see made.
We understand that you all are extremely busy, but if you can carve out roughly half an hour of your time to speak with one of us, we would really appreciate it! Among the four of us, we can generally accommodate any availability between 6:00 a.m. and 11:00 p.m. PST. Thanks so much for your support!
Hi everyone,
We have started the initial phase of our user research, and wanted to share with you all our findings so far.
First, we conducted a heuristic evaluation, which involves benchmarking the effectiveness of the website against industry usability principles. Then we ran a competitive analysis against the websites of similar products.
What we found is that Jupyter.org is doing a number of things well, including providing a breadth of useful and detailed Information, establishing credibility, and offering user flexibility, feedback, and ease-of-use. The issues we identified were shared by many of the competitors’ websites, such as minor bugs, some design inconsistencies, and missing calls-to-action.
Overall, the website is in great shape, and we have a preliminary roadmap for how we can make some improvements. For the next phase of our research, we will be conducting interviews, so please let us know if you’d be willing to speak with us for 30 minutes. You can also fill out this brief survey.
Thank you to everyone who has helped out so far, and if you have any questions, please don’t hesitate to ask! (The full report can be accessed here.)
Team iO (UCI Capstone Group)
@jhornig - remind me, what is the best way for the Steering Council to reach out to you to schedule time?
One more question as I'm pulling together the draft of this request: is this the program you're all in? Please send me the correct link if not.
@Ruv7 that is the correct link.
@jhornig do you mind posting that schedule so those of us in the nosebleeds can follow along? Thanks for the work you're doing so far!
Great, I shared the call for participation with the steering council earlier today. I asked folks to post here if they'd like to schedule time but if there is something else you prefer let me know and I can update the group with that detail.
@Ruv7 That would be perfect, thank you!
Here's our current project timeline, let us know if you have any questions about it!
@Ruv7 if you wouldn't mind sharing a brief survey via the Jupyter Twitter, we would really appreciate it!
To help guide a potential redesign strategy for jupyter.org, please fill out this brief survey about the data science tools you use. We appreciate your feedback! https://bit.ly/2IILpH8
@jhornig - thanks for the timeline, I shared some feedback with Tim with the goal of making this more visible and useful to the community. For the tweet, the voice of the post needs to come from your group, not from Jupyter. Please re-word that to make some mention of your group. Something like, "We're happy to share that we are partnering with a design team at UC Irvine..." Or something like that. This github issue should be in the survey intro also. In addition, I have some feedback on the survey wording and flow, has this already been activated/shared/launched? Not sure what to call it - basically are people already taking the survey?
@Ruv7 Joseph is working on re-wording the tweet and will get back to you on that. As for the survey, we actually have already begun taking in responses. We will look at the results at the end of this week to support our next research deliverables next week, but we will still gladly take any feedback you have for the wording and flow since we will keep the survey open for the duration of the whole project. Feel free to email me directly at cbui@berkeley.edu to discuss the survey. We've also just discussed with Tim on making the timeline more useful to the community to optimize the collaborative aspect of certain phases, so we will revise its representation based on that feedback. Thanks again for your help!
Also, just to keep everyone updated, we are wrapping up interviews this week and wanted to thank everyone who reached out and volunteered!
I would love to participate. I can meet from 8:30AM to 9:00 AM PST tomorrow (Wednesday, 24 April). How should we speak? Is there a Zoom channel you are using?
Hello Afshin,
This is Omar Filippelli. I will be taking the opportunity to interview you tomorrow from 8:30 - 9:00 am PST. I normally use Skype for the interview, but can switch to zoom if that is your preference. Let me know
Thank you! Omar
On Tue, Apr 23, 2019 at 9:20 AM cbui2019 notifications@github.com wrote:
@afshin https://github.com/afshin Thanks for reaching out! We're just scheduling interviewees with whichever team member has the availability that matches. One of our team members is available for 8:30am tomorrow, so he'll reach out to you :)
We're also working on launching a usability test by the end of the week. We would appreciate any feedback on the tasks that will be asked of participants. Join our conversation on discourse here https://discourse.jupyter.org/t/wip-re-design-of-jupyter-org-website/691/15?u=cmbui !
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/jupyter/jupyter.github.io/issues/331#issuecomment-485874413, or mute the thread https://github.com/notifications/unsubscribe-auth/ALXCKCI7PYXLUYFQGC2BEALPR4ZMVANCNFSM4HCSHU6Q .
Hi @iOmar2019! Let's please use the "jupyter" channel on http://calpoly.zoom.us/
FYI, there is a call that begins on that channel at 9AM, but we should be fine.
Thanks very much!
sounds good, is there a login I need to host a meeting on http://calpoly.zoom.us/? Also, I need to be able to record the conversation.
On Tue, Apr 23, 2019 at 10:43 AM Afshin Taylor Darian < notifications@github.com> wrote:
Hi @iOmar2019 https://github.com/iOmar2019! Let's please use the "jupyter" channel on http://calpoly.zoom.us/
FYI, there is a call that begins on that channel at 9AM, but we should be fine.
Thanks very much!
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/jupyter/jupyter.github.io/issues/331#issuecomment-485904252, or mute the thread https://github.com/notifications/unsubscribe-auth/ALXCKCOVFDHH6NZAWE263C3PR5DDXANCNFSM4HCSHU6Q .
I think @tgeorgeux can help you log in and record there.
Thanks!
On Tue, Apr 23, 2019 at 10:48 AM Afshin Taylor Darian < notifications@github.com> wrote:
I think @tgeorgeux https://github.com/tgeorgeux can help you log in and record there.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/jupyter/jupyter.github.io/issues/331#issuecomment-485906323, or mute the thread https://github.com/notifications/unsubscribe-auth/ALXCKCOOOTFBOE23ZIVUOVLPR5DXZANCNFSM4HCSHU6Q .
Good morning Afshin. The calpoly.zoom requires a calpoly login with student ID I don't have. Tim will be in another call this morning. do you think you can start the call? It will let me join your call.
On Tue, Apr 23, 2019 at 10:49 AM Omar Filippelli omarfilippelli@gmail.com wrote:
Thanks!
On Tue, Apr 23, 2019 at 10:48 AM Afshin Taylor Darian < notifications@github.com> wrote:
I think @tgeorgeux https://github.com/tgeorgeux can help you log in and record there.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/jupyter/jupyter.github.io/issues/331#issuecomment-485906323, or mute the thread https://github.com/notifications/unsubscribe-auth/ALXCKCOOOTFBOE23ZIVUOVLPR5DXZANCNFSM4HCSHU6Q .
Hi! Can we meet here for now? I don't have a way to record, unfortunately.
On Wed, Apr 24, 2019 at 4:33 PM Omar notifications@github.com wrote:
Good morning Afshin. The calpoly.zoom requires a calpoly login with student ID I don't have. Tim will be in another call this morning. do you think you can start the call? It will let me join your call.
On Tue, Apr 23, 2019 at 10:49 AM Omar Filippelli <omarfilippelli@gmail.com
wrote:
Thanks!
On Tue, Apr 23, 2019 at 10:48 AM Afshin Taylor Darian < notifications@github.com> wrote:
I think @tgeorgeux https://github.com/tgeorgeux can help you log in and record there.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub < https://github.com/jupyter/jupyter.github.io/issues/331#issuecomment-485906323 , or mute the thread < https://github.com/notifications/unsubscribe-auth/ALXCKCOOOTFBOE23ZIVUOVLPR5DXZANCNFSM4HCSHU6Q
.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/jupyter/jupyter.github.io/issues/331#issuecomment-486293187, or mute the thread https://github.com/notifications/unsubscribe-auth/AABG6KL63QPXSQBUPQOOFS3PSB4TDANCNFSM4HCSHU6Q .
I am in
On Wed, Apr 24, 2019 at 8:39 AM Afshin Taylor Darian < notifications@github.com> wrote:
Hi! Can we meet here for now? I don't have a way to record, unfortunately.
On Wed, Apr 24, 2019 at 4:33 PM Omar notifications@github.com wrote:
Good morning Afshin. The calpoly.zoom requires a calpoly login with student ID I don't have. Tim will be in another call this morning. do you think you can start the call? It will let me join your call.
On Tue, Apr 23, 2019 at 10:49 AM Omar Filippelli < omarfilippelli@gmail.com
wrote:
Thanks!
On Tue, Apr 23, 2019 at 10:48 AM Afshin Taylor Darian < notifications@github.com> wrote:
I think @tgeorgeux https://github.com/tgeorgeux can help you log in and record there.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <
https://github.com/jupyter/jupyter.github.io/issues/331#issuecomment-485906323
,
or mute the thread <
https://github.com/notifications/unsubscribe-auth/ALXCKCOOOTFBOE23ZIVUOVLPR5DXZANCNFSM4HCSHU6Q
.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub < https://github.com/jupyter/jupyter.github.io/issues/331#issuecomment-486293187 , or mute the thread < https://github.com/notifications/unsubscribe-auth/AABG6KL63QPXSQBUPQOOFS3PSB4TDANCNFSM4HCSHU6Q
.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/jupyter/jupyter.github.io/issues/331#issuecomment-486296120, or mute the thread https://github.com/notifications/unsubscribe-auth/ALXCKCJN4MSYKAE5AMJHRY3PSB5M3ANCNFSM4HCSHU6Q .
Hi @Ruv7, sorry for the late reply. Let me know if this would be adequate for Twitter:
We're happy to share that we’ve partnered with a design team at UC Irvine to help guide a redesign strategy for jupyter.org. They need participants for a short survey, so if you have time to help with their research, they would really appreciate it! https://bit.ly/2IILpH8
Here’s an interesting insight from one of our interviews so far: “Jupyter basically invented the field. Data science could not be data science without it.” What do you all think about that?
https://twitter.com/ProjectJupyter/status/1121462660388646912 - this went out, everyone please re-tweet and share with your followers.
Thanks so much @Ruv7. We're getting a lot of responses!
Here's our latest project plan.
I've updated the top level with deliverable dates. When I have a bit more time to organize files I'll drop in links to deliverables as appropriate.
Excellent, thanks @jhornig and @tgeorgeux - this is good stuff.
We’ve been working really hard on the Jupyter website redesign, and as result we’ve fallen behind on updating you all about our progress. Our apologies. We want to spend this week catching you up on everything that we’ve done so far.
First up is our affinity diagrams. We created two: one based on the functional needs of Jupyter, and one based on the emotional and social needs. All of these insights were gathered from our in-depth interviews with Jupyter users, non-users, contributors, and community members. The diagrams helped us create “jobs-to-be-done” for the website and the archetypes that we’ll be designing for. We’re going to share both of those later this week.
Please let us know if you have any feedback!
Hey everyone! Here's another update for you all. We aggregated our interview data (using affinity diagrams) and formulated jobs to be done, the emotional, social, and practical needs the new Jupyter.org website needs to fulfill.
We'll update you with our archetypes, cognitive walkthroughs, and sitemap later this week.
This all looks really great, thanks for all of your hard work in putting this together!
Two quick constraints that I think we should consider as well and I didn't see in the jobs to be done:
Hope those are helpful! Looking forward to seeing more updates as well!
Those are excellent points @choldgraf . We are definitely thinking about the modularity of jupyter.org. It will be built in a way that allows the community to easily update the website through pull requests.
We also plan on leading people to the proper project documentation pages instead of having different sets of documentation. We'll keep making progress on this. We hope the sitemap will help clear things up.
Hi team! Following with our daily update routine. Here are the main archetypes considered for our redesign effort. These archetypes are modeled from a behavioral perspective. This is a great method for validating user flows and site navigation. It focuses on understanding who does what, when, and why, helping us determine our approach to prioritizing the features and ultimate user experience design for Jupyter.org
As always, we are happy to get your early feedback and commentaries. Stay tune for our Cognitive Walkthroughs posting tomorrow.
Hi everyone! As Omar mentioned yesterday, here is a summary of our Cognitive Walkthrough. For context, CWs are basic interaction design exercises used to step into the shoes of a potential user and see how they might navigate the site based on their persona and hypothetical needs. In this case, we used the archetypes in Omar's post to approach Jupyter.org as first-time visitors. We tried our best to step into the shoes of these archetypes and used this exercise to help our understanding of the site's information architecture and possible user flows.
(Note: the archetype for "new user" is labeled as "visitor outside of data science" in this image)
Hi friends! My name's Graham, and I was added to the MHCID team in the beginning of May!
I'm excited to show our first concept for a sitemap of the website redesign:
Here's a brief explanation of each section with a little more detail than the graphic:
Home
About
History
Hall of Fame
Governance
Partnerships
Projects
Core
Orbit
Documentation
Community
Overview
Events
Blog
We're so excited to continue to iterate through our design process, and create a website that serves each and every one of you. Let us know what you think - we'll be coming back soon with much more!
Hey everyone, We're playing around with some new taglines and descriptions and wanted to get your thoughts on our current drafts:
Tagline: Compute together
Description: Project Jupyter is a free suite of tools for computing openly, transparently, and collaboratively, built by and for a worldwide community.
Let us know what you think, thank you!
This is a nice start! I think the word "interactive" should be in there. Interactive Computing is one of the things that ties together all of the tools in jupyter.
another thought is "data" or something along these lines should be in there as well, given that we are focusing on data analysis not computing in general
Thanks all for this work! Responding to @grrbam on the site map, since partners make up the community of people/organizations who support our work, I would advise that the "partnerships" tab which exists currently in the "about us" be moved to "community". Putting this topic in the "about us" elevates it to a point which may not make sense.
Regarding the tagline @jhornig - thanks for working on this, I would love to have this for our marketing! It will be tough to come up with one that feels right given all the many different use cases we have. Is there room in the timeline/task list to do further research on people's reactions or what is the plan here? This would be incredibly valuable output of this work but not sure it will get much feedback here. Quick note, from what I've seen open source software generally doesn't get pitched as "free" or no cost or any other term that refers to price, the marketing says simply "open source" and I suppose free is implied. Looking at taglines of other corporate entities that make a TON of different products for a ton of different types of users it seems like it leans toward something more cultural rather than trying to summarize what the thing is. That could be the direction to go in here though I would say that's not much easier than trying to solve the existing problem which is summarizing what Jupyter is in a catchy 3 - 4 word phrase. https://www.mycorporatelogo.com/10-corporate-giants-logos-and-taglines/ Open to your thoughts.
Thanks for your feedback @choldgraf! Two questions: it was mentioned to me that some folks make a distinction between "interactive computing" and "reproducible computing." Do you think there's value in trying to be more neutral in our language? And second, I think the word "computing" is generally understood (at least for the most part). But I worry that once you throw "interactive" in front of it, that it starts to become a bit jargon-y for the general public. What are your thoughts? Would love to hear others' input as well.
Hey @Ruv7, thanks for such a detailed response! The reason we threw "free" in there was because during our design jam with @tgeorgeux, we selected 'free' as one of the most important core values to individuals and contributors (more so than 'open'). So we were thinking it might be an important word that would stand out to people. But you're absolutely right that it's implied in "open source" (and everywhere else Jupyter is referred to as "open source") so I'm on board with making the switch back if we think it's more accurate.
Regarding the tagline, some of the research we did suggested that universally-known brands can get away with cultural/aspirational taglines, but lesser-known brands should lean toward a more descriptive tagline (though I'm happy to play with some aspirational taglines!). If this is something you would like to do further research on, I think we can accommodate for that. I'm happy to hop on a quick 15 min call to discuss further if you'd like.
Whenever I use the word "free" to describe Jupyter, I use the construction "free as in speech" and also "free as in beer", where the main point is freedom, not cost. I think that's what the core value is meant to indicate.
I've just returned from UCI this week where I have an opportunity to work with graduate students from UCI on their capstone project. The Capstone cycle for them is two quarters long (around 6 months). Given that Jupyter has limited design resources, I've asked them to work alongside the community to update the Jupyter.org website. The team is made up of four Students who are in UCI’s Informatics program; they have a combined 27+ years experience in UX, Design, and Development. I’ll let them introduce themselves below.
As some of you know, I started some background research on the website last year around this time, a task which was ambitious and went unfinished. I’ve asked the group to continue where I left off in terms of research, and to eventually write up a document that encodes some of the background, goals, vision, and direction of the Jupyter community/products. I’ve asked the team to keep the community updated with their progress, and they suggested a weekly update either here or on the Jupyter Discourse where they can update the status of work to get community input and feedback.
More updates to come over the next couple weeks as we all get into a good working groove. In the meantime, feel free to give them a warm Jupyter welcome!
Schedule and Status (Expected Delivery Date):
Research
Product Design
Final Deliverables