Re: Comment system, take two and a half
On 5/29/2012 9:35 AM, Rich Bowen wrote: In my view of this, comments should *not* be considered a permanent part of the document. Either they get incorporated into the document itself, or they get flushed. I really don't want to see comments sticking around forever on a doc. I consider them to be more of a means of contributing to the doc effort. Big +1 to this. -- Daniel Ruggeri
Re: Comment system, take two and a half
On 05/28/2012 09:38 PM, Gregg Smith wrote: Each branch different, 2.2 2.4 have some big differences between them in various areas. My 2 cents anyway. What I'm perhaps more curious to get sorted out is whether we should consider the trunk and the 2.4 documentation separate entities, or whether they should be linked, comment-wise. Currently, they are pretty much identical, but in the future it may be a good idea to keep them separate as we move towards 2.5/2.6. With regards, Daniel.
Re: Comment system, take two and a half
On 29 May 2012, at 8:50 AM, Daniel Gruno wrote: Each branch different, 2.2 2.4 have some big differences between them in various areas. My 2 cents anyway. What I'm perhaps more curious to get sorted out is whether we should consider the trunk and the 2.4 documentation separate entities, or whether they should be linked, comment-wise. Currently, they are pretty much identical, but in the future it may be a good idea to keep them separate as we move towards 2.5/2.6. My gut feel is that trunk shouldn't have comments at all - trunk is fluid, and changes without warning. Comments are very likely to get stale and become more of a problem than a help. Regards, Graham --
Re: Comment system, take two and a half
On May 29, 2012, at 5:04 AM, Graham Leggett wrote: On 29 May 2012, at 8:50 AM, Daniel Gruno wrote: Each branch different, 2.2 2.4 have some big differences between them in various areas. My 2 cents anyway. What I'm perhaps more curious to get sorted out is whether we should consider the trunk and the 2.4 documentation separate entities, or whether they should be linked, comment-wise. Currently, they are pretty much identical, but in the future it may be a good idea to keep them separate as we move towards 2.5/2.6. My gut feel is that trunk shouldn't have comments at all - trunk is fluid, and changes without warning. Comments are very likely to get stale and become more of a problem than a help. I've come around to thinking that they should be separate. I think it'll be useful to have comments on trunk, but, particularly on trunk, there needs to be no expectation that comments will stick around for any time at all. In my view of this, comments should *not* be considered a permanent part of the document. Either they get incorporated into the document itself, or they get flushed. I really don't want to see comments sticking around forever on a doc. I consider them to be more of a means of contributing to the doc effort. -- Rich Bowen rbo...@rcbowen.com :: @rbowen rbo...@apache.org
Re: Comment system, take two and a half
On 5/27/2012 3:20 PM, Daniel Gruno wrote: We could insist that all comments be made in English unless they are related to a specific translations, and as long as we keep the translations up to date with the suggestions and delete comments as they are implemented, there shouldn't be much clutter. 1 comment system, should request they be in English. Examples posted will benefit everyone this way. And if they post in some other language, people can always use one of the online translators on them. - When this moves to 2.4 and possibly 2.2, should we keep each branch separate, or should we unify it? That is, should f.x. core.html show the same comments for 2.2, 2.4 and trunk combined, or should they be kept separate? Each branch different, 2.2 2.4 have some big differences between them in various areas. My 2 cents anyway. Regards Gregg
Re: Comment system, take two and a half
Most of the kinks in the new comment system have now been sorted, as has most of the question on the actual implementation of it. However, a few questions remain, that I'd like some input on if possible: - Should we keep the various translations separate, or should it be one unified commentary? i.e. should the French pages separate comments from the English pages, or should they all just roll with the same comments? We could insist that all comments be made in English unless they are related to a specific translations, and as long as we keep the translations up to date with the suggestions and delete comments as they are implemented, there shouldn't be much clutter. - When this moves to 2.4 and possibly 2.2, should we keep each branch separate, or should we unify it? That is, should f.x. core.html show the same comments for 2.2, 2.4 and trunk combined, or should they be kept separate? I'm leaning towards the latter myself, as a lot of pages really have changed quite a bit, and it'd become confusing if someone is suddenly commenting on a 2.2 issue and it shows up in the 2.4 docs. Any input would be greatly appreciated. With regards, Daniel. On 05/23/2012 08:07 PM, Daniel Gruno wrote: Since people have begun talking about the idea of hosting/using this system within the ASF, I've added some more kinks to the system now. Those of you who have created an account (or those who create one and let me know) will now see a moderate link when they are viewing comments while logged in. This will take them to a new moderator site, where it's possible to track the latest activity, delete threads and track specific origins (origin tracking only applies to posts made after I revamped the moderator system, so old posts can't be tracked). An origin is basically a digest of an IP address (to both preserve the privacy policy and get rid of any trouble with IPv4/IPv6 mingling), and it allows you to either ban an origin from posting, view and delete any comments made by that origin or simply nuke everything ever posted by that origin. You can also opt in or out of receiving email notifications when a new post is being made (and opting in/out on a specific page is in the works). If you like, you can also register new sites to be used with the comment system. If you want to test out the features, be my guest and spam away on the trunk pages, so you can nuke your own origin to bits :) If this moves to infra, the plan is to use the committer IDs as your new login, so all committers essentially become moderators, but will still have to opt in in order to receive email notifications of new posts on the site (unless it's a reply to their own post, in which case they'll get a reply anyway) With regards, Daniel. - To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org For additional commands, e-mail: docs-h...@httpd.apache.org
