From 310d8d9fdd33826b9a6d5c1f9b1f8aa1c373c461 Mon Sep 17 00:00:00 2001 From: Juuso Lapinlampi Date: Sat, 30 Apr 2016 05:22:28 +0000 Subject: Remove bugs URL from package.json Why is this a thing? We never used pantsu/pomf issue tracking. It was disabled a long time ago in gogs, and now it doesn't even exist. For consideration, we could provide an email address here. There's no mailing list for bugs (yet) and it's unlikely to see one soon. Compliments commit bf4fbf5f8718c4668a57d7dc09880deb904fef1b. Inspired by ~alucard/pomf at Cuntflaps, though never reported to us. Reviewed-by: Eliot Whalan --- package.json | 3 --- 1 file changed, 3 deletions(-) (limited to 'package.json') diff --git a/package.json b/package.json index b1a2722..d8975e7 100644 --- a/package.json +++ b/package.json @@ -15,9 +15,6 @@ "Juuso Lapinlampi " ], "license": "MIT", - "bugs": { - "url": "https://git.pantsu.cat/pantsu/pomf/issues" - }, "devDependencies": { "grunt": "^0.4.1", "grunt-contrib-copy": "^0.8.2", -- cgit v1.2.3 From 2e6f6fc710535c22abfe5a90f8a5a0f042acd3ff Mon Sep 17 00:00:00 2001 From: Juuso Lapinlampi Date: Sat, 30 Apr 2016 05:53:38 +0000 Subject: Revert "Remove bugs URL from package.json", set email Actually on second thought, SemVer doesn't allow us to remove functionality without incrementing the major version number... which we don't want to do for this. Set the bugs email address to bugs@pantsu.cat. Hoping here bugs@ to be an alias to ewhal@ for the time being until a real mailing list will be reachable at that address. This fixes the issue for the time being without removing functionality. It is okay that we made a mistake. We don't need to increment the major version here now, because no release was tagged and released in this branch. Nevermind that Pomf isn't even published on NPM packages, so this "feature" is never seen in its current form in the npm(1) program. We'll still respect SemVer, for what little worth it may be to other tools. This reverts commit 310d8d9fdd33826b9a6d5c1f9b1f8aa1c373c461. Reviewed-by: Eliot Whalan --- package.json | 3 +++ 1 file changed, 3 insertions(+) (limited to 'package.json') diff --git a/package.json b/package.json index d8975e7..4cd5313 100644 --- a/package.json +++ b/package.json @@ -15,6 +15,9 @@ "Juuso Lapinlampi " ], "license": "MIT", + "bugs": { + "email": "bugs@pantsu.cat" + }, "devDependencies": { "grunt": "^0.4.1", "grunt-contrib-copy": "^0.8.2", -- cgit v1.2.3 From 36269146efd9bef78056acd20ae705ad4751392c Mon Sep 17 00:00:00 2001 From: Juuso Lapinlampi Date: Sat, 30 Apr 2016 06:30:58 +0000 Subject: package.json: Use lowercase pomf for package name One of NPM's rules [1] is: "New packages must not have uppercase letters in the name." This also follows the convention where Git repository names are lowercase. This change is mostly irrelevant to us, but it's a bug nonetheless. There's no concern over backwards compatibility regarding SemVer as far as I'm aware. This bug was introduced in 7d28ef53a8166cbdcb558a84d5a53cfd73472438. [1]: https://docs.npmjs.com/files/package.json Reviewed-by: Eliot Whalan --- package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'package.json') diff --git a/package.json b/package.json index 4cd5313..007976c 100644 --- a/package.json +++ b/package.json @@ -1,5 +1,5 @@ { - "name": "Pomf", + "name": "pomf", "version": "2.0.1", "description": "Kawaii file host", "homepage": "https://pantsu.cat/", -- cgit v1.2.3