On 12/06/2012 08:12, [email protected] wrote: > How frequently do you think the website would really go down? If some
To be honest, if somebody is competent and not malicious there should never really be a problem except in the case of gross negligence. Besides custom PHP development, and possibly broken/orphaned Rules, you cannot really break a Drupal website using the GUI backend. As long as you don't delete content/field definitions, you should be able to reverse changes using the backend. There is enough granularity to allow a Translations Manager of sort. There is also enough to allow somebody to manage Views/displays and content types without getting access to everything else. > data was lost what is the worse case scenario? What data is of > significant importance? At most I would expect one day of content to be > lost and a setup where Rubén didn't have to get involved in restoration. Only if data is actually deleted would it be a 'worse case'. Screwing up a View or something that controls display can be reversed (sometimes with some effort, but still). I'm not sure what Rubén stores behind the scenes, but as far as public information goes it would be all the posts and all user login details. I don't think membership is actually. I know Linode does a daily backup, although that fails once in a while. For example, one of my Linodes failed a daily backup yesterday. But in general that automated daily backup should be a relatively good failsafe in case the site sustains crippling damage -- whether by negligence or malice. A concern with giving someone a permission like "Administer Content" is that there exists the risk that existing data can be damaged or tampered with. The same with a User Administration permission. But like I mentioned, this won't happen for no reason. I realise that Rubén will have to really trust the people he gives website modification rights to, especially when there is no version control. Although, as you mentioned, with something like Linode's daily backup we can restore a recent backup and revoke that user's rights. As long as the server itself has not been compromised, we shouldn't have an issue. > I think the translation issue could probably be solved by better > management. We don't really have a manager right now. We have Rubén, a > developer. Lets put together some policies on this subject. > > For instance lets not add new languages until we have multiple > translators to participate. We can put out a list and once we have > sufficient volunteers (lets say 2 for now) we will add the language. > > Why don't we start this by creating a public wiki people can edit. Have a look at this thread: https://trisquel.info/en/forum/seriously-facing-trisquel-website-translations We were discussing translation management and I pointed Rubén to it in IRC. I'm not sure if he read all of it in much detail because he was travelling at that time. We also created a Translations wiki with most of the information we could put together, including a manually updated list of all pages: https://trisquel.info/en/wiki/website-translations I have not looked at this again because there is not much I can do directly. The wiki still needs to be updated and we should probably confirm with all the users currently listed as translators if they are actually still active. I have offered to help with translation management in that thread and multiple times in IRC. I realise that I have not been here that long and that I don't really have a big presence, like, for example, you with ThinkPenguin. Anyhow, my offer still stands but it is up to Rubén to do something going forward. I've given some (Drupal) implementation ideas in that thread, but beyond that I'm not going to actively pursue this any further. It is slightly frustrating but I understand why Rubén would be reluctant to allow anyone to just have access to the website's backend and I know his thoughts are more on the actual distro anyway. So I'll assist translators in IRC or wherever, but I'm also slowly moving my focus to learning about and assisting with bug fixing. > I think a good start is just getting up a wiki. I'm definitely willing > to write up some proposals on how I think the system should work. Then > we can post to the forum what changes and problems people see and see if > we can find solutions for them. > > Can anybody volunteer an appropriate place to start this wiki? Either on > the Trisquel site- or I can setup and fund a VPS to get us started. If > things don't work out- or we need to change them (like not use a VPS, > etc) we can go from there. Alternatively maybe there is a good freedom > friendly wiki elsewhere we can utilise. > > Suggestions? You could/should probably do that on a wiki here. We can all edit those pages and it would be the least amount of effort for the time being, unless you envision that we need more functionality to manage this? If you do a wiki here, give it a Book Outline of 'Documentation' and link it to one of the existing pages, maybe 'How to help'. With that outline setting we can create sub-pages that can be linked to your main wiki page. -- Morne Alberts
signature.asc
Description: OpenPGP digital signature
