xwiki-devs March 2009

xwiki-devs@xwiki.org

60 participants
146 discussions

[xwiki-devs] [Proposal] Find out active XE installations

by Vincent Massol

Hi devs, I think it would be interesting for us to know how many people install and use our software. Of course we'd need to do this in a non intrusive manner that adds value for the user. Here's an idea Ludovic and I have discussed: * In the administration page add a blog panel by default (replacing the create page panel for ex which IMO isn't needed there) showing the last 5 RSS feeds from xwiki.org -> This is useful for the admin users since they need to know the latest versions and news about the software they use -> They can remove the panel easily if they don't want to see news -> We can generate a unique id based on the user's system (http://johannburkard.de/blog/programming/java/Java-UUID-generators-compared… ) so that we can identify active installs We could then define what we call an active install (say a ping at least once every month for ex) and we can find: - how many new installs per day/month/year - how many users stop using xwiki after some time and what the average time it's used actively Obviously we won't get perfect data (people will remove the panel, others won't be connected to the internet, etc) that but it seems to me it would a good guess. Once we get this data we could display it on xwiki.org (we could even display it in the stats space with the other data). WDYT? Thanks -Vincent

15 years, 5 months

[xwiki-devs] GSOC 2009 : Google Docs Integration in XWIKI

by Arun Reddy

Hello devs, I am interested in the idea of "Google Docs Integration in XWIKI ". This idea is an extension to the existing Google Docs Plugin : http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/Google+Docs+Integrat… I have successfully installed that plugin with the help of sergiu and ludovic. Learnt how it works. Looking out how to integrate various google documents ( docs,spreasheets,. powerpoint) into xwiki. I will be happy if you can post few of your ideas on what all features can be included and considered for extending this feature. -- Best Regards, Arun Reddy

15 years, 5 months

[xwiki-devs] status of "Social Networking via OpenID support in Xwiki?" for GSOC?

by Niels Mayer

