xwiki-devs

xwiki-devs@xwiki.org

9400 discussions

Re: [xwiki-devs] [GSoC and XWiki] - First contact

by Vincent Massol

Hi Alina, Welcome and very cool! :) Please use the xwiki devs mailing list or IRC/Matrix to reply so that everyone can participate to the discussion. Thanks -Vincent > On 25 Mar 2018, at 16:07, Clément Aubin <aubincleme(a)gmail.com> wrote: > > Hi Alina! > > My name is Clément ; with Vincent (in CC of this email) I'm one of the > mentors for the GSoC project "Google Blocky Editor" [1]. > > First of all, I would like to thank you for applying to this GSoC > project. I've read the resume and the draft proposal you published on > the GSoC website, and for now, I'm pretty interested in helping you > archiving this project :). > > Before everything else, could you tell us if you had the chance to test > XWiki before (maybe in a company you worked for or just when searching > for a GSoC project) ? > > The XWiki Community uses two main channels to communicate : Matrix / IRC > [6] for day to day chat and mailing-lists [5]. As you will surely be > interacting with other community members over the next months, I suggest > that you sign up at least to our devs mailing-list and say hi, > presenting quickly your motivation for doing this GSoC project with us > (that way, other XWiki contributors will get to know you more easily :)). > > To respond to the question that you asked on [2] about the issue > XWIKI-15129, I suggest that you take a look at this file [3] ; it's a > template written in Velocity [4] that is used to display a diff between > two different document versions. We heavily rely on Velocity for > rendering templates inside of XWiki, and there is a very high chance > that you will need to use this language as part of the Blocky Editor > project. > > For solving this issue (and also for archiving this project), you will > need to take a look at our development practices [7]. They generally > sum-up the "etiquette" to follow during the development of code related > to XWiki. If you have some free time, taking a look at the different > categories proposed on [9] is a good shot, as it will help you better > understand how the XWiki ecosystem works. > > Finally, I've noticed that we have a significant time difference between > our geographical locations. Vincent and I both live in France, and we > have a 4 hour delta with Kazakhstan [8]. That's something we will need > to keep in mind. > > Please don't hesitate to come back to us if you have any other question, > > Thanks, > Clément > > [1] http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/BlocklyEditor > [2] > https://docs.google.com/document/d/1FmMdU3UkpF4x62S2YbIOsOt1LViI7e4SsfJm3Ov… > [3] > https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-core/xwi… > [4] https://velocity.apache.org/ > [5] http://dev.xwiki.org/xwiki/bin/view/Community/Discuss > [6] http://dev.xwiki.org/xwiki/bin/view/Community/Chat > [7] http://dev.xwiki.org/xwiki/bin/view/Community/DevelopmentPractices > [8] > https://www.timeanddate.com/worldclock/converter.html?iso=20180325T140000&p… > [9] http://dev.xwiki.org/xwiki/bin/view/Main/WebHome

6 years, 5 months

[xwiki-devs] [Contrib] Request for new extension "application-gardening"

by Clément Aubin

Hi everyone, I would like to propose a new contrib application that would provide a set of tools to an administrator in order to help him manage old wiki documents, by either moving them to a custom "Archive" space, or to a clone wiki serving as an archive. The idea would be to only target documents that need to be archived using a set of rules defined by an administrator. WDYT about this idea ? Thanks, Clément

6 years, 6 months

[xwiki-devs] [Vote] Skip 10.2RC1 and release 10.2 final

by Marius Dumitru Florea

Hi devs, We're 4 days late on the 10.2RC1 release which means we have only 1 day left till the 10.2 final release. We should either skip 10.2RC1 and release 10.2 final directly or postpone the 10.2 final by one week and release 10.2RC1 tomorrow. WDYT? +1 to skip 10.2RC1 Thanks, Marius

6 years, 6 months

[xwiki-devs] Comments on GSoC proposal for XWiki Android Authenticator

by Venkata Rama Koundinya Lanka

Hello Everyone, I am Venkata Rama Koundinya Lanka and I have fixed the issue to add material design and buttons and the link to the pull request can be found in the following proposal for project. The link is given below https://docs.google.com/document/d/1Ehnc4WMu_dS2L0w4rPUJQe0a272D6r4R3aORMmA… Please feel free to comment for improvements.

