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
Hi,
Following our recently accepted definition of Committers/Emeritus Committers
(see http://www.xwiki.org/xwiki/bin/view/Community/Committership) and the
email entitled "[Important] Definition of Committers and their roles and
responsibilities" I sent on the 28/12/2006, I have now reviewed the SVN logs
to see who have been active committers for the past year.
I've put some statistics on
http://www.xwiki.org/xwiki/bin/download/Community/HallOfFame/xwiki-mpy-svn-s
tats-20070102.zip/xwiki-mpy-svn-stats/index.html. I've also used another
tool to generate more information and to find out who's not been active for
more than 1 year. Note that other stats can be seen here too:
http://ohloh.net/projects/68
As a reminder the goals for this are:
* Get more active committers and more participations
* Establish rules for defining what a Committer is
* Get more transparent to the community by establishing rules and thus have
clear rules for accepting new committers
* Be fair to everyone
I have noticed that there are 3 areas of Committers in XWiki:
- Core Committers: Committers working on XWiki Core (i.e. the main XWiki
distribution)
- Committers working on applications built on top of XWiki (for example
Curriki). Of course Core committers can also be Application Committers
- Research Project Committers: We've had a few of them for the Google Summer
of Code for example and we have some new ones joining us to continue the
work on the P2P project.
Note that non Core Committers cannot commit to the Core. They need to send
patches as other contributors.
Core Committers
---------------
Thus I'd like to propose to confirm the following persons as Core Committers
(who have been active during the past 1 year):
- ludovic - Ludovic Dubost
- vmassol - Vincent Massol
- sdumitriu - Sergiu Dumitriu
- jeremi - Jeremi Joslin
- namphunghai - Phung Hai Nam
- marta_girdea - Marta Girdea
- jvdrean - Jean-Vincent Drean
- amelentev - Artem Melentev
- jkraemer - Jens Krämer
- tepich - Jiri Luzny
- wr0ngway - Matthew Conway
- slauriere - Stéphane Laurière
- torcq - Cédric Torcq
- moghrabi - Xavier MOGHRABI
- rewbs - Robin Fernandes
- sgaide (just 1 year) - Sébastien Gaïde - Sebastien has expressed the
desire to contribute an installer to XWiki. Thus even though he's not
committed for just a year I'm proposing to keep him as an active committer
Of course anyone on this list can decide to be moved to the Emeritus
Committer status if he/she wants.
Curriki Committers
------------------
- jeremi - Jeremi Joslin
- ludovic - Ludovic Dubost
Research Project Committers
---------------------------
- thimel - Arnaud Thimel
- chrabiehroy - Roy Chrabbieh
Emeritus Committers
-------------------
And I propose to move the following as Emeritus Committers:
- kevingc - Kevin Chiu
- hasseeb - Abdul Haseeb
- kaaloo (just 1 year) - Luis Arias
- bikash - bikash agarwalla
- thomas (just 1 year) - thomas doucedame
- akartmann - Alexis KARTMANN
- erwan (just 1 year) - Erwan Arzur
- ptcoder - Pedro Ornelas
- tim - Timothée Peignier
- davidbrady - David Brady
- alberto - Alberto Saavedra
- mpetrashev - Maxim Petrashev
- huyennt - Nguyen Thanh Huyen
- chungnv - Nguyen Viet Chung
- arjunan - Arjunan
- mileticn - Nebojsa Miletic
In addition the following ids have never committed and will thus not be
Committers (they were added as developers on
http://forge.objectweb.org/project/memberlist.php?group_id=170). If they
need to commit they'll have to be voted in:
- alis - Ali Sakebi
- cburleso - Cody Burleson
- denis - Denis Hovart
- dgrizzanti - David Grizzanti
- ebilange - Eric Bilange
- gflandre - Guillaume Flandre
- glaforge - Guillaume Laforge
- jdelaulanie - jean de laulanie
- ldesmarets - laurent desmarets
- leonardosouza - Leonardo Souza
- Mahefasoa - NY HERIARIVONY
- mjobert - Matthieu Jobert
- mno - Max Nokhrin
- nicka - Nick Astete
- nthomas - Nicolas Thomas
- poussin - Benjamin POUSSIN
- raffaello - Raffaello PELAGALLI
- ramihery - ramihajamalala hery
- tuan08 - Tuan Nguyen
- yunz - Yun Zhu
Of course this is just a proposal and anyone listed here who do not agree,
please contact me directly. It's very much possible I've made a mistake.
I'll allow for 1 week to ensure everyone has a chance to see this mail.
Thanks
-Vincent
___________________________________________________________________________
Yahoo! Mail réinvente le mail ! Découvrez le nouveau Yahoo! Mail et son interface révolutionnaire.
http://fr.mail.yahoo.com
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
Hi,
I think we need to cleanly separate the 1.0 skin from the Panels
application. I think they shouldn't be linked and it should be possible for
a user to upgrade to the XWiki 1.0 skin without requiring to install the
Panels application
(http://www.xwiki.org/xwiki/bin/view/Code/PanelsApplication).
Conversely, it would be nice if the Panels application could be used with
some other skin.
Any idea on how to achieve this? How easy would it be?
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,
Reminder: We need everyone who are committing to implement issues for 1.0 B2
and RC1 to assign issues to themselves (or unassign themselves if they
cannot do it). I'd like this to be finalized by today end of day.
I'll then do a full pass to see what's left and send a summary email. It's
probably there'll be lots of important issues not taken up so we'll have to
do some shuffling.
Make you select issues please choose with the following in mind:
1) no new features
2) as little as possible of improvements
3) bug fixes in priority
4) bug fixes raised in b1 in priority. There are several issues reported by
users on the list which we need to transform into jira issues (the best is
to ask users who are reporting them to do that in order to help)
5) Don't put any issues in 1.0. We should have issues only in B2 and RC1. We
must leave 1.0 free for any bug found when RC1 is released.
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
