Am 07/23/2013 07:38 PM, schrieb Kay Schenk:
On Mon, Jul 22, 2013 at 4:23 PM, Rob Weir<robw...@apache.org> wrote:
On Mon, Jul 22, 2013 at 6:13 PM, Ricardo Berlasso<rgb.m...@gmail.com>
wrote:
2013/7/22 janI<j...@apache.org>
On Jul 22, 2013 11:50 PM, "Marcus (OOo)"<marcus.m...@wtnet.de> wrote:
Am 07/22/2013 06:12 PM, schrieb Marcus (OOo):
Am 07/22/2013 05:16 PM, schrieb janI:
On 22 July 2013 17:09, Rob Weir<robw...@apache.org> wrote:
On Mon, Jul 22, 2013 at 3:46 AM, janI<j...@apache.org> wrote:
On Jul 22, 2013 8:59 AM, "Marcus (OOo)"<marcus.m...@wtnet.de>
wrote:
Am 07/22/2013 04:46 AM, schrieb Kay Schenk:
On Jul 20, 2013 11:38 PM, "Andrea Pescetti"<pesce...@apache.org
wrote:
Rob Weir wrote:
Remember, the number of people who have admin-related
questions
about
the wiki are very, very, very few in number. They will be best
served
by directing them to some variation of a page like the one we
have on
the main website:
http://www.openoffice.org/contact_us.html
Why not linking directly to it then? It would be enough to add
a
section
to
http://www.openoffice.org/contact_us.html
like the following:
* If you have technical problems with one of the OpenOffice
websites...
- For problems with the www.openoffice.org site: contact
dev@openoffice.apache.org and insert "[Website]" in the subject
- For problems with the https://issues.apache.org/ooo/ site:
contact
aoo-bugzilla-ad...@apache.org
- For problems with the wiki.openoffice.org site: contact
dev@openoffice.apache.org and insert "[Mwiki]" in the subject
- For problems with the https://translate.apache.org/ site:
contact
l...@openoffice.apache.org and insert "[Pootle]" in the subject
Regards,
Andrea.
This suggestion looks very reasonable to me.
In general also for me reasonable. But I don't want to rely on
the
subject prefix that the users have to insert manually. Rather, I
would
use
some aliases to see where the mail come from.
web-admin@ --> dev@
wiki-admin@ --> dev@
Marcus
sounds good to me, even though I dont think it will make a huge
difference'
having a contact link on wiki will cause trafic, and users pr
defitinition
choose the easy road.
Yes, users are lazy, but they also know what they want. They only
write to the dev list if there is no other option that sounds
closer
to what they were looking for.
So if we have have a page that gives them the appropriate options
for
support, reporting bugs, admin issues, etc., and order these
appropriately on
the page (most commonly needed at top), then we should do OK. The
idea that Dave had was to add these items to an existing contact
page
that already has these other options.
So the issue is that 99.99% of the visitors to a wiki page, if they
have a question, will have a product support question. Some, but
very
few, will have an admin-related question. It is OK to tell how to
get
admin help, but we need to make sure that we say, in the same
place,
how to get product support, and make the product support more
prominent by listing it first. That explains the ordering of
information on the contact page:
http://www.openoffice.org/contact_us.html
It is not perfect, but it gets most people closer to where they
want
to be.
which I why I wrote "sounds good to me".
Also, to the other idea, an alternative to a set of email aliases is
to use URL's of the form:
mailto:d...@openoffice.org?subject=[Pootle].
+1 that is a better idea, since we do not need to maintain extra
virtual
mail adresses
(I did not know that trix, thats pretty cool)
Yes, with this formatting it's OK.
However, we should extend the "contact_us.html" were needed to point
to
this site from, e.g., Wiki or Forum. No need to create a new page for
such purpose - ahm, if this was planned. ;-)
I updated the webpage and added some text and links at the end:
http://ooo-site.staging.apache.org/contact_us.html
Feel free to improve.
Does a user really need to subscribe to dev@ to get e.g. help with wiki
login ? I dont think that is very user friendly.
Indeed. Asking users that only need to resolve one problem to expose
their
private email addresses on a public list is not good, but asking them to
also subscribe to a list with a hundred email/day is really bad. Just
think
about the number of "please unsubscribe" emails that will come later...
Why not just have them enter an issue into BZ? We have categories for
these kinds of things. And an issue tracker is ideally suited
for...well... tracking issues. The reporter of the issue gets
updates, can follow up to questions, they don't need to expose their
address, it doesn't flood the list with unwanted traffic, it helps us
manage issues, etc.
-Rob
BZ requires registration also to enter an issue. I think using BZ is ideal
as opposed to "dev". Maybe there is a way to "nicely" usher in MWiki folks
to BZ.
BZ is already flooded enough with "issues" that are better suited in the
forums as they are more "How can I do this and that". IMHO no need to
linkmore of them to BZ.
Of course you don't have to subscribe to any mailing list. But when you
want an answer - and you expect one due to the technical problem you
want to have resolved - then it would be better; not everybody is
recognizing the new author as non-subscriber and writes the answer with
CC'ing the author.
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
