blog issueshttps://gitlab.torproject.org/tpo/web/blog/-/issues2021-01-07T20:52:34Zhttps://gitlab.torproject.org/tpo/web/blog/-/issues/33109Make (and then use) a blog account policy2021-01-07T20:52:34ZRoger DingledineMake (and then use) a blog account policyWe have a bunch of old accounts on the blog, and for basic security hygiene, we should clean them up.
Even better, let's take this chance to develop, and post somewhere, a policy for who should be able to have a blog account, and when w...We have a bunch of old accounts on the blog, and for basic security hygiene, we should clean them up.
Even better, let's take this chance to develop, and post somewhere, a policy for who should be able to have a blog account, and when we'll disable them due to inactivity or etc.
Here is a proposed start to such a policy:
* Any Tor Core Contributor can get a blog account, and it can stay active as long as they remain a core contributor.
https://gitweb.torproject.org/community/policies.git/tree/membership.txt
* We encourage everybody with an active blog account to do blog posts. Before you post, please work with the comms team to make sure the timing and content are best. [replace this short text with the longer text from steph's comment below]
* To limit security surface area, we will disable accounts that haven't logged in during the past n months. Accounts can always be re-enabled when people want to use them again.
(I suggest n=18 months. We should specify some avenue for how to request the account in the first place, and for how to request re-enabling.)
* Posters should be aware of, and follow, our blog comment moderation strategy:
https://trac.torproject.org/projects/tor/wiki/doc/community/blog-comment-policy
* We encourage guest posts from the broader community about topics that are important to Tor and Tor users. The best way to arrange a guest post is to get an existing Core Contributor to vouch for the guest, and then depending on the situation, either the core person will post it, or we'll make a blog account for the guest.Isabela FernandesIsabela Fernandeshttps://gitlab.torproject.org/tpo/web/blog/-/issues/15032Make blog.torproject.org mirrorable2021-11-18T03:02:01ZTracMake blog.torproject.org mirrorableThe blog at blog.torproject.org is an essential part of the torproject website that many users may want to visit. Though currently, mirror operators do not (cannot) mirror it due to its dynamic content (commenting capability). I suggest ...The blog at blog.torproject.org is an essential part of the torproject website that many users may want to visit. Though currently, mirror operators do not (cannot) mirror it due to its dynamic content (commenting capability). I suggest that we implement a method of exporting a static copy of the blog that can be mirrored.
**Trac**:
**Username**: martingaleJérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/web/blog/-/issues/40049make it possible to publish "same-day" posts2023-05-16T19:28:57ZIsabela Fernandesmake it possible to publish "same-day" postsHi there, this is a report from the comms team. Please keep in mind that the use case here is of a user that does not know command line.
- [x] web IDE crashes the browser because it requires so many resources from the computer. It take...Hi there, this is a report from the comms team. Please keep in mind that the use case here is of a user that does not know command line.
- [x] web IDE crashes the browser because it requires so many resources from the computer. It takes forever to load (15-45minutes) after many attempts. This is just to get to a place where you can upload an image, if an error occurs you have to start all over again. **action point**: document in a new issue in https://gitlab.torproject.org/tpo/web/lego/-/issues, see if it's possible to use lektor locally?
- [ ] takes ~15-30 minutes to upload a preview. normally the workflow involves a lot of back and forward with preview to fix markup mistakes. this 'editing and previewing' process ends up taking hours. **action point**: document in https://gitlab.torproject.org/tpo/web/blog/-/issues/40015
- [ ] if something in the build process breaks and the preview doesn't populate, it is not possible to tell what is wrong and more time is lost in figuring what to fix **action point**: document in a new issue in https://gitlab.torproject.org/tpo/web/blog/-/issues/
- [ ] doing anything more than adding a lead image (e.g., adding images inline, hyperlinking an inline image, resizing something) takes a
mixture of markup and HTML, which requires a lot of trial and error (see second item) **action point**: see if it's possible to use lektor locally?
- [ ] we always depend on a person to finalize the process, you have to (a) ask a web person to merge the request (b) keep checking the website for an hour+ to ensure its there (c) often ask the person to do another step to *actually* make the post live because something was forgotten in the merge process. this adds up to the time to complete the task. **action point**: request access to the web team
- [ ] currently is almost impossible to guarantee a post can be published on the "day-of", to do that we need to mobilize a lot of time to make sure the task can be done. **action point**: fix all of the above issues. :smile:Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/web/blog/-/issues/22845make new blog posts default to 'comments open', not 'comments closed'2020-06-27T14:30:03ZRoger Dingledinemake new blog posts default to 'comments open', not 'comments closed'Right now when I write a blog post, it defaults to "no comments".
asn got bit by this where he was wondering why his wilmington hackfest blog post had no comments.
I just almost got bit by it with no new blog post I'm working on.
Hope...Right now when I write a blog post, it defaults to "no comments".
asn got bit by this where he was wondering why his wilmington hackfest blog post had no comments.
I just almost got bit by it with no new blog post I'm working on.
Hopefully this is just a config setting change somewhere.HiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/22386Make the www.tpo script to pull blog rss files resume working2020-06-27T14:30:08ZRoger DingledineMake the www.tpo script to pull blog rss files resume workingSee include/blog-recent.wmi in the webwml git.
It gets included by en/index.wml in the webwml git.
It gets built on jenkins, when jenkins builds our website:
https://gitweb.torproject.org/project/jenkins/tools.git/tree/slaves/linux/web...See include/blog-recent.wmi in the webwml git.
It gets included by en/index.wml in the webwml git.
It gets built on jenkins, when jenkins builds our website:
https://gitweb.torproject.org/project/jenkins/tools.git/tree/slaves/linux/website-build-blog-snippets
In particular, by this script:
https://gitweb.torproject.org/project/jenkins/tools.git/tree/slaves/linux/website-build-blog-snippets/make-recent-posts
which looks like it loads this page from the blog:
https://blog.torproject.org/blog/feed
and that page seems to return 404 currently.
So we should either find out where that blog feed page is now, and change the link, or make one and make it available.HiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/22387Make unapproved comments visually different from approved comments2020-06-27T14:30:08ZRoger DingledineMake unapproved comments visually different from approved commentsRight now when looking at a blog post, e.g.
https://blog.torproject.org/blog/stem-release-15
There are some comments that are approved, and some that are unapproved, but they all look just like comments.
In the old blog, they were a dar...Right now when looking at a blog post, e.g.
https://blog.torproject.org/blog/stem-release-15
There are some comments that are approved, and some that are unapproved, but they all look just like comments.
In the old blog, they were a darker color and had the word 'unapproved' or 'unpublished' or something written over them.HiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/25011Match blog spacing in article to archive2020-06-27T14:29:59ZstephwMatch blog spacing in article to archiveReduce the spacing between the title, authoring info, and image inside the individual blog post to match the spacing on the main blog page (blog.torproject.org)Reduce the spacing between the title, authoring info, and image inside the individual blog post to match the spacing on the main blog page (blog.torproject.org)HiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/24440Match blog title post spacing to archive post title spacing2020-06-30T10:33:48ZstephwMatch blog title post spacing to archive post title spacingDecrease spacing on individual post titles to match archive page title spacingDecrease spacing on individual post titles to match archive page title spacingHiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/22013Migrate blog.tpo2020-06-30T09:19:09ZHiroMigrate blog.tpoThis ticket will be used to track blog.tpo migration to a newer drupal installation.
Here is a list of still open tickets:
[[TicketQuery(status=accepted|assigned|needs_information|needs_review|needs_revision|new|reopened,parent=legacy/t...This ticket will be used to track blog.tpo migration to a newer drupal installation.
Here is a list of still open tickets:
[[TicketQuery(status=accepted|assigned|needs_information|needs_review|needs_revision|new|reopened,parent=legacy/trac#22013,order=priority,format=table,col=status|summary|reporter|priority)]]HiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/22385Migrate new blog posts from old blog to new blog2020-06-27T14:30:08ZRoger DingledineMigrate new blog posts from old blog to new bloghttps://blog.torproject.org/blog/state-internet-censorship-indonesia
and
https://blog.torproject.org/blog/tor-browser-70a4-released
both got posted to the old blog but aren't on the new blog yet.https://blog.torproject.org/blog/state-internet-censorship-indonesia
and
https://blog.torproject.org/blog/tor-browser-70a4-released
both got posted to the old blog but aren't on the new blog yet.HiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/40004Migrate the blog out of Drupal and into a static site generator with a commen...2022-01-26T16:56:00ZGabagaba@torproject.orgMigrate the blog out of Drupal and into a static site generator with a comment service### Content
* [x] Import blog posts from Drupal
* [x] Import events from Drupal
* [x] Import comment archive
* [x] Configure RSS/Atom feeds (posts + events)
* [x] Implement categories to replace tags (depends on https://gitlab.torp...### Content
* [x] Import blog posts from Drupal
* [x] Import events from Drupal
* [x] Import comment archive
* [x] Configure RSS/Atom feeds (posts + events)
* [x] Implement categories to replace tags (depends on https://gitlab.torproject.org/tpo/web/blog/-/issues/40008)
* [x] Test Discourse comments embedding (depends on https://gitlab.torproject.org/tpo/tpa/team/-/issues/40183)
* [x] Test draft post feature
### Layout
* [x] Import relevant CSS styles from old blog
* [x] Setup 2-column responsive layout
* [x] Mirror header and footer contents from other Tor websites
### Deployment
* [x] Ensure functioning newsletter image URL redirections ([example](https://newsletter.torproject.org/archive/2021-11-01-privacy-is-a-human-right/))
* [x] Plan/implement publishing moratorium and comments section closure on Drupal
* [x] Full, final content import from Drupal
* [x] Setup static web mirrors for new site
* [x] Transition `blog.torproject.org` address
* [x] Fossilize old Drupal site (tpo/web/blog#40011)
* [ ] ~~Wind down Pantheon subscription~~ (tpo/tpa/team#40526)
* [ ] ~~Retire (or reconfigure) cache*.torproject.org machines~~ (tpo/tpa/team#40527)
### Workflow
* [x] Implement Review Apps for easy MR previews
* [x] Document final publishing workflow of the new blog
Documentation of the project requirements lives at https://gitlab.torproject.org/tpo/tpa/team/-/wikis/service/blogLaunch support's Forum and Blog migrationJérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.org2021-11-17https://gitlab.torproject.org/tpo/web/blog/-/issues/22014Migrate urls so we won't have dead links2020-06-27T14:30:10ZHiroMigrate urls so we won't have dead linksThis task takes care of ensuring that permalinks for migrated posts are maintained.This task takes care of ensuring that permalinks for migrated posts are maintained.HiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/33115Migrating the blog to a static web site with Lektor2021-07-22T19:30:16ZHiroMigrating the blog to a static web site with LektorWe have been having issues with the blog for a long time. The template we are using was developed for another purpose and never really finished.
We also spend a lot of money on Drupal that could rather be spent somewhere else.
I propose...We have been having issues with the blog for a long time. The template we are using was developed for another purpose and never really finished.
We also spend a lot of money on Drupal that could rather be spent somewhere else.
I propose to migrate the blog to a static website with lektor and have comments running from discourse.org. I have actually been in contact with discourse and they have offered to run a forum for us for free (legacy/trac#33105). Addittionally they would run an .onion and a torproject.org subdomain.
Moderation on discourse is much easier than on drupal comments (another pain point for the blog), and we would get a forum that we could use for other purposes too.
This is how the blog can be migrated.
- We will do mockups and approve them with all the parties involved.
- We will start migrating content and have it on staging for testing.
- Once we are happy we will archive the current blog into static pages and move the static bloc to blog.torproject.org.
What we will lose:
- Version history on posts.
- Old comments. I see no value in migrating old blog comments to discourse to be honest. It would be a lot of effort and the old comments will be archived anyways in the blog archive.
What we will gain:
- Once the blog has been migrated creating posts will be no different than editing anyone of our websites. It would actually be a bit easier since there are a few different template and pages in our website and the blog will just have posts.
- Anyone that is currently updating the websites will be able to help people with blog posts, therefore we will gain a lot more of blog admins.
- The blog will run from our static www rotation, so we will not have to run expensive services or 2 cache VMs in front of it to avoid paing a lot to a third party for page views.
- We will not have to update a service every now and again. The blog will run out of static HTML.
- We will be able to update the templates according to our styleguide.
- Functionalities that we will build won't break because of a drupal update.Launch support's Forum and Blog migrationHiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/22426Missing `#comments` anchor on article pages2020-06-27T14:30:06ZDavid Fifielddcf@torproject.orgMissing `#comments` anchor on article pagesClicking an "_X_ comments" link from the index takes you to a URL with a `#comments` anchor at the end, for example:
https://blog.torproject.org/blog/we-are-upgrading-our-blog#comments
It's supposed to scroll you down to the comments, ...Clicking an "_X_ comments" link from the index takes you to a URL with a `#comments` anchor at the end, for example:
https://blog.torproject.org/blog/we-are-upgrading-our-blog#comments
It's supposed to scroll you down to the comments, but the article page is missing the appropriate anchor.
This bit of HTML:
```
<section>
<h2>Comments</h2>
```
needs to change to something like this:
```
<section id="comments">
<h2>Comments</h2>
```HiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/22338Missing and mismatched blog posts2020-06-27T14:30:09ZArturo FilastòMissing and mismatched blog postsI noticed that some of the blog posts I wrote now give a permission denied error.
For example:
* https://live-tor-blog-8.pantheonsite.io/blog/ooni-bridge-reachability-study-and-hackfest (gives permission denied error)
* https://live-t...I noticed that some of the blog posts I wrote now give a permission denied error.
For example:
* https://live-tor-blog-8.pantheonsite.io/blog/ooni-bridge-reachability-study-and-hackfest (gives permission denied error)
* https://live-tor-blog-8.pantheonsite.io/blog/tor-project-hiring-developer-ooni (redirects to /blog/tor-misused-criminals), but then shows the correct article with a different author. I also don't see this appear in my list of posts: https://live-tor-blog-8.pantheonsite.io/users/artHiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/27566Missing link anchor for paginated comments2021-11-15T16:41:27ZtraumschuleMissing link anchor for paginated commentsClicking on the FIRST and LAST links for paginated comments does not jump down to the comments.Clicking on the FIRST and LAST links for paginated comments does not jump down to the comments.https://gitlab.torproject.org/tpo/web/blog/-/issues/22394Missing styling on user pages2020-06-27T14:30:07ZcypherpunksMissing styling on user pagesSome pages on the user pages are missing styling. For example;
https://blog.torproject.org/users/arma (see latest (top) post).
https://blog.torproject.org/users/arma?page=1 (all posts).
https://blog.torproject.org/users/gk?page=1 (all p...Some pages on the user pages are missing styling. For example;
https://blog.torproject.org/users/arma (see latest (top) post).
https://blog.torproject.org/users/arma?page=1 (all posts).
https://blog.torproject.org/users/gk?page=1 (all posts).
However, not all pages all like this. For example;
https://blog.torproject.org/users/arma?page=2
https://blog.torproject.org/users/gk?page=2HiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/22334Missing top-right links in blog2020-06-27T14:30:09ZteorMissing top-right links in blogThere are 9 links in the top right of https://www.torproject.org/ , and the new blog only has 2 in the top center left (and the blog link in the top right).
Did we deliberately remove:
* Documentation
* Press
* Contact
* Download
* Volu...There are 9 links in the top right of https://www.torproject.org/ , and the new blog only has 2 in the top center left (and the blog link in the top right).
Did we deliberately remove:
* Documentation
* Press
* Contact
* Download
* Volunteer
I'd like to put Download back if we can, not sure about the other ones.HiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/22724New blog comment css has only one layer of comment replies2020-06-27T14:30:04ZRoger DingledineNew blog comment css has only one layer of comment replieshttps://blog.torproject.org/comment/269444#comment-269444
is a reply to
https://blog.torproject.org/comment/269430#comment-269430
but with the new css we got for comments last week, they're at the same level of indentation.https://blog.torproject.org/comment/269444#comment-269444
is a reply to
https://blog.torproject.org/comment/269430#comment-269430
but with the new css we got for comments last week, they're at the same level of indentation.HiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/22625New blog events default to today2020-06-27T14:30:05ZRoger DingledineNew blog events default to todayWhen you make a new event on the blog, you can set the Start Time and the End Time. But when you have made the event, suddenly it's the top event on the frontpage. It turns out there's another, optional, time you can set, called "Calenda...When you make a new event on the blog, you can set the Start Time and the End Time. But when you have made the event, suddenly it's the top event on the frontpage. It turns out there's another, optional, time you can set, called "Calendar date", and if you don't set it, it fills in today.
We should make it fill in the same date as Start Time instead. Or make it leave the optional thing empty, and use the Start Time if Calendar date isn't filled in.
Long term goal should be having drupal copy the start date into the calendar date.HiroHiro