You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Rob Weir <ro...@apache.org> on 2012/07/10 00:39:58 UTC
comments.apache.org
This looks interesting/useful: https://comments.apache.org/
Would this make sense for our core files under /ooo-site ?
-Rob
Re: comments.apache.org
Posted by Andrea Pescetti <pe...@apache.org>.
Rob Weir wrote:
>>> ... https://comments.apache.org/
> But it would probably work for API pages, or building guide, pages
> that are technical instructions.
Yes, it would definitely be good to test it there. While it will only
cause maintenance/moderation nightmares if we put it on a high-traffic page.
Regards,
Andrea.
RE: comments.apache.org
Posted by "Dennis E. Hamilton" <de...@acm.org>.
+1 on piloting this on some site page.
- Dennis
-----Original Message-----
From: Rob Weir [mailto:robweir@apache.org]
Sent: Monday, July 09, 2012 16:38
To: ooo-dev@incubator.apache.org
Subject: Re: comments.apache.org
On Mon, Jul 9, 2012 at 7:05 PM, Dave Fisher <da...@comcast.net> wrote:
>
> On Jul 9, 2012, at 3:39 PM, Rob Weir wrote:
>
>> This looks interesting/useful: https://comments.apache.org/
>>
>> Would this make sense for our core files under /ooo-site ?
[ ... ]
In any case, might make sense to pilot this in a small, focused way to
see how users will use it.
But certainly exciting possibilities!
[ ... ]
Re: comments.apache.org
Posted by drew jensen <dr...@gmail.com>.
On Tue, 2012-07-10 at 17:35 +0200, Daniel Gruno wrote:
> On 07/10/2012 05:20 PM, drew jensen wrote:
> >
> > So - I wasn't sure on that - could I actually embed that into a page
> > right now, just by changing those variable in the js example and
> > 'go-live' with it, as a separate dashboard, for a set of files - just
> > like that, no further need to ask someone to create something?
> >
> > Best wishes,
> >
> > //drew
> >
>
>
> In theory yes, you could just use the snippets in place for either httpd
> or trafficserver (and add your own shortname, fx. ooo-test) and it would
> work, but to make it work properly, you'd first have to request project
> admin status on comments.a.o and then create those sites using the site
> creator (which will appear once you have the rights to do so). that
> would then give you a HTML snippet you can insert, as well as access to
> add non-committers as moderators and such ( see
> https://comments.apache.org/help.html#noncoms for that by the way).
>
> So, to reiterate, the proper way to go about testing this out is:
> 1) Ask Infra to add you (or your VP, whomever they allow) as a project
> admin.
Alright - not a TLP, yet, so no VP ;)
> 2) Create the site (or the sites) in the site chooser on comments.a.o
OK
> 3) Fetch the HTML snippet and insert it on the page(s) you wish to test
> it on (if you use the Apache CMS, please read the note regarding
> snippets and the CMS)
Great thanks
> Don't be afraid to ask Infra, they won't bite...hard.
>
Will do.
>
> With regards,
> Daniel.
Thanks much - that was exactly what I was asking.
Best,
//drew
Re: comments.apache.org
Posted by Daniel Gruno <ru...@cord.dk>.
On 07/10/2012 05:20 PM, drew jensen wrote:
>
> So - I wasn't sure on that - could I actually embed that into a page
> right now, just by changing those variable in the js example and
> 'go-live' with it, as a separate dashboard, for a set of files - just
> like that, no further need to ask someone to create something?
>
> Best wishes,
>
> //drew
>
In theory yes, you could just use the snippets in place for either httpd
or trafficserver (and add your own shortname, fx. ooo-test) and it would
work, but to make it work properly, you'd first have to request project
admin status on comments.a.o and then create those sites using the site
creator (which will appear once you have the rights to do so). that
would then give you a HTML snippet you can insert, as well as access to
add non-committers as moderators and such ( see
https://comments.apache.org/help.html#noncoms for that by the way).
So, to reiterate, the proper way to go about testing this out is:
1) Ask Infra to add you (or your VP, whomever they allow) as a project
admin.
2) Create the site (or the sites) in the site chooser on comments.a.o
3) Fetch the HTML snippet and insert it on the page(s) you wish to test
it on (if you use the Apache CMS, please read the note regarding
snippets and the CMS)
Don't be afraid to ask Infra, they won't bite...hard.
With regards,
Daniel.
Re: comments.apache.org
Posted by drew jensen <dr...@gmail.com>.
On Tue, 2012-07-10 at 15:37 +0200, Daniel Gruno wrote:
> On 07/10/2012 03:32 PM, drew wrote:
> > One question: Is it possible to subscribe to a subset of comments, so if
> > a comment feature were added to both the on-line USER and API guides
> > could someone subscribe to notifications for incoming comments to the
> > user docs but not the API docs?
> >
> > Otherwise - it looks interesting for sure.
> >
> > //drew
> >
>
>
> Why thank you for banning me on the test site and wiping all my comments
> ;'( *runs away crying*
Hi Daniel
Ah, I did ban you, didn't I - well, hmm think I'll go back and figure
out how to un-ban you..seems fair ;)
>
> On a more serious note, what you could do is add two separate comment
> shortnames, one for user docs and one for API docs, fx. ooo-user and
> ooo-api. That way, you'd have two separate dashboards (and you could
> even have separate moderator rights if you wanted) and two places to
> subscribe to, but from the reader's point of view it would just be one
> unified feature.
So - I wasn't sure on that - could I actually embed that into a page
right now, just by changing those variable in the js example and
'go-live' with it, as a separate dashboard, for a set of files - just
like that, no further need to ask someone to create something?
Best wishes,
//drew
Re: comments.apache.org
Posted by Daniel Gruno <ru...@cord.dk>.
On 07/10/2012 03:32 PM, drew wrote:
> One question: Is it possible to subscribe to a subset of comments, so if
> a comment feature were added to both the on-line USER and API guides
> could someone subscribe to notifications for incoming comments to the
> user docs but not the API docs?
>
> Otherwise - it looks interesting for sure.
>
> //drew
>
Why thank you for banning me on the test site and wiping all my comments
;'( *runs away crying*
On a more serious note, what you could do is add two separate comment
shortnames, one for user docs and one for API docs, fx. ooo-user and
ooo-api. That way, you'd have two separate dashboards (and you could
even have separate moderator rights if you wanted) and two places to
subscribe to, but from the reader's point of view it would just be one
unified feature.
With regards,
Daniel.
Re: comments.apache.org
Posted by drew <dr...@baseanswers.com>.
On Tue, 2012-07-10 at 12:56 +0200, Jürgen Schmidt wrote:
> On 7/10/12 1:37 AM, Rob Weir wrote:
> > On Mon, Jul 9, 2012 at 7:05 PM, Dave Fisher <da...@comcast.net> wrote:
> >>
> >> On Jul 9, 2012, at 3:39 PM, Rob Weir wrote:
> >>
> >>> This looks interesting/useful: https://comments.apache.org/
> >>>
> >>> Would this make sense for our core files under /ooo-site ?
> >>
> >> This is very cool.
> >>
> >> I think it can be used effectively on the API site, why, downloads, and many other parts of ooo-site.
> >>
> >> I would not add this to any NL sites without proper moderators.
> >>
> >
> > I would not put it on the main home page or the download page, or
> > similar pages where the extreme volume would almost certainly lead to
> > large numbers of out-of-place support questions being posted. On a
> > page with 5 million+ monthly hits, all it takes is 0.1% user confusion
> > for us to get flooded.
> >
> > But it would probably work for API pages, or building guide, pages
> > that are technical instructions. Release notes or install
> > instructions would be other examples, albeit with much greater
> > traffic.
> >
> >> I would start with one or two pages to get the formula correct. Once found turning the page on will become part of the site template and controlled from the ssi.mdtext in the templates dir.
> >>
> >
> > It would be good to know also how we manage this as pages are revised
> > and when we use this versus anonymous CMS. For example, if a user
> > puts a comment that says, "Step X should really say 'foo'", then if we
> > later modify that page, then we have the extra step of going back to
> > delete the comment, I assume.
> >
> >
> > In any case, might make sense to pilot this in a small, focused way to
> > see how users will use it.
> >
> > But certainly exciting possibilities!
>
> indeed and we had thought about such a feature in the past for our API
> reference.
>
> See for exmaple3 the PHP reference here
> http://www.php.net/manual/en/language.basic-syntax.php
>
> The question is how we can integrate the feedback in a proper way... But
> it is indeed very interesting.
>
Hi Juergen
Right, the idea of a feedback system for docs of more then just the API
has been bantered around a number of times.
Another example for the commenting system is on the documentation pages
for the trafficserver project:
http://trafficserver.staging.apache.org/docs/
The comment button is available for all the docs pages.
Moderation - seems that all comiters, from all ASF projects as
moderators by default. Indeed I just logged into the control panel and
fiddled a bit in the test project.. (oops, hope no one really wanted
those comments ;-)
Also found that I could subscribe for email notifications for incoming
comments, which as best as I can tell is at a project level.
One question: Is it possible to subscribe to a subset of comments, so if
a comment feature were added to both the on-line USER and API guides
could someone subscribe to notifications for incoming comments to the
user docs but not the API docs?
Otherwise - it looks interesting for sure.
//drew
Re: comments.apache.org
Posted by Jürgen Schmidt <jo...@googlemail.com>.
On 7/10/12 1:37 AM, Rob Weir wrote:
> On Mon, Jul 9, 2012 at 7:05 PM, Dave Fisher <da...@comcast.net> wrote:
>>
>> On Jul 9, 2012, at 3:39 PM, Rob Weir wrote:
>>
>>> This looks interesting/useful: https://comments.apache.org/
>>>
>>> Would this make sense for our core files under /ooo-site ?
>>
>> This is very cool.
>>
>> I think it can be used effectively on the API site, why, downloads, and many other parts of ooo-site.
>>
>> I would not add this to any NL sites without proper moderators.
>>
>
> I would not put it on the main home page or the download page, or
> similar pages where the extreme volume would almost certainly lead to
> large numbers of out-of-place support questions being posted. On a
> page with 5 million+ monthly hits, all it takes is 0.1% user confusion
> for us to get flooded.
>
> But it would probably work for API pages, or building guide, pages
> that are technical instructions. Release notes or install
> instructions would be other examples, albeit with much greater
> traffic.
>
>> I would start with one or two pages to get the formula correct. Once found turning the page on will become part of the site template and controlled from the ssi.mdtext in the templates dir.
>>
>
> It would be good to know also how we manage this as pages are revised
> and when we use this versus anonymous CMS. For example, if a user
> puts a comment that says, "Step X should really say 'foo'", then if we
> later modify that page, then we have the extra step of going back to
> delete the comment, I assume.
>
>
> In any case, might make sense to pilot this in a small, focused way to
> see how users will use it.
>
> But certainly exciting possibilities!
indeed and we had thought about such a feature in the past for our API
reference.
See for exmaple3 the PHP reference here
http://www.php.net/manual/en/language.basic-syntax.php
The question is how we can integrate the feedback in a proper way... But
it is indeed very interesting.
Juergen
>
>
> -Rob
>
>> Regards,
>> Dave
>>
>>>
>>> -Rob
>>
Re: comments.apache.org
Posted by Rob Weir <ro...@apache.org>.
On Mon, Jul 9, 2012 at 7:05 PM, Dave Fisher <da...@comcast.net> wrote:
>
> On Jul 9, 2012, at 3:39 PM, Rob Weir wrote:
>
>> This looks interesting/useful: https://comments.apache.org/
>>
>> Would this make sense for our core files under /ooo-site ?
>
> This is very cool.
>
> I think it can be used effectively on the API site, why, downloads, and many other parts of ooo-site.
>
> I would not add this to any NL sites without proper moderators.
>
I would not put it on the main home page or the download page, or
similar pages where the extreme volume would almost certainly lead to
large numbers of out-of-place support questions being posted. On a
page with 5 million+ monthly hits, all it takes is 0.1% user confusion
for us to get flooded.
But it would probably work for API pages, or building guide, pages
that are technical instructions. Release notes or install
instructions would be other examples, albeit with much greater
traffic.
> I would start with one or two pages to get the formula correct. Once found turning the page on will become part of the site template and controlled from the ssi.mdtext in the templates dir.
>
It would be good to know also how we manage this as pages are revised
and when we use this versus anonymous CMS. For example, if a user
puts a comment that says, "Step X should really say 'foo'", then if we
later modify that page, then we have the extra step of going back to
delete the comment, I assume.
In any case, might make sense to pilot this in a small, focused way to
see how users will use it.
But certainly exciting possibilities!
-Rob
> Regards,
> Dave
>
>>
>> -Rob
>
Re: comments.apache.org
Posted by Dave Fisher <da...@comcast.net>.
On Jul 9, 2012, at 3:39 PM, Rob Weir wrote:
> This looks interesting/useful: https://comments.apache.org/
>
> Would this make sense for our core files under /ooo-site ?
This is very cool.
I think it can be used effectively on the API site, why, downloads, and many other parts of ooo-site.
I would not add this to any NL sites without proper moderators.
I would start with one or two pages to get the formula correct. Once found turning the page on will become part of the site template and controlled from the ssi.mdtext in the templates dir.
Regards,
Dave
>
> -Rob
Re: Translator roles and access (was Re: comments.apache.org)
Posted by Dave Fisher <da...@comcast.net>.
On Jul 9, 2012, at 8:15 PM, Pedro Giffuni wrote:
> The site is cool but on an unrelated comment ...
>
> --- Lun 9/7/12, Rob Weir <ro...@apache.org> ha scritto:
> ...
>> This looks
>> interesting/useful: https://comments.apache.org/
>>
>> Would this make sense for our core files under /ooo-site ?
>>
>
> Quoting the site:
>
> "If you are not a committer, you will have to register
> an account with the system and have a project admin
> grant you moderator access."
>
>
> This happens to be the same access model we need for
> Pootle. (Runs and hides in a cave)
Why hide. It's brilliant. Comments can be translation suggestions! The trick is using that to bootstrap an NL community to have individuals earn enough merit to become Committers. Google translate can help others access the value of the suggestions. Non-committers can be given karma to moderate and then can help with translations.
A good question to ask Infrastructure is if the id system and moderator role in comments.apache.org can be reused by pootle.apache.org without losing id.apache.org.
Regards,
Dave
>
> Pedro.
Translator roles and access (was Re: comments.apache.org)
Posted by Pedro Giffuni <pf...@apache.org>.
The site is cool but on an unrelated comment ...
--- Lun 9/7/12, Rob Weir <ro...@apache.org> ha scritto:
...
> This looks
> interesting/useful: https://comments.apache.org/
>
> Would this make sense for our core files under /ooo-site ?
>
Quoting the site:
"If you are not a committer, you will have to register
an account with the system and have a project admin
grant you moderator access."
This happens to be the same access model we need for
Pootle. (Runs and hides in a cave)
Pedro.