Hi,
I think we need to improve the way we update the documentation. Right now I
see several issues are marked as closed even though we haven't documented
them. Typical examples include new macros. They should be documented on
xwiki.org before we close the issue IMO. At the very least if for some good
reason we cannot do it immediately at least a new issue for documenting them
should be created at the same time so that it's not forgotten and so that
it's implemented in the future.
Nobody likes documenting stuff so my belief is that someone who does
something must do it completely, i.e. design, implement, *document* and
support.
WDYT?
Thanks
-Vincent
___________________________________________________________________________
D�couvrez une nouvelle fa�on d'obtenir des r�ponses � toutes vos questions !
Profitez des connaissances, des opinions et des exp�riences des internautes sur Yahoo! Questions/R�ponses
http://fr.answers.yahoo.com
Hi,
I have renamed a few JIRA components to improve consistency. Namely I've
renamed them so that similar components appear next to each other. For
example "Web Service Plugin" became "Plugin - Web Services", . etc. Removed
"XWiki" in front of some components as 1/ everything is about XWiki and 2/
it wasn't consistent with how other components were named.
I've also added a "Macros & Filters" component requested by Sergiu.
Here's what we have now:
- Actions and URLs (Lead: Ludovic Dubost)
- Admin (Lead: Ludovic Dubost)
- APIs (Lead: Ludovic Dubost)
- Applications (Lead: jeremi Joslin)
- Build (Lead: Vincent Massol)
- Core (Lead: jeremi Joslin)
- Default Wiki (Lead: Ludovic Dubost)
- Documentation & xwiki.org
- Editor - Wiki (Lead: Ludovic Dubost)
- Editor - WYSIWYG (Lead: Phung Hai Nam)
- JSR168 Module (Lead: Ludovic Dubost)
- Macros & Filters
- Other (Lead: Ludovic Dubost)
- Packaging (Lead: jeremi Joslin)
- Plugin - AntiSpam (Lead: Ludovic Dubost)
- Plugin - Other (Lead: Ludovic Dubost)
- Plugin - Web Services (Lead: Ludovic Dubost)
- Plugin API (Lead: Ludovic Dubost)
- Rights Management (Lead: Ludovic Dubost)
- Scripting - Groovy (Lead: Ludovic Dubost)
- Scripting - Velocity (Lead: Ludovic Dubost)
- Storage (Lead: Ludovic Dubost)
- Storage - JCR (Lead: Artem Melentev)
- User Interface
- Web Services (Lead: Arthur Casals)
- Wiki features (Lead: Ludovic Dubost)
I'm not sure what "Packaging" is about. I would be for renaming it to
Import/Export but looking at the issues there I think there are other things
in it, like packaging in the sense of distribution of files. In any case
there seems to be 2 in one there. WDYT?
In the future I think it's a good idea that most of these component match
module names in svn (this is what we have in Cargo, Maven ,etc - ie in
projects using fully maven2's directory structure). There are of course a
few transversal components like Build. Anyway we'll see how it goes.
Let me know if you think it's missing components/etc. We have to be careful
not to have too many too.
Any time you are using Other as the component it means we should have
something else. BTW I haven't done it but it's a good idea to look at what's
currently in Others so see the missing components...
Thanks
-Vincent
___________________________________________________________________________
D�couvrez une nouvelle fa�on d'obtenir des r�ponses � toutes vos questions !
Profitez des connaissances, des opinions et des exp�riences des internautes sur Yahoo! Questions/R�ponses
http://fr.answers.yahoo.com
Hi all,
As http://jira.xwiki.org/jira/browse/XWIKI-562 says, the Beta2 will have two
types of users, beginners and advanced. The difference is in the possible
actions that the user has access to directly from the interface (all the
functions can still be accessed from the right URL). We must decide which
are these actions.
Here is my proposal:
- create:
- page
- blog entry
- space
- edit: just the top button (no submenu) with the default editor. It will be
possible to switch between the 3 available tabs: WYSIWYG, wiki and page
access rights.
- show
- comments
- attachments
- history
- attributes
(no code)
- print
- pdf
- preview
- delete - admins only
Switching to the "advanced" status: in the user profile (still looking for a
better solution).
Waiting for your opinions.
Sergiu
com.xpn.xwiki.store.XWikiHibernateStore.searchDocumentsNames supports a
selectColumns parameter which is supposed to specify which columns should be
selected.
This parameter is used when building the select string, but the columns are
not included in the returned list, so this parameter just makes a bigger
select string and increases the execution time.
In order to include the specified columns in the result, I propose this:
- if selectedColumns is the empty string, keep the previous behavior (return
a list of document names)
- if selectedColumns is not empty, then return a list of hashmaps, with the
column name as the key, with a special name for the document name (for
example docname)
Hi,
As per a page
http://www.xwiki.org/xwiki/bin/view/Community/BuildingInEclipse there are a
couple of issues if one tries to build XWiki inside eclipse.
Is it of interest to get this working properly ? if so there is a .classpath
file that fixes some (trivial) problems (
http://www.xwiki.org/xwiki/bin/download/Community/BuildingInEclipse/.classp…
).
The catus ant task def has some errors (inside eclipse anyway) - seems to be
due to the interaction between cactus-ant and junit the following warning is
issued:
A class needed by class org.apache.cactus.integration.ant.CactusTask cannot
be found: junit/framework/TestListener xwiki-trunk build.xml line
211
This actually prevents the ant script from being executed correctly - since
I don't (currently) run the targets that needs this I can get around the
problem by simply commenting out the taskdef - however I'm a bit stumped on
how to fix this properly (since the class in question should be available).
Assuming building in eclipse is desired (and that the svn repository should
contain the .classpath and other . files used by eclipse) shall I simply
open a couple of jira's for these problems ?
Cheers,
Dan
PS. Apologies for preempting any discussions on xwiki-dev by creating the
"BuildingInEclipse" page, I assumed that since I could create content on the
wiki then it was ok to do so... In future I'll discuss on dev list prior to
creating xwiki.org content :)
Hi devs,
I had already sent an email saying that we needed one more release (Beta 3)
as there were lots of bugs raised in Beta 1. Actually it seems we're going
to need also a Beta 4 as there are really too many issues in JIRA and not
enough committers and contributors working on them.
I'm thus proposing the following (I have modified JIRA accordingly: Renamed
RC1 in Beta 3, moved unassigned issues from Beta 3 to Beta 4, moved
unassigned issues from Beta 2 to Beta 3):
* 1.0 Beta 2: 8 Jan 2007
* 1.0 Beta 3: 22 Jan 2007
* 1.0 Beta 4: 19 Feb 2007
* 1.0 RC 1 : 5 Mar 2007
* 1.0 Final : 19 Mar 2007 (actually this is assuming RC1 is good enough in
which case we'll label it as 1.0)
The idea is to have releases every 2 weeks which is the best way to get
feedbacks from users and know in advance of any issues. It also gives us a
nice tempo to work with. I believe this is much better than increasing the
duration times for each release.
Of course if suddenly we get lot of help then we could possibly delivery 1.0
earlier ;-)
AFAICS there are 5 active committers currently working on 1.0:
* Sergiu
* Marta
* Ludovic
* Nam
* Vincent (me)
It would be real nice if we get contributions in form of patches from other
users and developers lurking here. Anything you can help fix in JIRA is a
great help. We have also a big need in term of documentation help. For
example we need to document all macros/plugins/etc in the Code Zone
(http://www.xwiki.org/xwiki/bin/view/Code/). We have also other needs like a
skin authoring guide, a configuration guide, better tutorials, etc. This is
something anyone can easily contribute to.
I'll send another email on the Beta 2 status.
Let me know if there's any issue with the above.
Thanks
-Vincent
___________________________________________________________________________
Yahoo! Mail r�invente le mail ! D�couvrez le nouveau Yahoo! Mail et son interface r�volutionnaire.
http://fr.mail.yahoo.com
Hi,
I often see queries like "select something where doc.fullName !=
XWiki.SomeTemplate", which is definitely not nice. I would like to add a new
property to the document class, which indicates if the document is a
template. Also, we should provide an api to select documents containing a
certain type of objects, like:
$xwiki.searchDocumentsWithObjects("XWiki.ArticleClass", [extraquery],
[count, start])
This should behave like the current searchDocuments, but it also writes the
from and where parts of the query that tie the right type of object to the
document, and filters out the template documents.
Hi,
Here's the status on Beta 2:
* Fixed issues: 55!
* Open issues: 37
* Yesterday was a record day: 17 issues were fixed! Well done to Marta and
Sergiu who set up a new record on issue closing: :-)
* Days remaining (including week end ;-)): 4
Here are the remaining assignments:
* eveilleau thomas 1
* Francois Le Droff 1
* Ludovic Dubost 3
* Marta Girdea 10
* Phung Hai Nam 5
* Ravaneswaran Chinnasamy 1
* Sergiu Dumitriu 13
* Vincent Massol 3
Could you please all review your assignments to ensure they can be done
before the 8th. They need to be finished for the 7th so that I can starting
cutting the release on the 8th morning. If you know you cannot finish some
please reassign them to a later release.
Thanks everyone
-Vincent, 1.0 Release Manager
___________________________________________________________________________
Yahoo! Mail r�invente le mail ! D�couvrez le nouveau Yahoo! Mail et son interface r�volutionnaire.
http://fr.mail.yahoo.com
Hi All,
In response to a comment on
http://www.xwiki.org/xwiki/bin/view/Main/Download I created
/Main/BuildingInEclipse detailing how I'd managed to get XWiki to be built
in eclipse... only it's gone !
Was there something wrong with it, or was it accidentally deleted ? If the
later is the case, can it be recovered or should I re-do it. If there was a
reason for it being deleted please let me know so I don't make the same
error twice :)
Thanks
Dan