I've noted some more comments about widget integration in general, but nothing as specific or useful (IMHO) as a project to integrate http://www.google.com/friendconnect/ ( http://www.youtube.com/v/N94s7ix0JPo&hl=en&autoplay=1 ) with Xwiki. That way people with the appropriate ID/credentials compatible w/ google friendconnect's OpenID would be able to login and leave authenticated comments on a wiki. A while back Thilina Buddhika ( http://www.mail-archive.com/devs@xwiki.org/msg07563.html ) expressed interest in this subject on this list; I was wondering if that interest continues, or if others might find this an interesting pursuit for GSOC 2009. The user experience should be that those w/ openID credentials should get an automatic login into Xwiki, and that the same authentication would also drive the friendconnect "widgets." I think the widgets themselves could easily be integrated into Xwiki's existing panel system. Therefore, the main work would be in creating a smoothly-integrated OpenID-based auth system giving appropriately credentialed users an automatic "authenticated guest" login. This login allows authenticated comments and registration, making commenting much easier and straightforward in Xwiki. Also, registration could always associated with a real user and not a spam account at mail.ru... Although the construction of widget "panels" itself might be simple, some of the authorization issues might be thorny. For example, do you publicly display your friends-list-widget-panel to all unauthenticated users and search engines, or do only logged-in users get access? Likewise, when "friends" log in or view your site, they might automatically receive special privilege based on their authenticated-friend status, e.g. view-access to a private part of the wiki, for example. This might require extension of the Rights system in Xwiki with extra roles alongside "unathenticated user", such as "openid authenticated user" and "openid authenticated friend." ... Here's the original messages and a summary of replies: On 02 Feb 2009, Thilina Buddhika wrote: [xwiki-devs] Possible project ideas for XWiki in GSoC 2009 I have a growing interest on XWiki and willing to take part in its development. I am also planning to apply for GSoC 2009 (yet to be announced) and I have realised that XWiki is a challenging and promising open source project for GSoC 2009. When watching the developer list, I found this mail by Niels Mayer with the subject,* "Social Networking via OpenID support in Xwiki?"*. And It looks like an intersting idea. I also found that there was a GSoC 2008 project related to this idea [1]. So is it possible to continue this project further? Other than the above idea, I would like to know the other possible project ideas for GSoC 2009. If it is too early I am posting about this, then lets leave it for the next couple of weeks. Anyway I am trying to get familiarized with Xwiki until the GSoC 2009 is announced. [1] - http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/SSOAndOpenIDSupport ................................... from: Niels For some strange reason, I think this is an excellent idea :-) > > Of these, which has the easiest to integrate: > http://www.google.com/friendconnect/ > http://developers.facebook.com/connect.php > > http://developer.myspace.com/Community/blogs/devteam/archive/2008/12/09/int… > > Friendconnect has always looked most interesting of the lot, since it will > give you a variety of customizable friendconnect "widgets" . Once you > request and customize a particular instance, google generates the code and > presents it in a scrollable textarea. > > Reusing the framework of one of Xwiki's existing panels is a good way to > wrap Google Friendconnect socialnetworking into an Xwiki site. You'd > basically take the code and paste it into the panel document. Then layout > one or more of the google panels into the "sidebars" in Xwiki. This permits > xwiki to layout the friendconnect panels as if they were :"one of it's > own." > > Probably the easiest first-experiment would be to take an existing panel > that you probably don't use, like /xwiki/bin/inline/Panels/Welcome; as > 'Admin' click "edit" and then paste in the google code between > #panelheader("Welcome") and #panelfooter(). Later, create more via > http://nielsmayer.com/xwiki/bin/view/Panels/CreatePanel ... > > This video shows what happens on the google-side: > http://www.youtube.com/v/N94s7ix0JPo&hl=en&autoplay=1 > > I haven't looked at friendconnect's OpenID implementation so I don't know > how it would coexist or overlap w/ Xwiki's auth. > I'd assume you'd create an implementation per > > http://svn.xwiki.org/svnroot/xwiki/platform/core/trunk/xwiki-core/src/main/… > follow instructions in > > http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Authentication#HCustomA… > > You mentioned GSOC 2008 and > http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/SSOAndOpenIDSupport > ... > what is the status of any code completed to date? > ............................... Vincent Massol: I'm pretty sure we'll all want to have widget integration as a GSOC > 2009 project (open social, etc). > ............................... Thomas Mortagne: > The OpenId authenticator and provider already works pretty well based > in the current not very clean authentication api with some hack > > because Markus did not had choice to do this otherwise. I just did not > had time to integrate it yet in the trunk but Raffaello Pelagalli > started do to some test with it to integrate between > http://l10n.xwiki.org and xwiki.org farms (l10n is on its own instance > > of XWiki). > > See http://jira.xwiki.org/jira/browse/XWIKI-2630 , > http://jira.xwiki.org/jira/browse/XWIKI-2588 and > http://jira.xwiki.org/jira/browse/XSALBATROSS-34 > > .................................. Markus Lanthaler: > Right. The implementation is complete but I guess the tests are still > missing (kind of difficult to write meaningful tests for it). > > The implementation supports both, RP and server. XWiki can accept OpenIDs > from other sites as well as issue OpenIDs to be used on other sites > supporting OpenID. That way you can use your XWiki account all over the web > > (well at least on sites that support OpenID). > > Niels http://nielsmayer.com

15 years, 5 months

by Thomas Mortagne

On Wed, Mar 25, 2009 at 15:51, Sergiu Dumitriu <sergiu(a)xwiki.com> wrote: > tmortagne (SVN) wrote: >> + if (header.getLevel().getAsInt() <= HeaderLevel.LEVEL2.getAsInt()) { > > Couldn't the level be Comparable? Actually, as an enum, it already is. Improving the code by using it. Thanks Sergiu > > -- > Sergiu Dumitriu > http://purl.org/net/sergiu/ > _______________________________________________ > devs mailing list > devs(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/devs > -- Thomas Mortagne

15 years, 5 months

[xwiki-devs] [Proposal] XE 1.9 + XE 2.0 + Roadmap for XE 1.9

by Vincent Massol

Hi devs, XE 2.0 ===== We've had discussion about XE 2.0 in the past. I think now is the right time to release it and we should prepare to do so. Two reasons; 1) We've had a lot of new features (new rendering, new wysiwyg, webdav, REST, office import, usability improvements, etc) added recently in 1.8 and this alone warrants calling it 2.0. The new rendering and new wysiwyg could be set as default in XE 2.0. 2) XE 1.0 marked a stability level. XE 2.0 will mark another stability level (I'm thinking about the old wysiwyg editor which could be said to be stable...) 3) It's been almost exactly 2 years since we released XE 1.0, it's high time for a major release. However since we still have a bit of work to fully finish the new rendering and new wysiwyg and since we want user feedback from 1.8 to ensure we get a rock solid 2.0 release I propose to have a XE 1.9 release before the XE 2.0 (which would be a promotion of XE 1.9 final with the config change to have new syntax/wysiwyg as defaults). The other advantage of releasing XE 2.0 is that we want to start the maintenance period for the old rendering/old wysiwyg as early as possible to get new people to use the new system. Once 2.0 is released we'll continue releasing bugfix versions of 1.9.x from time to time but we'll advise people to switch to 2.x. I propose we keep support for the old 1.0 syntax (either using the old code or using the 1.0 --> 2.0 syntax converter) for 1 year. This is the time we have to make our existing users switch to the new syntax. Note that with the automatic converters it shouldn't be something too difficult. Roadmap for XE 1.9 ================ General:It's a stabilization release meaning we must resist putting new things in it and fix what doesn't work well enough. Content proposal: * Finish/stabilize/document new rendering - Thomas/Vincent * Finish/stabilize/document new wysiwyg editor - Marius/Anca * Finish/stabilize/document office importer + doc splitter/management - Asiri * Finish/stabilize/document webdav - Asiri * Finish/stabilize/document REST support - Fabio * Finish/stabilize/document new blog application - Sergiu/Guillaume * Continue UI improvements (ex: new treeview, new search interface, full list to be defined) - JV/Ecaterina/Guillaume * Fix search using lucene plugin - ???? * Finish XE French translations - JV/Guillaume * Fix other bugs (watchlist, page names with special chars, etc) - All * Refactoring of apps to use more of SSX - Jerome? Note: I don't think we can commit to have a new skin system or a new skin in place for the 1.9 timeframe. Proposed Dates: * 1.9M1: 6 April * 1.9M2: 4 May * 1.9RC1: 18 May * 1.9RC2/Final: 1 June * 2.0: 15 June WDYT? Thanks -Vincent

15 years, 5 months

Re: [xwiki-devs] [xwiki-notifications] r17994 - in platform/core/branches/xwiki-core-1.8: xwiki-core/src/main/java/com/xpn/xwiki/doc xwiki-core/src/test/java/com/xpn/xwiki/doc xwiki-rendering/xwiki-rendering-api/src/main/java/org/xwiki/rendering/block xwiki-rendering/xwiki-rendering-api/src/main/java/org/xwiki/rendering/internal/renderer xwiki-rendering/xwiki-rendering-api/src/main/java/org/xwiki/rendering/internal/renderer/chaining xwiki-rendering/xwiki-rendering-api/src/main/java/org/xwiki/rendering/liste

by Sergiu Dumitriu

tmortagne (SVN) wrote: > + if (header.getLevel().getAsInt() <= HeaderLevel.LEVEL2.getAsInt()) { Couldn't the level be Comparable? -- Sergiu Dumitriu http://purl.org/net/sergiu/

15 years, 5 months

[xwiki-devs] [Proposal] New Search Interface

by Ecaterina Valica

Hi devs, This week I've been working on making a new UI proposal for the existing XWiki search interface. I would really apreciate your feedback on my proposal mockups that can be found at http://incubator.myxwiki.org/xwiki/bin/view/Mockups/Search+Interface#propos… If you're interested in more information, other mockups variation and analysis can be found on the same page. Thank you, Ecaterina Valica

15 years, 5 months

[xwiki-devs] About idea on Xwki Jabber, Google Talk and Skype Integration

by Tharindu Madushanka

Hai, I am an undergraduate student at University of Moratuwa, Faculty of Information Technology. I have experience working with Jabber protocol and I am interested in knowing more information about this idea on* integrating Jabber, Google Talk and Skype with XWiki*. I am new to Xwiki project and learning it these days. Few things I need to know are as follows, actually I need to clarify whether I got the idea correctly 1) Xwiki users should be able to save their jabber logins at their profile page including password for the jabber id and also it should allow users to enter any private jabber server details as well 2) Once user loggs in it will login to the specified accounts 3) At some where on wiki web page we need to display the chat list * - It includes all Google Talk, Jabber or Skype contacts - I mean XWiki user can chat with any of his im friends from this chat tool, this will be a private chat * - XWiki users could be invited to join for a group chat by someone who creates a group, by using the chat tool on web page * *This is what I have understood by the project idea, can you *please correct me if there is any confusion between what I have understood with the idea given at XWiki site itself* *Ques1 & 2* What is meant by 'tool should allow to list the chats actively launched or monitored by the wiki' ? What is meant by 'A Jabber AJAX chat tool can also be integrated for users not having Jabber or Google talk installed' ? I could not understand above two sentenses fully that were at XWiki ideas page. Please can any body clarify me on this. Thank you, *H.T.M. Gamage ** *Student,* * Faculty of Information Technology, University of Moratuwa, SriLanka. Mobile: +94 (71) 5518852 ChatID: tharindufit Blog : tharindufit.wordpress.com

