clarify PULL_REQUST_TEMPLATE.md & CONTRIBUTING.md #1291
No reviewers
Labels
No Label
🔍🤖 Search Engines
approved
dependencies
duplicate
feedback wanted
high priority
I2P
iOS
low priority
OS
Self-contained networks
Social media
stale
streaming
todo
Tor
WIP
wontfix
XMPP
[m]
₿ cryptocurrency
ℹ️ help wanted
↔️ file sharing
⚙️ web extensions
✨ enhancement
❌ software removal
💬 discussion
🤖 Android
🐛 bug
💢 conflicting
📝 correction
🆘 critical
📧 email
🔒 file encryption
📁 file storage
🦊 Firefox
💻 hardware
🌐 hosting
🏠 housekeeping
🔐 password managers
🧰 productivity tools
🔎 research required
🌐 Social News Aggregators
🆕 software suggestion
👥 team chat
🔒 VPN
🌐 website issue
🚫 Windows
👁️ browsers
🖊️ digital notebooks
🗄️ DNS
🗨️ instant messaging (im)
🇦🇶 translations
No Milestone
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: privacyguides/privacytools.io#1291
Loading…
Reference in New Issue
No description provided.
Delete Branch "pr-template"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Deploy preview for privacytools-io ready!
Built with commit ddeacef5ba70c463433973fcd8e1516a455d0918
https://deploy-preview-1291--privacytools-io.netlify.com
Deploy preview for privacytools-io ready!
Built with commit
33933f2f8b
https://deploy-preview-1291--privacytools-io.netlify.com
@ -1,19 +1,17 @@
<!-- PLEASE READ OUR CONTRIBUTING GUIDELINES (https://github.com/privacytoolsIO/privacytools.io/blob/master/.github/CONTRIBUTING.md) BEFORE SUBMITTING -->
<!-- PLEASE READ OUR CODE OF CONDUCT (https://github.com/privacytoolsIO/privacytools.io/blob/master/CODE_OF_CONDUCT.md) AND CONTRIBUTING GUIDELINES (https://github.com/privacytoolsIO/privacytools.io/blob/master/.github/CONTRIBUTING.md) BEFORE SUBMITTING -->
First hint that we do want the discussion issue to exist.
I may want to check that wiki page and if there is a better one.
oops. Anyway the previous formatting was very unhelpful in my opinion as it just went to issue page and forced me to use search as no one (me included) never changed the link.
and I think
The
fits here better thanThis
, even if there is probably no practical difference.@ -2,3 +1,4 @@
<!-- PLEASE READ OUR CODE OF CONDUCT (https://github.com/privacytoolsIO/privacytools.io/blob/master/CODE_OF_CONDUCT.md) AND CONTRIBUTING GUIDELINES (https://github.com/privacytoolsIO/privacytools.io/blob/master/.github/CONTRIBUTING.md) BEFORE SUBMITTING -->
## Description
Oh and I wonder if we should also mention CODE_OF_CONDUCT.md on the top, but if we get a project that is full of hate, I guess we can refer to it separately.
@ -15,3 +13,3 @@
- [ ] This project has an [associated discussion](https://github.com/privacytoolsIO/privacytools.io/issues).
- [ ] The project is [Free Libre](https://en.wikipedia.org/wiki/Free_software) and/or [Open Source](https://en.wikipedia.org/wiki/Open-source_software) Software
* Netlify preview for the mainly edited page: <!-- link or Non Applicable? Edit this in afterwards -->
I think this is more clear formatting.
We recently had a PR that listed the fork here.
Open source and free software are very overlapping, but open source is more inclusive and I think it's what we actually care about here instead of free software movement.
Example case: I remembered @blacklight447-ptio and @dawidpotocki discussing VeraCrypt recently as VeraCrypt is not free software, but is open source software.
I was discussing that TrueCrypt (from which VeraCrypt is forked) IS NOT Open Source.
It's not Open Source. Please read definition at https://opensource.org/osd and then read TrueCrypt license. For bonus points you can also read Free Software definition at https://www.gnu.org/philosophy/free-sw.html.
First thing in license and it already makes it not open source
According to current OSI president Simon Phipps:
From https://en.m.wikipedia.org/wiki/TrueCrypt
Do I understand correctly that that leaves two choices where to go with this PR?
And what do you think of the PR itself?
Wait, is the case of VeraCrypt even relevant to this PR other than my comment being incorrect in case of OSIs preference being heard? Is it just free software vs open source software? How about Free Libre Open Source Software?
Tbh, if you can read the source code, I call it open source, no matter what license.
I think everybody at this point in time knows what free/libre software is.
Perhaps replace
free software
with[free](https://www.gnu.org/philosophy/free-sw.html)/[libre software](https://www.wikipedia.org/wiki/Libre_software)
to create:Another common term is FLOSS but I personally prefer the term "free/libre".
I mostly agree with @blacklight447-ptio that open-source is too broad and doesn't get to the point of being able to read the software and remix the software.
Some suggestions 👍
@ -1,19 +1,17 @@
<!-- PLEASE READ OUR CONTRIBUTING GUIDELINES (https://github.com/privacytoolsIO/privacytools.io/blob/master/.github/CONTRIBUTING.md) BEFORE SUBMITTING -->
<!-- PLEASE READ OUR CODE OF CONDUCT (https://github.com/privacytoolsIO/privacytools.io/blob/master/CODE_OF_CONDUCT.md) AND CONTRIBUTING GUIDELINES (https://github.com/privacytoolsIO/privacytools.io/blob/master/.github/CONTRIBUTING.md) BEFORE SUBMITTING -->
I would probably tidy this up a bit to:
Is this somewhat redundant due to already having a "Resolves"? Could we remove this line in favor of having the "Resolves"?
@ -2,3 +1,4 @@
<!-- PLEASE READ OUR CODE OF CONDUCT (https://github.com/privacytoolsIO/privacytools.io/blob/master/CODE_OF_CONDUCT.md) AND CONTRIBUTING GUIDELINES (https://github.com/privacytoolsIO/privacytools.io/blob/master/.github/CONTRIBUTING.md) BEFORE SUBMITTING -->
## Description
Hmm, I'm not sure but it doesn't hurt to add it as a comment at the top as a reminder.
@ -1,19 +1,17 @@
<!-- PLEASE READ OUR CONTRIBUTING GUIDELINES (https://github.com/privacytoolsIO/privacytools.io/blob/master/.github/CONTRIBUTING.md) BEFORE SUBMITTING -->
<!-- PLEASE READ OUR CODE OF CONDUCT (https://github.com/privacytoolsIO/privacytools.io/blob/master/CODE_OF_CONDUCT.md) AND CONTRIBUTING GUIDELINES (https://github.com/privacytoolsIO/privacytools.io/blob/master/.github/CONTRIBUTING.md) BEFORE SUBMITTING -->
👍 I think I also need to clarify that discussion issue means software suggestion to distinguish it from discussions about news which we hoped to move to the forums.
I guess
@ -2,3 +1,4 @@
<!-- PLEASE READ OUR CODE OF CONDUCT (https://github.com/privacytoolsIO/privacytools.io/blob/master/CODE_OF_CONDUCT.md) AND CONTRIBUTING GUIDELINES (https://github.com/privacytoolsIO/privacytools.io/blob/master/.github/CONTRIBUTING.md) BEFORE SUBMITTING -->
## Description
👍
@privacytoolsIO/editorial What are your thoughts on the Open Source Software vs Free/Libre Software?
So currently the template states:
While the suggested change is:
From my observation of ptio, it seems like we aim for the software ptio suggests to be free/libre but also accept software that isn't "free" (apologies, I don't have examples at the moment, but I'm sure there are throughout the site). So the free/libre aspect seems to be our goal, not a requirement. If this is true, then the suggested change makes sense to implement and we could also expand it to something like this for clarity?
Why not just
oh, I forgot to comment these, but GItHub remembers
@ -1,19 +1,17 @@
<!-- PLEASE READ OUR CONTRIBUTING GUIDELINES (https://github.com/privacytoolsIO/privacytools.io/blob/master/.github/CONTRIBUTING.md) BEFORE SUBMITTING -->
<!-- PLEASE READ OUR CODE OF CONDUCT (https://github.com/privacytoolsIO/privacytools.io/blob/master/CODE_OF_CONDUCT.md) AND CONTRIBUTING GUIDELINES (https://github.com/privacytoolsIO/privacytools.io/blob/master/.github/CONTRIBUTING.md) BEFORE SUBMITTING -->
Sorry, I have to mess it up, because if there are multiple issues,
Resolves: #1, #2
closes only#1
.No, I seem to be simplifying it more due to the other thread where I remove mentioning on the issue.
It seems that this PR became wider than intented.
@ -8,2 +8,4 @@
- English only.
- Be constructive.
- Please feel free to *review changes* in the *files changed* tab of any
pull request at any time.
The only change I could do towards https://github.com/privacytoolsIO/privacytools.io/issues/1296, but I don't feel comfortable closing it in case there will be ideas and concensus for something more.
@ -9,1 +9,4 @@
- Be constructive.
- Please feel free to *review changes* in the *files changed* tab of any
pull request at any time.
- See also our [Code of Conduct](https://github.com/privacytoolsIO/privacytools.io/blob/master/CODE_OF_CONDUCT.md)
I think it should be mentioned together with "rules" which I would be comfortable removing entirely instead pointing only to it. We also don't have the "English only" documented anywhere else. Do we?
I didn't start removing things here as they are both mentioned.
I understand the priority to be that the source code can be seen.
aargh, spot a typo and make it more typo again
I understand the priority to be that the source code can be seen. However I am not sure if IMAP is OSS, isn't it the protocol?
Should this again be Free / Open Source Software?
@ -5,3 +5,3 @@
Resolves: #none <!-- The number of the issue that is resolved by this pull request. If there is none, feel free to delete this line -->
Resolves: #none <!-- A link to the (discussion) issue resolved by this pull request. There must be a discussion issue here at GitHub, before a pull request of software/service suggestion can be considered for merging. -->
#### Check List <!-- Please add an x in each box below, like so: [x] -->
I think this is necessary if we are removing the "has associated discussion" part.
I noticed it by accident
@ -9,1 +9,4 @@
- Be constructive.
- Please feel free to *review changes* in the *files changed* tab of any
pull request at any time.
- See also our [Code of Conduct](https://github.com/privacytoolsIO/privacytools.io/blob/master/CODE_OF_CONDUCT.md)
Not anywhere else, no. I think it's good to add a link to it as a reminder.
I think it means the provider allows IMAP so users can access it via client that's open source.
@ -9,1 +9,4 @@
- Be constructive.
- Please feel free to *review changes* in the *files changed* tab of any
pull request at any time.
- See also our [Code of Conduct](https://github.com/privacytoolsIO/privacytools.io/blob/master/CODE_OF_CONDUCT.md)
Sorry, could you clarify? It's good to add a link to the CoC as a reminder here, or should English-only be documented somewhere else?
I kind of would like to have language specific subforums and accept contributions or at least feedback in other languages too, assuming we have team member(s) fluent in that language.
LGTM
@ -9,1 +9,4 @@
- Be constructive.
- Please feel free to *review changes* in the *files changed* tab of any
pull request at any time.
- See also our [Code of Conduct](https://github.com/privacytoolsIO/privacytools.io/blob/master/CODE_OF_CONDUCT.md)
Sorry, I meant to say I think we only have this English only version of the CoC at the moment so adding a link to it like your change does I think is good 👍🏼
Yeah, I would think so for consistency
Thanks!