github-starred/firejail
2
0
Fork 0
mirror of https://github.com/netblue30/firejail.git synced 2026-05-15 14:16:14 -06:00
Code Issues 531 Projects Packages Wiki Activity Actions 6

[GH-ISSUE #2713] Switch from Wordpress site to Github Pages #1708

New issue
Closed
opened 2026-05-05 08:22:01 -06:00 by gitea-mirror · 6 comments
gitea-mirror commented 2026-05-05 08:22:01 -06:00
Owner
Copy link

Originally created by @chiraag-nataraj on GitHub (May 21, 2019).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2713

I've seen several requests on here (at the end of issues, for example) to update things on the website. It might be easier to manage if we move from the current Wordpress site to a Github page, since other people can also help maintain it.

Just a thought.

Originally created by @chiraag-nataraj on GitHub (May 21, 2019). Original GitHub issue: https://github.com/netblue30/firejail/issues/2713 I've seen several requests on here (at the end of issues, for example) to update things on the website. It might be easier to manage if we move from the current Wordpress site to a Github page, since other people can also help maintain it. Just a thought.
gitea-mirror 2026-05-05 08:22:01 -06:00
gitea-mirror commented 2026-05-05 08:22:04 -06:00
Author
Owner
Copy link

@smitsohu commented on GitHub (May 21, 2019):

There is also #2090

<!-- gh-comment-id:494385206 --> @smitsohu commented on GitHub (May 21, 2019): There is also #2090
gitea-mirror commented 2026-05-05 08:22:05 -06:00
Author
Owner
Copy link

@chiraag-nataraj commented on GitHub (May 21, 2019):

Yup. But I presume moving our official documentation is slightly different from the website (which provides common usage, etc), so while it's related, I'd regard it as a separate goal.

<!-- gh-comment-id:494399468 --> @chiraag-nataraj commented on GitHub (May 21, 2019): Yup. But I presume moving our official documentation is slightly different from the website (which provides common usage, etc), so while it's related, I'd regard it as a separate goal.
gitea-mirror commented 2026-05-05 08:22:06 -06:00
Author
Owner
Copy link

@chiraag-nataraj commented on GitHub (May 28, 2019):

@netblue30, thoughts?

<!-- gh-comment-id:496706183 --> @chiraag-nataraj commented on GitHub (May 28, 2019): @netblue30, thoughts?
gitea-mirror commented 2026-05-05 08:22:08 -06:00
Author
Owner
Copy link

@chiraag-nataraj commented on GitHub (May 29, 2019):

Let's move the discussion over to #2729.

<!-- gh-comment-id:496989706 --> @chiraag-nataraj commented on GitHub (May 29, 2019): Let's move the discussion over to #2729.
gitea-mirror commented 2026-05-05 08:22:10 -06:00
Author
Owner
Copy link

@tredondo commented on GitHub (Mar 14, 2021):

Let's move the discussion over to #2729.

I wasn't around when this decision was made, but it seems the migration to Wordpress is pretty involved, mainly due to the comments and the blog (which still has entries there as of this month), so IMO it would make sense to keep it separate from the meta ticket (#2729). In that vein, I'll continue here.

So regarding the comments migration issue raised by @SkewedZeppelin,

The important bit about it is how low barrier it is. ie. no need to create a forum account or anything.

I think GitHub is a pretty low barrier of entry, and prevents spam very well.

find a solution for the comments

We now have GitHub discussions, which can host unanswered comments from Wordpress. For resolved Q&As, I think the best palce would be the Wiki FAQ, so I took the liberty to create some examples.

I went through all the Wordpress pages, and here are the ones with comments, as well as the date of the most recent comment. I think we should focus on the most recent ones first, and I also think it's fine if old comments are left in peace.

If anyone wants to continue the work, feel free :)

