@bd808 That sounds great! :) Let us know if you need any help.

In T234632#5604919, @brennen wrote:

During planning discussions, it came up that we'd like to have this session happen prior to T235372, on the theory that there's a natural progression from one to the other.

Thanks @brennen ! I have added you as co-lead.

Hey @bd808 and @srodlund , that would be fantastic if possible! Could you both confirm that you would like to go ahead with this, ASAP? I think the committee will be removing sessions without a confirmed leader soon.

@jeena Awesome, thank you! :) I will add you as a session leader for both, please feel free to fill out the rest of the template as you see fit.

In T234634#5580278, @apaskulin wrote:

I’m assuming session leaders need to be attending the conference?

We're still looking for a session owner for this session, as well as T235371 and T235372, in order for the proposed sessions to go ahead. @kostajh @Florian @hashar @jeena @Tgr @bd808 would you be interested in leading any of these sessions?

Hi all, we're still looking for a session leader in order for this session to go ahead. :) Once we have one, we can proceed to narrow the scope down, perhaps splitting into subtopics based on feedback here.

Hey all, we are still looking for session leaders in order for this session to go ahead. :) Would anyone like to take it up? @Tgr @Addshore @Quiddity ?

Ah, okay. :) Is anyone else interested in leading this? @TK-999 , if you'd like, maybe someone else can lead, and you can co-lead and learn the ropes from them along the way?

Thanks for the feedback! As proposed above, I have edited the title of this session to focus on MediaWiki core, and added two sessions: T235371 and T235372 for discussing adoption/long-term maintenance and complex multi-service development.

Maybe something on the line of "best practices & useful methods for remote teams - volunteers and staff alike?"

In T234634#5566953, @TK-999 wrote:

Storing documentation in a VCS repo, perhaps next to source code even, could be an interesting alternative to consider, as it might allow for an easier review and contribution process. The session could also look at some other open source projects to see how they store and curate documentation.

@TheDJ That makes sense - I think we can definitely add more specific goals once we start the process of building this session. Would you and/or @Tpt like to be the session leader/co-leader?

In T234634#5565267, @brennen wrote:

One suggestion for a focus: Maintenance & cleanup of existing docs. This has come to mind thinking about docs and new developer onboarding - there's a ton of material but it's not always clear how it relates to the current state of things or how to navigate it. Technical debt lives in the documentation as much as anywhere...

@hashar Hmm, good point. If we were to break the scope down into a couple of more focused discussions, what would you suggest?

Hi all, thanks so much for the feedback! Based on the comments, it sounds like it might be a good idea to:

Sorry for missing this. The redesign happened, but the implementation is unstable and work in progress. I've created the follow-up post on GitHub. :)

The slides for the talk can be accessed here if anyone wants: https://docs.google.com/presentation/d/1G-zqkIW1kHvGTUtEAv--opDYQQbwyqo2Mhd7OQEYH5Y

Hi Rachel, I am more than happy to present at the opening talk. :) We are currently still trying to reach a consensus on which tasks would be good for the hackathon, but we should be able to sort things out by then.

Just wanted to post that @maskaravivek 's solution works for me (for the most part). If no issues, we will be pushing a release with this implementation very shortly. :)

I cherry-picked the change onto our 2.8-release branch - should be fine to just release this in 2.8, no need to wait for 2.9. :) Thanks @Nemo_bis !

I saw your mailing list post. Nicely-written, well done! :)

Hi @Tanvidadu1998 , I trust you received Srishti's email? :) I think you can start writing updates about your progress at https://www.mediawiki.org/wiki/Google_Summer_of_Code/2018#Community_bonding_period . So for instance if you subscribed to wikitech-l as we talked about yesterday, you can add that to your updates. Please feel free to carry on with the other community bonding period steps mentioned on that page, as well as the project-specific tasks that Vivek suggested like reading documentation, and update via that page as you go.

Hi @Aklapper , we extended our Outreachy deadline to Mar 29, and I can confirm that I see this proposal in my Outreachy dashboard.

Hi @maskaravivek , @K0x3rr spoke to me about the same thing over email, and I explained to him that this project is eligible for both GSoC and Outreachy, but that T188877 is reserved solely for GSoC. :)

Thanks for submitting your proposal. It looks great to me in general, and the list of bugfixes is impressive! :)

@Gupta-meghna64 thanks for the update! The previous apps that you have worked on look amazing. Well done. :)

Thanks @ayushin78 . :)