Task:Comments2Talk - Revision history

amigadave: fix link

2010-04-08T15:10:09Z

fix link

← Older revision		Revision as of 15:10, 8 April 2010
Line 11:		Line 11:
	There was also a big discussion and a plan at the time on [[/Task:ITt_Collaboration#ITt_application_catalog_feeds\|ITt application catalog feeds]], and this would be a straight forward implementation of that plan.		There was also a big discussion and a plan at the time on [[/Task:ITt_Collaboration#ITt_application_catalog_feeds\|ITt application catalog feeds]], and this would be a straight forward implementation of that plan.

-	Comments on [[Main ~~page~~\|Maemo wiki]], [http://bugs.maemo.org Maemo bugzilla] and [http://garage.maemo.org Maemo Garage] can stay the way they are. :)	+	Comments on [[Main Page\|Maemo wiki]], [http://bugs.maemo.org Maemo bugzilla] and [http://garage.maemo.org Maemo Garage] can stay the way they are. :)

	== Dependencies ==		== Dependencies ==

amigadave: links

2010-04-08T15:07:10Z

links

← Older revision		Revision as of 15:07, 8 April 2010
Line 9:		Line 9:
	The main reason to push this is the new Maemo Brainstorm, that ideally would be officially released with the new way of handling comments. Talk and Brainstorm are naturally tied together.		The main reason to push this is the new Maemo Brainstorm, that ideally would be officially released with the new way of handling comments. Talk and Brainstorm are naturally tied together.

-	There was also a big discussion and a plan at the time on [~~http://wiki.maemo.org~~/Task:ITt_Collaboration#ITt_application_catalog_feeds\|ITt application catalog feeds], and this would be a straight forward implementation of that plan.	+	There was also a big discussion and a plan at the time on [[/Task:ITt_Collaboration#ITt_application_catalog_feeds\|ITt application catalog feeds]], and this would be a straight forward implementation of that plan.

-	Comments on ~~http://~~wiki~~.maemo.org~~, http://bugs.maemo.org and http://garage.maemo.org can stay the way they are. :)	+	Comments on [[Main page\|Maemo wiki]], [http://bugs.maemo.org Maemo bugzilla] and [http://garage.maemo.org Maemo Garage] can stay the way they are. :)

	== Dependencies ==		== Dependencies ==

twaelti at 08:36, 22 October 2009

2009-10-22T08:36:44Z

← Older revision		Revision as of 08:36, 22 October 2009
Line 39:		Line 39:
	* It would be nice to offer a recommendation to [http://maemo.org/news/planet-maemo/ Planet Maemo] blogs willing to follow the practice - http://maemoteam.wordpress.com/ comes to mind.		* It would be nice to offer a recommendation to [http://maemo.org/news/planet-maemo/ Planet Maemo] blogs willing to follow the practice - http://maemoteam.wordpress.com/ comes to mind.
	* Same recommendation for [http://maemo.org/news/community/ Garage news] - it's probably not worth attempting to hack GForge to do that automatically.		* Same recommendation for [http://maemo.org/news/community/ Garage news] - it's probably not worth attempting to hack GForge to do that automatically.
		+	[[Category:Talk]]

qgil: /* Rationale */

2009-05-10T11:18:09Z

Rationale

← Older revision		Revision as of 11:18, 10 May 2009
Line 12:		Line 12:

	Comments on http://wiki.maemo.org, http://bugs.maemo.org and http://garage.maemo.org can stay the way they are. :)		Comments on http://wiki.maemo.org, http://bugs.maemo.org and http://garage.maemo.org can stay the way they are. :)
		+
		+	== Dependencies ==
		+
		+	[[Task:Single sign-on]] is a dependency to have this system working flawlessly. However, if we need to choose between waiting the full implementation or go ahead with e.g. Brainstorm and make users have twoi logins at the beginning, I would go for the latter. It all depends on the planned dates to complete Single Sign-On, Brainstorm and Comments2Talk.

	== In practice ==		== In practice ==

qgil: /* Rationale */

2009-05-10T10:57:54Z

Rationale

← Older revision		Revision as of 10:57, 10 May 2009
Line 9:		Line 9:
	The main reason to push this is the new Maemo Brainstorm, that ideally would be officially released with the new way of handling comments. Talk and Brainstorm are naturally tied together.		The main reason to push this is the new Maemo Brainstorm, that ideally would be officially released with the new way of handling comments. Talk and Brainstorm are naturally tied together.

-	There was also a big discussion and a plan at the time on [[http://wiki.maemo.org/Task:ITt_Collaboration#ITt_application_catalog_feeds\|ITt application catalog feeds]], and this would be a straight forward implementation of that plan.	+	There was also a big discussion and a plan at the time on [http://wiki.maemo.org/Task:ITt_Collaboration#ITt_application_catalog_feeds\|ITt application catalog feeds], and this would be a straight forward implementation of that plan.
		+
		+	Comments on http://wiki.maemo.org, http://bugs.maemo.org and http://garage.maemo.org can stay the way they are. :)

	== In practice ==		== In practice ==

qgil: /* In practice */

2009-05-10T10:56:21Z

In practice

← Older revision		Revision as of 10:56, 10 May 2009
Line 12:		Line 12:

	== In practice ==		== In practice ==
		+
		+	=== Brainstorm ===
		+	[[Task:Maemo_brainstorm\|The future Brainstorm]] is centered on creating ideas, proposing solutions ans rating them up/down. All this functionality is being designed as a Midgard CMS module and this is good. But comments on ideas are also allowed, and they could be much better handled in tmo threads.
		+
		+	This is where we should put our focus for a first sprint. As opposed to the rst of existing maemo.org channels, this is new and it is better that is released with the right infrastructure in place to avoid future changes, move of comments to a different system, etc.

	=== Downloads ===		=== Downloads ===
Line 19:		Line 24:
	* Question: a new application generates automatically a new thread or do we wait for a first commenter to click a link that would create it? Whatever is technically easier. Probably creation of a new thread by default is better anyway: more awareness to more users, even if then many threads risk to remain empty.		* Question: a new application generates automatically a new thread or do we wait for a first commenter to click a link that would create it? Whatever is technically easier. Probably creation of a new thread by default is better anyway: more awareness to more users, even if then many threads risk to remain empty.
	* Question: what happens to all the current comments and ratings? One possibility would be to keep what exists as it is and start with the new system with Maemo 5.		* Question: what happens to all the current comments and ratings? One possibility would be to keep what exists as it is and start with the new system with Maemo 5.
		+	* Question: by default new versions of an application would stay in the same thread - but what is a developer does a major upgrade in a same OS release, can he define a way to start a new thread?
		+
		+	=== News ===
		+	A new entry creates automatically a new thread in tmo where all the comments are handle. This applies to:
		+	* [http://maemo.org/news/announcements/ Announcements]
		+	* [http://maemo.org/news/events/ Events]
		+	* [http://maemo.org/community/council/ Council blog]
		+	* It would be nice to offer a recommendation to [http://maemo.org/news/planet-maemo/ Planet Maemo] blogs willing to follow the practice - http://maemoteam.wordpress.com/ comes to mind.
		+	* Same recommendation for [http://maemo.org/news/community/ Garage news] - it's probably not worth attempting to hack GForge to do that automatically.

qgil: New page: {{task|proposed}} == Rationale == Now there is http://talk.maemo.org - an excellent platform to handle comments and discussions in the Maemo community. It's much more powerful than the c...

2009-05-10T10:43:08Z

New page: {{task|proposed}} == Rationale == Now there is http://talk.maemo.org - an excellent platform to handle comments and discussions in the Maemo community. It's much more powerful than the c...

New page

{{task|proposed}}

== Rationale ==

Now there is http://talk.maemo.org - an excellent platform to handle comments and discussions in the Maemo community. It's much more powerful than the current infrastructure for comments in maemo.org, so why not use it.

The change would also bridge much better the ''traditional'' maemo.org and InternetTabletTalk communities: commenters on announcements, maemo.org blogs, downloads or brainstorm would land on talk.maemo.org and regular users of t.m.o would be more aware of what is being originated in other parts of maemo.org.

The main reason to push this is the new Maemo Brainstorm, that ideally would be officially released with the new way of handling comments. Talk and Brainstorm are naturally tied together.

There was also a big discussion and a plan at the time on [[http://wiki.maemo.org/Task:ITt_Collaboration#ITt_application_catalog_feeds|ITt application catalog feeds]], and this would be a straight forward implementation of that plan.

== In practice ==

=== Downloads ===
Reggie had created a spec but it is currently [http://www.internettablettalk.com/wiki/index.php?title=Maemo.org_Syndication gone]. A couple of thoughts while it is recovered:

* A page like http://maemo.org/downloads/product/OS2008/personal-menu/ should contain all the basic information but then the comments and votes would be originated in a tmo thread (the basic infrastructure is in place since tmo also handle 5 star ratings). Probably not easy, though.
* Question: a new application generates automatically a new thread or do we wait for a first commenter to click a link that would create it? Whatever is technically easier. Probably creation of a new thread by default is better anyway: more awareness to more users, even if then many threads risk to remain empty.
* Question: what happens to all the current comments and ratings? One possibility would be to keep what exists as it is and start with the new system with Maemo 5.