I downloaded xwiki-0.9.840-src.tar and got the error:
tar: A lone zero block at 98831
I used to get this when building tars from Ant - I don't think it
breaks anything but it just looks bad. I take it xwiki isn't tarred
up using gnu tar?
Alistair
Hi,
We want to change the way the community work.
We want to create 2 groups:
* One group of developer. A developer is a user who contributes to the
project in the form of code or documentation. They take extra steps to
participate in a project, are active on the developer mailing list,
participate in discussions, provide patches, documentation,
suggestions, and criticism. Developers are also known as contributors.
(Definition from
http://www.apache.org/foundation/how-it-works.html#roles)
* One group of committer around XWiki.
A committer is a developer that was given write access to the code
repository. Not needing to depend on other people for the patches,
they are actually making short-term decisions for the project.
We also want to change the way to become committer on XWiki. Before
becoming committer on XWiki, you have to "earn" the merit to be part
of the development community. For those of you who are already
committer on XWiki, you will keep this right if you want. You just
have to send me a mail OFF LIST before the 9february to stay committer
and tell me why you want to stay committer.
We will write some rules to lead the project soon.
what do you think about that?
--
Blog: http://www.jeremi.info
LinkedIn: https://www.linkedin.com/profile?viewProfile=&key=1437724http://www.xwiki.org
skype: jeremi23 -- msn et gtalk : jeremi23(a)gmail.com
Hi the XWiki Team,
I found in the mailing list archives that you are planning to use maven to
build xwiki. I am a committer to the apache pluto project, which uses
maven2. Thus i got some experience on maven 2. (Mr. Vincent Massol must be a
maven master, since he is on the maven team :) I would like to help you
migrate to maven.
I checked out the xwiki source from subversion, and am trying to re-organize
the project layout and create pom.xml files. Currently i am still dealing
with the dependencies. I would like to propose to separate the xwiki project
into small subprojects, and decouple the APIs from the implementation (such
as user api and different implementations, plugin api and different plugin
implementations, etc.). That will make the source more clear and more
readable.
I don't know how to help on this topic. Re-organizing the project layout
introduces too many modifications on the project, which may have a lot of
impacts on the current development, and it's difficult to generate svndiff
and create patches. I would like to know if it is possible to apply for
joining the dev team and create a new branch in svn for the maven migration.
I am taking a look at the JCR spec currently, since I created a java wiki
engine project (
http://people.apache.org/~zheng/elsie/<http://people.apache.org/%7Ezheng/elsie/>)
and am thinking of refactoring it using JCR and apache jackrabbit. I
found
that you are also planning to implement the xwiki repository using JCR. I
would like to help and contribute to this subproject too.
Best regards.
--
ZHENG Zhong
- http://heavyz.blogspot.com/
- http://people.apache.org/~zheng/ <http://people.apache.org/%7Ezheng/>
I noticed that XWIKI-177, an issue I reported, was recently marked "Won't
fix". A comment was made to the effect that the current behavior isn't a
bug.
This issue affected my design of my "XWiki Aggregate Document PDF Generator"
(http://www.xwiki.org/xwiki/bin/view/Dev/AggregateDocs). I wanted to use the
xwiki.getDocument() function to retrieve documents for inclusion in the
generated PDF, but due to XWiki's current behavior, I had to resort to using
HTTP downloads (a much slower and less robust approach).
I guess I'm having a hard time understanding why the current behavior
described in XWIKI-177 is the intended behavior. It really seems like a bug
to me.
Stephen
