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

The 'Report new issue on github' link is faulty #19

Open
johanneskonst opened this issue Dec 21, 2011 · 4 comments
Open

The 'Report new issue on github' link is faulty #19

johanneskonst opened this issue Dec 21, 2011 · 4 comments

Comments

@johanneskonst
Copy link

On page http://pear2.php.net/PEAR2_Pyrus the link to report a new issue is faulty, should be changed to https://github.com/pyrus/Pyrus/issues/new

Regards,

@gauthierm
Copy link
Contributor

Hmm.. you're right. This is broken because there is no database on the pear2.php.net website so some assumptions are made about packages--namely that they are all hosted in the pear2 project.

To fix, a database layer will have to be added containing meta information about packages. Adding a database is intended at some point anyway to enable ratings and stats tracking.

Brett, is there anywhere in the pear2 package.xml spec where bug URLs can be specified?

@saltybeagle
Copy link
Member

This is just an issue with the Pyrus packages, which are moving to pyrus.net. The idea is that these packages will no longer be hosted on the pear2 org account, nor the pear2.php.net channel — right now we're in a transition phase so the Pyrus packages have incorrect links at the moment.

@boenrobot
Copy link
Member

I have to ask... why is this separation necesary? From a user's point of view, it looks like an overkill.

e.g. are the PEAR2 dev tools going to be in pyrus.net or pear2.php.net? With two sites, this is easily going to get confusing.

Is the long term plan to completely abstract away the installer from the protocol/channel or what?

@saltybeagle
Copy link
Member

The idea is that these tools are for all of PHP, not just PEAR. By moving them to a PEAR-agnostic domain name we're trying to emphasize that fact.

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

No branches or pull requests

4 participants