Hi devs,
I see that we keep adding stuff regularly to oldcore and the reason is "my code depends on oldcore so I cannot depend on oldcore in new modules".
First, this is not completely true. We have several modules that already depend on oldcore.
Also we cannot wait indefinitely that the new model magically appears (that won't happen… :)).
I think it's fine to depend on oldcore when a new module requires to use the model and when the bridge (DAB) is not enough. However we need to be careful about one thing: that oldcore itself doesn't use that new module. So sometimes it will mean extracting stuff from oldcore into a separate module so that it can use the other new module ;)
Personally I now think we need to continue splitting oldcore and it's more important that we create new modules for specific domains, even if they use old code and even if they use the com.xpn namespace when moving oldcode) than keep everything as it is and make oldcore grow fatter…
Of course sometimes it may just be too complex but at least we should consider it and when possible create new modules depending on oldcore.
WDYT?
Thanks
-Vincent
I am a student from india ,doing major in mathematics and computing, IIT
Delhi . I am very keen to be a member of xwiki family.
i am interested in the project :Improved wiki page history
I have a strong backround in computer skills like java,c and web
development related skills : html, css, javascript , jquery , sql , php.
I have knowlwdge in matlab too.
Please tell me if i need knowledge in other fields too for this project ,
as i like this idea and it's use in future aspects.
Best regards,
Arpit Goyal
Hi devs,
I`ve worked on allowing the customization of the User Directory and,
implicitly, the ability to search for users in a wiki. The jira issue [1]
has 3 attached images, but I am going to link them here [2][3][4] too for
commodity.
The idea is simple: Use the livetable to display users (pages with
XWikiUsers objects in them) and display a selection of extra columns
(XWikiUsers class property names) that are stored in the user's profile
page as preferences. Each user can define his/er own view over the user
directory and can also reset it to default.
This feature comes as a complementary to the previous one [5] (that is
still waiting for your votes, BWT :) ). Combined, the two allow an admin to
display newly added user fields in the user's profile and other users to
perform user searches based on (and not only) these fields.
The only inconvenience with this approach is related to the workspaces
application in the way that a workspace has a different membership
relationship (membership to the workspace's group) than a normal XE
instance or a farm subwiki (pages with XWikiUsers objects in them). Please
see the jira issue [6] about this inconvenience and also the chosen and
implemented solution (with an example).
I`d like your vote if this is a feature that is to be integrated in XWiki,
as proposed by the 2 pull requests [7][8] that are available.
Thanks,
Eduard
----------
[1] http://jira.xwiki.org/browse/XE-1131
[2]
http://jira.xwiki.org/secure/attachment/24775/customizableUserDirectory-def…,
no customization, default columns)
[3]
http://jira.xwiki.org/secure/attachment/24776/customizableUserDirectory-cus…
screen)
[4]
http://jira.xwiki.org/secure/attachment/24777/customizableUserDirectory-cus…
with extra columns added)
[5] http://xwiki.markmail.org/thread/22snpab3czfdexln (mail: [VOTE] merge
branch 'feature-user-profile-information-editor' into master in 4.0M2)
[6] http://jira.xwiki.org/browse/XWIKI-7648 (workspaces issue with the
implemented solution)
[7] https://github.com/xwiki/xwiki-enterprise/pull/18
[8] https://github.com/xwiki/xwiki-platform/pull/42
Hi devs,
Since we're working on a major new release I'd like to propose removing deprecated methods that have been deprecated since 2.x (except for script apis, i.e. script service and classes in *.api.* package).
WDYT?
Thanks
-Vincent
Hello,
I tried to build all modules under xwiki-platform-core, but the build
process hanged on PreemtiveLockTest, so I had a look at the code and
noticed some problems:
1. PreemtiveLockProvider.lockBlockingThread is concurrently accessed and
updated despite being an unsynchronized HashMap. It must be synchronized.
2. The deadlock recovery algorithm is "if there is a deadlock, ignore
the fact that the lock is locked and proceed." To me this seems
unintuitive. When a deadlock is detected, an exception should be thrown
and the thread aborted.
3. Presumably, the thread which is deprived of its lock is supposed to
at least be blocked until the thieving thread unlocks the lock, but
there is a race condition so both threads may run simultaneously.
4. Related to 3., the 'owners' stack in the lock is concurrently
accessed without synchronization in 'currentThreadOwnsAllLocks'.
As of deadlock detection, do we really need it? If so, would
java.lang.management.ThreadMXBean.findDeadlockedThreads() be sufficient?
In my opinion, the implementation PreemtiveLock should be discarded and
the LockProvider should return an ordinary ReentrantReadWriteLock.
Best Regards,
/Andreas
Hi there!
My name is Melania Galea and I am a student in Romania. I have worked with
OpenNMS for gsoc 2011 on the "Converting OpenNMS to use Hibernate" project.
The experience was amazing, I learnt a lot about working on a real-life
application inside an open source community. I am a pasionate Java
developer who promotes the benevolent sharing of knowledge. As far as my
technical experience goes, I enjoy working both on the backend and frontend
sides of an application. I have worked with java and many others integrated
technologies such as Spring or Hibernate, as well as with several
Java-based web frameworks such as Wicket or Spring MVC. I have currently
discovered a passion for node.js and javascript as together with my friends
I developed a customized IRC application. From the projects you proposed
for this year's gsoc, the "Annotations for images and other content types"
project was the most appealing to my skills. I would very much enjoy
working on this XWiki module.
I hope we will work together this summer.
Thank you,
Melania Galea
Hi all,
I am Vishnu, student from India, doing my Bachelors in Electronics and
Communication.
I am interested in contributing to XWIKI through GSOC 2012 in project " XWiki
HTML/OpenSocial Gadgets ".
I have very fluent experience in HTML, CSS and JavaScript. During my
academic year 2010, I have participated in an India wide web project
competition called "The Great Mind Challenge" conducted by IBM and stood
among "Top 20" teams from India.
The same year(2010) through GSOC, I have worked for MIFOS (Micro Finance
Open source) where I converted the framework from struts to Spring. Here I
have worked on "Freemarker" template language and Spring MVC. You can find
the code I have written at
http://google-summer-of-code-2010-mifos.googlecode.com/files/Vishnu_vardhan…
Also
Right now I am able to build and run xwiki.
Please suggest me where should I start from.
Thanks,
Vishnu.
Hi,
I am Sumedha Kodithuwakku. I am an undergraduate student in Computer
Science and Engineering. I have developed few gadgets using the Google
Gadgets API. Therefore I have a good understanding on gadget development
and related technologies (HTML/Java Script and also I'm familiar with
jQuery) . Therefore I would like to work on the above project as my GSoC
project.
Any suggestions or materials which will help me to start in this will
be much appreciated.
Thanks.
--
Sumedha Sanjeewa
Undergraduate
Department Of Computer Science & Engineering,
University Of Moratuwa,
Sri Lanka.
Hi devs,
Eddy has 3 pull requests active that I think we should include for 4.0M2:
* User profile customization
* User directory customization
* Annotation/Comment merge
I'd like to propose to delay the 4.0M2 release by 2 days (from Monday 26 to Wednesday 28) to allow us to accept them and release them. IMO we need to do this since we want to have max feedbacks about them, especially the annotation/comment merge which includes a migration.
WDYT?
Thanks
-Vincent