Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

added tags.yaml #61

Merged
merged 1 commit into from
Apr 27, 2016
Merged

added tags.yaml #61

merged 1 commit into from
Apr 27, 2016

Conversation

sanchojaf
Copy link
Contributor

No description provided.

video:
title: 'Video'
description: 'Video'

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sanchojaf Little bit pedantic but please remove empty line.

@IvanGoncharov
Copy link
Member

@MikeRalphson @bobby-brennan @RomanGotsiy @mittsh @oliver-xapix-io @darklynx
Please review these list.
But attach your comments only to the line in question, this allow discussing each tag separately.

description: 'Jobs'
lead_generation:
title: 'Lead Generation'
description: 'Lead_Generation'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Underscore here

@sanchojaf
Copy link
Contributor Author

Here others tags used for classified APIs

  • Affiliate
  • Annotation
  • API Management
  • Application
  • Art
  • Artificial Intelligence
  • Audio
  • Audio Transcription
  • Auth
  • Authentication
  • Auto
  • Automobile
  • Badge
  • Banking
  • Barcode
  • Business Intelligence
  • Car
  • City
  • Clothing
  • Cloud
  • Cloud Computing
  • Commerce
  • Compute
  • Container
  • Content
  • Creative
  • Currency
  • Data
  • Delivery
  • Diagram
  • Dictionary
  • Domain
  • Drink
  • Employment
  • Energy
  • Environment
  • Federal
  • Food
  • Forum
  • Gaming
  • Geo
  • Government
  • Healthcare
  • Hiring
  • Identity
  • Image Conversion
  • Image
  • Information
  • Insurance
  • Integration
  • Invoicing
  • Legal
  • Library
  • Local News
  • Machine Learning
  • Mapping
  • Media
  • Monitoring
  • Music
  • Network
  • News
  • People
  • Platform
  • Product
  • Profile
  • Publishing
  • Push Notifications
  • Research
  • Retail
  • Sales
  • Scheduling
  • Science
  • Scraping
  • Security
  • Shipping
  • SMS
  • Sports
  • Spreadsheet
  • State
  • Support
  • Task
  • Television
  • Testing
  • Ticket
  • Translate
  • Transportation
  • Travel
  • University
  • Visualization
  • Voice

Any consideration for evaluate if we added or not?

@IvanGoncharov
Copy link
Member

@sanchojaf Let's not over do. I think it does not make sense present user with more than 50 tags.
IMHO, all tags should be seen on one screen + user shouldn't be bored reading them to the end.

Your initial commit has ~70 so it's already too much and adding more doesn't help to solve the problem.
If you come up with some alternatives which are more generic it would be helpful.
For e.g. Phone & SMS => Communication, and similar things.

@sanchojaf
Copy link
Contributor Author

@IvanGoncharov, make sense for me.

@RomanHotsiy
Copy link
Member

RomanHotsiy commented Apr 20, 2016

Any consideration for evaluate if we added or not?

I've looked through the list you've already provided and I believe we shouldn't add more tags there.

Your initial commit has ~70 so it's already too much

Totally agree, If consider the use case of presenting this list somewhere (e.g. in menu) then even 50 is too much. Maybe we can shrink this list down to ~30-40 tags?
There are groups of very similar tags in your commit that from my point of view should be joined together:
(this is not full list, just things I could notify quick)

  • Accounting, Billing, Financial, Ecommerce, Payment Processing -> Payment or eCommerce
  • Continuous Integration, Code Review, Developer Tools -> Developer Tools
  • Advertising, Marketing -> Marketing
  • Issue Tracking, Error tracking -> Issue Tracking
  • Help Desk, Customer support -> Customer support
  • Chat, Messaging -> Messaging
  • Telephony, Phone -> Telephony,
  • Server Monitoring, Monitoring -> Monitoring

There are a few tags that can be created from others, e.g.:

  • Email marketing = Marketing + Email
  • Cloud storage = Cloud Platform + Storage

We will have keywords to cover things that won't be covered by tags.

@sanchojaf what do you think?

@sanchojaf
Copy link
Contributor Author

@RomanGotsiy I like all your suggestions +1,

only I have doubt with first group:

  • Accounting, Billing, Financial, Ecommerce, Payment Processing -> Payment or eCommerce

I propose the next for the this case :

  • Accounting, Billing, Financial -> Financial
  • eCommerce (keep for marketplace or others store apis)
  • Payment Processing -> Payment

@darklynx
Copy link

+1 to simplify Payment Processing => Payment

@darklynx
Copy link

darklynx commented Apr 20, 2016

btw, are there RESTful APIs for Storage that are not cloud? :) (skipping the difference between public and private clouds)

@RomanHotsiy
Copy link
Member

RomanHotsiy commented Apr 20, 2016

@sanchojaf
Agree about eCommerce

+1 to simplify Payment Processing => Payment

I would even join Payment to Financial

@darklynx
Copy link

darklynx commented Apr 20, 2016

If I understand correct "financial" is about online banking, finance management, personal finances which are B2C APIs, whereas "payment" APIs are usually targeting merchants and allow them to accept online / mobile / offline payments from their customers - typically B2B APIs. They seem to me as totally different groups of API, but of course they are about money and finances.

Also I'm not sure where the trading / conversion / stock APIs would be directed. If the goal is to minimize initial list, then "financial" probably should cover anything that is money/finances/currencies etc. related...

