Hi,
   My name is Abhinav and I am very
interested in the "LDAP server implementation"project you’ve recently posted on GSOC-2013 project ideas list. I am
currently doing my Masters in Computer Applications at Anna University,
Chennai, India. I have been interested in working with Java and LDAP Server and was
hoping to find out a little more about this project. So I would be able
to effectively shape my proposal for this project, demonstrating why I
am a quality candidate for this project.
I am looking forward to a reply from you.
Hi , my name is Sushil Kumar and i'm an undergraduate student at JIIT ,
Noida (India) . I would like to work on the project Advanced Email
Integration via GSOC 2013 . I consulted about the work that need to be done
in this project on IRC channel and got a nice explanation . But there was a
dilemma between what have to be done in this project and what has already
being done here
https://github.com/xwiki-contrib/xwiki-application-mailarchive .
Well here are the bullet points which i have understood after two days of
talks on IRC .
- A SMTP server is required to receive mails and then to attach them as
XWikiComments object to a document.
- sdumitriu suggested me to use Apache James , but he said that its a
full blown mail server and we only need receiving part hence we need to
slice that part out.
- I found it very hard to slice the SMTP part and embed it with Jetty (
its hard without rewriting the code from scratch and taking help from James
and MailArchive plugin )
Now after all these i have certain doubts regarding what exactly needs to
be done in this project .
- Do we have to integrate a mail server or have to write our own SMTP
receiver ?
- If we have to integrate a mail server do we have to slice out the SMTP
part only?
- Or is it something entirely different from these two points.
P.S. The same dilemma exists for the Jabber part too. But will figure it
out once Email Integration is well understood.
Thanks and Regards
Sushil Kumar
FTR I've configured the Jenkins build promotion plugin this weekend on our CI.
What it does now is flag XWiki Enterprise promoted builds with a green star.
An enterprise build is promoted when all the functional tests jobs pass.
The name of this promotion is "Release to QA"
Thanks
-Vincent
Hi devs,
This is not the final proposal, but the state of an iteration.
I want to have a consistent 'Create' step across creating
wikis/workspaces/spaces/pages.
You can see some work done at
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/CreateImprovements
The 'Create Workspaces' step will contain multiple steps, just like a
wizard, but with the mention that you don't need to go across all the steps
in order to 'Create'. You can enter the name and just rely on the defaults
(default type selected, location according to the context, standard
members).
I still need to make proposals for Step 2 and Step 3.
Today I just show the consistency between Workspaces, Spaces and Pages, by
having the "Type" selector that will list Flavors, Templates, etc.
Thanks,
Caty
The XWiki development team is proud to announce the availability of XWiki 5.0 Release Candidate 1.
This is mostly a stabilization release leading to 5.0 but we included a few bonus items: Distribution Wizard improvements to support multiwiki use cases and the ability to see which extensions have updates.
You can download it here: http://www.xwiki.org/xwiki/bin/view/Main/Download
Make sure to review the release notes:
http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki50RC1
Thanks
-The XWiki dev team
Hi guys,
We now have an @Unstable annotation and we need to use it.
I see for example that the Job or Extension module APIs are regularly broken and they're not tagged as Young APIs. IMO they should.
Here are some recent examples in 5.0RC1:
https://gist.github.com/vmassol/5428600
If we don't use and we continue to break APIs all the time there's no point in having created this new concept of young apis.
Some modules have already had several releases done and were done before we created the @Unstable annotation. We should review them and decide if we consider them young apis or not. If so then we should mark it in the release notes and add @Unstable annotations to them.
WDYT?
Thanks
-Vincent
Hi,
*
My name is Rafaela. I am currently pursuing a MSc program in Computer
Science at the Technical University of Denmark, after finishing my Computer
Engineering BSc program at Politehnica University in Bucharest.
I am planning to apply to this year's GSoC edition and, after scanning
through most of the proposed projects, I have to say that the ones proposed
by XWiki have definitely got my attention. The ones that I'm quite
interested in are the ones about advanced e-mail integration, improving the
messaging feature and translation in context.
I've already cloned the xwiki-platform repository and I am starting to look
over the codebase. Is there anything more I can do to get a better overview
of the mentioned projects so that I can decide on which I'd like most to
work on?
Have a nice day,
Rafaela Voiculescu
*
Hi devs,
Since our goal is to have the SOLR implementation be the default search and
since our goal is to move the lucene impl to xwiki contrib as a retired
project, I propose that whenever a JIRA issue affecting the Lucene search
is closed in the current SOLR implementation, we close it as duplicate.
I've just done that for http://jira.xwiki.org/browse/XWIKI-6228
Hope it's fine with you.
Thanks
-Vincent
Hello everyone!
Could someone with access to the XWiki-Contrib repo on GitHub (
https://github.com/xwiki-contrib) add me as a member? I'm planning on
further developing the Xinit project and perhaps some of the other projects
in the near future. My username is "rebelthor" (https://github.com/rebelthor
).
Thanks!
--
Best Regards,
Daniel Patriche
XWiki SAS SysAdmin
Hi devs,
A single wiki model is mostly used to demo XWiki and to test its features.
In production usually we have a multiwiki model, because of its
flexibility.
Since 5.0M2 we also have virtual mode enabled by default, meaning that is
even easier to create and manage subwikis/workspaces.
No matter if you want independent wikis or workspaces, both cases share a
Main Wiki. I propose to call the Main Wiki a 'Portal'.
The Portal purpose is to:
- both: manage the wikis/workspaces, being the point where you create new
wikis/workspaces;
- both: help the navigation between wikis/workspaces, by being the 'home'
point for them;
- workspace: manage the global users, providing access to a User Directory;
- workspace: will provide a global view of users' activities in workspaces;
- wikis: will provide a webhome (similar to what we have on myxwiki.org)
that states the purpose of the farm.
Workspace already has a custom menu in which there is present the 'Main'
wiki
http://incubator.myxwiki.org/xwiki/bin/download/Improvements/PortalMenu/cur…
I've made a proposal for the content of the menus in
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/PortalMenu that we
shall discuss.
'Portal' entry is present in the menu and also in the Breadcrumbs. The
'home' icon should be always present in the breadcrumbs, followed by the
Wiki/Workspace WebHome and then should be user defined (according to a
custom parent/child relation).
By having it clearly stated in the menu and in the breadcrumb, it will
improve the navigation between workspaces (and will give a home point for
the wikis).
In single wikis, the Portal entry is skipped.
Thanks,
Caty