 So let's get started. Hi My name is Jacob. I always knows Jay Perry and this is Tatiana and So today we're going to talk about The future of groups on Drupal.org or groups to Drupal.org cool and I think the way we'll do it with people that are here is we'll sort of be a little interactive So if you have questions feel free to ask them although we do need to have my I just see if it was taped down. So yeah, if you have questions or comments Feel free to go up to the microphone and we can just sort of go back and forth as we have this discussion. So yeah, so first sort of start with everyone knows sort of the history of groups it was created to provide groups user groups on Drupal.org and so the future of groups like all the other content on Drupal.org is sort of tied into the content strategy that we've been working on for over the past year and so the Basically, we've been looking at user research on who's been accessing what how many pages we have Where does content fit best and and how we've been sort of dividing things up into our subsites and groups is one of them And so you can see more about this at a talk that Tatiana gave yesterday So yeah, I would invite everyone to go there and watch that to give a little more background about The overall content strategy. So this will be about specifically what's happening with user groups on Drupal.org So so what are they used for you can see here? These are the the main the main user groups, so We're doing announcements. So one of the things that groups were doing was sending out emails to people because there's this notification system We have project-based groups because projects on Drupal.org weren't able to do the collaboration that we can do there We have initiatives That also we didn't really have the ability to do any collaboration on Drupal.org local user groups and interest groups, so we have our local cities and something like events organization all here on GDO so how does that look as we're looking into the future? As we are putting together the content The strategy we see that the announcements are really blogs that we can put on Drupal.org project-based groups really is a subset of projects which We'll get into in a moment and the working group initiatives is going to be part of another initiative content type and as Drupal.org itself is moving to organic groups to structure its content That's why it makes a lot of sense to start moving those things into Drupal.org We're going to focus first here on project-based groups The other two are sort of well-defined and then we'll talk about local user groups after that So first projects so who why does that look like crap up there? That's really odd Fullscreen this button Ah That's so sad. Okay. Well, I'm gonna like walk. I'll just push that laser pointer. Okay, so the gobbly goop Groups look so nice here So we have media you can sort of tell because you can see Dave Ruiz face there We have media there where we have a group's discussion. We have news pages. We have events We have that stuff. We have the media Landing page in the middle here, which maybe I can use my man. Ah, there we go We have the media landing page here So this has some of the metadata for the media project itself And then we have this whole Drupal media org which has its own events and a Guide and then links to both of these pages and so we've seen this in a few other projects But this is a really good example of of how groups and the limitations of Drupal.org has Fragmented how just a simple project could work So we're hoping to help solve that problem and the way we're planning to do that is by basically integrating the project-based groups into project pages so all projects will become groups and We can then assign content to project pages This also gives us the ability to do events. We can do documentation We can be using panelizer for our layouts, but for now, I think everyone's going to be the same And we can also do things like maintainers through OG. We can have documentation maintainers So I believe there's a documentation Is there a documentation talk? Don't remember. Well, we talked a little bit during content strategy But documentation is the big one that will come into Projects so when you go to a project page you can go to the documentation to that project page instead of going over to the Book section and then trying to find it through the myriad of whatever is there So that is an example of what we could end up seeing like this So that still looks like crap. All right. Oh, well, so here's here's an idea of here's the media page Here are links that would go to the different sections. So like the events that They would have the documentation pages that they would have The developers page you'd still have the metadata on the front page and you'd have your download links Here's an example of the developers tab which may like open up more information about the Download tab or the downloads and then you can have your version control information here and and stuff around developers So so we're sort of starting to move this way where everything could be on one page So you could take those three pages and put it into one Any questions or feedback about that? Yeah, go for it I'm just wondering if you were planning to have it that a user would be able to say what the default one they land on He's Oh the default tab. Yeah, um Probably Not at the moment I'm just trying to think of like how we do that Hasn't been really discussed but most likely we'll keep the same Interface for all the project pages and maybe Neil has a user as in You want to use some modules or user as in you want to maintain some modules? That's a good point actually Because Emily is shaking her head as we're arguing about how like I like I really want these download things here But I don't really care about the metadata, right and and so is that sort of where you're getting at? It's not so much. Don't care about it. This is like it's not the stuff I care about every time I go to the page, right? So you probably look at it once but then you want to be able to Interesting. Yeah, that that's Yeah, well Yeah, you'll need a whole design process if we do something like that probably be more like the The if you double-click the if you have a mouse and you know to double-click the date on Issue comments, it'll toggle and remember we're at toggled or the field sets on issues will remember where they are So yeah, that's good feedback though because that might I like the idea mainly from a standpoint We might be able to make the front page actually more contextual for people who have actually never visited there So we can hide a bunch of the crap that you know people might not want but Yeah, so I know it's all useful depends on who you are, right? So Yeah, so context switching would be interesting. Thank you for that So, yeah, any other questions about projects as groups comments? Cool. All right so next So we're looking at doing moving projects over and Initiatives and and those other things, but what about our local user groups and our interest groups? and and so the future does these groups and groups to triple dot org and Are our right now reigning idea is no So we're looking at migrating local and interest groups also into triple dot org Which would basically be the rest of groups to triple dot org The first and big thing is is actually integrating user profiles better. So you have a unified Area for your profile instead of two profiles Everything gets indexed into solar. So there are ways we could make groups work into solar But it's a little more work and it doesn't really make sense to have two sites for that Just talked about user profiles You can have an activity stream Possibly on your user profile your credits as you're talking and things doing documentation Can all be put into the existing systems? We have on triple dot org and then as we're deploying features a lot of the features that Individual groups need are things that our editors need for marketing or projects need it can be all deployed Once instead of multiple times and lastly and I think the biggest thing we've seen with the Drupal 6 to Drupal 7 upgrade Which hasn't been happening is that it's been really hard to find? good consistent contribution to groups, so It'll lower our maintenance costs as we just have one site to maintain it and just for some data I think we have something like It's like 5% of the content on like in the whole Drupal dot org ecosystem is on groups It's a very small percentage. So when we looked at Seeing what content, you know, how big of an impact this would have It really didn't look like it it would have that much so And yeah, so yes questions comments so I'm the community leading Melbourne in Australia and so we use groups, but We started using meetup because someone created a meetup group and I was wondering what One of my colleagues actually created a module to integrate with the meetup API so that it could post Events on GDO potentially It was for GDO then but it would be really great to have some integration like that so that you don't have to post it to multiple places Yeah, so we'll talk about events here in a moment But the idea is we're still trying to parse out. Well, we'll talk about events in a moment, but yeah So let's talk first about local user groups I'm hoping that maybe the recording will show this better. I'm not hopeful It's okay. It shows the gist. So as you see here, here's like three different types of local user groups We have Pittsburgh that has one little layout design thing. We have I believe that's China sorry China and then here's like Seattle so we have like all these different types of Interfaces for their groups sort of reminds me of this, you know, it's like the MySpace you can do whatever you want good or bad mostly bad So what we end up having here? We want to try to like get this together into a good layout system and Let's see One way of doing that is basically taking putting together communities that have a centralized presence on Drupal.org and get their functionality, but not not the not the MySpace ish part Here's an example from mozilla.org Basically, you can click around to each country and it'll show all the listings of user groups and those user groups will have a similar layout another way to look at it is sort of like Facebook pages people have a lot of Customizability that they can do on their pages, but they all have a similar layout So when you visit their pages, you're not inundated with Various layouts that that make it hard to find things That's the big thing we're going for there So speaking about events So here's the Drupal.org slash events which I believe is mainly I Think that's actually either text based. I think it's actually be manually copied in Yeah So that that's that's going to go away and then we have a GDO events page Which is a listing of events per per group And those will all be migrated into this new events system. We have events dot Drupal.org which is for the Drupal comms But we're looking at something similar to Drupal But putting more of our Drupal.org features into it so Looking at integrating what Drupal has and you can see again the map with the user groups will be basically trying to do something similar to that so you can see what user groups are happening what events are happening and Good suggestion about meetup because even even if we give all the event functionality, I know that there's a lot of Culture or business rules that sort of dictate the need for meetup like people on meetup.com searching for other meetups in their local area and I can understand that even Right so so yeah, so the statistics it'd be great to have statistics It would be great to have registration data on that It'd be great to alleviate different camps and I don't think meetups going away Just because it it does what it does and and like the github conversations I think integration is probably better than than nothing but again all really preliminary So I would say you know, so I like the idea, but we'll see we'll see how it goes make an issue So how are we actually going to do this so Basically Projects we're gonna have to do a manual audit for them go through each project and figure out who what projects have a mapping on GDO and then take those projects and Provide basically give them a migration path so we can get them on to Drupal.org Don't think there's actually that many projects so that shouldn't be too hard The second part is that the local and interest groups since they don't exist on Drupal.org We are not going to do an automatic migration So what's going to happen is there's a little migrate button that we are going to post probably This is a again draft mock-up But the idea is we will add a migrate button and then we will have a window of Probably a few months that we we won't create new groups on Drupal.org It'll be sort of a beta period to try this out And it'll give a chance for all the existing GDO groups to migrate themselves over and have that namespace And then once that's done Yeah, so so yeah, so the next part is we won't be doing OG panels We are looking for specific group pages. There may be Various layouts we need to adapt that may make sense for them, but we're not we'll do that on a case-by-case basis I'm curious about feedback here polls. How polls are they useful in groups? Just raise of hands, I guess Perfect. All right, so that's about as good as yeah, so so poll migration is unlikely Yeah, as yeah Discussions are now posts on Drupal.org so they will will migrate will migrate all of the discussions into posts and Notifications we are improving notifications in general on Drupal.org and so what you expect out of GDO should be Over on Drupal.org as well Any questions about migration? Comments things I'm missing. Yeah, I think so the period of migration Yeah, yeah go Tim For manual migration There's actually going to be a decent chance that the period to do that will map closely to the long-term support window for Drupal 6 Because we will be migrating from a Drupal 6 site that we won't be upgraded So yeah, it'll probably be pretty close to whatever that winds up being right Yep I think that's probably about right and then when that manual migration of my hope is that while that if We can put together the frameworks properly we can start the migration of local user groups a little bit after we start doing the migration of projects and so Manual migration projects are going to take a while and so like three or whatever months And then give them that window and then once that migration is done and Drupal 6 is like then Then we'll cut that off which leads us into the next part The GDO sunset beautiful sunset so yes So once you have a migrated group we the hope is that all of your nodes there will redirect to something on Drupal.org Hopefully once you hit the migrate your group will be turned read only so nothing else will be posted there But it will it so so it'll still be there, but you won't be able to access it The user authentication will eventually be turned off on GDO all together And so the the sites that did not migrate and things are just left there They just will be left there and then eventually we'll go to HTML archival where We'll add all the URL redirects we did in Drupal We'll probably just paste into an HD access or add. I don't know exactly what we're going to do there But something like that where they'll just do its thing Yeah, so Questions about sunset Go for Yeah, it'll just be a static site some page. So Yeah, yeah, so content that can be migrated will get a chance to Content that can't will be migrated will redirect and content that doesn't migrate will just stay there. So, yeah So yeah, and then Timeline so right now documentation and projects have higher priority Q4 is sort of the the timeline. We're working documentation like next week. I believe we've already started working on documentation Yeah, it's a long process so Yeah, so so documentation starting projects has started Event listing and local user groups will happen after that. So expect something near q1 Yeah, q1 q2 and then we're hoping. Hmm. Oh, yeah, so The hopeful eventual sunset will be mid 2016 And then all this is subject to change depending on how long the documentation migration goes How hard it is to get projects over etc. I can't say that we've done I can't say we've done We already have og on Drupal.org so That part's been done. We're working on migrating either panelizer or page manager to sort of manage that part We are working on the content types So so there has been some work already done to lay the framework out. And so, yeah, we'll see hopefully that probably yeah I assume with migration you'd be doing content types that are fairly easy to map But I know with at least our group. We've got custom content pains On the front page and stuff like that. Yep. Is that we'll just have to recreate them or those are going away So, yeah, yeah, it's the only way you could really do it. Yeah, so so the myspace ish Yeah, the myspace pages are going away So basically actually all the custom pages are going away So a lot of places have to add, you know, either custom events pages or custom random pages of whatever and I don't foresee those Going into The new system those aren't going to be migrated We will have the ability to create Pages that will have panelizer on it. So you could you know add those as as items later, but Right now, I think we're trying to streamline down basically everyone to a consistent UI Yeah Yeah Right. Yep. So so yeah, we're right now working on the design for all those pages and I'll tell sort of dictate But I'm pretty sure that Regardless of the design, we won't be migrating any of that that previous stuff. So It would be really really hard and from six to seven. I don't even know if there's a really good migration path There is an og panel. So I see Emily's Yeah, and it's not a good idea Yeah, we want actual designs not ramp stuff. Yeah, and I think that's part of why we want to migrate on the group owners schedule With the button. Yep. So all of the custom stuff won't be it won't be pulled out from under you Until you do it yourself. Yeah Yeah, exactly. Well, it's like a migration button say here warning You're gonna have these things go away and and if you really liked polls well, I'm sorry, you know and Yeah, so that's probably how we'll Will there be any way will there be any way to see what it looks like the first Right. Yeah, well, we'll test it in staging and maybe even have a staging load for for the migrate button We'll have to figure it out. Yeah, so this is why the timelines are subject to change Because it's a software project. Yeah, I I imagine since the layouts will become similar You'll get a chance to see like we'll be migrating projects for instance to new pages Yes, right. Yeah, there won't be a whole lot True. Yeah famous Oswords. Yeah in theory, but yeah, we have Jira We use internally on top of the Drupal.org as you queue. So we'll do it when Jira tells us to do it And Tim's our project manager. He sometimes tells us what to do. Yeah, so yeah Cool, well, thanks that that that basically Those are the slides. So Yeah, let me I love to have other questions comments. Feel free to Go up There ain't All right, cool. Well, thank you so much