My strongest skills are in java,j2ee,and jms architecture and
development - I am also pretty good at documenting stuff (I used to
write articles for computer magazines explaining some high tech topic) -
followed by DB and infrastructure stuff like machines, OS, networking,
TCP/IP and Internet, etc. etc. (
http://www.anilgurnani.com should give a
pretty good idea about me) on the infrastructure front, I can provide
hosting space, subversion, wikis, downloads, mirrors in US - etc. etc.
through my previous venture (
http://www.oncr.com)
Doing some documentation may be a good starting point (as I will need to
learn before I can document) - is there any particular type of
documentation that is currently needed?
Thanks
Anil
-----Original Message-----
From: Sergiu Dumitriu [mailto:sergiu.dumitriu@gmail.com]
Sent: Wednesday, May 09, 2007 9:52 AM
To: xwiki-dev(a)objectweb.org
Subject: Re: [xwiki-dev] xwiki dev ideas
Hi,
You probably did notice from the mailing lists that we do need
developers (and testers), especially at this point, when XWiki 1.0
should be out in a few days, and when the XWiki 2.0 architecture must
be finalized and implemented. So your help is very appreciated.
"Not hard to implement" differs from person to person. Could you tell
us what are your strong points? Java, databases, html+css, javascript,
velocity, testing, documentation?
On 5/9/07, Gurnani, Anil <agurnani(a)bear.com> wrote:
Ok so I have been a member of the dev mailing list for
over six months
and I have been playing with the latest releases of xwiki for six
months
and now I am itching to contribute :-)
Anybody has any ideas for some cool (yet not very hard to implement
cause my understanding of the code is very minimal at this point)
feature to get my feet wet?
Anil
Sergiu
--
http://purl.org/net/sergiu
***********************************************************************
Bear Stearns is not responsible for any recommendation, solicitation,
offer or agreement or any information about any transaction, customer
account or account activity contained in this communication.
***********************************************************************