| 28 Mar 2018 |
 hexmode | https://riot.im/app/#/group/+mwstake:matrix.org | 17:30:24 |
| hexmode | sabinemelnicki: could you verify that you can see all rooms on the link above? | 17:31:58 |
 cicalese | So, I tried logging out. If I go to that link , it requires me to log in or create an account. So, sadly, we cannot use it as an information page for anonymous users. | 17:35:27 |
 groundginger | Why can't I click that link | 17:40:47 |
| cicalese | For some reason it thinks it is a file link. I had to cut and paste. | 17:42:09 |
| groundginger | Same | 17:43:28 |
| hexmode | try +mwstake:matrix.org | 17:51:54 |
| cicalese | That is a clickable link, and it does work both from the desktop app and the browser. In the browser, it actually takes you to the page that allows you to grab the URL of the community (group). But, you can't see the group page without logging in. | 19:01:13 |
|  benfletcher99 joined the room. | 19:23:34 |
 rundg | @hexmode:matrix.org: there may be a BOM corrupting the JSON | 19:43:43 |
| hexmode | Another version of riot.im indicated there was another error. or at lest the message was different. | 19:44:59 |
| hexmode | We probably just need to file an issue on it. | 19:45:14 |
| hexmode | freephile: this looks like the issue I was seeing: https://github.com/vector-im/riot-web/issues/6263 | 19:51:19 |
| benfletcher99 | I'm back, sorry I'm jumping in and out of my holiday. I'm glad there has been some thoughts on a bit more structure, I would 100% agree with that. I am struggling to follow all the directions that conversations are heading down. Although I think it is key is that we don't have "stove pipes" so we need ensure we are providing group updates. Combined we probably have all the skills and represent most of the stakeholders, that iterative feedback is crucial for each stream of work. A real success of the create camp was the visual editor issue that was mentioned others weren't aware and a solution was created. I didn't even know that existed but would have murdered someone if that happened to me. If I talk through the workflow as I understand it, or naively believe it should work. Someone says "this is a good idea or this is an issue" we all agree and then it is raised as a Phab ticket. A team then says they are interested and they form a team to tackle it. Do we create a room for them at this point? Maybe I come from too rigid a background but how we do it at work is using an agile board https://goo.gl/images/crZMN6. There are loads of tasks floating around in the back log and these priorities change. When you select one of the tasks you drive it to completion and then you move onto the next one. You don't necessarily do just one but you also don't spread yourself so thin that you don't complete any. What I'm trying to say is that I believe we need to have list of our backlog and then collectively priortise and volunteers to drive solutions. At the same time we have a level of visibility and feedback because we can all offer smart ideas. So my suggestion would be: | 20:31:11 |
| benfletcher99 | sorry return posts it early... | 20:32:06 |
| benfletcher99 | I would go with Cindy's suggestion but make it clear that general is for high level, "hey guys look at what we have just done" or "does anyone else think we need a security white paper?". Random should be as it says, veering off all over the place keeping us sane. | 20:33:47 |
| cicalese | Yes, separate rooms for conversation. Conversation may result in specific tasks that get created in Phabricator. Phabricator tasks are managed on the Phabricator workboard: https://phabricator.wikimedia.org/project/view/1071/. If we need more structure for the Phab tasks, I also created some subprojects, which you can see on the right sidebar of https://phabricator.wikimedia.org/project/profile/1071/. Each subproject can have its own workboard. And we can create more subprojects if necessary. But, all of that is to wrangle individual tasks. Discussion leading up to tasks would be in rooms here. (I also come from a very rigid, process-oriented background, so I apologize to those who are now freaked out by how good all of this process makes Ben and me feel.) | 20:43:29 |
| groundginger | Same | 21:17:19 |
|  Sam Wilson joined the room. | 22:24:54 |
| cicalese set the room topic to "MediaWIki Stakeholders' Group general discussion". | 22:31:58 |
| Room Avatar Renderer. | 22:37:31 |
| cicalese | I have updated the list of rooms in the Communication section in the right sidebar of https://www.mediawiki.org/wiki/MediaWiki_Stakeholders%27_Group. Feel free to fix any errors, please. | 23:50:20 |
| cicalese | And please join whatever rooms you want to. | 23:50:59 |
| 29 Mar 2018 |
 darenwelsh | Some feedback ... These are all under a section "Communication" that also includes links to a mailing list, a phab task, and blue jeans (what is that?). It might help to explicitly group by medium (riot, phabricator, etc) | 00:32:25 |
| darenwelsh | Or instead of re-ordering it, just explicitly say the medium in parenthesis. | 00:41:11 |
| darenwelsh | Like "Projects: Showcase wiki (riot chat)" | 00:41:44 |
| cicalese | That would be fine. If anybody would like to edit it in that manner, please feel free. | 01:58:41 |
|  dataspects changed their profile picture. | 03:57:54 |
| benfletcher99 | I have put a background description in https://riot.im/app/#/room/#mwstake-showcase:matrix.org. Please join if you want to show off your skills or just be part of the awesomeness. | 09:25:30 |
| darenwelsh | Tune in to watch today's EVA (led by James Montalvo who developed and wrote their procedures) https://www.youtube.com/watch?v=wwMDvPCGeE0 | 12:03:04 |
