rev. 9/23/96 Scopus bug tracking system - investigate... rev. 4/23/96 some porting projects you might help with (talk to Jonathon) (most run on dec, need to be rebuilt and tested under solaris 2.4) - discuss - eos - modem - nfs (TALK TO DIANE AND WDC!) - olc - xterm Subject: Work Ideas You should set yourself a schedule, with specific pieces you expect to accomplish each week (or more often). You can have your partners in crime go over the schedule, you can ask me to look at it, and you can certainly adjust as you find that creating the world takes a little more than an afternoon, but it is helpful to set such a schedule. My belief is that the pc, mac, and kerberos folks know what they are working on. That just leaves the UNIX people hanging. Please report accomplishments to milestones@mit.edu and have fun! it's only a project, after all. UROP Type Projects 1. neos servers port to solaris 2. version server port to solaris (jyp investigating) 3. discuss server port to solaris 4. review bugtracking packages 5. build netprob for SGI (cat investigating) 6. check other lockers--see if they have SGI versions--if not, consider building For those who may not know- I maintain a list of "significant Athena software packages" in file what_runs_where at the top level of the info locker- you can use it to quickly check on what's there now. Note that it does not cover everything that might be out there - it's oriented towards end-users and may miss lockers that contain developer tools and things mostly of interest to staff. And give me a holler if a) you find something wrong or b) feel that I'm missing something that ought to be there (given the end-user focus). Alexp 7. check other lockers--see if they have Sol 2.4 versions--if not, consider checking operation and rebuilding where needed 8. pick an athena source package. build it. study the sources. document the following four scenarios a. a bug has been reported--what does someone need to know to find and fix? b. we are moving the package to a new OS--what do you need to know? c. we are implementing an enhancement--what do we need to know? d. what changes, improvements, etc. do you recommend for future planning? consider architecture diagrams, protocol specs, and other documentation-- suppose you came back to the package in a year and had to quickly get familiar again, what do you need? 9. Figure out TRACK--why does it thrash? 10. investigate and if necessary implement library/daemon/etc. for simple network time protocol 11. There's always bugs in netprob to do... Bug Sqashing a. get familiar with xnetprob/netprob b. read through the list c. sqish 12. Or you could dig through suggest and the olc logs and see what's there... 13. kerberized lpc (see matt) 14. kerberized lert admin tools 15. GUI tools a. read the software engineering FAQ on Portable GUI builders b. take a look at the magazines and see what they recommend c. pick up a few d. code equal prototypes in several e. recommend one (or more) tools for DCNS 16. personal "web checker" go to url, see if it changed, if so, show or ask owner? should allow customized time between checks should allow customized order of checking let the user start/restart without losing the key here is probably the user interface. note: web stuff gives dates of last mod, so the network side of this can be done reasonably easily. Received: from PACIFIC-CARRIER-ANNEX.MIT.EDU by po8.MIT.EDU (5.61/4.7) id AA10226; Mon, 1 Apr 96 09:18:25 EST Received: from CASCADE.MIT.EDU by MIT.EDU with SMTP id AA23487; Mon, 1 Apr 96 09:18:22 EST From: sao@MIT.EDU Received: by cascade.MIT.EDU (5.57/4.7) id AA15120; Mon, 1 Apr 96 09:19:14 -0500 Message-Id: <9604011419.AA15120@cascade.MIT.EDU> To: Jonathon Weiss Cc: moties@MIT.EDU, sao@MIT.EDU Subject: Re: Jonathon Weiss: UROP hiring schedule In-Reply-To: Your message of "Fri, 29 Mar 1996 20:11:07 EST." <199603300111.UAA00384@the-other-woman.MIT.EDU> Date: Mon, 01 Apr 1996 09:19:13 EST Hi, Jonathon! Thanks for taking the lead on this. I've got several potential UROP projects, mostly in the lottery space: -Modifications to PE and HASS-D client and server code so that students can view their assignments using the same application they used to make their choices. (enroll/xenroll or phedu/xphedu) (Requires C and Unix shell script skills.) -Revision of the internal lottery algorithm used for the freshman housing lottery. (Requires C skills. Some Mac experience preferable.) -"operationalization" of the system used to send out bulk PGP-signed freshman fifth-week-flag messages. (Actually, we may want to consider if this is an appropriate UROP project or not) (Requires Unix shell script skills. Some PGP preferable) Keep me posted... :Andy Received: from SOUTH-STATION-ANNEX.MIT.EDU by po8.MIT.EDU (5.61/4.7) id AA23405; Sat, 30 Mar 96 08:58:26 EST Received: from GREEN-ACRES.MIT.EDU by MIT.EDU with SMTP id AA09943; Sat, 30 Mar 96 08:58:25 EST Received: by green-acres.MIT.EDU (5.0/4.7) id AA29881; Sat, 30 Mar 1996 08:59:18 -0500 Message-Id: <9603301359.AA29881@green-acres.MIT.EDU> To: moties@MIT.EDU, jweiss@MIT.EDU Cc: delgado@MIT.EDU Subject: urop work Date: Sat, 30 Mar 1996 08:59:17 EST From: Diane Delgado Content-Length: 1798 UROP For the ABS Project Proposal Implement an improved user-interface which will help Administrators and Operators use the ABS more easily. This project is broken down into serveral phases, each of which can be implemented separately. Ideally we would expect to have item (1) accomplished and the other items are optional, depending opon the time and the skill of the person assigned to the task. 1. Implement simple ascii screen-based client for operators Consists of implements the following family of functions from the ABS API: Manage Devices (add, delete, show, modify) Manage Tapes (add, delete, show) Manage Jobs (show, cancel, delete) Perform Dump These groups are disjoint, so if the UROP is only able to complete say the first 2, this is a big help. 2. Implement operator GUI with the operations listed in (1). The UROP can be creative here by adding things like graphing the percentage of volumes completed for dumps, etc. 3. There is work available to do the same for the Administrator's client, but I will be realistic and assume that the student probably won't get this far. The ABS is a well-documented system and our team performs code reviews, so we would expect to conduct a review of the student's code for his benefit and ours. This is a good oportunity for a student to work in a more structured development environment and to gain exposure to technologies such as ONC RPC which are used in industry. Also, we are working with Brian (the customer) during the next month to prototype a screen oriented interface, so we expect to have a visual model for the student to use by the time he is ready to begin work. NEW IDEA!!! do a "mime mailcap editor" which lets people interactively and sensibly diddle their mailcap files... investigate, compare/contrast, and analyze the mailcap, mhn-profile, mime-types, etc. in use by netscape, mhn, metamail, pine, etc. design and defend a common solution (if feasible) or lay out some kind of manageable approach to this problem. if time permits, implement tools for managing the problem!