<!-- gh-comment-id:798831498 --> @tredondo commented on GitHub (Mar 14, 2021): > Let's move the discussion over to #2729. I wasn't around when this decision was made, but it seems the migration to Wordpress is pretty involved, mainly due to the comments and the blog (which still has entries there as of this month), so IMO it would make sense to keep it separate from the meta ticket (#2729). In that vein, I'll continue here. So regarding the [comments migration](https://github.com/netblue30/firejail/issues/2729#issuecomment-739971836) issue raised by @SkewedZeppelin, > The important bit about it is how low barrier it is. ie. no need to create a forum account or anything. I think GitHub is a pretty low barrier of entry, and prevents spam very well. > find a solution for the comments We now have GitHub discussions, which can host unanswered comments from Wordpress. For resolved Q&As, I think the best palce would be [the Wiki FAQ](https://github.com/netblue30/firejail/wiki/Frequently-Asked-Questions), so I took the liberty to create [some examples](https://github.com/netblue30/firejail/wiki/Frequently-Asked-Questions/_history). I went through all the Wordpress pages, and here are the ones with comments, as well as the date of the most recent comment. I think we should focus on the most recent ones first, and I also think it's fine if old comments are left in peace. * [ ] https://firejail.wordpress.com/download-2/ - May 2020 * [ ] https://firejail.wordpress.com/download-2/release-notes/ - Aug2020 * [x] https://firejail.wordpress.com/features-3/ - I've [added the only relevant Q to the Wiki FAQ](https://github.com/netblue30/firejail/wiki/Frequently-Asked-Questions/_compare/50cc5519791d82e160606a40c6105dfe50839976...c86268f4f52bfa4aa978b4212ca58e0406bb8816) * [ ] https://firejail.wordpress.com/features-3/man-firejail/ - Aug 2020 * [x] https://firejail.wordpress.com/documentation-2/ - created a [discussion](https://github.com/netblue30/firejail/discussions/4096) for the only relevant comment * [ ] https://firejail.wordpress.com/documentation-2/basic-usage/comment-page-1/#comments - Nov 2020 * [ ] https://firejail.wordpress.com/2021/01/21/firejail-tips-and-tricks/ - Feb 2021, all answered by @netblue30 * [ ] https://firejail.wordpress.com/documentation-2/building-custom-profiles/ - Mar 2019 * [ ] https://firejail.wordpress.com/documentation-2/firefox-guide/ - Feb 2021 * [ ] https://firejail.wordpress.com/documentation-2/linux-capabilities-guide/ - all old or sort of answered * [ ] https://firejail.wordpress.com/2017/05/15/linux-mint-sandboxing-guide/ - comments left to be addressed: starting from the Netflix one, through to the last (Aug 2019) * [ ] https://firejail.wordpress.com/support/ - Feb 2021. This has 280+ comments. * [ ] [The blog](https://firejail.wordpress.com/blog/) - the blog *after* [Tips and tricks](https://firejail.wordpress.com/2021/01/21/firejail-tips-and-tricks/) don't have any comments. That one has 8. I haven't looked at old blog posts, and we should think about what to do with the comments on blog posts * replace the comments feature with a note at the bottom pointing users to the GitHub Discussions? * let them be separately from GitHub at all? * Is the blog moving anywhere? If anyone wants to continue the work, feel free :)
gitea-mirror commented 2026-05-05 08:22:10 -06:00
Author
Owner
Copy link

@SkewedZeppelin commented on GitHub (Mar 14, 2021):

@tredondo

Perhaps replace the comments feature with a note at the bottom pointing users to the GitHub Discussions?

GitHub (Discussions) requires an account. A comment on the WordPress doesn't.

One of the nice things about GitLab is its 'service desk' feature where anyone can email in and an issue is created.
Discourse can also be configured this way.

More wholesome solutions like traditionally SourceForge or more recently Sourcehut feature a built-in mailing list.

@rusty-snake put a lot of effort in remaking the site, it is not an easy task at all.
It is sad to see it rot.

<!-- gh-comment-id:798833929 --> @SkewedZeppelin commented on GitHub (Mar 14, 2021): @tredondo > Perhaps replace the comments feature with a note at the bottom pointing users to the GitHub Discussions? GitHub (Discussions) requires an account. A comment on the WordPress doesn't. One of the nice things about GitLab is its 'service desk' feature where anyone can email in and an issue is created. Discourse can also be configured this way. More wholesome solutions like traditionally SourceForge or more recently Sourcehut feature a built-in mailing list. @rusty-snake put a lot of effort in remaking the site, it is not an easy task at all. It is sad to see it rot.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
serialize_remounts_v2
landlock_v4
landlock
release-0.9.64
release-0.9.62
gitlab_ci
LTSbase
fred_ctests
docs
0.9.80
0.9.80-rc1
0.9.78
0.9.76
0.9.76-rc4
0.9.76-rc3
0.9.76-rc2
0.9.76-rc1
0.9.74
landlock-split
0.9.72
0.9.72rc1
0.9.70
0.9.68
0.9.68rc1
0.9.66
0.9.66rc1
0.9.64.4
0.9.64.2
0.9.64
0.9.64rc1
0.9.62.4
0.9.62.2
0.9.62
0.9.56.2-LTS
0.9.60
0.9.60-rc1
0.9.58.2
0.9.58
0.9.58-rc1
0.9.56-LTS-release
0.9.56-LTS
0.9.56
0.9.56-rc1
0.9.54
0.9.54-rc2
0.9.54-rc1
0.9.52
0.9.38.12
0.9.50
0.9.50-rc1
0.9.48
0.9.46
0.9.46-rc1
0.9.44.10
0.9.44.8
0.9.44.6
0.9.38.10
0.9.44.4
0.9.38.8
0.9.44.2
0.9.44
0.9.44-rc1
0.9.38.4
0.9.42
0.9.42-rc2
0.9.38.2
0.9.42-rc1
disable-globalcfg
0.9.40
0.9.40-rc1
0.9.38
0.9.38-rc1
0.9.36
0.9.36-rc1
0.9.34
0.9.34-rc1
0.9.32
0.9.32-rc1
0.9.30
0.9.30-rc1
Labels
Clear labels   
LTS merge

   
LTS merge

   
bug

   
bug

   
converted-to-discussion

   
doc-todo

   
documentation

   
duplicate

   
enhancement

   
file-transfer

   
firecfg

   
firejail-in-firejail

   
firetools

   
graphics

   
help wanted

   
information_old

   
installation

   
invalid

   
modif

   
moved

   
needinfo

   
networking

   
notabug

   
notourbug

   
old-version

   
overlayfs

   
packaging

   
profile-request

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
question_old

   
removal

   
runtime-permissions

   
sandbox-ipc

   
security

   
stale

   
wiki

   
wiki

   
wontfix

   
wordpress

   
workaround
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#1708
No description provided.
Delete branch "%!s()"

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?