Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Apache: Docs

Relaxing docs review policy?

 

 

Apache docs RSS feed   Index | Next | Previous | View Threaded


rbowen at rcbowen

Mar 28, 2012, 6:36 AM

Post #1 of 5 (168 views)
Permalink
Relaxing docs review policy?

It has been mentioned several times that we'd have more translations if we'd relax the review policy a little.

I'd like to propose that we loosen it up on trunk, so that the translations can at least get into the tree, and then actively solicit reviews (on users@, for example) before pushing them into trunk. I think that by requiring review of the patches, rather than putting them into trunk, we make it unreasonably hard for reviewers to actually have a look at them. Whereas if they were in trunk, reviewers could look at the rendered docs on the /docs/trunk web site, and we'd be more likely to get feedback.

Thoughts?

--
Rich Bowen
rbowen [at] rcbowen :: @rbowen
rbowen [at] apache


rumble at cord

Mar 28, 2012, 6:57 AM

Post #2 of 5 (147 views)
Permalink
Re: Relaxing docs review policy? [In reply to]

On 28-03-2012 15:36, Rich Bowen wrote:
> It has been mentioned several times that we'd have more translations
> if we'd relax the review policy a little.
>
> I'd like to propose that we loosen it up on trunk, so that the
> translations can at least get into the tree, and then actively solicit
> reviews (on users@, for example) before pushing them into trunk. I
> think that by requiring review of the patches, rather than putting
> them into trunk, we make it unreasonably hard for reviewers to
> actually have a look at them. Whereas if they were in trunk, reviewers
> could look at the rendered docs on the /docs/trunk web site, and we'd
> be more likely to get feedback.
>
> Thoughts?
>
> --
> Rich Bowen
> rbowen [at] rcbowen <mailto:rbowen [at] rcbowen> :: @rbowen
> rbowen [at] apache <mailto:rbowen [at] apache>
hm, I'd say +1 or +½.
I like the idea that we can "test out" the translations that way, and of
course there would be some form of rudimentary check when it gets pushed
to the trunk, but I'm always a bit skeptical about letting unknown stuff
onto the live server. Having said that, I do feel that the committers on
this project are quite competent and capable of preventing any bad
things from lingering on, so I have some confidence that this could
work, and in the case of someone pushing something awful, it
would/should be spotted pretty quick and fixed. Also, as this is the
trunk, which not that many users look at, it should allow us some
leniency towards making mistakes in it.

With regards,
Daniel.


mads at toftum

Mar 28, 2012, 7:08 AM

Post #3 of 5 (150 views)
Permalink
Re: Relaxing docs review policy? [In reply to]

On Wed, Mar 28, 2012 at 09:36:18AM -0400, Rich Bowen wrote:
> It has been mentioned several times that we'd have more translations if we'd relax the review policy a little.
>
> I'd like to propose that we loosen it up on trunk, so that the translations can at least get into the tree, and then actively solicit reviews (on users@, for example) before pushing them into trunk. I think that by requiring review of the patches, rather than putting them into trunk, we make it unreasonably hard for reviewers to actually have a look at them. Whereas if they were in trunk, reviewers could look at the rendered docs on the /docs/trunk web site, and we'd be more likely to get feedback.
>
> Thoughts?
>
I think we'd be ok to skip the review for translated docs in trunk as
long as we stick to our current model of getting a second set of trusted
eyes on it before backporting. But I don't think it's a good idea to go
fishing for reviews at random spots like users@.

vh

Mads Toftum
--
http://soulfood.dk

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe [at] httpd
For additional commands, e-mail: docs-help [at] httpd


kess at kess-net

Mar 28, 2012, 8:40 AM

Post #4 of 5 (146 views)
Permalink
Re: Relaxing docs review policy? [In reply to]

On Wednesday 28 March 2012 15:36:18 Rich Bowen wrote:
> It has been mentioned several times that we'd have more translations if
> we'd relax the review policy a little.
>
> I'd like to propose that we loosen it up on trunk, so that the translations
> can at least get into the tree, and then actively solicit reviews (on
> users@, for example) before pushing them into trunk. I think that by
> requiring review of the patches, rather than putting them into trunk, we
> make it unreasonably hard for reviewers to actually have a look at them.
> Whereas if they were in trunk, reviewers could look at the rendered docs
> on the /docs/trunk web site, and we'd be more likely to get feedback.
>
> Thoughts?

+1 for putting them in trunk

Kess


i.galic at brainsware

Apr 3, 2012, 4:17 PM

Post #5 of 5 (140 views)
Permalink
Re: Relaxing docs review policy? [In reply to]

----- Original Message -----
> It has been mentioned several times that we'd have more translations
> if we'd relax the review policy a little.
>
>
> I'd like to propose that we loosen it up on trunk, so that the
> translations can at least get into the tree, and then actively
> solicit reviews (on users@, for example) before pushing them into
> trunk. I think that by requiring review of the patches, rather than
> putting them into trunk, we make it unreasonably hard for reviewers
> to actually have a look at them. Whereas if they were in trunk,
> reviewers could look at the rendered docs on the /docs/trunk web
> site, and we'd be more likely to get feedback.
>
>
> Thoughts?

So we're making trunk CTR? Like for the code?
+1

> --
> Rich Bowen
> rbowen [at] rcbowen :: @rbowen
> rbowen [at] apache


i

--
Igor Galić

Tel: +43 (0) 664 886 22 883
Mail: i.galic [at] brainsware
URL: http://brainsware.org/
GPG: 6880 4155 74BD FD7C B515 2EA5 4B1D 9E08 A097 C9AE


---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe [at] httpd
For additional commands, e-mail: docs-help [at] httpd

Apache docs RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.