Home   Info   DevZone   Wiki   UsersWeb  |  MainWeb  |  InfoWeb  |  DevZoneWeb  |  SupportWeb
[ ProjectPackages ] [ not logged in ] [ Web: Imported ] goto:  options [ get info on or edit ] [ login or new user ] [ list of topics, hubs & nodes, or recent changes ]

Note that this is not a real working group, just an example.

PersonalWeb Package Hierarchy

• org.jos.PersonalWeb
  • hypermedia
  • wordprocessor
  • PIM
    • calendar
  • handheldcomputer (proposed)
  • presentation
  • security
  • server (proposed)
  • webstructures
    • wiki (proposed)
    • ring (proposed)
    • hierarchy (proposed)

The PersonalWeb Package

_ Package _ _ Description _ _ Subproject Web Page_ _ Contact _ _ Date _ org.jos.PersonalWeb A personal web for an individual, holding letters, journal entries, business, etc. none yet BradNeuberg 3JAN98 org.jos.PersonalWeb.hypermedia Provides hyperlinking resources for all PersonalWeb applications. none yet BradNeuberg 3JAN98 org.jos.PersonalWeb.wordprocessor Word processor focused on hypermedia text none yet BradNeuberg 3JAN98 org.jos.PersonalWeb.PIM Personal Information Manager built to work within PersonalWeb. none yet BradNeuberg 3JAN98 org.jos.PersonalWeb.wordprocessor.calendar Specific calendar functions for PIM none yet BradNeuberg 3JAN98 org.jos.PersonalWeb.handheldcomputer Synchronizes a smaller PersonalWeb on a hand held computer with a PC none yet BradNeuberg 3JAN98 org.jos.PersonalWeb.presentation Presentation portion of PersonalWeb software none yet BradNeuberg 3JAN98 org.jos.PersonalWeb.security Provides security for PersonalWeb nodes none yet BradNeuberg 3JAN98 org.jos.PersonalWeb.server A server to have a PersonalWeb structure exist over an entire network, not just one computer none yet BradNeuberg 3JAN98 org.jos.PersonalWeb.structures Framework for commonly-used web structures none yet BradNeuberg 3JAN98 org.jos.PersonalWeb.structures.wiki Provides a WikiWikiWeb type structure none yet BradNeuberg 3JAN98 org.jos.PersonalWeb.structures.ring Provides a ring-like web structure none yet BradNeuberg 3JAN98 org.jos.PersonalWeb.structures.hierarchy Provides a hierarchical web-based structure none yet BradNeuberg 3JAN98

Reserved Packages

_ Package _ _ Description _ _ Contact _   _ Date _ none yet none yet none yet none yet

How to Propose New Packages

1. Read the Namespace and Package Frequently Asked Questions (NamespacePackageFAQ)

1. Proposals for new packages must be announced to the appropriate mailing list for comment. The title of the e-mail should start with "Namespace: ". A proposal must include a charter that describes the scope and intent of the package.

1. Proposals may also be added to the Proposals section of the Packages wiki page.

1. A timeframe of at least 48 hours for comment and objections is required before the proposed package can be added to the Reserved section of the Packages wiki page.

1. The package being proposed must have a wiki page with a charter. The page may have any other relevant material, but the charter is essential.

1. The Reserved packages page will have a hierarchy of package names linked to the corresponding wiki page.

1. Comments/Concerns regarding a proposal should be voiced on the discussion list and not on a Wiki page. These comments should be replies to the proposal or to previous replies to the proposal, to keep related material in the same thread.
   • before this rule, you could previously comment at CommentOnPackages

How to Edit this Page

All new package names including root nodes, parent nodes, and leaf nodes must first be proposed by placing them in the Proposed list [I disagree with this; it's too beauracratic - BradNeuberg]. You must also add your package to the Package Hierarchy and mark it as (proposed).

Please keep the proposed list sorted on date (newest entries on top) and keep the rest sorted by package name. Omit the .* at the end of a package name.

Content of these pages are owned and copyrighted by the poster.
Hosted by: