Ian writes: > On Sat, Aug 6, 2016 at 11:18 AM, Arne Babenhauserheide <[email protected]> > wrote: >> >> > It is certainly true that I'm preoccupied with other things (namely >> making >> > a living - an unfortunate necessity for most people). Should someone >> else >> > come along with the time, motivation, and expertise to take over as >> > coordinator, I would welcome it. No such person has come forward. >> >> For the past 2 years, except for money allocation, that person has been >> Steve. He merges pull requests and all volunteers respect his decisions >> on merging. For the volunteer work we’re not missing leadership. > > If Steve is interested in taking over as coordinator then I would be more > than happy to discuss it with him.
It would be great if you could take it up with him. >> a) that new site works when uploaded into Freenet and > > This seems like an unnecessary complication. The new site will be > primarily aimed at new users, if they're already using Freenet then it is > preaching to the converted. We need a site with news. These news should also be available in Freenet. > The detailed content will be in Github Wiki which can be mirrored into > Freenet, but this should not be a barrier to the website redesign. We already have a wiki. Why not https://wiki.freenetproject.org? As I already wrote, using the new design for a landing site like https://get.freenetproject.org and keeping the current site would void all these problems. We would have a cool, low maintenance site to show new users without having to convert all existing content and forward the links. >> b) it preserves all inbound links and > This is desirable, unless it becomes a significant impediment to a > redesign. Do we know which inbound links receive significant traffic? I don’t. But from what I saw in the past years, we cannot predict which guide will become popular. There are several existing tutorials by other people. The pattern of activity on Freenet tutorials is pretty erratic. >> c) is actually finished, so it does not require us volunteers to spend >> half a year of work to make it actually work (like re-translating >> everything, re-integrating the infrastructure to deploy it, etc). > > The new site will require re-translation, but this should not be turned > into an obstacle to the redesign. Since the new site will focus on > education of non-Freenet users, it should have a lot less copy requiring > translation. > >> However I would much prefer if your proposal would not be to task a >> designer with redesigning it "from the ground up", but with "making the >> Freenet site rock" and leaving it to the designer whether to break >> everything (and invest the work to integrate everything) or to just >> create a better theme and restructure existing content. > > Designers don't make that kind of decision, the role you're thinking of is > Chief Marketing Officer. We don't have one of those, but fortunately I > have a good understanding of marketing. Then let me ask you in your role of chief marketing officer: Why do you prefer redesigning from the ground up over fixing what is broken on the acustung site? I ask for your reasons because in the answers to your question how the site should be changed which you once linked, 5 out of 6 people said they would only do smaller changes (like fixing the download site and reducing the complexity of the menu). Rewriting the site from scratch has the cost¹ that all the existing work on fixing the site for specific use cases is lost, and that links need to be converted and content be transferred. However this cost calculation is only valid when the new site actually replaces the site. The cost would be much reduced when making the new site a dedicated landing site and keeping the old site for the tasks the new site isn’t intended to fulfil. That’s why I’m suggesting to put that site at https://get.freenetproject.org ¹: With cost I mean all resources — money plus required volunteer work. Best wishes, Arne -- Unpolitisch sein heißt politisch sein ohne es zu merken
signature.asc
Description: PGP signature
_______________________________________________ Devl mailing list [email protected] https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
