Hello Michael,

thank you for your interest in JSPWiki :-) Some tasks that come quick to
mind:
- the haddock template is not 100% complete yet
- new skins for default template
- new page providers (f.ex. subversion-based page provider, obfuscated page
provider), plugins (display math equations, f.ex) or filters
- export pages to pdfs
- given a "root" page, the ability to build either a pdf book or an epub one
- increasing our unit test suite, migrate it to JUnit 4, use mocks to
reduce build time instead of build TestWikiEngines
- complete the integration test suite (or rewrite using another tool)
- some translations are missing resources
- oauth login
- serialize workflows
- tools to import pages from other wikis
probably not fitting on a two weeks span, but worth looking at:
- refactor the code to reduce the package cycles
- introduce a dependency injection container
- make the markup parser pluggable (so jspwiki could be able to understand
other wiki syntaxes, like, f.ex. markdown)

I'm also cc'ing our dev list so anyone with features in mind can provide
more ideas.

In any case, whatever your students end up with, I'd encourage them to
subscribe to the dev list, ask there whatever they need, and of course
attach patches of their work so it can be reviewed/incorporated on current
trunk. Also, if they could document their work at jspwiki-wiki.apache.org
that be wonderful too.


HTH,
juan pablo


On Tue, Feb 2, 2016 at 3:43 PM, Sale, Michael <ms...@stonehill.edu> wrote:

> Good Morning Juan Pablo
>
>
>
> I know this is email is quite out of the blue but I hope it finds you well.
> I am a faculty member at Stonehill College in Easton, Massachusetts, USA
> and I am teaching a computer science senior seminar course.  The main focus
> of this course is making changes to legacy software or software that a
> developer has never worked with before.  JSPWiki is the system we are using
> as a code base for the semester and the students will be tasked with adding
> features, changing functionality, and fixing bugs in the program.
>
>
> I am emailing you because you seem to be the one of the project leaders on
> this Apache project and I wanted to ask you a favor that would greatly
> assist me.
>
>
> I am looking for about 5 or 6 non-trivial maintenance tasks that the
> JSPWiki community is looking to have completed in the software.  I looked
> at the issues database but wanted to touch base with you.  I am looking for
> new features, improvements to current features, and bug fixes in the
> system.  We have the source code for the latest release.
>
>
> It is important to the instructors that these tasks are non-trivial.  What
> I mean by that is that the changes required will most-likely affect many
> classes in the system and will take some “code learning and discovery” to
> effectively make the change.  One of the main focuses of the project is how
> to figure out what classes will need to be changed and how a change should
> be made responsibly.  Their iterations are 2 weeks long, so tasks that can
> fit in that time frame would be wonderful.
>
>
> Again, I know this email is out of the blue, but I’d really appreciate any
> help or guidance you can provide.
>
>
> Have a wonderful day.
>
>
> Respectfully,
>
> Mike Salé
>
>
>
>
>
> --
>
> Michael J. Salé
>
> Asst. Professor of Management
>
> Management Information Systems Program Director
>
> Business Administration
>
> Stonehill College
>
>
>
> Email: ms...@stonehill.edu
>
> Phone: 508.565.5629
>
> Office: Stanger Hall 102
> Office Hours: M 4-5pm, T 1-2pm, R 1-2pm, F 1-2pm
>
>
>

Reply via email to