6 years, 6 months

[xwiki-devs] [Contrib] Request repository for "color-themes"

by Ecaterina Moraru (Valica)

Hello devs, I want to publish additional Color Themes inside the Contrib organisation. These themes will be complementary to the xwiki-platform-flamingo-themes [1] module, and in the future we could move optional/deprecated themes from platform there (for example Kitty, Marina, etc). I will want to contribute the Dawn (color-theme-dawn), Mandarin (color-theme-mandarin), Pantera (color-theme-pantera) and Snowdrop (color-theme-snowdrop) color themes. I would need: - a repository on xwiki-contrib called "color-themes" https://github.com/xwiki-contrib/color-themes/ - a JIRA project called "COLORTHEMES" https://jira.xwiki.org/browse/COLORTHEMES/ I will use separate Components for each theme - username: evalica A related mail thread is [xwiki-devs] Color Themes Questions http://markmail.org/message/v75q2klsouu72mo7 I prefer having the themes grouped on Contrib, but as individual modules, because the themes are related and small enough; while needing individual dependencies, active installs count and platform version independence. Thanks, Caty [1] https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwi…

6 years, 6 months

[xwiki-devs] Regarding working on ideas of GSOC, 2018

by AADITYA KUMARRAI IET Lucknow Student

Hello Sir, This is Aaditya Kumar Rai,pursuing Computer Science Engineering (currently in Second Year ) at one of Premier Government college in India. I have good hand on working over open source projects based on Programming & Full Stack Development in Web and Applications, as I have already developed : a) Library management System(using Python) b)Retrieving Processing and Visualizing data with Python(Under guidnace of Prof.Charles Severance ,University Of Michigan) Currently working on : a) A dynamic website development that will work on Availability of all resources to college students (using HTML ,CSS, Javascript,AngularJS for back-end NodeJS) As I have extreme interest to explore open source arena more deeper to enhance my knowledge further so that i can gain industrial experience too. Sir, i am applying for GSOC first time and due to unavailability of Guidance ,i have lost much of time in preparation for GSOC,18. I am helpless ,please guide and help me and I am pretty much sure that within such short of time , i will put my all efforts and skills to fix bugs and Patch it additional to submission of Proposals and will prove Myself best for those given Projects. I have good deal of experience with development in,C HTML5, CSS3 ,Advanced Python , Javascript & PHP, I find myself able to work on following ideas:- a) Idea 1 -Google Blockly Editor b) Idea 2 - Idea : Translation in context c) Idea 3 - .idea : XWiki-StaticSiteGen Brief description: I am little bit confused on how to start? How can i show my worth to you or should i directly focus on proposal or any bug patches first or discuss my solution first? Please guide me from here on how to proceed further. Thanking You! Regards.. Aaditya Kumar Rai -- ------------------------------ *Institute of Engineering & Technology,* <http://www.ietlucknow.ac.in> Sitapur Road,Lucknow Uttar Pradesh,India PIN : 226021

6 years, 6 months

[xwiki-devs] Regarding Project for Google Summer of Code

by Venkata Rama Koundinya Lanka

Hello everyone, My name is Venkata Rama Koundinya Lanka, studying third year, computer science in Vasireddy Venkatadri Institute of Technology. I have experience in developing android apps and I have previously done an internship in android. I would like to contribute to the project *Finish and improve Android XWiki Authenticator and Contacts Synchronization* for this Google Summer of Code. I will be obliged if someone can guide me on how to get started and how to proceed. Thanking You, Venkata Rama Koundinya Lanka

6 years, 6 months

[xwiki-devs] Regarding Project for GSoC

by Venkata Rama Koundinya Lanka

6 years, 6 months

[xwiki-devs] Color Themes Questions

by Ecaterina Moraru (Valica)

