"Junior Jobs"?

I took a minute to go through the bugs on sourceforge and pick out some of the less-involved ones that would be better suited for someone who is just getting into c++/qt/etc. Mostly GUI-related issues and some minor projects suitable for beginners. I’ve seen this discussed on the list earlier, would anyone object to me labeling these bugs as junior jobs? I was planning on following the b.k.o convention of prefixing “JJ:” to these bugs:

vibrations: Replace Cancel/OK buttons with Close?
https://sourceforge.net/tracker/?func=detail&aid=2728368&group_id=165310&atid=835077

vibrations: Triggering Force engine does not trigger vector
https://sourceforge.net/tracker/?func=detail&aid=2728372&group_id=165310&atid=835077

vibrations: list of frequencies not sorted
https://sourceforge.net/tracker/?func=detail&aid=2734399&group_id=165310&atid=835077

vibrations: Scale slider misbehaving
https://sourceforge.net/tracker/?func=detail&aid=2728345&group_id=165310&atid=835077

GAMESS input: symmetry issue
https://sourceforge.net/tracker/?func=detail&aid=2712161&group_id=165310&atid=835077

Windows fragment dialog is list, not tree
https://sourceforge.net/tracker/?func=detail&aid=2663883&group_id=165310&atid=835077

Dave

On Apr 7, 2009, at 6:05 PM, David Lonie wrote:

I took a minute to go through the bugs on sourceforge and pick out
some of the less-involved ones that would be better suited for
someone who is just getting into c++/qt/etc.

These are all good ideas. I also see a few on the Feature tracker:
2624401 AutoOpt needs “Best Available”

2597403 Avogadro should optionally display the full path of the file

2459727 Check for new updated version

2436162 Export Multiple Conformers to Multiple Files

1976211 Display E in window

1919987 Get molecules from web (or from PDB)

1850602 Eyecandy::drawZoom should use drawCone

From the TODO list:

  • Write tutorials for the Wiki
  • Addition of context tooltips to tools, engines, etc.
  • Add a menu to access tools not available in the toolbar.
  • Run through the Krazy results to find errors/warnings and fix them
  • Find poorly documented classes from the API docs and ask about them:
    Avogadro: Avogadro API Documentation

Simple plugins are also useful. I particularly like writing Color
plugins, and now they can have preferences.

Another useful “junior job” is to update some of the contributed code.
I have bits for constraining optimizations to planes, and creating
supercells which can be updated.

And of course getting things like this onto the wiki is a very useful
contribution. Right now, I’m hoping to get through the end of the
semester (and grading) and life will be better. :slight_smile:

Cheers,
-Geoff