 Great, go ahead. Great. All right, so welcome to the very basic fabricator. The plan for today is to give a very basic introduction to fabricator. And this is probably going to take 15 or 20 minutes. Then we have space and time for questions and answers. So am I still screen sharing? If not, I should do that now. You should try again. OK, perfect. So this is mediawiki.org slash wiki slash fabricator. And this is the central planning page. This also explains why we are changing to fabricator. So you can see here the history behind it, the reasons why we're doing this. You see the past steps here. So you can read up the whole story for the last months, how this decision was made and why, and what work has been already done on this. So originally now I wanted to show you logging in and creating an account. But unfortunately, we have not yet enabled a registration because we still have to sort out small things which took longer than expected. So I'm now only going to show you how it will look like in a few days when you're going to try this. So when you go to fabricator wiki media.org, I should probably show that first. This is the page. I should zoom in a little bit. And I'm already logged in here. But normally in the upper right corner, you would see a power button how it looks like. And when you click on that, you will have a button which allows you to register. This uses OAuth. So you will end up on the media wiki.org page where OAuth asks you to allow access. Afterwards, you go back to fabricator. You define your username, which does not have to be exactly the same. The email address, your real name. And then you click Register, and you will receive an email. And you're supposed to verify it. And the instructions are in the email. So this is how things are supposed to work. Once we have completely enabled registration. Sorry that it's not there yet. So this is the front page. As you can see, there's a few pieces of information here. You see the activity here, what has happened. You can take newly created tasks. You also have an overview of what's assigned to yourself, what you are supposed to work on. And I'd first like to show you how to create a task. So fabricator is a tool which is not only for managing bug reports and tasks, but this is the first thing that we're after now in the next weeks to enable. And the tool to manage tasks and bugs and fabricators is called Manifest. So to create a task, you click the plus button here in the corner, and then it allows you to. Now or at a certain point later? Sorry again. Would you like questions as we go or at a certain point later? You can ask if you want to. Go ahead. So prior to Wikimedia, I ought to ask we use JIRA. And one of the things that was really great about this kind of main page in JIRA was that it was like customizable modules so individual users could have a module on this page that was things assigned to them or things in a specific project. Does fabricator have that ability on this main page? To some extent. I've only played a little bit with JIRA, so I'm not entirely sure if it's the same. But what you're seeing here, the front page, this is already customized stuff. So it's not a default view. And we're very happy to sort out specific requests and if they're doable. And even if it's not doable currently, upstream has been impressively helping us and being responsive, basically. I can reply a bit more about this. So this is totally custom. So it looks like this because we have decided that it should look like this. As a user, if you don't like it, you can create your own homepage. You can just go to the application dashboards and you can create whatever you want. Cool. Thanks, Kevin. All right, so creating a task. Either in the upper corner, it's not only about tasks, as you can see. You can also create design images and other things. Or you just click report a problem here. And it will bring you to a very clean, simple form to report your problem. So I can enter now some title. I can put people into the CC list. For example, Kim Jill or others. And you can easily also remove these people again by clicking the small X button. You can define visibility, though this is something to keep as is normally. You can because you are an admin, but users are not going to see this. Oh, thanks. Yeah, that was part of it. Thank you, true. You're right. Yeah, I was thinking of removing my admin for a short moment, but then I couldn't have shown you other things later. And projects is a type of head. So tasks can be part of a project. Tasks can also be part of several projects or no project at all. So this is very different from, for example, if you're used to Buxilla, where you have a structure that one task or bug report is part of one product and one component. While here, the task can be part of zero projects. So a new user who might not know where to file it just leaves it empty, and the tree editor picks it up and puts the right project there. Or it can be part of several projects. And if you're used to Buxilla, you also know keywords, for example, like accessibility and so on, which are across components. And it's going to be the same here that these keywords in Buxilla, like accessibility and so on, will also be projects. So once this is set up here, you could also add accessibility here as a project. Thinking about from our public users of this perspective, if we can change the label of the field to projects and tags or something along those lines. And I would say the same thing about the next field after that. If this is in user-facing, we might want to make sure that we use very clear and not jargony labels for some of these fields. We can change that. We do soon, or we will soon, remove this weird extra field here, or at least make it non-editable anymore. This is just not fixed yet. OK. Yeah. Then you can define security restrictions, because RT will also be immigrated to a fabricator. That's the tool mostly used by operations. And they have specific requirements that tasks are not entirely public. And this will automatically set restrictive access for it. And then you can add a description to your task, as usual, trying to provide steps to reproduce and whatever. And you see this is like an HTML editor or whatever editor you want to compare it with. There's things to put here. Advanced, we will also be able to create tasks by sending the web interface. So this is the simple, except for the visible here, as I'm an admin, but this is the simple interface that normal average users will see. You see that there's, for example, right now no priority fields. Let me go back to the front page of fabricator and go to Projects here. And here we have several projects. And I now go to the active ones here, not the ones that have already joined. So these are the active projects we currently have. And I want to join a project called Tree Adgers. So I'm now on the project page for Tree Adgers. Every project has an overview page like this. So you can see the open tasks here, and also the go-to work boards. I don't think it's set up for this project, but I will show you in two minutes. I want to join this Tree Adgers project because here it says join with a typo this project to obtain permissions to set priorities, status, and design fields. So this is the way how we currently create a simple bug task creation interface. And now if I reload this form, you see that there's a few more fields, like assigned to, where I can enter one developer or whoever is supposed to work on this, and also setting a priority. So this is creating tasks. Any questions so far? Yeah, I had a question. I was wondering in the description and possibly in the title, does it have the same kind of data shortcuts where you can have bug colon something, garret colon something, git colon? Does it support the same sort of auto linking that a bugzilla does? Currently not like that, because in bugzilla, this is the customization in our code via regular expressions. And we currently do not have it like this here. There is a markup language on its own in Fabricator. Some parts might even collide. It's pretty simple to media wiki markup. And I think we have to see in the future how this works. What I recommend for the time being is using full URLs, because they are fail-safe. But you can do T number for a task that's in Fabricator. Yes, but that's exactly stuff that's internal to Fabricator. So if I want to link to another task, which starts with T, I just enter T123, and it will provide the pop-up and be rendered differently. And the pop-up will tell me what this task is. I should show this, probably, because you also have a description preview down there, which is also something you don't have in bugzilla, for example. And if this worked, obviously it doesn't for me. Ah, now it comes, OK. So you see down here in the description preview, it's rendered differently. And if I put my mouse pointer over it, you see the actual task you're linking to. In the same way, there's other things, like, for example, using some, what's the names? Using the add sign, for example, to mention people, like Greg is registered here. So there's more things like that, but they're all in the documentation. And I'm going to link to later. So I just wanted to show some examples for this. Can a new task be created via an email inbox, or is it strictly via the web GUI? Can you repeat this, please? Can I create a new task by sending an email? So an email to new task? You will be able to. Yeah, I think it's probably not very visible, but here it's written in small fonts that you can also create tasks by sending an email. Because this is also how RT works and operations needs this. I quickly want to show you the project dashboard. As you see, the TRIOjust project here, there's a workboards link in that corner, but there's nothing set up here. We want to increase, sorry, you might want to increase the font in general for the. Even more. OK, I already did. All right, OK. All right, thanks. So this is a workboard. And this is currently the workboard for the project called Fabricator Production Instance, which we obviously have not completely finished yet. Otherwise, you would be able to log in and do other stuff already. So you see you can define columns here, like backlog, which is the one by default, and further ones which you might prefer yourself, like ready to go or doing. You see how many tasks are in this column. You can also define a maximum of tasks in this column. And you can filter the view sort of differently, do lots of things here. So this is basically how workboards look. And you can also simply move tasks here via drag and drop with your mouse pointer. So you can see this here. And the quick way to add it then, of course, is to click here to go to the Edit View. Andre, does this support adding up story point totals for everything in a column? We have not yet support for story points. This would be a custom field that we can easily introduce. However, we're currently waiting for a burn down chart extension, which is developed by a third party volunteer, together with upstream a bit. And Wikimedia Germany is currently playing with this on laps instance. And once they're happy with functionality, we are going to introduce, I think they call it UI points or something as a custom field here. But this will be a few weeks after we're done with, for example, migrating, Vaxilla and RT and everything. One thing that there, Andre, is that you can, so you see on the backlog column is that number six. And on the right to go is number seven. So you can visually limit the number of things in progress, for instance, if you have a can band system where you want to limit the number of tasks in progress. You can visually do that. All right, yes, thanks. As I was zooming in anyway, I'm going to zoom in a bit more because you can see how the interface changes if you see the top bar. You still have the search field there. But if I zoom in a lot, it's pretty nice design. So I should also work on other devices with smaller screens. All right, let's go back to the project overview. I should still have a bigger size here like this. Overview page. Andre, before you go back, can you just on here quickly say what's making the colors, if I didn't miss that? Why do I have them? The colors on the left here? Yeah. This is the priority field in the task itself. OK, thanks. And as you can see here, oh, I'm already part of this project. But I should probably show you instead for a project I'm not part of, like analytics. Andre, can you actually show where that priority is assigned in a task for me and us in the room? Can you repeat that, please? The color is assigned by priority. Can you actually show in an actual task how that is set and where that is set? So I'll just click the one task we have here in analytics. And it's probably, yeah, priority normal, because normal is orange and high is red. But I'm not sure if we just play somewhere like which color means which priority. Yeah, that'd be really cool if there was some secondary. That might be a good idea. Yeah, you're right. And if you want to change the priority here or other fields, you see that this is a separate view from editing. So this is just displaying information here. Well, if you want to change the data here, you go to Edit Task from Vexolavisa for years. So you can follow a task by subscribing it to it if you're interested in an actual task while if you want to follow a whole project or want to become a member of it, you just click Edit Members. No, join project. Sorry, Edit Members is because I'm an admin probably. So you join this project, and then you also receive notifications for it. So any kind of changes in the open tasks of that project you receive notifications for. So if you're a developer or just interested in the progress there, this is a good way to follow up. If this is not fine-grained enough, there's lots more settings for notifications in Fabricator which are linked from the Help page that I'm going to show you later. All right. So I should probably still cover searching for a short moment. You see the search? Sorry. We're on tasks. I saw that when you were in the task, it said Create Subtasks. Is that the Fabricator equivalent of a blocker issue? Create. I didn't totally get it. So you were here on this one, and there's an item on the right-hand side that says Create Subtasks. Ah, Subtasks. Is that the Fabricator? Is that the concept of like in Godzilla we have like a blocker or kind of parent issue? Is this the Fabricator equivalent? This is a bit like the Depends on and Blocks in Godzilla exactly. Thanks. So to search for things, there's this bar here up there. So if I enter, for example, Login, and press the Enter key, I get the list here of tasks which include the word Login if I can change again my query. But as Fabricator consists of several applications and the task tracker is just one, you get the results here for all the tools and applications included. If you only want to search for tasks, you can here click the document type or explicitly go via the front page project. No, I should go back. Sorry. Front page manifest here. And then I can go to Advanced Search. And there you have way more options to group things by. I enter contains one. You also see here that the results look a bit different. So for example, here you can have the colors and more information and to sign in dates and so on. Because this is a specific view for tasks. And you can share this search URL. You might not be aware of it, but the URL that you have in your browser, this is a static one but a specific query. So if you want exactly these results or run the search again in a few days or want to share this with team members, you can, for example, put it on a wiki page to share the search. Last thing I have on my list, I'm already 20 minutes slow. Sorry. Up here, there's the link to my user page. If I had already set a nice image or avatar, this wouldn't be this gray white thingy here. But your user page allows you to see your last activity, what you have worked on, and what else do we have? Yeah, you can also edit your profile and put way more information there. And this is also, I don't want to go too much into details, but this will also be the way how you will be able to claim the imported tasks from Vaxilla and RT by filling in your information here. But this is stuff to sort out probably in an advanced session. All right. Before we end up with general questions and answers, I just want to go back again to the fabricator page on MioWiki.org, because there we also have the migration timeline which shows you which tasks we still have to work out. This will change. It's not definite when you see some dates. It's a bit optimistic, because there's always things that you didn't expect. And down here, yeah, it gets started. You're very invited to play with the test instance on fab-01.wmflaps.org. And you see here there's also more information, like a comparison to what Vaxilla offered. And we have a help and an FAQ which might also answer some of your questions. And if it doesn't, add an entry to the talk discussion page, and we're happy to answer. All right, that's it from my side so far. Please comment, question, whatever. Will the migration from me saving my own bugs that either I created or that were assigned to me, is that going to happen automatically as long as I have the right email person there, or is there some manual process that has to happen beyond adding my email person? So Chase can probably better answer this in detail. But the basic idea is you register in this system at some point in the very soon future. We're going to import the RT and Vaxilla tickets. Then you say in the fabricator which email was yours in Vaxilla, which you used as an ID there. Then you verify this. And then we are very likely going to run a script in the background, which will in the database link these tasks and accounts as it should be to your account. This will not happen immediately because it needs to scale. And we have per month about 500 active Vaxilla users. And if they all try at the same time, but this is very high level explaining how it's supposed to work. OK. Andre, if you go to the main page of fabricator and the setting stuff in the bottom left-hand corner, if you show the email portion, I think that'll make more sense. You mean now on the wiki or fabricator itself? Fabricator itself. And then go to bottom left-hand corner, the Customize Applications link. Thank you. And then if you go to email addresses underneath the link. Thank you. So basically, if you add an email here, and then you get an email and you verify it, more or less, that is all that you would need to use an end user. And if the email that you register with initially is the same email that you had in whatever legacy systems, and you verified it, then you're done. But as far as the tideliness of the metadata getting backdated, I mean, obviously it's hard to test at the scale that will have it. But it's taking a couple minutes per user for the data set we have now, or a minute anyway. So it may take a couple days or a week, I don't know, to work through the backlog of initial sign-up rush. But the idea being that you don't have to go back through and assign to yourself 10,000 tickets or whatever from Bugzilla, that should all work fine. Well, another question about the kind of mentioning of users, when you did the account setup, you had both an email address, a username, and a real name. When you're mentioning someone or adding them to a bug or a fast, can you match on all three of those things? In Fabricator itself, you only have your Fabricator username. So normally you don't have to deal at all with any kind of email addresses or so. Yeah, I'm actually thinking more along the lines of a few weeks ago I sent out a thread basically saying that some people have user names on Bugzilla that are different from their IRC or on Wiki or in real life names. And it's very difficult to find them in Bugzilla in order to assign a pass to them or mention them. So if people are entering real names or email addresses, we pretty much know what people's email addresses are internally. If there's some way to include emails in search, that's at least a consistent way to find people. Well, emails aren't going to be public. This is a common complaint about Bugzilla that email addresses are displayed. It's the second most common complaint I get about Bugzilla that you don't have enough privacy. So I'd rather recommend that people add additional information to their user page on Fabricator if they use other nicknames and other systems. Yeah, that's still a little circular because you have to know their username in order to find their user page in order to reference them. No, you can search for the real name of the user, as long as the user, of course, has introduced it in your profile. You can search for them in Fabricator, but not in assigning a pass to them? Yes, yes. I mean, of course, you have to search first, and then you will know the username. So I'm now in the create new task one, and the assigned field is here, as I'm a member of the triage group. And you see Kim has the username QGil, but as he has entered his full name, I can also just enter Kim, and the proposal will be there. So it's up to the users if they want to expose or enter their real name. And I mean, you can also enter, additionally, your IRC nick if you want to, and then it would be also found here. So it's a bit up to the users how much multiple strings in the real name field, then that would be a much greater likelihood that they would be able to match something when searching for them. Andre, I have a question from IRC. How and when is the migration of current projects like Puggle going to happen? How? I didn't catch the second word, sorry. How and when? How and when? So we currently have the migration plan on the media wiki org slash wiki slash fabricator page, which tells you some dates we plan to start with the RT migration, and then with the Buxilla migration. This date here says earliest 29. As I said before, these dates are very optimistic. This might also be one week later. And it's the same with Buxilla, because we still have a few things to sort out. And as usual, things are more complicated than expected. So RT has a smaller user base, mostly operations and lower level things. So this can happen on a weekday. While for Buxilla, we prefer to start on a Friday and take the weekend, so developers on their workdays are a bit less affected by it. That's my basic answer. I'm not sure if that answers the question, though. You might just say how long in advance they'll be notified of that change. I think the intention is at least two weeks. Yes, that's true, at least two weeks. We currently have a banner already up on Buxilla, but it doesn't tell you dates. But exactly, we want to notify at least two weeks in advance. Right now, I think we haven't talked yet to legal if we can do that, but we might even notify by email once all registered Buxilla users if we're allowed to do that. And yeah, I think that's what I want to say. So I just got another IRC question via private message which asks where people should report self. And basically, it's similar to Buxilla in the tool itself. So we have a project called fabricator in fabricator. There you can create tasks. And if you're an advanced user or a bit tech savvy, you might also be able to figure out first if this is rather something that also should go into upstream development, which means developers which just work full-time on fabricator and are not consumers like we are, basically, here in downstream. More questions, please. Hi, this is S in the office. Will WMF users be so identified, especially? I mean, right now in Buxilla, when somebody chimes in, you kind of go look if it's a wikimedia.org account and kind of think more attention. When we're trying to manage a project, and John does it, this is absolutely top priority for the next quarter, how do you kind of go, well, that's some person I've never heard of from the community? Or are we going to solve that socially? I think we should solve that socially, because we don't, as I said, we don't expose, for example, the email address if it was at wikimedia.org one. We also have staffers, WMF people in Buxilla who use, for example, a Gmail address or so on. So I'd rather propose to solve that socially, that you use a username with WMF suffix or something like that. So if you continue that, we have pretty strict policies on wiki about who can have WMF suffix. Will you and the other people kind of maintain fabricator be policing that to make sure only WMF will add a suffix WMF to their user names? I don't plan to police that. If somebody who you should follow tells you to do things in your company, you should better do them. But I'm not the police guy at the corner checking. I might tell you if I'm in the mood and realize. I don't know. The converse of that. Anyone can put WMF at the end of their name. It's not meaningful with fabricator. That's a good point. That's a very good point. Yeah, you're right. We need to think more about that. You're right. You tend to be a lot of, that's kind of my point. I think, I'm not sure if this is still experimental, but I think we allow linking to the MediaWiki account in just to be clear, Laila said that Bugsilla is out of scope for the WMF suffix explicitly said so. Yeah, so none of that is actually what I'm saying. What I'm saying is just making it sure. Yeah, OK, maybe we can talk more offline. I think this is maybe more of a complex conversation. I think if there's abuse in user names, we can just act as other Wikimedia projects. I guess there's processes for deal with abuse with user names. OK, yeah, that sounds cool. I think back to, as is the original question, was kind of more along the lines of, for those who maintain the fabricator, does the concept of a staff account or a staff flag account, even if the rights don't change, just for the way OIT manages like a WMF account on Wiki is slightly different, then even if the rights are not different, they can be administered differently. When someone leaves, we turn them off. That kind of thing. To be discussed, I don't think we have discussed this. I guess we could set up a group in fabricator itself, which is invite only, but you cannot simply become a member of. I don't think it's currently possible to display something next to the username, depending on whoever the user is part of that group. But I've seen this implementation in Buxilla, and I guess we can sort this out in a few months if we want to have something like that. Are you waiting for questions? I have tons more. Go ahead. So I was looking, it seems like projects can have multiple boards, but I looked at a few, and none of them actually do have more than one work board. So how does that work, and what would be the point of that? Projects don't have multiple work boards. Yeah, I myself am not aware that this is possible. You would have, for example, sprints as projects, and they can have a board. But as far as I know, you cannot have several work boards for one project. Well, it does stay plural. I mean, if you go to the project page, there's a link to work boards. And everyone I've been to, it's either there. It hasn't been set up, or you just see one. But I would make sense to have previous sprints, or backlog, or things like that. If the problem is the plural s, then it's the plural s, which is the problem. The truth is that as of today, one project is one work board. And if you need more work boards, then you need more projects. Cool. OK. Andre, where are the quips? I'm afraid that is a severe regression from Baxilla. Quips are these small sentences that are displayed at the top of the search results, which anybody can add such quips in the system. So mostly funny sentences or so. And I hope that somebody is going to provide an extension in upstream fabricated to support that. Can I ask that once we are actually allowed to log in, we have another meeting maybe that just focuses on custom dashboard creation for the main page? Because I think that can be super useful, but probably only once we can actually log in. I volunteer doing that. I have plenty of fun with dashboards. And I would love to share this passion with others. Thank you. All right, I'll put you on the camera, Dukin. Is there any concept of wanting maybe a work board to come on the dashboard being up all the time, like if we had a dashboard in the office or just a read-only view of that kind of thing? Is that a simple thing to put together? I didn't understand. Imagine if I have a giant TV that's over by Jared's desk and it has Jared's team's projects in real time on the board, just as if a status board, a display board, a kiosk, keep using words. So I see why not. The only thing is the real-time refresh. You would need to reload that browser with your magical script. Yeah, there's plug-ins for that. Cool, so that's easy for a read-only perspective. Oh, OK, yeah, so I think I caught that earlier when Andre made a change to something. There's no kind of nice, modern, age-axing as to any of the interface on the fabricator. Everything requires paper, though. There is some real-time daemon that you can run that does this kind of stuff with Node.js, but it really hasn't been an implementation priority. I don't necessarily know how it performs on scale, but it would do stuff like someone just edited the ticket you're viewing kind of stuff with a little pop-up. Real cool, especially for teams that are coming from Trello and expect that kind of thing to happen. So heavily used in the code review space, obviously. And I would expect that it would be looked at in conjunction with that. Cool. Are there general APIs for reading fabricator data? There's a whole mess of APIs, and it's all JSON rest-based. So yeah, there's a pretty nice Python wrapper. Python dash fabricator, written by the discuss guys, and that's a fairly good introduction to the API overall, and transmission. Thanks, guys. Any more questions? Last chance? OK, awesome. Thank you. Thanks for the great talk, Andre. Thank you, everybody. All right.