Hi devs, I need your input on some questions: 1. (Important) Where to commit Color Themes? 2. Where do we move old / deprecated Color Themes? 3. What should a Flamingo Theme contain? --- 1. Where to commit Color Themes? We have a running vote for a new default Color Theme. So where should this theme be committed? When considering this question think about the default theme, but also to the other Color Themes variations that won't be voted as a default. A. Platform ( https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwi… ) PRO: Being default makes sense to be committed in Platform and to not have a dependency towards a Contrib extension. CON: It will depends on an 10.x XWiki version. The themes could be used for any XWiki > 6.2. Having them outside Platform would allow installation also on older versions. CON: Slow release process for outside contributions CON: Grouped: in the current implementation they come as a package, you cannot install an individual module in a separate Flavor. B. Grouped on Contrib but as individual modules (example https://github.com/xwiki-contrib/color-themes/tree/master/color-theme-icebe… ) CON: Grouped versioning and release process. Each theme could have its own component on JIRA. PRO: Medium contributions: The Maven / JIRA / module setup is done only in the beginning, but still there are technical knowledge to be known how to contribute a theme. PRO: XWiki version independent - can be installed on older instances C. Individual on Contrib (example https://github.com/xwiki-contrib/color-theme-iceberg) PRO/CON: Independent versioning and release process. Still we will be spammed with JIRA projects for each theme. CON: Slow contributions since you need to know how to create Maven modules, provide JIRA components for each theme, release on Nexus, always ask for a repo, etc. D. Individual as XARs on e.x.o PRO: Easy / rapid contributions: you just need to provide a XAR PRO: Platform version independent CON: Cannot be referenced as a dependency from a .pom CON: No blaming or versioning of sources --- IMO the default theme should be committed in Platform (A), but all the other proposals should be in Contrib either grouped (B) or individual (C). I prefer version B (grouped on Contrib) since the themes are very similar in concept and for me it doesn't justify all the independent projects on JIRA, etc. It would be similar to what I did for Icon Themes, see https://github.com/xwiki-contrib/icon-themes Other notes: 1.1 The themes from Platform that were not default, should be made as extensions. This is the case for Garder, Kitty, Marina. 1.2 xwiki-platform-flamingo-theme-bootswatch https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwi… should be put in Contrib, as extensions, since they don't relate to XWiki. 1.3 Keeping just the default in Platform is also good for Flavors. Not all themes work for all Flavors. Each Flavor would add the dependency they want. Still this means more work in selecting these themes. --- 2. Where do we move old / deprecated Color Themes? This question applies for old Color Themes. For example when we retired Colibri, we moved all the themes in the Attic https://github.com/xwiki-attic/skin-colibri/tree/master/xwiki-platform-colo… even though those themes still worked (since we made them backwards compatible). Also the majority of themes on e.x.o are as XARs. How will we deprecate those? Also how do we mark themes that are not good looking anymore? Also this point is very subjective. I guess the answer to this question depends on what were we vote to commit the Color Themes. --- 3. What should a Flamingo Theme contain? (difference between Skin and CT) The Colibri Color Themes contained just colors. Now with the Flamingo Themes's Advanced section you could easily remove the need to have a Skin and add there also CSS rules, etc. The Bootswatch (xwiki-platform-flamingo-theme-bootswatch) themes are a very bad example, since they change quite a lot of styling and not just variables. I just want to enforce that default themes and especially themes that are provided by XWiki Development Theme should contain only variables. If there are things we need to override we should fix them first in the Skin, not just abuse the "Advanced" section capabilities and power. This is important since the changes done in the Skin apply for all the Themes. You don't need to duplicate the "hack" for all the themes. --- Let me know what you think. Thanks, Caty

6 years, 6 months

[xwiki-devs] [XWiki Day] BFD#170

by Alex Cotiugă

Hello devs, This Thursday is BFD#170: http://dev.xwiki.org/xwiki/bin/view/Community/XWikiDays#HBugfixingdays Our current status is: * -30 bugs over 120 days (4 months), i.e. we need to close 30 bugs to have created bugs # = closed bugs # * -95 bugs over 365 days (1 year) * -99 bugs over 500 days (between 1 and 2 years) * -315 bugs over 1600 days (4.3 years) * -711 bugs since the beginning of XWiki See https://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=10352 Here's the BFD#170 dashboard to follow the progress during the day: https://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=14090 Happy Bug Fixing Day, Alex

6 years, 6 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs