René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Is the proposal issue necessary or not?","articleBody":"The README [mentions](https://github.com/java/devjava-content#content-proposal):\r\n\u003e All content must start with a `Content Proposal`. This will be in the form of a GitHub issue using the `Content Proposal` issue template.\r\n\r\nand it differentiates from requests as it seems to expect a `[requested]` issue before that:\r\n\u003e Look through the [requested](https://github.com/java/devjava-content/labels/requested) issues and find something that you feel uniquely capable of writing\r\n\r\nThis also seems to be strengthened by the [`Content Proposal` issue template](https://github.com/java/devjava-content/blob/main/.github/ISSUE_TEMPLATE/content-proposal.yaml) which expects a `Request Issue`.\r\n\r\nHowever, it seems that the `[approved]` label is typically put on accepted content requests (at least after this repo was opened for Community Contributions).  \r\nFurthermore, both #45 and #49 didn't seem to need a proposal issue, the request (followed by the future author being assigned to it) seemed to be sufficient.\r\n\r\nTherefore, I propose to remove the distinction between content proposals. I would suggest to:\r\n- Add an issue template for requests (or remove the `Request Issue` field from the `Content Proposal` template).\r\n- Create a Pull Request template from the current `Content Proposal` template since it makes sense for PRs to mention the request issue (and all other fields from there).\r\n- Clean up the tags so only the tags actually being used are listed. For example, I haven't seen any usage of the `[in progress]` label.\r\n- Adapt the README to reflect this workflow.","author":{"url":"https://github.com/danthe1st","@type":"Person","name":"danthe1st"},"datePublished":"2023-11-06T21:01:16.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/58/devjava-content/issues/58"}