From version < 39.1 >
edited by Ecaterina Moraru (Valica)
on 2017/10/20 18:00
To version < 40.1 >
edited by Denis Gervalle
on 2017/10/21 21:51
< >
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.evalica
1 +xwiki:XWiki.dgervalle
Content
... ... @@ -110,6 +110,7 @@
110 110  * Cristina Rosu
111 111  * Alex Cotiugă
112 112  * Guillaume Delhumeau
113 +* Denis Gervalle
113 113  
114 114  = Todos for Admins =
115 115  

This page hosts information and project ideas for the open source project XWiki related to the Google Code-In 2017 program.

XWiki has also been participating to Google Summer of Code since 2005.

About Code-In

You can learn a lot about the program by reading the Code-In website. The timeline of this year's edition is given here.

XWiki Guidelines

Being part of the XWiki community means knowing our rules and practices. As a Code-In student you need to make sure you read and apply our guidelines.

For Code-In mentors please follow the following guidelines for creating Code-In tasks.

Task List

This will be available on the Code-In website, but for now here's a list of example tasks:

Non-repeatable Tasks

List of non-repeatable example tasks from our issue tracker:

TypeKeySummaryStatusCreated Date
ImprovementXWIKI-16961Display the SOLR index size in the Admin UIOpen08-Jan-2020
TaskXWIKI-15906platform.index translations keys from oldcore should be move to platform-indexOpen26-Nov-2018
ImprovementXWIKI-15562Mark XWiki classes, templates and sheets as hidden at creation stepOpen06-Sep-2018
ImprovementXWIKI-15446Replace the untranslated "info" example box on the Scheduler job sheetOpen18-Jul-2018
BugXWIKI-15354Inconsistency in the font style of a filtered columnOpen14-Jun-2018
ImprovementXWIKI-15266Automatically set the content to HTML when using a "User list" property in LivetablesOpen15-May-2018
BugXWIKI-15119The Applications panel entries are not properly alignedOpen15-Mar-2018
BugXWIKI-15049NotificationsApplicationsPreferencesMacro stylesheet not using Color Themes variablesOpen22-Feb-2018
BugXWIKI-14977The color themes alignment is broken when one of them is testedOpen26-Jan-2018
ImprovementXWIKI-14824Support indenting header level in the include macroIn Progress07-Nov-2017
BugXWIKI-14811Bad layout when using a font larger than the default oneIn Progress30-Oct-2017
ImprovementXWIKI-14784Display the user avatar instead of just the name in the "Author" columns of the LivetablesOpen17-Oct-2017
BugXWIKI-14690OFF toggle isn't showing properly for some color themes on IE11Open12-Sep-2017
ImprovementXWIKI-14436Livetable shows 'emptyvalue' for objects with no contentOpen03-Feb-2011
BugXWIKI-12646Page name out of bound for Document Tree, Activity Stream, Space Index and on Children viewerOpen02-Oct-2015
ImprovementXWIKI-11420XWikiSyntax* translations are very hard to maintainOpen08-Nov-2014
ImprovementXWIKI-11296The wiki editor doesn't have a consistent name across the wikiOpen22-Oct-2014
ImprovementXWIKI-11271Use round borders on the user profile sections to be consistent with the user profile menuOpen21-Oct-2014
ImprovementXWIKI-11269WYSIWYG word is not consistent on different pagesOpen21-Oct-2014
ImprovementXWIKI-11131Improve the "Changing password" pageOpen29-Sep-2014
ImprovementXWIKI-11127Improve the "Last Author" field to display the author's avatar on AWM livetablesOpen29-Sep-2014
ImprovementXWIKI-11043Use Flamingo-like button styling when editing DashboardOpen16-Sep-2014
ImprovementXWIKI-10884"Version summary" and "Is a minor edit" are looking different on ie10 and Chrome36 than in Firefox31Open29-Aug-2014
ImprovementXWIKI-10871Misalignments in the class editor on mobileOpen28-Aug-2014
ImprovementXWIKI-10857The "Browse" button and the background doesn't fit on IE10/11Open28-Aug-2014
ImprovementXWIKI-10722Activity icons are overlappingOpen04-Aug-2014
ImprovementXWIKI-10227On small resolutions the Search filter field from Rights is too smallOpen07-Apr-2014
ImprovementXWIKI-10039In Report step, add titles to summary elements (status, actions)Open11-Feb-2014
ImprovementXWIKI-8143Don't display document language when it's the default languageOpen16-Aug-2012
TaskXWIKI-7902Remove dependency on retired commons-httpclientOpen11-Jun-2012
ImprovementXWIKI-6331Improve page save comment when adding/removing annotationOpen21-Jan-2011
ImprovementXWIKI-6316Remove reference to XWiki.XWikiUserTemplate from XWiki.RegistrationOpen05-Apr-2011
ImprovementXWIKI-6267Trim server name aliasesOpen26-Apr-2010
New FeatureXWIKI-5826Send event when user authenticateOpen23-Dec-2010
ImprovementXRENDERING-61Add ability to have a box drawn around TOC macro by using a TOC macro parameter + ability to position location of TOC macroOpen22-Feb-2009
ImprovementXINFRA-32Document the redirect featureOpen03-Apr-2008
ImprovementXINFRA-22Document the Feed pluginOpen05-Mar-2008
ImprovementTASKMAN-36Provide a translation when Project is emptyOpen12-Dec-2014
ImprovementLDAP-11Allow setting LDAP authenticator SSL keystore password in configurationOpen05-Jul-2013
ImprovementINTMAP-58Map Shape provider iconOpen12-Aug-2019
ImprovementHELPCENTER-16Make Help use IconThemesOpen15-Mar-2018
BugHELPCENTER-9Missing title when adding 'Example' macro in the DashboardOpen24-Aug-2017
BugFAQ-21Search doesn't work for custom FAQ-structuresOpen20-Mar-2020