15 years, 5 months

[xwiki-devs] [GSoc 2009] XWiki integration with OpenOffice

by Cristina Scheau

Hi! My name is Cristina Scheau , a graduating student in Computer Science at “Politehnica” University from Bucharest. I worked 6 months on .NET framework at http://bsgroup.ro/ , coding in VB.NET (most part) , and in C# some features. I also worked 6 months at http://www.amamobile.com/ as JAVA Programmer. Last summer I was intern at http://www.crestatech.com in Santa Clara, CA, where I developed an application using C and VC++. I’ve also worked at some personal projects using JavaScript, AJAX, HTML,PHP,antlr. I am interested in more Xwiki projects but especially in Xwiki integration with Open Office. I have some questions regarding this topic. 1. For the server side, can one reuse the code from Xword?(or is it desired a totally new implementation?) 2. The project includes also the Xwiki integration with Open Office spreadsheet and presentation or just with OO Writer? Another problem ( i don’t know if this is the right place to post) is that, I suggest a small improvement of UI for Xword. If the user cannot connect to the wiki server (changing the Xword options), a notification message should be displayed. It is a little bit confusing displaying only an empty navigation space and all the action buttons in the ribbon being enabled ( I saw that the buttons issue is set in JIRA so i won’t give details). I mention that I used Xword 1.0.0.66. Thanks in advance, Cristina Scheau

