Features/Join Limits: Difference between revisions

Created page with "<noinclude>{{GoogleTrans-en}}{{TOCright}} Category:Feature Page Incomplete JoinLimits</noinclude> <!-- All fields on this form are required to be acc..."
 
Godiard (talk | contribs)
No edit summary
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<noinclude>{{GoogleTrans-en}}{{TOCright}}
<noinclude>[[Category:Feature Page Incomplete]]
[[Category:Feature Page Incomplete]]
[[Category:FeatureLanded|Join Limits]]
[[Category:Feature|JoinLimits]]</noinclude>
[[Category:Features requested by OLPC AU]]</noinclude>
 
<!-- All fields on this form are required to be accepted.
We also request that you maintain the same order of sections so that all of the feature pages are uniform.  -->
 
<!-- The actual name of your feature page should look something like: Features/Your Feature Name.  This keeps all features in the same namespace -->


== Summary ==
== Summary ==
Line 20: Line 15:
* Last updated: (5 November 2013)
* Last updated: (5 November 2013)
* Percentage of completion: 0%
* Percentage of completion: 0%
== Detailed Description ==
== Detailed Description ==


Line 28: Line 22:


If and only if the maximum_participant field is set is it used to set the limit of joiners.
If and only if the maximum_participant field is set is it used to set the limit of joiners.
Also see [[Features/Can share]]. The difference here is that I am proposing to leverage the maximum_participants setting as opposed to creating a new field in activity.info. Also, this is not just a binary share/no share.


== Benefit to Sugar ==
== Benefit to Sugar ==
Line 60: Line 56:


== Comments and Discussion ==
== Comments and Discussion ==
* http://lists.sugarlabs.org/archive/sugar-devel/2013-November/045586.html
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]
----
----
[[Category:Features requested by OLPC AU]]