Web Team issueshttps://gitlab.torproject.org/tpo/web/team/-/issues2022-11-23T18:03:57Zhttps://gitlab.torproject.org/tpo/web/team/-/issues/45make a list of licenses and copyright policies used in web repositories2022-11-23T18:03:57ZKezmake a list of licenses and copyright policies used in web repositoriesquoting from the TPA version of this ticket (tpo/tpa/team#40974):
> in this week's all hands, we discussed copyright policy and established we should at least make an inventory of what licenses are used by which team. we should make a t...quoting from the TPA version of this ticket (tpo/tpa/team#40974):
> in this week's all hands, we discussed copyright policy and established we should at least make an inventory of what licenses are used by which team. we should make a tour of our git repositories (an interesting exercise in itself) and figure out which repository is using which license.
>
>if we do find repositories *without* licenses, we should mark that as a bug and set a license. make sure we have a stated policy on inbound=outbound, for example, and, why not, start using CONTRIBUTING and code of conducts and proper READMEs for all repos...
>
>the output of this should possibly be a RFC setting a team-wide policy about copyright assignment as well.https://gitlab.torproject.org/tpo/web/team/-/issues/42TPA-RFC-37: Lektor replacement2023-05-15T20:46:41ZanarcatTPA-RFC-37: Lektor replacementconsider a replacement, what that entails, what we could use for this, and whether it's worth it. see [TPA-RFC-37](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-37-lektor-replacement) for drafting...consider a replacement, what that entails, what we could use for this, and whether it's worth it. see [TPA-RFC-37](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-37-lektor-replacement) for drafting...https://gitlab.torproject.org/tpo/web/team/-/issues/33Documenting and maintaining media.tpo2023-02-03T14:22:56ZKezDocumenting and maintaining media.tpoIn #32 we decided to leave media.tpo as-is. However it's still [undocumented](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/service#undocumented-service-list) and has no listed maintainers. The service should be documented in a wiki...In #32 we decided to leave media.tpo as-is. However it's still [undocumented](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/service#undocumented-service-list) and has no listed maintainers. The service should be documented in a wiki page either in this repo, or tpo/tpa/team. If we have existing documentation or know of a current maintianer, those should be listed. Otherwise, we'll need to write new documentation and find a maintainer for it.https://gitlab.torproject.org/tpo/web/team/-/issues/41Serve styled 404 page2023-11-01T20:25:06ZHiroServe styled 404 pageThe styleguide has a 404 page (https://gitlab.torproject.org/tpo/web/styleguide/-/issues/4) that would be nice if we would serve in apache.The styleguide has a 404 page (https://gitlab.torproject.org/tpo/web/styleguide/-/issues/4) that would be nice if we would serve in apache.https://gitlab.torproject.org/tpo/web/team/-/issues/25Design search.tp.o2024-02-14T02:23:38ZHiroDesign search.tp.oThis ticket is created to list a set of requirements that need to be considered when designing search.tp.o.
The following list of ideas was collected during this www meeting in December 2019 http://meetbot.debian.net/tor-meeting/2019/to...This ticket is created to list a set of requirements that need to be considered when designing search.tp.o.
The following list of ideas was collected during this www meeting in December 2019 http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-12-19-13.59.txt
* IDEA: respect locales
* IDEA: user search bar commands (hiro, 14:21:17)
* IDEA: searches should be scoped to current website (hiro, 14:24:08)
* IDEA: the searchbox should be on all the pages to make it easily
accessible (hiro, 14:28:25)
* IDEA: display the local website contents and offer a link for
'search in all torproject' (hiro, 14:29:54)https://gitlab.torproject.org/tpo/web/team/-/issues/50Make web searches for Tor Browser more useful2024-01-25T19:58:46ZPhilipp Winterphw@torproject.orgMake web searches for Tor Browser more useful(I'm filing this under community/outreach for lack of a better component.)
When people try to get a copy of Tor Browser, they likely search for "tor download" in their favourite search engine. The phrase "tor download" results in the fo...(I'm filing this under community/outreach for lack of a better component.)
When people try to get a copy of Tor Browser, they likely search for "tor download" in their favourite search engine. The phrase "tor download" results in the following:
* Google's first result points to our download page. The second result is techspot.com/downloads/5183-tor-browser.html, a third-party download site.
* Bing's first result also points to our download page. The second result is tor.en.lo4d.com, a third-party download site.
* Same story with Yahoo: the first results points to our download page and the second is a third-party download site.
* Yandex's first three results point to our download pages. The fourth is a third-party download site.
* Baidu's top results are all third-party download sites:
* tor-browser-download.en.softonic.com
* tor.brothersoft.com (unrelated to us)
* tor-browser.updatestar.com/en
There are a few things we could do to make web searches for Tor Browser more useful:
* Gus pointed out that we can mention GetTor in torproject.org's website description. Google makes this possible over some sort of webmaster UI. Maybe other search engines provide similar functionality. Our website's description could say something along the lines of "Unable to load this website? Send an email to !gettor@tp.o to get Tor Browser".
* Reach out to receptive third-party download sites. We recently discovered t-browser.sourceforge.net over baidu. It seems to be a third-party download site with good intentions. We could reach out to such webmasters and work with them to make their sites more useful.https://gitlab.torproject.org/tpo/web/team/-/issues/1collect 404 errors on our websites2021-10-07T13:36:37Zemmapeelcollect 404 errors on our websitesMaybe we could have a way of knowing the most popular 404s we have?
I want to have it for when the new website is launched, but also for the different lektor services it would be very interesting to have access to them.
This was done a...Maybe we could have a way of knowing the most popular 404s we have?
I want to have it for when the new website is launched, but also for the different lektor services it would be very interesting to have access to them.
This was done a while ago (8 years) with good results: legacy/trac#2072https://gitlab.torproject.org/tpo/web/team/-/issues/31Some reorg suggestion for media.tpo2022-03-17T15:05:48ZIsabela FernandesSome reorg suggestion for media.tpoI was checking media.torproject.org to ask to upload some assets and the style guideline to it and saw they are already there inside of /images folder. thanks!
I wonder if we could re-org things a little bit. I would suggest to add thos...I was checking media.torproject.org to ask to upload some assets and the style guideline to it and saw they are already there inside of /images folder. thanks!
I wonder if we could re-org things a little bit. I would suggest to add those assets and the style guide to a folder /design-assets and leave images there. This way it will be easier for folks to find.
Should be moved to design-assets:
[DIR] Donate/
* images/Download/
* images/Onion Icon/
* images/Powered/
* images/Support/
* images/Tor Browser/
And the style guide pdf file: [Tor Style Guide v1.3.pdf](https://media.torproject.org/image/Tor%20Style%20Guide%20v1.3.pdf)
I will leave /official-images alone for now, it has some logos but those are old files from 2011. So maybe in the future we could actually create an archive with the history of tor logos dunno. If we do create some type of 'historical archive' we should look at /outdated and see what should go there.
I also have no idea what that slide file is: [Slides.odp](https://media.torproject.org/image/Slides.odp) Should we either move it to outdated (now that we have /templates) or delete if folks thinks is ok.
We could also update the readme file from media.tpo root dir to have an index of the folders it hosts and a phrase explaining what each folder is for.
To help folks find things.
The readme inside of /images should be updated as well as we are moving logos etc out of there. /images should be photos, graphs and screenshots. Not necessary design assets for one to use on their app or site.
And we should have a readme for /design-assets explaining what those are and that folks should follow the style guide.