Re: [VOTE] Proposal: new xml-commons subproject for standards-based files: commentsto Dirk

[Dirk-Willem van Gulik <di...@covalent.net>]

> Shane_Curcuru@lotus.com wrote:

> > Of all the xml committers, I feel confident that we have a good
> > half-dozen people who will be active and can help manage mailing
> > lists, etc., including myself.  But perhaps I shouldn't assume - maybe
> > some of those people who gave this proposal their +1 will step up
> > again and assert they'll help out with the organization, etc.
> > explicitly...
>
> Just tell me how I as a non-committer can help. This project is a Good
> Idea (TM) and something I did before - an ideal entrance point for me as
> a xml.apache.org newbie. :-))

That is easier than you think; simply work on the code; the doc's - review
changes, make comments, edit code; and send a patch to the mailing list.
The only difference between a committer and any other contributer is that
the first can commit directly; whereas the latter needs a little help. But
apart from that - everyone's input is valuable.

Specifically

-	Follow the changes, comment on them.
-	Check out/update your source tree
	regularly; try it, test it, give feedback.
	Do general QA...
-	Doc's, installation, operation procedures, there
	is a lot which can always be improved.
-	Send patches (the more - the merrier (until
	you get punished with commit access - and
	just doubled your burden :-)).
-	During release time; check out the code; test
	it; help signing off on the release.

and this list goes on and on..

Dw


---------------------------------------------------------------------
In case of troubles, e-mail:     webmaster@xml.apache.org
To unsubscribe, e-mail:          general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org

Re: [VOTE] Proposal: new xml-commons subproject for standards-basedfiles: commentsto Dirk

[Martin Stricker <sh...@gmx.de>]

Dirk-Willem van Gulik wrote:
> Martin Stricker wrote:
> > Just tell me how I as a non-committer can help.
> 
> That is easier than you think; simply work on the code; the doc's -
> review changes, make comments, edit code; and send a patch to the
> mailing list.
> The only difference between a committer and any other contributer is
> that the first can commit directly; whereas the latter needs a little
> help. But apart from that - everyone's input is valuable.
> 
> Specifically
> 
> -       Follow the changes, comment on them.
> -       Check out/update your source tree
>         regularly; try it, test it, give feedback.
>         Do general QA...
> -       Doc's, installation, operation procedures, there
>         is a lot which can always be improved.
> -       Send patches (the more - the merrier (until
>         you get punished with commit access - and
>         just doubled your burden :-)).
> -       During release time; check out the code; test
>         it; help signing off on the release.
> 
> and this list goes on and on..

Thanks, Dirk! So now I hope we'll get started with xml-commons quickly.
I'll look esopecially at the Perl part and will search the CPAN for
modules we might want to use. Eventually I'll get myself into the
Xerxes.pm-code rto look for nice bits there... but this part has to be
discussed on the xerces-p list.

Best regards,
Martin Stricker
-- 
Homepage: http://www.martin-stricker.de/
Registered Linux user #210635: http://counter.li.org/

---------------------------------------------------------------------
In case of troubles, e-mail:     webmaster@xml.apache.org
To unsubscribe, e-mail:          general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org