@sanchojaf
Copy link
Contributor Author

Hi,

Any general recommendation with current names?

  • singular vs plural? e.g: bookmarks, calendars, analytics, etc
  • avoid more that one word ? e.g: event_management, cloud_platform, file_management ..
  • change a word for a more general ? e.g: photo by image

Similar tags that should be joined together:

  • office | business | enterprise => business ?
  • developer_tools | tools => tools ?
  • project_management | issue_tracking | time_tracking => project_management ?

Thant is the current list that we have (~57):

  • accounting
  • analytics
  • backend
  • blogging
  • bookmarks
  • business
  • calendars
  • charting
  • cloud_platform
  • cms
  • collaboration
  • crm
  • customer_support
  • dashboard
  • database
  • developer_tools
  • digital_signature
  • ecommerce
  • education
  • email
  • enterprise
  • erp
  • event_management
  • file_management
  • financial
  • forms
  • hosting
  • iot
  • issue_tracking
  • jobs
  • lead_generation
  • location
  • marketing
  • messaging
  • mobile
  • monitoring
  • nlp
  • notifications
  • office
  • package_management
  • payment
  • personal_information_management
  • photos
  • project_management
  • real_estate
  • reference
  • search
  • sentiment_analysis
  • social
  • storage
  • surveys
  • telephony
  • time_tracking
  • tools
  • translation
  • version_control
  • video

@IvanGoncharov
Copy link
Member

IvanGoncharov commented Apr 21, 2016

Any general recommendation with current names?

@sanchojaf Idea is to create list which:

  • User could look at the tag and have some expectation of what inside. For example Reference doesn't meet this criterion.
  • Don't describe a finite set of APIs instead add more open-ended categories. For example Translation is too specific and same goes Sentiment Analysis. If start adding this level of granularity we will have a huge amount of tags. Instead categories like Text or Machine learning describe the same APIs and much more.
    • Amount of tags will grow through time some we should start from a smaller set. We can always add new tags but we can't delete existing ones.

@IvanGoncharov
Copy link
Member

singular vs plural? e.g: bookmarks, calendars, analytics, etc

I think it should be decided on per case basis. For example, bookmark don't make any sense. But at the same time, offices don't make any sense either.

avoid more that one word ? e.g: event_management, cloud_platform, file_management ..

Fully agree, but it should be recommendation not rule.

change a word for a more general ? e.g: photo by image

Yes, it should be the dominating rule. But I think we should go even more generic.
phone => image => media or media content
In the other case, what is the category for GIF animation like Coub for example?

Similar tags that should be joined together:

office | business | enterprise => business ?

IMHO business is bad name, when I hear it I don't

developer_tools | tools => tools ?

I think it's too much, developer tools is generic enough.
Fully abstract categories like tools should be used only as last resort, If nothing else apply.

project_management | issue_tracking | time_tracking => project_management ?

👍

Thant is the current list that we have (~57):

@sanchojaf Please don't post list in this thread, this makes it hard to scroll/read.
You doing good job keeping PR in sync with disscussion 👍

description: 'Backend'
blogging:
title: 'Blogging'
description: 'Informational site published with discrete entries'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMHO, blogging is part of social

@oliver-xapix-io
Copy link
Contributor

I like your categorizations, folks! <3

@@ -0,0 +1,111 @@
accounting:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Merge with Financial?

@IvanGoncharov
Copy link
Member

@sanchojaf I don't like Managment it's too generic to be useful.
Instead, I propose to split managment into following:

  • Support + CRM part of Management => Customer relation
  • Calendars + Events + part of Managment => Time management
  • Project Managment

Everything else looks good 👍

@sanchojaf
Copy link
Contributor Author

@IvanGoncharov I agree,

but I think that 'Event management' is more general that 'Time management'.

Calendars + Events + part of Management => Event Management ?

@MikeRalphson
Copy link
Collaborator

@sanchojaf @IvanGoncharov 'Event Management' sounds like corporate events / wedding planning. +1 for 'Time Management' in this context.

@IvanGoncharov
Copy link
Member

I have exactly the same association as @MikeRalphson and Wikipedia agree with us:

Event management is the application of project management to the creation and development of large scale events such as festivals, conferences, ceremonies, formal parties, concerts, or conventions.

As for Time manegment Wikipedia says:

Time management is the act or process of planning and exercising conscious control over the amount of time spent on specific activities, especially to increase effectiveness, efficiency or productivity.

Which is also not ideal, but I can't think of anything better.

@sanchojaf
Copy link
Contributor Author

@IvanGoncharov @MikeRalphson agree, I added 'Time managment' tag.

@IvanGoncharov
Copy link
Member

@sanchojaf Please remove Calendars and Events.

@IvanGoncharov IvanGoncharov changed the title added tags.json added tags.yaml Apr 26, 2016
@IvanGoncharov
Copy link
Member

Everything else looks good for me.
@sanchojaf Could you please sqash all commits in one.
And let's wait untill tomorow to give other people time to review final version.

@sanchojaf
Copy link
Contributor Author

@IvanGoncharov done, sqashed all commits in one

@IvanGoncharov
Copy link
Member

@sanchojaf Thank you.

If anyone can show just cause why this PR cannot lawfully be merged into master, let them speak now or forever hold their peace

@IvanGoncharov IvanGoncharov merged commit 19b327e into APIs-guru:master Apr 27, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants