1 / 48

uPortal Documentation Roadmap

uPortal Documentation Roadmap. John Fereira, Cornell University Andrew Petro, Yale University. Official web site JA-SIG Wiki Mailing lists Jira Issue Tracking system Future of uPortal Documentation How you can contribute. Overview. URL: http://www.uportal.org

nadine-morse
Télécharger la présentation

uPortal Documentation Roadmap

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. uPortal Documentation Roadmap John Fereira, Cornell University Andrew Petro, Yale University

  2. Official web site JA-SIG Wiki Mailing lists Jira Issue Tracking system Future of uPortal Documentation How you can contribute Overview

  3. URL: http://www.uportal.org See also: http://www.ja-sig.org demo Official uPortal Website

  4. Official uPortal Website (cont.)

  5. Official uPortal Website (cont.)

  6. Official uPortal Website (cont.)

  7. Official uPortal Website (cont.)

  8. Official uPortal Website (cont.)

  9. Official uPortal Website (cont.)

  10. Official uPortal Website (cont.)

  11. Official uPortal Website (cont.)

  12. Main docs page: http://www.uportal.org/docs.html Roles: http://www.uportal.org/roles.html Administrator pages: http://www.uportal.org/administrators/index.html Implementation pages: http://www.uportal.org/implementors/index.html Developer pages: http://www.uportal.org/developers/index.html User/Subscriber pages: http://www.uportal.org/users/index.html Meetings: http://www.uportal.org/meetings/index.html Release notes: http://www.uportal.org/release/notes.html Additional links: http://www.uportal.org/additional.html Link to Wiki: http://jasigch.princeton.edu:9000/ Official uPortal Website links

  13. URL: http://jasigch.princeton.edu:9000 Open to anyone Spaces Integrated with Issue Tracking System Demo uPortal Wiki

  14. uPortal Wiki

  15. uPortal Wiki

  16. uPortal Wiki

  17. uPortal Wiki

  18. uPortal Wiki

  19. uPortal Wiki

  20. uPortal Wiki

  21. uPortal Wiki

  22. jasig-announce@unm.edu Low traffic Open membership uPortal releases, conferences, training classes Archive: https://list.unm.edu/cgi-bin/wa?A0=jasig-announce jasig-portal@unm.edu High traffic Open membership Discuss anything related to uPortal Archive: https://list.unm.edu/cgi-bin/wa?A0=jasig-portal jasig-dev@unm.edu Medium traffic Membership restricted to uPortal framework developers Coordination of development work Archive: https://list.unm.edu/cgi-bin/wa?A0=jasig-dev uPortal Mailing Lists

  23. Move old, obsolete documentation to wiki (uPortal 1) Migrate content developed on wiki to main site Capture more mailing list content on wiki Documentation in xml (Anakia) http://jasigch.princeton.edu/uportaltest/index.html Future of uPortal Documentation

  24. http://jasigch.princeton.edu:9000/jira uPortal Issue Tracking System

  25. Commercial product free to our open-source project Java web application hosted on Clearinghouse machine Successor to our Bugzilla What is JIRA?

  26. Issues are a superset of Bugs Bugs New Features Improvements Tasks

  27. Documenting Known Issues

  28. Change Logs / Release Notes

  29. Planning future releases

  30. Understanding Risk / Obstacles

  31. Developers take issues, becoming Assignees. Assignees are responsible for resolving the issue. They “start progress” on an issue to indicate actively working on it. Once they think it’s resolved, they mark it resolved. Assignees

  32. Submitting an issue

  33. Select project and issue type

  34. Summarize, Categorize

  35. Describe

  36. Reporters have an important role

  37. Comment

  38. CVS Integration and patching

  39. Speaking of Patches

  40. Vote?

  41. Our issue tracking and reporting is only as good as its data You can help by reporting issues Keeping “affects version” metadata correct Drawing attention to important issues we’re overlooking Commenting, adding your insight Posting patches Help track issues

  42. Contribute to the Wiki

  43. Perhaps start with…

  44. Wikis are all about collaborative editing There’s built in versioning and rollback So please feel welcome to edit But you can also post comments Even if you’re not ready to edit…

  45. Notice something outdated, something to fix, something confusing? Open an issue Post a patch Committer? Edit the CVS. Instant gratification. uPortal documentation has an issue tracking space in JIRA. Contribute to the static website

  46. We aspire to be Friendly Welcoming Mutually supportive You have experiences, answers to share Help on the mailing lists

  47. Help Harvest from the Lists Email: Pros: Threaded discussion Freeform Flexible Cons: Becomes “stale” very quickly Not easily updateable, editable Scrolls off the top of our inboxes to be forgotten Tracking concrete issue tokens Capture the “final answer” – and able to update when the final answer Changes.

  48. Speakers: John Fereira and Andrew Petro Track: New Concepts Presentation Title: uPortal Documentation Roadmap Date: 06/14/2005 Time: 2:00 PM – 3:00 PM The End Questions ? Speaker Evaluation Info:

More Related