15 years, 5 months

[xwiki-devs] Listing developers and contributors, copyright policy

by Sergiu Dumitriu

Hi devs, In the early days of XWiki, we used to put @author tags inside Java source files. Later on, we decided that this is a bad practice, and started removing them, on the premise that we will have a NOTICE file listing all authors and contributors. And although we managed to remove almost all @author tags, the NOTICE file doesn't list any developers or contributors, listing just XWiki as a company as the copyright holder. This would be OK if we had a policy stating that all Intellectual Properties belong to XWiki. But we don't. So, shouldn't we make an official policy? Here are some alternatives: I. Individual copyright - we list developers - we list all contributors and their contributions - contributors retain the IP for their submitted code II. Collective copyright - we list developers - we list all contributors and their contributions - XWiki as a collective is the only copyright holder, and we specify that any submitted patch will be the property of the community - having a non-profit organization would help III. Umbrella copyright with acknowledgments - we don't list developers - we list all contributors (including devs) - XWiki SAS as a company is the only copyright holder, and we specify that any submitted patch will be copyrighted by XWiki IV. Umbrella copyright, no acknowledgments - we don't list developers or contributors (in the pom, the web hall of fame can and should still exist) - XWiki SAS is the only copyright, and we specify that any submitted patch will be copyrighted by XWiki Currently we're doing IV, but we don't make this explicit. I'd vote for II, as this is a more Open way. On the technical side, Maven already provides support for listing contributors and developers, for the moment these sections are empty. We can change the NOTICE template to automatically list them. An important question is where do we list people? - In the parent pom, which implies frequent releases of the parent, which means frequent version changes for all the other modules. - In each project's pom, which means that new contributions will only require releasing the affected module, but it will be harder, if not impossible, to aggregate contributions. -- Sergiu Dumitriu http://purl.org/net/sergiu/

15 years, 5 months

← Newer
1
...
4
5
6
7
8
9
10
...
15
Older →

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 March 2009