Add Issues in PEAR repository and after it, detach the fork from upstream to have main code

[Neustradamus]

Dear @pear team, @jparise, and current contributors: @ashnazg, @CloCkWeRX, @troymccabe, @kenguest, @cweiske, @mj, @till, @Jehan,

In first, I wish you a Happy New Year 2024!

It is possible to add "Issues" section into the pear source repository?

• https://github.com/pear/XML_Parser2

Can you detach the upstream repository from the original place: https://github.com/CloCkWeRX/XML_Parser2?

• https://support.github.com/contact?tags=rr-forks

The goal is to have the main source code in PEAR organization like, for example:

• https://github.com/pear/Auth_SASL

Thanks in advance.

PS: If @CloCkWeRX removes this repository, it will be directly good about the second part.

[ashnazg]

I've made the request to have this pear repo detached from @CloCkWeRX 's repo, which will make the pear repo the top parent.

[ashnazg]

I've also added Issues here.

[Neustradamus]

@ashnazg: Thanks a lot!
Can you do the same request for https://github.com/pear/Auth_SASL2?

[ashnazg]

Submitted the fork detachment request for Auth_SASL2 too.

[Neustradamus]

@ashnazg: Thanks a lot!

Can you look others at the same time?

There are others (no changes in upstream if I have looked correctly):

• https://github.com/pear/Services_UseKetchup (to unarchive too)
• https://github.com/pear/openid
• https://github.com/pear/HTTP_OAuth
• https://github.com/pear/PHP_LexerGenerator
• https://github.com/pear/Savant3
• https://github.com/pear/Services_ProjectHoneyPot
• https://github.com/pear/Payment_PagamentoCerto

---

https://github.com/pear/PHP_CodeSniffer
About upstream: squizlabs/PHP_CodeSniffer#3932

---

It will be nice to add upstream changes?

https://github.com/pear/HTTP_Upload
1 diff on upstream: pear/HTTP_Upload@master...erj1:HTTP_Upload:master

https://github.com/pear/PEAR_PackageFileManager_Git
7 diffs on upstream pear/PEAR_PackageFileManager_Git@master...armen:PEAR_PackageFileManager_Git:master

https://github.com/pear/HTTP_Header2 (please look)
5 diffs on upstream pear/HTTP_Header2@master...pear:HTTP_Header:master

https://github.com/pear/PHP_Beautifier
25 diffs on upstream pear/PHP_Beautifier@master...clbustos:PHP_Beautifier:master
-> https://github.com/clbustos/PHP_Beautifier/issues

[till]

What's the nature of these requests?

[till]

@ashnazg I think that "guy" is some kind of bot.

He's been pestering me about fixing something in some code I archived for months.

If you look at his socials, that's all he does. Except for reposting rss feeds.

[Neustradamus]

@till: I am not a bot...

You have archived your repository because I have requested to add "Issues" section...

[till]

@till: I am not a bot...

You have archived your repository because I have requested to add "Issues" section...

As I explained to you before, I have archived it because it's a service wrapper for a web service that no longer exists.

It does not make sense to address your nitpicks in code that cannot be used anymore.

We do open source in our spare time and your nagging is not helpful nor does it motivate anybody. Especially when it doesn't address any issues.

Please acknowledge that you understand.

[Neustradamus]

Good news, two have been detached :)

• https://github.com/pear/XML_Parser2
• https://github.com/pear/Auth_SASL2

Thanks @ashnazg!

@till: No problem about the service is no longer exists.
But it is possible to detach to have the main place here, and archived after?

[till]

@till: No problem about the service is no longer exists.

But it is possible to detach to have the main place here, and archived after?

Again, what is the significance?

[Neustradamus]

@till: The main code in PEAR and after in personal repository, not inversed.

@ashnazg: Can you look? (It is easy to do for):

• https://github.com/pear/openid
• https://github.com/pear/HTTP_OAuth
• https://github.com/pear/PHP_LexerGenerator
• https://github.com/pear/Savant3
• https://github.com/pear/Services_ProjectHoneyPot
• https://github.com/pear/Payment_PagamentoCerto

There is a v1 and v2 on PEAR (like for example Auth_SASL/Auth_SASL2) but it is attached:

• https://github.com/pear/HTTP_Header2

After, it is needed to check an update from upstream for:

• https://github.com/pear/HTTP_Upload
• https://github.com/pear/PEAR_PackageFileManager_Git
• https://github.com/pear/PHP_Beautifier