Hello XWikiers,
This proposal is about adding a new blog type: the isolated blog.
An isolated blog is a blog that is created in a given space (local blog),
the blog categories and posts are created/visible only in that space.
The objective of creating this separate blog type is to allow having
independent blogs in the same wiki and to not break the actual blog use
cases.
An isolated blog is subject to following conditions:
*Posts*
- The isolated blog posts will be created in the local blog space
- Only blog posts located in the local space will be displayed in the
blog home page
- Prevent the global blog to display posts from isolated blogs
*Categories*
- New blog categories are created into the local blog space
- On the blog post form only categories located in the isolated blog
space will be displayed
- The 'Categories' panel display only categories located in the isolated
blog space
- Categories from isolated blogs are not displayed in the global blog
category panel
*Panels*
- Only display local posts in the 'recent posts' panel for isolated
blogs.
- Prevent isolated blog posts to be displayed in the global blog 'recent
posts' panel.
- Only display local unpublished posts in the 'Unpublished posts' panel
for isolated blogs
- Prevent unpublished posts from isolated blogs to be displayed at
global blog 'Unpublished posts' panel.
- Isolated blogs will be removed from any RSS feed but will be visible
on the one matching the isolated blogs.
- The 'archives' panel will not be modified because it already follows
the isolated blogs conditions in the case of local blogs
*How to create an isolated post?*
On the Blog/Management page
- Add a checkbox "Isolate this blog"
- When the checkbox is checked:
- Create an isolated blog in place of a local blog.
- Create the default categories (News, Personal, Others) into
the local space
WDYT?
Hi,
With Mohammed, we have prepared design proposal
(http://design.xwiki.org/xwiki/bin/view/Proposal/BlogImagethumbnails) in
order to improve the visual aspect of the Blog application. Currently the
application is not really visual, and compared to the competition, it does
not look appealing as it could be.
This is why we propose to introduce image thumbnails linked to blog post,
and to use those images when displaying blog posts as lists. Since pictures
are better than words, see the screenshot in the design page for more
details.
WDYT ?
--
Denis Gervalle
SOFTEC sa - CEO
Hello
I wish to redesign l10n.xwiki.org , improve it's usability and make it more dynamic as my GSoC project. Can anyone provide me link to the codebase? I was looking up on github, and found this https://github.com/xwiki-contrib/application-l10n but it says
"This repository is very outdated compared to what is on l10n.xwiki.org right now"
Kindly help.
Regards
Abhishek
Hi Thomas ,
Sorry to bother you again..
As suggested by you, I created an account on l10n.xwiki.org and was looking around how the stuff works, but I was completely lost. There is a side bar showing the list of available applications, but when I open one of them say Curriki. I could not find how to provide translations in my preferred language.
Can you please help me out in figuring out how the stuff works so that I can create a proper user flow for the redesign (roadmap of which I'll eventually submit in my GSoC proposal)
I have already subscribed to the mailing list as you suggested.
I really look forward to work on the redesign of this project since this is an interesting project of XWiki.
Kindly spare some time from your schedule to help me, as it shall help in my GSoC proposal
Thanks and regards
Abhishek
________________________________
From: Thomas Mortagne <thomas.mortagne(a)gmail.com>
Sent: Friday, March 10, 2017 2:24:08 PM
To: Abhishek Sharma; XWiki.org
Subject: Re: Improve l10n.xwiki.org GSoC Project
Hi Abhishek,
I just saw your message on IRC (I guess it was you). Most of XWiki
committers are GMT+1 or +2 so you sent your message not long before
people start arriving probably.
It's great to see someone interested in improving that old thing :)
It's a very important part of the XWiki project but it's hard to find
devs interested in working on it.
The first thing to do usually is look at http://gsoc.xwiki.org/. In
case of http://l10n.xwiki.org you should also probably create an
account there and look at how it works (maybe try translating a few
things in some not complete language you master for example) to better
understand the (many) things that could be improved.
Also you should use the mailing list instead of sending me mails
directly, see http://dev.xwiki.org/xwiki/bin/view/Community/MailingLists.
Welcome in XWiki community :)
On Fri, Mar 10, 2017 at 8:43 AM, Abhishek Sharma
<hello.abhishek(a)outlook.com> wrote:
> Hello Thomas,
>
>
> I am a student from India, and a budding UX Designer.
>
> I found the Improve l10n.xwiki.org GSoC project quite interesting and wish
> to work on it, Can you please let me know, how to get started? Is there
> anything I can do to increase my chances of selection other than working on
> my proposal?
>
>
> Thank you for your time
>
>
> Regards
>
> Abhishek
--
Thomas
Hi Sarthak,
Glad to see someone interrested in this project !
On Fri, Mar 10, 2017 at 4:35 PM, Sarthak Gupta
<sarthakgupta072(a)gmail.com> wrote:
> Hi,
> I am Sarthak Gupta, a first year undergraduate from Birla Institute of
> Technology, Ranchi, India. I am looking forward to participate in GSoc17
> with the organisation. I am good at several languages like HTML, CSS,
> JavaScript and C. I have a basic knowledge of Java.
> While going through the ideas page, I found that the project "Translation
> in context" http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/#
> HTranslationincontext
>
> would be interesting for me to work on.
> This is what I understood:
> So, the X-wiki provides a 'translation macro' which is of course used to
> translate content. So, as far as I think, this translation macro will be
> used in a more better way to translate the content on the page. As given we
> will be able to select and translate any given content on the webpage.
>
> Using HTML5 renderer, I will be able to find the translation macro(how to
> do that is my pain I guess :P). Then as given in examples (like
> pantoon.mozilla.org), I should be able to incorporate it into the webpage.
> Please correct me if something's wrong.
>
> Also some guidance on the line "The idea is also to make easy to contribute
> to http://l10n.xwiki.org from your local wiki by sending your corrections
> to it." is required.
http://l10n.xwiki.org is where we actually store reference
translations and where translator can contribute right now. The idea
would be to translate directly in the wiki and then (automatically or
not) send the translations from your XWiki instance to l10n.xwiki.org
(if you have an account). You could see this as a commit/push.
>
> Sarthak Gupta
--
Thomas Mortagne
Hi Chetan,
If it's not already the case you should look at
http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/Guidelines.
Also make sure you send mails to the devs mailing list and not me directly.
Regarding XWiki Android Authentication project know that's it's about
continuing to work on an already existing project and that several
students already expressed there interest in participating to it
during GSOC so the competition might be tough to be selected.
On Wed, Mar 8, 2017 at 7:26 PM, Chetan Kaushik <dynamitechetan(a)gmail.com> wrote:
> Hi sir,
> I am Chetan, 2nd year undergraduate Student of Computer Science Engineering.
> I am interested in doing the XWiki Android Authentication project for GSoC
> 2017.
> Can you please guide me regarding this.
>
> regards
> Chetan Kaushik
> github.com/dynamitechetan
--
Thomas Mortagne
Hi devs,
The idea today is to do a Test Day with priority to fixing long
standing flickering (integration mostly) tests.
You can find known flickering tests on
http://jira.xwiki.org/issues/?filter=14240. The goal is to really fix
them, not just add some random wait here and there ;)
If you are really not confident with the area around those specific
flickering tests here are some other ideas for this kind of Day:
* obviously add more tests and increase the code coverage
* move tests from enterprise to platform. Needed for the platform
flavor and removal of XE
* update jacoco covering setup (we often forget to increase it when
adding more tests)
* move more tests from JMock to Mockito
* work on new test setups and tools:
** improve docker containers for packaging XWiki (possibly several for
multiple DBs and Servlet containers).
** work on spreading Jenkins platform job into one job per maven
module so that build can be spread on various agents (groovy
scripting)
** Research/Use Jenkins 2 Pipeline plugin with the new DSL and commit
the jenkinsfile in SCM
** Test platform to run contrib extension tests on various versions of
XWiki automatically
* Speedup existing tests (research xwiki startup time, remove
unnecessary modules, etc)
When what you fix can be linked to an issue, tag it with "testday"
(same idea as "bugfixingday" when doing BFD). If not then answer to
this mail to explain what you did.
Good Test Day !
Hello everybody.
*TL;DR:* Notifications are nothing but standard Events from the Observation
Manager, marked as "Storable" and stored by
the Event Stream. They can be displayed in the top bar of the wiki and/or
sent by e-mails periodically. Since this is
overlapping with the Watchlist features, the idea in the future is to
re-implement the watchlist using the notification
mechanism and to push the current Watchlist module to contrib. Need your
agreement to go in that way.
*Background:*
A few weeks ago I've sent a proposal about the Notifications feature. I've
made some work since, and talked with Vincent
to define a vision.
Let me introduce you what I've already done and what I'm going to do in the
following days:
* I am going to introduce 2 interfaces: *StorableEvent* and
*TargetableEvent* (currently I have only implemented a
*NotificationEvent* that represent both).
* *StorableEvent*: when an event from the Observation Manager implements
this interface, it means this event will be
logged (stored) by the Event Stream.
* *TargetableEvent*: introduce a list of "targets", which are the IDs of
the entities who are targeted by this event.
Example: when someones replies to your forum topic, an
event called "someone has answered to your
topic" is sent with the topic creator as target.
* As I said, storable events are stored by the Event Stream, which is
currently implemented by the Activity Stream
module. So it means a *StorableEvent* is currently stored as an
*ActivityEvent* but this remains technical and not visible
from the outside.
* I have introduced the role *StorableEventConverter* which convert a
*StorableEvent* to an Event from the Event Stream.
Each application can provide its own converter (to store additional
parameters for example) but there a default one
that is used if nothing else is defined.
See:
https://github.com/xwiki/xwiki-platform/blob/e5a3cc7b6a5cbe82b1668d9d30fbf6…
* I have added the "target" field (a list of string) to the Event and the
*ActivityEvent* classes. I have also updated the
hibernate mapping for *ActivityEventImpl* accordingly.
See:
https://github.com/xwiki/xwiki-platform/blob/81172b2dfd994ddd727efe93daf8fa…
* I have introduced an *EventStatus* class (and *ActivityStatusImpl*) to
store in the wiki which notifications has been seen
by a specified user. This is important because we want to distinguish new
notifications from those the user have
marked as read. Hibernate mapping has been updated as well in the
Activity Stream module.
See:
https://github.com/xwiki/xwiki-platform/blob/e5a3cc7b6a5cbe82b1668d9d30fbf6…
See:
https://github.com/xwiki/xwiki-platform/blob/81172b2dfd994ddd727efe93daf8fa…
* I am going to introduce the *StorableEventDescriptor* role. The
components will give some meta-information about a
storable event: the pretty name of the event, the application that can
send it and a short text giving a description
about the event. We need this to expose to the user the list of events
that she can subscribe to.
(Right now I have implemented this as XObjects called "*NotificationType*"
which is an error)
* I have introduced the concept of NotificationPreference. It's an XObject
stored in the user profile. When a user wants
to subscribe to a particular type of event, this xobject is created with
the id of the event and the media used for
the notification ('web notification', 'email' or both).
In the future, this preferences should handle some more precise filters.
Like: "I am interested in the notifcations
sent by the Forum Application but only when it comes from the wiki A and
not the wiki B."
* I have introduced the role *NotificationDisplayer*. It's a component that
generates the XDOM to display in the
notifications menu. Each application can implement its own displayer, but
failback to a default one.
* The *DefaultNotificationDisplayer* tries to render the template
'notifications/{eventType}.vm' and failback to
'notifications/default.vm'. It means you can create your own displayer
either by implementing a custom
*NotificationDisplayer* or by creating a template in the right location.
* The *NotificationManager* is responsible for getting the notifications
for the current user, according to its
preferences.
* I have implemented a UI which load the notification asynchronously and
display them in the notification menu, just
below the watchlist options.
See:
http://jira.xwiki.org/secure/attachment/33586/WIP-NotificationsMenu.png
* Unread notifications are displayed with a different styling that others.
* The user has the ability to mark a notification as read.
* I have implemented a preferences page in the user profile, which list all
*StorableEventDescriptor*.
See:
http://jira.xwiki.org/secure/attachment/33587/WIP-NotificationsPreferences.…
* As a proof of concept, I am going to make the Blog Application send some
custom events that will be displayed in the
notifications menu.
Problems:
* We clearly have some overlapping of concerns with the Watchlist. The UI
is even very bad since the Watchlist options
are displayed in the same "bell" menu than the notifications without
being connected together. It's confusing.
* That is why we propose, with Vincent, to remove the Watchlist as it is,
and re-implement its feature using the
notifications abilities.
* The email sending is not implemented yet, and will not for the 9.2
release.
* We don't have a filter to not display similar notifications. For example,
a user saving a document 10 times in 10
minutes will generate 10 notifications. Possible flooding.
* When a user registers, all the notifications that are stored since the
beginning of the wiki are unread by her. It
does not make sense to tell her "you have 1 000 000 000 unread
notifications" so we need to store a starting date for
each user.
Do you see any problem with that vision?
Thanks you,
--
Guillaume Delhumeau (guillaume.delhumeau(a)xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
Hi,
Your candidacy does seems interesting but the policy at XWiki is to talk
with the community ideally, not just the official mentor. Basically the
mentor is the community but I have the duty to make sure the student will
have answers to his/her questions and follow the his/her progress ;)
The XWiki main REST API is documented on http://platform.xwiki.org/
xwiki/bin/view/Features/XWikiRESTfulAPI and the good news is that some of
the limitations the API had last year that Fitz had to work around during
the GSOC project have been fixed since. Still ideally this application
should work with the oldest possible version of XWiki and not require
anything newer than 8.4.x which is the current LTS.
On Sun, Mar 5, 2017 at 2:39 PM, Pawan Pal <pawanpal004(a)gmail.com> wrote:
> Hi Thomas,
>
> I am Pawan Pal an Undergraduate student in University of Delhi, India. I
> have experience in Android Development (My GitHub Profile
> <https://github.com/pa1pal>). I am an open source enthusiast, Udacity
> Android Developer Nanodegree holder also have working experience in
> organizations.
>
> I looked in to the Current codebase of Android Authenticator. I need the
> XWiki Rest api documentations which is used in the app.
> I also like to do major improvements such as using Retrofit2 library for
> rest client with okhttp. Also using RxJava2 can improve the codebase.
>
> Although the codebase is well structured. But it would be best if we use
> Google's MVP (model view presenter) architecture for android. The code
> maintainibility will become much easier then. Right now most of the classes
> have 500+ lines of code.
>
> Thanks. Please reply!
>
> --
> Pawan Pal
> *pa1pal.github.io <http://pa1pal.github.io> *
> *B.Tech (Information Technology and Mathematical Innovation)*
> *Cluster Innovation Centre, University of Delhi*
>
>
>
>
>
>
>
--
Thomas Mortagne
--
Thomas Mortagne