chat_gregor_julia_on_camp_dashboard.txt

gregor [6:33 PM] 
https://github.com/hoodiehq/editorial/issues/61 – Stephanie from Digital Ocean is looking into this as well, you’d work with her. You’d make a great team I think, she is good with writing / managing, you are good at coming up with the right information architecture and ux, sounds good?

[6:36] 
I had a cal with Stephanie last week, she added notes to the issue description, can you read it and we chat then?

julia [6:39 PM] 
let me take a look

[6:41] 
All right awesome I read it

gregor [6:43 PM] 
any questions?

julia [6:48 PM] 
cool i read again and took the information down

[6:49] 
I pretty much understood that it will be a page divided up between some sections

[6:50] 
Contribute to hoodie: -how to become a contributor / maintainer. Mascots: showcase different tracks, understand each teams workflow and have information from each track so contributors can access it. and then the tracks themselves, under tracks i read that maybe also include git workflow and formatting pertaining to each track and then show issues for new contributors (yfpr) but also show all issues tagged under the category

gregor [6:51 PM] 
I think things like git / pull request workflows can go into a generic category, as it is relevant to all teams

julia [6:52 PM] 
true thats what i thought

[6:52] 
but didn't know

[6:52] 
so git workflow and pull request formats should just go under Contribute to hoodie on top

[6:53] 
idk im envisioning like a main section when you open it

[6:53] 
Heres how to become a contributor

[6:53] 
or maybe like show what kinds of stuff we got first like not only code but design, docs, editorial

gregor [6:53 PM] 
yeah it should be an overview

[6:54] 
but it ideally would also directly show open issues that people can grab, not only text explaining how to contribute

[6:54] 
something more with an app dashboard character in my head

julia [6:56 PM] 
okay so maybe it can link you to some text if you wanna read specifics

[6:56] 
but it contains an overall but then the dashboard of issues

gregor [6:57 PM] 
yes exactly, there should be documentation that we can link to, but it should also dynamically load and display things directly from github

julia [6:57 PM] 
what exactly would you be showing from github. issue title and then whats written in it?

gregor [6:59 PM] 
I could imagine that we make a new repository where we put in all issues for new and existing contributors that are well described. We tag these issues with "yfrp" or another tag for people who contributed before, and with tags for the different teams like "design" or "documentation"

[6:59] 
then we load all the issues and pull request and display them by category and status

[7:01] 
for example, just an idea, if I’d come to the page for the first time, the page would be in a "first time contributor" mode and it would display the first few open yfpr issue from all categories. If I’m a designer, I could click on "more design issues" or sth similar and it would show me the dashboard for the design team, highlighting all issues for first-time contributors

julia [7:01 PM] 
got ya

[7:02] 
that includes then a lot of work on this new repository

gregor [7:03 PM] 
yeah, my idea is instead of new people coming to hoodie and having to find their way around all the repositories, there should be a single place which has all open issue prepared for them. Of course there will still be the other repos, but ...

julia [7:03 PM] 
so how will it work

gregor [7:03 PM] 
... one idea is to win more project maintainers from all teams, that will help spot issues spread around different repos and prepare more actionable issue in this central repo

julia [7:04 PM] 
you make an issue on the repo you want but also on that one other repo

gregor [7:05 PM] 
let’s say I got this issue here: https://github.com/hoodiehq/hoodie-account-client/issues/31

[7:05] 
it’s not very well described, at least not for contributors new to the project

[7:06] 
I could invest some time and describe it better by adding more information to it

[7:06] 
when I do that, I would create it in the central repository we talk about, and then close https://github.com/hoodiehq/hoodie-account-client/issues/31 in its favor

julia [7:06 PM] 
I see that makes sense

gregor [7:07 PM] 
the idea is to have a place that unites the different teams, so we work together on this, and also having a healthy competion in some way :simple_smile: where all teams try to keep having  a threshold of issues ready to contribute to

julia [7:07 PM] 
so who will be in charge of writing to the main central repo

[7:07] 
do you begin to submit to the central repo only then?

gregor [7:07 PM] 
you mean creating these issues?

julia [7:07 PM] 
yes

gregor [7:08 PM] 
everyone. On this contributors dashboard thing we want to create, I’d also like to add documentation on how to create these issues

[7:08] 
the idea is to also grow the maintainers team, not only contributors

julia [7:08 PM] 
it makes sense

[7:08] 
how do you envision starting all of this :smile:

gregor [7:08 PM] 
and maintainers are people how do reviews for pull request, who review open issues, find new ones, and create these contributor-friendly issues

[7:09] 
https://media.giphy.com/media/ujUdrdpX7Ok5W/giphy.gif (1MB)
julia [7:09 PM] 
sounds like we need small things here and there like figuring out tag names, workflows and how to create issues

gregor [7:10 PM] 
I think I have a pretty clear idea about these. What I don’t know is how the UX for the actual dashboard could look like

[7:11] 
I wonder if we can start with dummy content, making as if we would have issues for the different groups ready, and then focus more on what people will see who want to contribute to Hoodie, or people how want help maintain it

julia [7:11 PM] 
yeah we can definitely start with that

[7:11] 
but yo should probably also be writing the stuff you have a clear idea about

[7:12] 
what exactly do you wanna see on the dashboard you mentioned all issues but you can filter between design, editorial etc. and add filters on top like YFPR

[7:12] 
issue title, and description?

gregor [7:14 PM] 
maybe just the title, but I can click on it and it would show me the description and a link to the issue?

[7:15] 
For me, I’m confused on a higher level right now, I don’t know what to put into this and what to leave out :simple_smile: I don’t know how to call it. My thoughts jump back and forth

[7:16] 
for example I thought maybe we call this whole thing "camp" like the current release. We can keep the camp even after this release, it’s the place where all the contributors hang out and get the latest and greatest

[7:17] 
it would also fit because we said for the Hoodie "Camp Release" we want to focus on contributors. I makes all sense in one moment and then I’m totally confused in the next :simple_smile:

[7:17] 
I’m sure you have been there, in this place where you know you can figure this out, but you haven’t yet, and you go circles

julia [7:19 PM] 
yes

[7:19] 
I like the camp title and idea

[7:19] 
it makes sense to me too

gregor [7:20 PM] 
yeah to me, too :simple_smile: But then I think we should also put in progress updates and/or sth like this: http://gr2m.github.io/milestones/

[7:21] 
and then it grows and I wonder if this is not getting too big? Maybe not, but for a start, what’s the minimum viable thing here?

julia [7:21 PM] 
what do you mean

[7:22] 
put in progress updates

[7:22] 
I don't understand

gregor [7:22 PM] 
I mean updates from Hoodie, the product, that we work on.

[7:23] 
hmmm maybe I’m biased here because I’m a coder

julia [7:23 PM] 
you want an updates page that looks like that?

[7:23] 
i barely understand milestones to be honest :confused:

gregor [7:24 PM] 
the idea is to have something like an overarching roadmap, which we currently have
1. Camp Release
2. Village Release
3. City Release

these 3 milestones have different things that need to be done before we it’s done, all teams have their respective contributions

[7:25] 
or to put it in a more generic way: for returning contributors / maintainers, how do we answer the questions: Where are we with Hoodie right now, what’s next, what’s the plan after taht?

[7:27] 
but instead of only showing a snapshot of the roadmap, it would be nice to have something like a log, where we say things like
– Jenn finished the "Camp Release Press Release"
– Carolina created the Camp Release Illustration
– Nick finished documentation for hoodie.store
– Magda translated the hoodie.account docs to Russian (edited)

julia [7:28 PM] 
that makes sense now

gregor [7:28 PM] 
so maybe there are three main sections in the camp dashboard
1. Contribute – show open issues, dive into sections of the different teams
2. Roadmap – show where we are, what’s next, what happened lately
3. Documentation – for contributors & maintainers

julia [7:29 PM] 
it makes a lot of sense i just wasn't understanding the milestones design

[7:29] 
its not as easy to understand but when you put it in words i get it

gregor [7:29 PM] 
thanks for your patience with me, I’m glad you can make sense of all that :simple_smile:

julia [7:30 PM] 
yeah i like how you put it in 3 main sections

[7:30] 
we can probably sketch how these will look like you have enough ideas

gregor [7:31 PM] 
yeah first time I came up with these sections idea, that makes sense to me, too :simple_smile: also we could start with the "Contribute" section to get things going, and then add the other sections later

julia [7:31 PM] 
yeah i agree we can do that :simple_smile:

gregor [7:32 PM] 
okay, what’s our next step?

julia [7:32 PM] 
we can literally sketch on a paper what you envision this looking like because you've got a lot of it written down so try to come up with how it will look

[7:32] 
i can help

gregor [7:35 PM] 
okay great, I’ll try to add a summary of what we discussed to the issue: https://github.com/hoodiehq/editorial/issues/61 (edited)

new messages
julia [7:37 PM] 
awesome, add the three sections and all that that you came up with that boiled down

gregor [7:38 PM] 
aye aye