You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Jürgen Schmidt <jo...@googlemail.com> on 2012/01/25 17:49:06 UTC
[CODE]: "Registration..." menu entry in the Help menu
Hi,
I have seen the "Registration..." menu entry in the "Help" menu. I tend
to remove this entry completely or at least remove it by default and
make it configurable for potential later use.
At the moment it opens a Url [1] in the browser that is not working at all.
Any opinions or comments on this?
If not I will remove it as proposed.
Juergen
[1] survey.services.openoffice.org/user/index.php
Re: [CODE]: "Registration..." menu entry in the Help menu
Posted by Jürgen Schmidt <jo...@googlemail.com>.
On 1/26/12 2:32 PM, Jürgen Schmidt wrote:
> On 1/26/12 2:15 PM, Rob Weir wrote:
>> 2012/1/25 Jürgen Schmidt<jo...@googlemail.com>:
>>> Hi,
>>>
>>> I have seen the "Registration..." menu entry in the "Help" menu. I
>>> tend to
>>> remove this entry completely or at least remove it by default and
>>> make it
>>> configurable for potential later use.
>>>
>>> At the moment it opens a Url [1] in the browser that is not working
>>> at all.
>>>
>>> Any opinions or comments on this?
>>>
>>
>> Clearly the current action of the Registration menu item --- a form
>> for user to fill out information and send to Oracle -- no longer is
>> useful for us.
>>
>> But is there anything like a registration that does make sense for us?
> I am not sure and I personally don't like it.
>
> But that was the reason why I would prefer to simply remove the menu
> entry and don't remove the feature completely. It can be done via a
> simple config item ;-)
>
>>
>> Or in general, what do want the "first launch" experience to be for
>> user, after they install?
> It think this is something different or do you mean the already disabled
> first start registration wizard?
>
> I really like for example the StartCenter from Symphony or also from the
> RedFlag Office. I think we should work on a better user experience on
> the start center. Help users to get started and solve their typical
> problems. For example easier access to the most often used templates, to
> the recent documents, finding help or documentation, ...
>
>>
>>> If not I will remove it as proposed.
>
> I will remove it for the next snapshot build via the config item. A
> change that can be easy reverted.
ok the comment was misleading, the config item only disable the menu. We
should probably remove it completely, make things easier.
Juergen
>
> Juergen
>
>>>
>>> Juergen
>>>
>>>
>>> [1] survey.services.openoffice.org/user/index.php
>
Re: [CODE]: "Registration..." menu entry in the Help menu
Posted by TJ Frazier <tj...@cfl.rr.com>.
@Dennis, in line,
On 1/28/2012 18:41, Dennis E. Hamilton wrote:
> @TJ
>
> Thanks for opening up some interesting aspects to think about
> concerning initial user experience and support for newcomers to AOO.
>
> One reaction: I see a big difference between configuring builds to
> have one more language-dependency and configuring a URL to sniff
> languages though. The life-cycle and skills/karma required could be
> quite different. What is a good way to invite broad participation in
> this area?
I don't see any need for a URL. I envision the Welcome doc as part of
the download.
>
> Also, I don't think the document should be put in a writable location
> if it is part of the install.
I tend to favor a writable location because it empowers the user. It
behooves us to remember that our software is a guest on the user's
hardware (programs that persistently forget this, on /my/ machine, tend
to end up in the bit-bucket). Also, every location is "writable" – just
some are easier than others.
However, considering the needs of multi-user central installations, I am
not unalterably opposed to an unalterable doc. We should merely mention
that users need to save any changed version to their own space.
>
> For writable documents, that seems to be something that is more
> appropriate for a sample or even part of an included mini-tutorial.
> It might then be better to identify them as templates so they will
> not over-write the initial file by default if modified and saved.
>
> Finally, as a means for feedback, encouraging exploration and
> contribution, wouldn't a link to a web/wiki page be better for that?
These are not mutually exclusive. We should have both.
>
> This is an interesting area. I wonder how to avoid scope creep and
> deal with the registration menu entry in a way that works for now and
> that can be expanded into a broader "welcome/starter" link. I know
> some first-run presentations tend to be sticky, with a way to stop it
> (and an indication on how to obtain it from the Help pull-down
> whenever it is to be revisited). Is this a candidate for that sort
> of thing?
I'm trying to design out any avoidable maintenance headaches. I envision
a simple link to a page like the Mwiki documentation:
http://wiki.services.openoffice.org/wiki/Documentation
where we always have to update links for different versions, new stuff,
&c. If we ever have a good "getting started" tutorial, it should be
listed there. The link in the Welcome doc wouldn't change.
I also see the Help menu link ("Welcome") as a simple "open the
Welcome.odt doc" command, which also wouldn't change. --/tj/
>
> -----Original Message----- From: TJ Frazier
> [mailto:tjfrazier@cfl.rr.com] Sent: Saturday, January 28, 2012 14:34
> To: ooo-dev@incubator.apache.org Subject: Re: [CODE]:
> "Registration..." menu entry in the Help menu
>
> Hi, all! Comments in-line.
>
> On 1/28/2012 14:23, Dennis E. Hamilton wrote:
>> If the welcome document is stored locally in the installation
>> locally, having it as an ODT might work.
>>
>> It does mean that translations will be required.
>>
>> Opening of a web page has the advantage of being able to adapt to
>> browser language settings on a server and also being able to
>> update the document over time. The URL could also be release-
>> specific (which would allow further customization).
>>
>> I think it is also important to consider the threat surface of
>> both approaches, especially if the document will be opened or the
>> URL fetched under the privileges of the install process.
>>
>> - Dennis
>>
>> PS: I suppose this is also an area that might be subject to
>> distribution-specific customization, including in-enterprise
>> distributions.
>>
> @Dennis: all good points to keep in mind, but please also keep in
> mind that the same work has to be done for a welcome in a doc or on a
> web page (customize, translate,&c.). We have lots of folks who can do
> that in Writer ...
>
>> -----Original Message----- From: Kay Schenk
>> [mailto:kay.schenk@gmail.com] Sent: Saturday, January 28, 2012
>> 09:37 To: ooo-dev@incubator.apache.org Subject: Re: [CODE]:
>> "Registration..." menu entry in the Help menu
>>
>> On Thu, Jan 26, 2012 at 8:02 AM, Rob Weir<ro...@apache.org>
>> wrote: [ ... ]
>>> The closest to registration that we might have is to encourage
>>> the user to sign up for the ooo-announce list. But this is just
>>> one of several things we want to tell the user. Maybe after
>>> install we automatically launch a web page, or even load an ODF
>>> document, with content like:
>>>
>>>
>>> -- Welcome message from the project -- Highlights of the
>>> release, link to detailed release notes -- Where to for
>>> documentation -- Where to go for support -- Extensions and
>>> templates informations -- Invitation / Instructions on joining
>>> ooo-announce mailing list -- Links to official social media, our
>>> blog. Google+, Twitter, Facebook, etc.
>>>
>>> If we do this in ODF format, as a document, then we can also use
>>> it as a quick demonstration of the capabilities of the editor,
>>> showing a really good looking, well formatted document, etc. A
>>> good first experience for the user.
>>>
>>
>> +1
>>
>> I like this proposal a LOT! We tell them something interesting and
>> we don't have to maintain any additional DBs. Much less hassle in
>> the long run! :) So simple, and yet so good!
>>
>>
> +1 also. A three-bang good idea!!! Some more thoughts: * Store the
> doc as writable, so the user can make changes. Empowerment. * Turn on
> the Record Changes feature (mention this in the doc), and solicit
> advice from the users as to what is helpful, what is not, and what
> would be helpful. /tj/
>
>> [ ... ]
>>
>>
>>
>
>
>
>
RE: [CODE]: "Registration..." menu entry in the Help menu
Posted by "Dennis E. Hamilton" <de...@acm.org>.
@TJ
Thanks for opening up some interesting aspects to think about concerning initial user experience and support for newcomers to AOO.
One reaction: I see a big difference between configuring builds to have one more language-dependency and configuring a URL to sniff languages though. The life-cycle and skills/karma required could be quite different. What is a good way to invite broad participation in this area?
Also, I don't think the document should be put in a writable location if it is part of the install.
For writable documents, that seems to be something that is more appropriate for a sample or even part of an included mini-tutorial. It might then be better to identify them as templates so they will not over-write the initial file by default if modified and saved.
Finally, as a means for feedback, encouraging exploration and contribution, wouldn't a link to a web/wiki page be better for that?
This is an interesting area. I wonder how to avoid scope creep and deal with the registration menu entry in a way that works for now and that can be expanded into a broader "welcome/starter" link. I know some first-run presentations tend to be sticky, with a way to stop it (and an indication on how to obtain it from the Help pull-down whenever it is to be revisited). Is this a candidate for that sort of thing?
-----Original Message-----
From: TJ Frazier [mailto:tjfrazier@cfl.rr.com]
Sent: Saturday, January 28, 2012 14:34
To: ooo-dev@incubator.apache.org
Subject: Re: [CODE]: "Registration..." menu entry in the Help menu
Hi, all! Comments in-line.
On 1/28/2012 14:23, Dennis E. Hamilton wrote:
> If the welcome document is stored locally in the installation
> locally, having it as an ODT might work.
>
> It does mean that translations will be required.
>
> Opening of a web page has the advantage of being able to adapt to
> browser language settings on a server and also being able to update
> the document over time. The URL could also be release- specific
> (which would allow further customization).
>
> I think it is also important to consider the threat surface of both
> approaches, especially if the document will be opened or the URL
> fetched under the privileges of the install process.
>
> - Dennis
>
> PS: I suppose this is also an area that might be subject to
> distribution-specific customization, including in-enterprise
> distributions.
>
@Dennis: all good points to keep in mind, but please also keep in mind
that the same work has to be done for a welcome in a doc or on a web
page (customize, translate, &c.). We have lots of folks who can do that
in Writer ...
> -----Original Message----- From: Kay Schenk
> [mailto:kay.schenk@gmail.com] Sent: Saturday, January 28, 2012 09:37
> To: ooo-dev@incubator.apache.org Subject: Re: [CODE]:
> "Registration..." menu entry in the Help menu
>
> On Thu, Jan 26, 2012 at 8:02 AM, Rob Weir<ro...@apache.org>
> wrote: [ ... ]
>> The closest to registration that we might have is to encourage the
>> user to sign up for the ooo-announce list. But this is just one
>> of several things we want to tell the user. Maybe after install
>> we automatically launch a web page, or even load an ODF document,
>> with content like:
>>
>>
>> -- Welcome message from the project -- Highlights of the release,
>> link to detailed release notes -- Where to for documentation --
>> Where to go for support -- Extensions and templates informations --
>> Invitation / Instructions on joining ooo-announce mailing list --
>> Links to official social media, our blog. Google+, Twitter,
>> Facebook, etc.
>>
>> If we do this in ODF format, as a document, then we can also use it
>> as a quick demonstration of the capabilities of the editor, showing
>> a really good looking, well formatted document, etc. A good first
>> experience for the user.
>>
>
> +1
>
> I like this proposal a LOT! We tell them something interesting and
> we don't have to maintain any additional DBs. Much less hassle in the
> long run! :) So simple, and yet so good!
>
>
+1 also. A three-bang good idea!!! Some more thoughts:
* Store the doc as writable, so the user can make changes. Empowerment.
* Turn on the Record Changes feature (mention this in the doc), and
solicit advice from the users as to what is helpful, what is not, and
what would be helpful.
/tj/
> [ ... ]
>
>
>
Re: [CODE]: "Registration..." menu entry in the Help menu
Posted by TJ Frazier <tj...@cfl.rr.com>.
Hi, all! Comments in-line.
On 1/28/2012 14:23, Dennis E. Hamilton wrote:
> If the welcome document is stored locally in the installation
> locally, having it as an ODT might work.
>
> It does mean that translations will be required.
>
> Opening of a web page has the advantage of being able to adapt to
> browser language settings on a server and also being able to update
> the document over time. The URL could also be release- specific
> (which would allow further customization).
>
> I think it is also important to consider the threat surface of both
> approaches, especially if the document will be opened or the URL
> fetched under the privileges of the install process.
>
> - Dennis
>
> PS: I suppose this is also an area that might be subject to
> distribution-specific customization, including in-enterprise
> distributions.
>
@Dennis: all good points to keep in mind, but please also keep in mind
that the same work has to be done for a welcome in a doc or on a web
page (customize, translate, &c.). We have lots of folks who can do that
in Writer ...
> -----Original Message----- From: Kay Schenk
> [mailto:kay.schenk@gmail.com] Sent: Saturday, January 28, 2012 09:37
> To: ooo-dev@incubator.apache.org Subject: Re: [CODE]:
> "Registration..." menu entry in the Help menu
>
> On Thu, Jan 26, 2012 at 8:02 AM, Rob Weir<ro...@apache.org>
> wrote: [ ... ]
>> The closest to registration that we might have is to encourage the
>> user to sign up for the ooo-announce list. But this is just one
>> of several things we want to tell the user. Maybe after install
>> we automatically launch a web page, or even load an ODF document,
>> with content like:
>>
>>
>> -- Welcome message from the project -- Highlights of the release,
>> link to detailed release notes -- Where to for documentation --
>> Where to go for support -- Extensions and templates informations --
>> Invitation / Instructions on joining ooo-announce mailing list --
>> Links to official social media, our blog. Google+, Twitter,
>> Facebook, etc.
>>
>> If we do this in ODF format, as a document, then we can also use it
>> as a quick demonstration of the capabilities of the editor, showing
>> a really good looking, well formatted document, etc. A good first
>> experience for the user.
>>
>
> +1
>
> I like this proposal a LOT! We tell them something interesting and
> we don't have to maintain any additional DBs. Much less hassle in the
> long run! :) So simple, and yet so good!
>
>
+1 also. A three-bang good idea!!! Some more thoughts:
* Store the doc as writable, so the user can make changes. Empowerment.
* Turn on the Record Changes feature (mention this in the doc), and
solicit advice from the users as to what is helpful, what is not, and
what would be helpful.
/tj/
> [ ... ]
>
>
>
RE: [CODE]: "Registration..." menu entry in the Help menu
Posted by "Dennis E. Hamilton" <de...@acm.org>.
If the welcome document is stored locally in the installation locally, having it as an ODT might work.
It does mean that translations will be required.
Opening of a web page has the advantage of being able to adapt to browser language settings on a server and also being able to update the document over time. The URL could also be release- specific (which would allow further customization).
I think it is also important to consider the threat surface of both approaches, especially if the document will be opened or the URL fetched under the privileges of the install process.
- Dennis
PS: I suppose this is also an area that might be subject to distribution-specific customization, including in-enterprise distributions.
-----Original Message-----
From: Kay Schenk [mailto:kay.schenk@gmail.com]
Sent: Saturday, January 28, 2012 09:37
To: ooo-dev@incubator.apache.org
Subject: Re: [CODE]: "Registration..." menu entry in the Help menu
On Thu, Jan 26, 2012 at 8:02 AM, Rob Weir <ro...@apache.org> wrote:
[ ... ]
> The closest to registration that we might have is to encourage the
> user to sign up for the ooo-announce list. But this is just one of
> several things we want to tell the user. Maybe after install we
> automatically launch a web page, or even load an ODF document, with
> content like:
>
>
> -- Welcome message from the project
> -- Highlights of the release, link to detailed release notes
> -- Where to for documentation
> -- Where to go for support
> -- Extensions and templates informations
> -- Invitation / Instructions on joining ooo-announce mailing list
> -- Links to official social media, our blog. Google+, Twitter, Facebook,
> etc.
>
> If we do this in ODF format, as a document, then we can also use it as
> a quick demonstration of the capabilities of the editor, showing a
> really good looking, well formatted document, etc. A good first
> experience for the user.
>
+1
I like this proposal a LOT! We tell them something interesting and we
don't have to maintain any additional DBs. Much less hassle in the long
run! :) So simple, and yet so good!
[ ... ]
Re: [CODE]: "Registration..." menu entry in the Help menu
Posted by Kay Schenk <ka...@gmail.com>.
On Thu, Jan 26, 2012 at 8:02 AM, Rob Weir <ro...@apache.org> wrote:
> 2012/1/26 Jürgen Schmidt <jo...@googlemail.com>:
> > On 1/26/12 2:15 PM, Rob Weir wrote:
> >>
> >> 2012/1/25 Jürgen Schmidt<jo...@googlemail.com>:
> >>>
> >>> Hi,
> >>>
> >>> I have seen the "Registration..." menu entry in the "Help" menu. I tend
> >>> to
> >>> remove this entry completely or at least remove it by default and make
> it
> >>> configurable for potential later use.
> >>>
> >>> At the moment it opens a Url [1] in the browser that is not working at
> >>> all.
> >>>
> >>> Any opinions or comments on this?
> >>>
> >>
> >> Clearly the current action of the Registration menu item --- a form
> >> for user to fill out information and send to Oracle -- no longer is
> >> useful for us.
> >>
> >> But is there anything like a registration that does make sense for us?
> >
> > I am not sure and I personally don't like it.
> >
> > But that was the reason why I would prefer to simply remove the menu
> entry
> > and don't remove the feature completely. It can be done via a simple
> config
> > item ;-)
> >
> >
> >>
> >> Or in general, what do want the "first launch" experience to be for
> >> user, after they install?
> >
> > It think this is something different or do you mean the already disabled
> > first start registration wizard?
> >
>
> The closest to registration that we might have is to encourage the
> user to sign up for the ooo-announce list. But this is just one of
> several things we want to tell the user. Maybe after install we
> automatically launch a web page, or even load an ODF document, with
> content like:
>
>
> -- Welcome message from the project
> -- Highlights of the release, link to detailed release notes
> -- Where to for documentation
> -- Where to go for support
> -- Extensions and templates informations
> -- Invitation / Instructions on joining ooo-announce mailing list
> -- Links to official social media, our blog. Google+, Twitter, Facebook,
> etc.
>
> If we do this in ODF format, as a document, then we can also use it as
> a quick demonstration of the capabilities of the editor, showing a
> really good looking, well formatted document, etc. A good first
> experience for the user.
>
+1
I like this proposal a LOT! We tell them something interesting and we
don't have to maintain any additional DBs. Much less hassle in the long
run! :) So simple, and yet so good!
>
> So not really registration -- we're not collecting names and addresses
> for marketing purposes. But I think getting users connected via
> ooo-announce and social media is a key part of having an effective
> relationship with the users going forward. Such opt-in relationships
> are very powerful, especially with the social media, since they are
> two-way communications.
>
> > I really like for example the StartCenter from Symphony or also from the
> > RedFlag Office. I think we should work on a better user experience on the
> > start center. Help users to get started and solve their typical problems.
> > For example easier access to the most often used templates, to the recent
> > documents, finding help or documentation, ...
> >
> >
> >>
> >>> If not I will remove it as proposed.
> >
> >
> > I will remove it for the next snapshot build via the config item. A
> change
> > that can be easy reverted.
> >
> > Juergen
> >
> >>>
> >>> Juergen
> >>>
> >>>
> >>> [1] survey.services.openoffice.org/user/index.php
> >
> >
>
--
----------------------------------------------------------------------------------------
MzK
"Follow your bliss."
-- attributed to Joseph Campbell
Re: [CODE]: "Registration..." menu entry in the Help menu
Posted by Kay Schenk <ka...@gmail.com>.
Hi Nancy K --
On Thu, Jan 26, 2012 at 8:30 AM, Nancy K <na...@yahoo.com> wrote:
> I would like to add that one of the reasons I have not jumped in to help,
> is that I do not know where my skills could best be applied. I have the
> time, I have college training in PHP/mySQL, Javascript, web design AS
> degree - but have not used these in a year, so feel my tools of the trade
> slipping. That is what I would get out of volunteering - pride of
> finishing a job, helping this project helps me at the same time.
>
> What I would like to see is a radio check box of skills (Xhtml, PHP, CSS,
> CSS3, etc) that would pop up a link to where those skills could best be
> used for starters. This way I can jump in quicker - and then at a later
> time start branching into skill areas I have no experience in but want to
> try.
>
> Right now I am getting the emails from this list
> ooo-dev@incubator.apache.org and listening to descriptions of progress
> that I am not familiar. There is a lot of great information on your sites
> and I am eager to start somewhere - but poor Rob cannot be expected to
> answer everyone.
No "poor Rob" is not the only one who can or is even expected to answer all
questions. That responsibility falls on the "community" at large.
> I think radio buttons or a site map for getting started - or something
> like a presentation of 'If you have these skills, we currently need your
> help (link)there'.
>
You are right -- we don't really have anything like this on the "Get
Involved" page, for example, and we need to. I don't know if we'll
incorporate the "radio links" you suggest but please check back (say a week
from today) to
http://incubator.apache.org/openofficeorg/get-involved.html
and hopefully you'll see more specific direction/ideas for how to get
involved.
>
> Please let me know if this already exists - I have looked around the
> wiki's and development and web design areas and I really do like to
> organize information - if that is where I could help?
>
Do apply for a wiki account -- this is a very easy way to get involved --
and organize away! Yes, it's a bit daunting at first...but thanks for
stopping by and showing such interest!
Nancy
>
> Nancy Web Design
> Free 24 hour pass to lynda.com.
> Video courses on SEO, CMS,
> Design and Software Courses
>
>
>
> ________________________________
> From: Rob Weir <ro...@apache.org>
> To: ooo-dev@incubator.apache.org
> Sent: Thursday, January 26, 2012 8:02 AM
> Subject: Re: [CODE]: "Registration..." menu entry in the Help menu
>
> 2012/1/26 Jürgen Schmidt <jo...@googlemail.com>:
> > On 1/26/12 2:15 PM, Rob Weir wrote:
> >>
> >> 2012/1/25 Jürgen Schmidt<jo...@googlemail.com>:
> >>>
> >>> Hi,
> >>>
> >>> I have seen the "Registration..." menu entry in the "Help" menu. I tend
> >>> to
> >>> remove this entry completely or at least remove it by default and make
> it
> >>> configurable for potential later use.
> >>>
> >>> At the moment it opens a Url [1] in the browser that is not working at
> >>> all.
> >>>
> >>> Any opinions or comments on this?
> >>>
> >>
> >> Clearly the current action of the Registration menu item --- a form
> >> for user to fill out information and send to Oracle -- no longer is
> >> useful for us.
> >>
> >> But is there anything like a registration that does make sense for us?
> >
> > I am not sure and I personally don't like it.
> >
> > But that was the reason why I would prefer to simply remove the menu
> entry
> > and don't remove the feature completely. It can be done via a simple
> config
> > item ;-)
> >
> >
> >>
> >> Or in general, what do want the "first launch" experience to be for
> >> user, after they install?
> >
> > It think this is something different or do you mean the already disabled
> > first start registration wizard?
> >
>
> The closest to registration that we might have is to encourage the
> user to sign up for the ooo-announce list. But this is just one of
> several things we want to tell the user. Maybe after install we
> automatically launch a web page, or even load an ODF document, with
> content like:
>
>
> -- Welcome message from the project
> -- Highlights of the release, link to detailed release notes
> -- Where to for documentation
> -- Where to go for support
> -- Extensions and templates informations
> -- Invitation / Instructions on joining ooo-announce mailing list
> -- Links to official social media, our blog. Google+, Twitter, Facebook,
> etc.
>
> If we do this in ODF format, as a document, then we can also use it as
> a quick demonstration of the capabilities of the editor, showing a
> really good looking, well formatted document, etc. A good first
> experience for the user.
>
> So not really registration -- we're not collecting names and addresses
> for marketing purposes. But I think getting users connected via
> ooo-announce and social media is a key part of having an effective
> relationship with the users going forward. Such opt-in relationships
> are very powerful, especially with the social media, since they are
> two-way communications.
>
> > I really like for example the StartCenter from Symphony or also from the
> > RedFlag Office. I think we should work on a better user experience on the
> > start center. Help users to get started and solve their typical problems.
> > For example easier access to the most often used templates, to the recent
> > documents, finding help or documentation, ...
> >
> >
> >>
> >>> If not I will remove it as proposed.
> >
> >
> > I will remove it for the next snapshot build via the config item. A
> change
> > that can be easy reverted.
> >
> > Juergen
> >
> >>>
> >>> Juergen
> >>>
> >>>
> >>> [1] survey.services.openoffice.org/user/index.php
> >
> >
>
--
----------------------------------------------------------------------------------------
MzK
"Follow your bliss."
-- attributed to Joseph Campbell
Re: [CODE]: "Registration..." menu entry in the Help menu
Posted by Nancy K <na...@yahoo.com>.
I would like to add that one of the reasons I have not jumped in to help, is that I do not know where my skills could best be applied. I have the time, I have college training in PHP/mySQL, Javascript, web design AS degree - but have not used these in a year, so feel my tools of the trade slipping. That is what I would get out of volunteering - pride of finishing a job, helping this project helps me at the same time.
What I would like to see is a radio check box of skills (Xhtml, PHP, CSS, CSS3, etc) that would pop up a link to where those skills could best be used for starters. This way I can jump in quicker - and then at a later time start branching into skill areas I have no experience in but want to try.
Right now I am getting the emails from this list ooo-dev@incubator.apache.org and listening to descriptions of progress that I am not familiar. There is a lot of great information on your sites and I am eager to start somewhere - but poor Rob cannot be expected to answer everyone. I think radio buttons or a site map for getting started - or something like a presentation of 'If you have these skills, we currently need your help (link)there'.
Please let me know if this already exists - I have looked around the wiki's and development and web design areas and I really do like to organize information - if that is where I could help?
Nancy
Nancy Web Design
Free 24 hour pass to lynda.com.
Video courses on SEO, CMS,
Design and Software Courses
________________________________
From: Rob Weir <ro...@apache.org>
To: ooo-dev@incubator.apache.org
Sent: Thursday, January 26, 2012 8:02 AM
Subject: Re: [CODE]: "Registration..." menu entry in the Help menu
2012/1/26 Jürgen Schmidt <jo...@googlemail.com>:
> On 1/26/12 2:15 PM, Rob Weir wrote:
>>
>> 2012/1/25 Jürgen Schmidt<jo...@googlemail.com>:
>>>
>>> Hi,
>>>
>>> I have seen the "Registration..." menu entry in the "Help" menu. I tend
>>> to
>>> remove this entry completely or at least remove it by default and make it
>>> configurable for potential later use.
>>>
>>> At the moment it opens a Url [1] in the browser that is not working at
>>> all.
>>>
>>> Any opinions or comments on this?
>>>
>>
>> Clearly the current action of the Registration menu item --- a form
>> for user to fill out information and send to Oracle -- no longer is
>> useful for us.
>>
>> But is there anything like a registration that does make sense for us?
>
> I am not sure and I personally don't like it.
>
> But that was the reason why I would prefer to simply remove the menu entry
> and don't remove the feature completely. It can be done via a simple config
> item ;-)
>
>
>>
>> Or in general, what do want the "first launch" experience to be for
>> user, after they install?
>
> It think this is something different or do you mean the already disabled
> first start registration wizard?
>
The closest to registration that we might have is to encourage the
user to sign up for the ooo-announce list. But this is just one of
several things we want to tell the user. Maybe after install we
automatically launch a web page, or even load an ODF document, with
content like:
-- Welcome message from the project
-- Highlights of the release, link to detailed release notes
-- Where to for documentation
-- Where to go for support
-- Extensions and templates informations
-- Invitation / Instructions on joining ooo-announce mailing list
-- Links to official social media, our blog. Google+, Twitter, Facebook, etc.
If we do this in ODF format, as a document, then we can also use it as
a quick demonstration of the capabilities of the editor, showing a
really good looking, well formatted document, etc. A good first
experience for the user.
So not really registration -- we're not collecting names and addresses
for marketing purposes. But I think getting users connected via
ooo-announce and social media is a key part of having an effective
relationship with the users going forward. Such opt-in relationships
are very powerful, especially with the social media, since they are
two-way communications.
> I really like for example the StartCenter from Symphony or also from the
> RedFlag Office. I think we should work on a better user experience on the
> start center. Help users to get started and solve their typical problems.
> For example easier access to the most often used templates, to the recent
> documents, finding help or documentation, ...
>
>
>>
>>> If not I will remove it as proposed.
>
>
> I will remove it for the next snapshot build via the config item. A change
> that can be easy reverted.
>
> Juergen
>
>>>
>>> Juergen
>>>
>>>
>>> [1] survey.services.openoffice.org/user/index.php
>
>
Re: [CODE]: "Registration..." menu entry in the Help menu
Posted by Rob Weir <ro...@apache.org>.
2012/1/26 Jürgen Schmidt <jo...@googlemail.com>:
> On 1/26/12 2:15 PM, Rob Weir wrote:
>>
>> 2012/1/25 Jürgen Schmidt<jo...@googlemail.com>:
>>>
>>> Hi,
>>>
>>> I have seen the "Registration..." menu entry in the "Help" menu. I tend
>>> to
>>> remove this entry completely or at least remove it by default and make it
>>> configurable for potential later use.
>>>
>>> At the moment it opens a Url [1] in the browser that is not working at
>>> all.
>>>
>>> Any opinions or comments on this?
>>>
>>
>> Clearly the current action of the Registration menu item --- a form
>> for user to fill out information and send to Oracle -- no longer is
>> useful for us.
>>
>> But is there anything like a registration that does make sense for us?
>
> I am not sure and I personally don't like it.
>
> But that was the reason why I would prefer to simply remove the menu entry
> and don't remove the feature completely. It can be done via a simple config
> item ;-)
>
>
>>
>> Or in general, what do want the "first launch" experience to be for
>> user, after they install?
>
> It think this is something different or do you mean the already disabled
> first start registration wizard?
>
The closest to registration that we might have is to encourage the
user to sign up for the ooo-announce list. But this is just one of
several things we want to tell the user. Maybe after install we
automatically launch a web page, or even load an ODF document, with
content like:
-- Welcome message from the project
-- Highlights of the release, link to detailed release notes
-- Where to for documentation
-- Where to go for support
-- Extensions and templates informations
-- Invitation / Instructions on joining ooo-announce mailing list
-- Links to official social media, our blog. Google+, Twitter, Facebook, etc.
If we do this in ODF format, as a document, then we can also use it as
a quick demonstration of the capabilities of the editor, showing a
really good looking, well formatted document, etc. A good first
experience for the user.
So not really registration -- we're not collecting names and addresses
for marketing purposes. But I think getting users connected via
ooo-announce and social media is a key part of having an effective
relationship with the users going forward. Such opt-in relationships
are very powerful, especially with the social media, since they are
two-way communications.
> I really like for example the StartCenter from Symphony or also from the
> RedFlag Office. I think we should work on a better user experience on the
> start center. Help users to get started and solve their typical problems.
> For example easier access to the most often used templates, to the recent
> documents, finding help or documentation, ...
>
>
>>
>>> If not I will remove it as proposed.
>
>
> I will remove it for the next snapshot build via the config item. A change
> that can be easy reverted.
>
> Juergen
>
>>>
>>> Juergen
>>>
>>>
>>> [1] survey.services.openoffice.org/user/index.php
>
>
Re: [CODE]: "Registration..." menu entry in the Help menu
Posted by Jürgen Schmidt <jo...@googlemail.com>.
On 1/26/12 2:15 PM, Rob Weir wrote:
> 2012/1/25 Jürgen Schmidt<jo...@googlemail.com>:
>> Hi,
>>
>> I have seen the "Registration..." menu entry in the "Help" menu. I tend to
>> remove this entry completely or at least remove it by default and make it
>> configurable for potential later use.
>>
>> At the moment it opens a Url [1] in the browser that is not working at all.
>>
>> Any opinions or comments on this?
>>
>
> Clearly the current action of the Registration menu item --- a form
> for user to fill out information and send to Oracle -- no longer is
> useful for us.
>
> But is there anything like a registration that does make sense for us?
I am not sure and I personally don't like it.
But that was the reason why I would prefer to simply remove the menu
entry and don't remove the feature completely. It can be done via a
simple config item ;-)
>
> Or in general, what do want the "first launch" experience to be for
> user, after they install?
It think this is something different or do you mean the already disabled
first start registration wizard?
I really like for example the StartCenter from Symphony or also from the
RedFlag Office. I think we should work on a better user experience on
the start center. Help users to get started and solve their typical
problems. For example easier access to the most often used templates, to
the recent documents, finding help or documentation, ...
>
>> If not I will remove it as proposed.
I will remove it for the next snapshot build via the config item. A
change that can be easy reverted.
Juergen
>>
>> Juergen
>>
>>
>> [1] survey.services.openoffice.org/user/index.php
Re: [CODE]: "Registration..." menu entry in the Help menu
Posted by Rob Weir <ro...@apache.org>.
2012/1/25 Jürgen Schmidt <jo...@googlemail.com>:
> Hi,
>
> I have seen the "Registration..." menu entry in the "Help" menu. I tend to
> remove this entry completely or at least remove it by default and make it
> configurable for potential later use.
>
> At the moment it opens a Url [1] in the browser that is not working at all.
>
> Any opinions or comments on this?
>
Clearly the current action of the Registration menu item --- a form
for user to fill out information and send to Oracle -- no longer is
useful for us.
But is there anything like a registration that does make sense for us?
Or in general, what do want the "first launch" experience to be for
user, after they install?
> If not I will remove it as proposed.
>
> Juergen
>
>
> [1] survey.services.openoffice.org/user/index.php
Re: [CODE]: "Registration..." menu entry in the Help menu
Posted by TJ Frazier <tj...@cfl.rr.com>.
On 1/25/2012 11:49, Jürgen Schmidt wrote:
> Hi,
>
> I have seen the "Registration..." menu entry in the "Help" menu. I tend
> to remove this entry completely or at least remove it by default and
> make it configurable for potential later use.
>
> At the moment it opens a Url [1] in the browser that is not working at all.
>
> Any opinions or comments on this?
>
> If not I will remove it as proposed.
>
> Juergen
>
>
> [1] survey.services.openoffice.org/user/index.php
>
>
When I try from the Help menu in 3.3, I get the Oracle site:
https://hs-ws1.oracle.com/RegistrationWeb/registration/default/en_US/register-login.jsp?legacy=true&tgtPrd=OpenOffice.org&prd=registration&uuid=urn%3Ast%3A4e5ecde9-d047-4889-9767-fbdb713cf09c
which is certainly not what we want, whether or not it works.
+1 for remove.
/tj/
Re: [CODE]: "Registration..." menu entry in the Help menu
Posted by Oliver-Rainer Wittmann <or...@googlemail.com>.
Hi,
On 25.01.2012 17:49, Jürgen Schmidt wrote:
> Hi,
>
> I have seen the "Registration..." menu entry in the "Help" menu. I tend to
> remove this entry completely or at least remove it by default and make it
> configurable for potential later use.
>
> At the moment it opens a Url [1] in the browser that is not working at all.
>
> Any opinions or comments on this?
>
> If not I will remove it as proposed.
>
> Juergen
>
>
> [1] survey.services.openoffice.org/user/index.php
+1 for removal
Best regards, Oliver.