Hi Steven, shath...@e-z.net wrote on 03/05/2012 04:35:56 PM:
> XALAN-C Google Summer of Code - 2012 > > Here are some areas where the Google Summer of Code (GSOC-2012) > can have a good impact on preparing for product releases. > > GSOC-2012 can help with infrastructure/automation projects by > creating release builds for XALAN-C evaluation and distribution. > > I am willing to participate as a mentor this summer. > > Does the XALAN PMC wish me to work on this? Any committer can volunteer to do this. You don't need the PMC's approval, but it's something that I'd be happy to see. I would suggest that your read this (http://community.apache.org/guide-to-being-a-mentor.html) first to get an understanding of the commitment. > Deadline for mentoring organization application > Friday March 9, 2012 at 23:00 UTC That's the deadline for the various open source organizations to apply for participation in GSoC. I expect that Uli and the com-dev team will handle the ASF's application. We don't need to worry about this date, but would be good to get project ideas entered into JIRA soon so that when students start showing up they'll see these proposed projects in the list and have nearly a month to put together their project application / detailed proposal. For reference, here's the full GSoC 2012 timeline: http://www.google-melange.com/gsoc/events/google/gsoc2012 > Sincerely, > Steven J. Hathaway > <shatha...@apache.org> > > AUTOMATE THE UNIX BUILDS OF XALAN-C LIBRARY SOURCES > =================================================== > > Provide binary library packages for AIX, HPUX, SOLARIS, LINUX > > 1> Extract the code base from the SVN repository. > > 2> Compile on UNIX systems the binary packages for the XALAN-C library. > > 3> Package the development and release builds as tar files and compressed > tar files. > > 4> Post the build scripts to JIRA and possibly a public accessable web site. > > 5> Post the assembled packages on a public accessable web site. > > > AUTOMATE THE BUILDS OF XALAN-C DOCUMENTATION SOURCES > ==================================================== > > Note: Doxygen and GraphViz programs are now available for Windows platforms. > They have only been used by the XALAN-C team on Linux and UNIX platforms. > > The XALAN-C User Guild can be built using the Xalan command-line > utility and simple script files. > > The XALAN-C Interactive API Reference pages are constructed with > the Doxygen and GraphViz programs on Linux and UNIX platforms. > > 1> Extract the code base from the SVN repository. > > 2> Create scripts to build the XALAN-C User Guide. > > 3> Create scripts to build the XALAN-C API Reference. > > 4> Create scripts to assemble a documentation package into tar and zip files. > > 5> Post the scripts to JIRA. > > 6> Post the documentation packages on a public accessable web site. > > The current scripts in the XalanDocs branch build the User Guide on > a Windows platform and the API Reference on a UNIX/Linux platform. > > > UPGRADE XERCES-C TO USE WINDOWS VISUAL STUDIO .NET 2011 (Beta) > ============================================================== > > 1> Extract the XERCES-C code base from the SVN repository. > > 2> Provide the Microsoft VS 2011 solution and project files in a > directory that can be directly included in the XERCES-C code base. > > 3> Build the core library and sample programs. > Evaluate the sample programs for issues. > > 4> Cleanup the unwanted side-effects found in the solution and > project files as the result of Visual Studio Upgrade. > > 5> Prepare zip files of the Microsoft VS 2011 directory elements > needed to patch the code base repository. > > 6> Post these patches to JIRA > > > UPGRADE XALAN-C TO USE WINDOWS VISUAL STUDIO .NET 2011 (Beta) > ============================================================= > > 1> Extract the XALAN-C code base from the SVN repository. > > 2> Provide the Microsoft VS 2011 solution and project files in a > directory that can be directly included in the XALAN-C code base. > > 3> Build the core library and sample programs. > Evaluate the sample programs for issues. > > 4> Cleanup the unwanted side-effects found in the solution and > project files as the result of Visual Studio Upgrade. > > 5> Prepare zip files of the Microsoft VS 2011 directory elements > needed to patch the code base repository. > > 6> Post these patches to JIRA > > AUTOMATED BUILDS OF FOR PACKAGE MANAGEMENT SYSTEMS > ================================================== > > __ Create Debian Linux packages > > __ Create Red Hat Linux packages > > __ Create Solaris UNIX packages > > __ Create BSD UNIX packages > > __ Create AIX UNIX packages > > __ Create Microsoft Installer packages > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: xalan-dev-unsubscr...@xml.apache.org > For additional commands, e-mail: xalan-dev-h...@xml.apache.org Michael Glavassevich XML Technologies and WAS Development IBM Toronto Lab E-mail: mrgla...@ca.ibm.com E-mail: mrgla...@apache.org
