FOP is an open source project, and everybody can contribute in his own
way, so you can reopen closed issues as you want if needed, and submit
patches as you want.

That said, IMHO, apart in a company quality context, testing closed
issues will not help very much (typically, an issue is closed after
developer's checks, and it is often monitored by the opener who reopen
it if needed)
you can check old opened issues against FOP TRUNK, since there is no
systematic checks for opened issues after each commit.
You can find fixed issues that haven't been closed.

Le 01/05/2011 02:25, darshan a écrit :
> Dear All,
> I am a post graduate student at the Australian National University 
> taking a course on Free and Open Source Software Development. Part of 
> the course requirement is to study an open source project of my choice, 
> make a contribution and write a report by the end of May 2011.
> I have been going through the fop site and documents and from the 'How 
> you can help' topic on the page 
> http://xmlgraphics.apache.org/fop/dev/index.html
> I thought the best way I could contribute is  by testing newly-closed 
> issues to make sure they are truly closed. By doing this I can gradually 
> understand how the system works and hopefully start make more 
> contributions like submitting bug reports and patches.
> Can I start from the most recent fix form the page 
> http://xmlgraphics.apache.org/fop/changes.html#Code_FOP%20Trunk ? please 
> guide me as to what would be the best way of doing it and also I would 
> be really glad if you could suggest me any other way to contribute that 
> would help the project better.
> Best regards,
> Darshan Pradhan
> u4729...@anu.edu.au


Reply via email to