Revision history [back]

Please take a look at etherpad.org. I realise that live messaging may seem overkill when wikis would do or could do, but: there may be something valuable in marketing or just in getting things done (user-dev centric documentation) by having a place where customers, company, consumers and others can involve themselves more directly in occasionally concerted activities. It doesn't have to be from nothing, as you could put current public docs there as a launch stage.

Please take a look at etherpad.org. I realise that live messaging may seem overkill when wikis would do or could do, but: there may be something valuable in marketing or just in getting things done (user-dev centric documentation) by having a place where customers, company, consumers and others can involve themselves more directly in occasionally concerted activities. It doesn't have to be from nothing, as you could put current public docs there as a launch stage.

Please take a look at etherpad.org. I realise that live messaging may seem overkill when wikis would do or could do, but: there may be something valuable in marketing or just in getting things done (user-dev centric documentation) by having a place where customers, company, consumers and others can involve themselves more directly in occasionally concerted activities. It doesn't have to be from nothing, as you could put current public docs there as a launch stage.

Please take a look at etherpad.org. I realise that live messaging may seem overkill when wikis would do or could do, but: there may be something valuable in marketing or just in getting things done (user-dev centric documentation) by having a place where customers, company, consumers and others can involve themselves more directly in occasionally concerted activities. It doesn't have to be from nothing, as you could put current public docs there as a launch stage.

I didn't remove the second ? from the header because: https://together.jolla.com/question/87348/long-strings-in-short-text-fields-are-not-draggable-they-do-not-scroll/

Please take a look at etherpad.org. I realise that live messaging may seem overkill when wikis would do or could do, but: there may be something valuable in marketing or just in getting things done (user-dev centric documentation) by having a place where customers, company, consumers and others can involve themselves more directly in occasionally concerted activities. It doesn't have to be from nothing, as you could put current public docs there as a launch stage.

I Built-in Etherpad server-client software on the phone?

*I didn't remove the second ? from the header because: https://together.jolla.com/question/87348/long-strings-in-short-text-fields-are-not-draggable-they-do-not-scroll/https://together.jolla.com/question/87348/long-strings-in-short-text-fields-are-not-draggable-they-do-not-scroll/ *

Please take a look at use etherpad.orgEtherpad(s). I realise that live messaging may seem overkill when wikis would do or There is motivating value in even-nearer-to-live interaction. For example, consider user-developer centred documentation: a pad could do, but: there may be something valuable in marketing or just in getting things done (user-dev centric documentation) by having a place where create further connections between customers, company, suppliers, consumers and others others, especially benefitting the effort of those who find they work better, harder or more effectively when they see a collaborative document change, and grow, even as they supply amendments to the same process. They can involve themselves more directly participate in occasionally concerted activities.

It doesn't have to be from nothing, as you could put current public docs there as a launch stage.stage. This gamification of a difficult area (documentation) will build on the current processes afoot on this forum.

Built-in Etherpad server-client software on the phone?

Please use Etherpad(s). There is motivating value in even-nearer-to-live interaction. For example, consider user-developer centred documentation: a pad could create further connections between customers, suppliers, consumers and others, especially benefitting the effort of those who find they work better, harder or more effectively when they see a collaborative document change, and grow, even as they supply amendments to the same process. They can directly participate in concerted activities.

I humbly suggest that scheduled pad use oughtn't to be set up except, for example, between two or three editor-collaborators. It's hard to work as a crowd, so small groups might see more success. It doesn't have to be from nothing, nothing as you could put current public docs there as a launch stage. This gamification of a difficult area (documentation) will build on the current processes afoot on this forum.

Built-in Etherpad server-client software on the phone?

Please use Etherpad(s). There is motivating value in even-nearer-to-live interaction. For example, consider user-developer centred documentation: a pad could create further connections between customers, suppliers, consumers and others, especially benefitting the effort of those who find they work better, harder or more effectively when they see a collaborative document change, and grow, even as they supply amendments to the same process. They can directly participate in concerted activities.

I humbly suggest that scheduled pad use oughtn't to be set up except, for example, not try scheduled except between two or three editor-collaborators. It's hard to work as a crowd, so crowd and small groups might see more success. progress. It doesn't have to be from nothing as you could put nothing: use current public docs there as a launch stage. This gamification of a difficult area (documentation) will build stage on the current processes afoot on this forum.

Built-in Etherpad server-client software on the phone?together subdomain.

tl;dr Please use host Etherpad(s). .

There is motivating value in even-nearer-to-live interaction. For example, consider user-developer centred documentation: a pad could create further connections between customers, suppliers, consumers and others, especially benefitting the effort of those who find they work better, harder or more effectively when they see a collaborative document change, and grow, even as they supply amendments to the same process. They can directly participate in concerted activities.

I humbly suggest to not try scheduled except between two or three editor-collaborators. It's hard to work as a crowd and small groups might see more progress. It doesn't have to be from nothing: use current public docs as a launch stage on the together subdomain.