Repeatable Tasks

  • Fix 20 links on xwiki.org that point to the platform or enterprise wikis with redirects and replace them with the redirect reference. Success criteria:
    • Use minor edits
    • Provide a link to revision diffs
  • Find and update 5 screenshots of XWiki features on xwiki.org that are not up to date with the latest version of XWiki. Success criteria:
    • Use the same attachment name that exist
    • Provide the URLs to the old + new images
    • Use a similar size of image than what exists
  • Find an replace 20 images on xwiki.org that don't use the {{image}} macro yet and replace them with that macro. Success criteria:
    • Provide a link to the version diff for each image replaced
  • Convert 1 unit test written in JMock, into a Mockito test using XWiki's MockitoComponentMockingRule or MockitoComponentManagerRule. Success criteria:
  • Increase test coverage (as measure by Jacoco) for a single module by 1%, by adding new tests to existing test suites. Success criteria:
    • Pull Request
    • pom.xml modified in the PR to match the new coverage threshold and build passing with quality profile (-Pquality).
  • Replace at least 1 call to deprecated using alternative valid APIs
    • The module build is still passing
    • Pull Request
  • Move 1 unused deprecated method/class to Legacy module (using AspectJ for methods). Success criteria:
    • Full build of commons, rendering, platform still passing without failure
    • Pull Request
  • Remove 1 coding violation from https://sonarcloud.io/organizations/xwiki/issues?resolved=false (commons or rendering). Success criteria:
  • Find and fix 5 broken links on xwiki.org (Example of wording it). Success criteria:
    • Link to the revision diff fixing each broken link
  • Run and report result of 10 tests from http://test.xwiki.org/xwiki/bin/view/Main/WebHome. You should a combination of XWiki versions, Browser type+version, Database type+version that doesn't already exist, and create a new result entry. Success criteria:
    • New entries on test.xwiki.org
    • Q: How to ensure that the students has really executed the test? Example
  • Become a community member: create an account on xwiki.org, then log in with that account on the forum, create an account on Riot. Success criteria:
    • Post a new topic on the forum to introduce yourself and mention your Riot chat id.
  • Setup a development environment (for Code tasks only). Install the XWiki client docker image or some virtual box VM (we still need to create that!). Create an account on jira.xwiki.org. Create a github account. Success criteria:
    • Screenshot of the shell with jira and github account printed with an echo (TBD more precisely) 
  • Write a blog post about XWiki (Example of wording.
  • Find one place that doesn't allow the UI to be translated (missing translation keys). Success criteria:
    • Point to the code containing the hardcoded string
  • Implement a new ColorTheme. Success criteria:
    • PR in the "Extra ColorTheme Pack" extension project in xwiki-contrib (we neeFind one place that doesn't allow the UI to be translated (missing translation keys). Success criteria: d to create it)
    • Screenshot of the home page using the Color Theme
    • Documentation of it on the extension page on e.x.o
  • In 1 UI test replace all setup code which use the UI by REST calls
    • The test is still passing
    • Pull Request
  • Design a new logo for an extension found on Main. Success criteria:
    • Original logo (doesn't exist on the web already and cannot be considered as plagiarism)
    • Screenshot of the logo in action
    • Right sizes so that be can used on JIRA project, on e.x.o. TODO: decide what we do for the icon inside XWiki when the extension is installed
    • XINFRA issue created to use the logo on JIRA, e.x.o, etc.
  • Design a logo for XWiki participation in GCI and GSOC. Success criteria:
    • Post the logo on a wiki page that will have been prepared for that
    • Original logo (doesn't exist on the web already and cannot be considered as plagiarism)
  • Interview an XWiki contributor or user. Don't forget to mention that you are doing this as part of GCI 2017 and also try to explain them about the program a bit. Write a blog post about your interview. Success criteria:
    • Link to blog post
  • Write 3-paragraph essay to explain what is XWiki to grandpa/grandma (Credit goes to Drupal). XWiki is quite a foreign concept to many people. e.g. people who are not in the tech world; Grandpa/Grandma old generation. We want to produce a short essay to allow us to explain what XWiki is to those people. Deliverables: Write a blog and link to it for mentor to review. A short essay about XWiki which can be understand by a Grandpa/Grandma, a high school student who plays a lot of basketball, or a waitress/waiter who works in a Mexican or Chinese restaurant. Success criteria:
    • Link to blog post
    • Original work and not plagiarism.
  • Design a T-shirt for the XWiki community. We would give them to GSOC students and some Code-In students who did good work + more generally whenever we want to single out a member of the xwiki community who's doing a good job at participating. Success criteria:
    • Original work
    • Must look nice when printed
    • Related to XWiki, should use the XWiki logo somewhere

Contact us

You can ask for more information about the Code-In and interact with the community and mentors through the usual communication channels: mailing list or the chat channel.

Mentors

Current list of people who accepted to mentor GCI:

  • Thomas Mortagne
  • Vincent Massol
  • Pawan Pal
  • Marius Florea
  • Clément Aubin
  • Shubham Jain
  • Eduard Moraru
  • Ecaterina Moraru (Valica)
  • Cristina Rosu
  • Alex Cotiugă
  • Guillaume Delhumeau
  • Denis Gervalle

Todos for Admins

  • Create short videos of various features for which there is not yet others. Not repeatable task, we need to create one task for each feature ourself.
  • Create an onboarding docker image with a full dev environment set up (maven, firefox, IDE, Git, settings.xml, etc)
  • Idea: check this task from FOSSASIA as an example of a task with good level of information.
  • Idea: check https://www.katacoda.com/learn for creating onboarding tutorials

Previous Google Code-In editions

This is our first participation!

Get Connected