The Task Force November Revolution seemed stalled so I (Jack) have usurped the role that I volunteered for. The revolution is dead; long live the king! At least until the revolution is revived.
SUnit for compatibility (VW, VA, and Smalltalk standard methods)
Update all comments
Work toward a consistent style
Make sure the existing Collections are completely documented and understandable
Begin collecting either in the code or on this Wiki oddities, refactoring candidates, new methods
submit those changes for approval
Decide next step
Suggested by Goran that we copy the Collections classes and work on the copy
This avoids having a protacted debate with Squeakers on every minor change we make
At some point the copy may be copied back and replace the original or we just offer a superior Collections suite
Jack would like to work on the original
I'd rather each of my changes becomes immediately useful to the community and don't want to work for a year on something that may be tossed if I don't finish it.
Comments welcome - note the attempt at recategorization
Future
Identify useful additional methods
Compatibility with other Smalltalks
Look for subclasses in standalone packages whose methods could be genealized and raised to Collection classes
Identify useful new Collections Abstract Data Types
Look in existing packages for collections which could be generalized and made generally available.
Documentation
Real documentation (A first for Squeak since the Blue Book?)
Collect or develop examples (beyond the SUnit tests)
Rules Jack would like to apply to how we make changes (up for discussion)
We will have working SUnit tests in place before undertaking any code change
We will fully comment all classes and methods
SUnit test will not be re-written to match code change - Any code changes must work with the exiting SUnit test (I don't want to break things that are working now)
Information related to Collections which we should be aware of:
