why another PEAR channel? :)

Open
#3 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
18/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
drupal, php
Domain
api

Research direction

No source file, test, or entry point is named. Start by reviewing how FeatureServer relates to PEAR channels and the Drupal, Symfony, and Magento integrations mentioned; done would be a clear maintainer-approved explanation of why this channel approach was chosen.

Written by the indexing model from the issue text.

Description

Hello,

as far I see the feature server and pear channel having very close aim, but however the PEAR and it's channel server a bit more famous in php world(at least for me, because used it even before drupal) and have a some successful integration examples in others projects like Symfony or Magento I am curious is it were on radar when development of feature server began and why it's were not chosen?

I might be wrong, but would like to hear something back if it's so :)

Thank you!

Dominant language
PHP
Stars
46
Forks
14
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from developmentseed/FeatureServer

All issues in developmentseed/FeatureServer

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.