[Tails-dev] documentation contribution process too bureaucratic?

2013-03-14 Thread adrelanos
Hi! I made the assumption, that you'd like to have more people improving documentation and thought may like to get feedback if someone feels that something prevents people from contributing, like I do. Taking this as an example todo item: https://tails.boum.org/todo/document_timezone/ Looks fair

Re: [Tails-dev] documentation contribution process too bureaucratic?

2013-03-15 Thread sajolida
On 14/03/13 19:38, adrelanos wrote: > Hi! > > I made the assumption, that you'd like to have more people improving > documentation and thought may like to get feedback if someone feels > that something prevents people from contributing, like I do. Yes, that would be great to have more people writ

Re: [Tails-dev] documentation contribution process too bureaucratic?

2013-03-15 Thread adrelanos
sajol...@pimienta.org: > On 14/03/13 19:38, adrelanos wrote: >> Hi! >> >> I made the assumption, that you'd like to have more people improving >> documentation and thought may like to get feedback if someone feels >> that something prevents people from contributing, like I do. > > Yes, that would

Re: [Tails-dev] documentation contribution process too bureaucratic?

2013-04-04 Thread sajolida
>> A much more reliable way to do so it to >> be open to contributions, review them and publish them once they are >> mature. > > Yes, agreed. That is a good compromise. In wikipedia they (used to) have > a feature called sighted versions / flagged revisions. In essence, > causal visitors will se

Re: [Tails-dev] documentation contribution process too bureaucratic?

2013-07-02 Thread adrelanos
sajol...@pimienta.org: > >>> A much more reliable way to do so it to be open to >>> contributions, review them and publish them once they are >>> mature. >> >> Yes, agreed. That is a good compromise. In wikipedia they (used >> to) have a feature called sighted versions / flagged revisions. >> In

Re: [Tails-dev] documentation contribution process too bureaucratic?

2013-07-05 Thread intrigeri
Hi, adrelanos wrote (02 Jul 2013 23:04:55 GMT) : > Proposing content in the wiki just doesn't work out, probable because > the spam filter kicks in and forbids transmission due to many links. What makes you think so? > I ended up with a gateway took to long error, which I'll paste below > in quo

Re: [Tails-dev] documentation contribution process too bureaucratic?

2013-07-05 Thread adrelanos
intrigeri: > Hi, > > adrelanos wrote (02 Jul 2013 23:04:55 GMT) : >> Proposing content in the wiki just doesn't work out, probable because >> the spam filter kicks in and forbids transmission due to many links. > > What makes you think so? I am probable wrong, just because I had trouble adding l

Re: [Tails-dev] documentation contribution process too bureaucratic?

2013-07-06 Thread intrigeri
Hi, adrelanos wrote (05 Jul 2013 16:25:37 GMT) : The gateway did not receive a timely response from the upstream server or application. Apache/2.2.22 (Debian) Server at tails.boum.org Port 443 >> >> This looks like a "server busy" problem much more than a spam filter >> false posit

Re: [Tails-dev] documentation contribution process too bureaucratic?

2013-07-06 Thread adrelanos
intrigeri: > Hi, > > adrelanos wrote (05 Jul 2013 16:25:37 GMT) : > The gateway did not receive a timely response from the > upstream server or application. Apache/2.2.22 (Debian) > Server at tails.boum.org Port 443 >>> >>> This looks like a "server busy" problem much more than a spam

Re: [Tails-dev] documentation contribution process too bureaucratic?

2013-07-06 Thread Alan
Hi, On Sat, 06 Jul 2013 13:34:30 +0200 intrigeri wrote: > > adrelanos wrote (05 Jul 2013 16:25:37 GMT) : > > > Still having the same issue. > > I could reproduce that, and got the same error message, but in the end > my changes *are* saved: only the wiki update was not finished within > the Ap

Re: [Tails-dev] documentation contribution process too bureaucratic?

2013-07-10 Thread intrigeri
Hi, Alan wrote (06 Jul 2013 15:35:40 GMT) : > However, it will probably become irrelevent as soon as we switch to > redmine to track issues. Does anybody has an idea when it will > happen ? Soon. > If it is "soon", I propose we ignore the issue. Yes.