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.
Wed, Oct 16
@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.
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.
Tue, Oct 15
Sun, Oct 13
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?"
Sat, Oct 12
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.
Fri, Oct 11
Thu, Oct 10
Tue, Oct 8
@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:
Mon, Oct 7
Sat, Oct 5
Fri, Oct 4
Wed, Oct 2
Jun 9 2019
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. :)
May 18 2019
The slides for the talk can be accessed here if anyone wants: https://docs.google.com/presentation/d/1G-zqkIW1kHvGTUtEAv--opDYQQbwyqo2Mhd7OQEYH5Y
May 15 2019
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.
Mar 4 2019
Feb 28 2019
Feb 27 2019
Aug 4 2018
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. :)
Jun 15 2018
Jun 13 2018
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 !
Apr 26 2018
I saw your mailing list post. Nicely-written, well done! :)
Apr 25 2018
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.
Apr 2 2018
Mar 29 2018
Hi @Aklapper , we extended our Outreachy deadline to Mar 29, and I can confirm that I see this proposal in my Outreachy dashboard.
Mar 25 2018
Mar 21 2018
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. :)
Mar 20 2018
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. :)
Mar 19 2018
Thanks @ayushin78 . :)
Thanks for the update, @harisanker24 !
Happy to see that you have updated your proposal! The new formatting looks great and much more readable. :)
Mar 18 2018
I agree with @maskaravivek - the outcome of the quiz should not affect reputation/points. :)
Thanks for submitting your proposal! :) It looks good to me in general, but I have a few suggestions:
- In the timeline it is good that you have frontloaded your work and allocated time for mockups, testing and debugging, etc. However, I personally think too little time is allocated for implementation. E.g. For Phase 1 I would recommend moving "Decide the information which will be displayed in the stats info page. Improve it through community discussion." up into the mockup week so that you have at least 2 weeks for implementation.
- We appear to be missing 5 days in June? ;) If you are allocating that time for writing your midpoint report, please do mention that.
Mar 16 2018
Nice to see you have submitted a proposal, and the apps you have worked on before look great. :) A few suggestions:
Mar 15 2018
Mar 13 2018
GitHub project link would be great!