Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Services Directory Feature Request List"
Line 2: | Line 2: | ||
=== Notes from Feb 9th call === | === Notes from Feb 9th call === | ||
− | Mike Taylor, Nathan | + | Mike Taylor, Todd Williams, Riyad, Todd Williams, Nathan |
* Suggestion to name tab something than "Services" - i.e., "Consult/Train" | * Suggestion to name tab something than "Services" - i.e., "Consult/Train" | ||
** Maybe have two tabs - 1 for Consulting, 1 for Training | ** Maybe have two tabs - 1 for Consulting, 1 for Training | ||
** Promote members on services just like we do with plugins | ** Promote members on services just like we do with plugins | ||
− | * Link to the new membership pages when they go online | + | * Link to/from the new membership pages when they go online |
* Technolgy Segemention is lower priority - let's see how many companies list first | * Technolgy Segemention is lower priority - let's see how many companies list first | ||
+ | * Link the Category pages on eclipse.org with Services, just like plugins | ||
+ | |||
== High Priority == | == High Priority == | ||
* Prominant linkage to services from main EPIC Page. | * Prominant linkage to services from main EPIC Page. | ||
* Categorization by "services type" AND technology segments serviced | * Categorization by "services type" AND technology segments serviced | ||
− | + | * Services Types: | |
− | + | ** Training | |
− | + | ** Consulting | |
* Fields in the listing | * Fields in the listing | ||
** Title (short Description of Service) | ** Title (short Description of Service) | ||
Line 26: | Line 28: | ||
== Medium Priority == | == Medium Priority == | ||
− | + | ||
== Low Priority == | == Low Priority == | ||
* Currently the best implementation path is to have an entry for each service type offered. For example, 1 entry for training, 1 for consulting. Perhaps at some point these could be linked and a company offering multiple services could list both in the same entry. | * Currently the best implementation path is to have an entry for each service type offered. For example, 1 entry for training, 1 for consulting. Perhaps at some point these could be linked and a company offering multiple services could list both in the same entry. | ||
+ | * Ability to classify and sort/find by geographic regions served | ||
* Technology Subgroup within the | * Technology Subgroup within the | ||
** RCP | ** RCP |
Latest revision as of 14:37, 9 February 2007
EPIC Services Page Feature Requests.
Notes from Feb 9th call
Mike Taylor, Todd Williams, Riyad, Todd Williams, Nathan
- Suggestion to name tab something than "Services" - i.e., "Consult/Train"
- Maybe have two tabs - 1 for Consulting, 1 for Training
- Promote members on services just like we do with plugins
- Link to/from the new membership pages when they go online
- Technolgy Segemention is lower priority - let's see how many companies list first
- Link the Category pages on eclipse.org with Services, just like plugins
High Priority
- Prominant linkage to services from main EPIC Page.
- Categorization by "services type" AND technology segments serviced
- Services Types:
- Training
- Consulting
- Fields in the listing
- Title (short Description of Service)
- URL
- Contact URL
- Long Descrption
- Company Name and background
- Location
- Graphic/Logo
- Member Company tag
Medium Priority
Low Priority
- Currently the best implementation path is to have an entry for each service type offered. For example, 1 entry for training, 1 for consulting. Perhaps at some point these could be linked and a company offering multiple services could list both in the same entry.
- Ability to classify and sort/find by geographic regions served
- Technology Subgroup within the
- RCP
- IDE
- Modeling
- Embedded
- GUI