I think most of us agreed that the current registration API (the "register" param) isn't optimal. We should probably have a specific interface/API for that.
It could be an interface on Protocol objects (Bug #20774).
If you are talking about the first time registration
that is offered users at first run:
1. We should also discuss the front end (GUI) for this.
2. We should also discuss the data collected.
3. We should also consider larger entities (like schools).
Please tell me if it is worth to file additional bugs for
1. As we have parallel installations of LibO (partly
still Ooo) and MS-O, I observed first time users
considering the registration dialogue as a bug,
and switching straight away to the other office.
2. Not only to back up my arguments that LibO is very
apt for schools, I'd appreciate some stats about
how many schools are using LibO. An additional list
of such reference schools would be nice to have, as well.
I'd suggest a check box: Is your installation part of a
larger entity/company, and if so, present an additional
form dialogue: type of institution, amount of work
stations, employees; maybe also:
(i) If you are not a representative of your site,
could you possibly state an email address where to
ask for an official registration of your company?
(ii) If you are a represenative...
3. Maybe in exchange for registering schools etc.
officially (and allowing us to name them), we could
offer special tweaks to roll out LibO within their
network, disabling the first run registration dialogue
or centralising settings (server based).
* * *
Hopefully I didn't jump onto a dead horse, just
didn't dare open a brand new ticket for this.
(In reply to comment #2)
> If you are talking about the first time registration
> that is offered users at first run:
Did you mean to add this comment to a libreoffice bug? This is a bug against the Telepathy D-Bus specification.
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-spec/issues/40.