Group Management System - Revision history

Zehra: added category

2016-12-05T17:02:53Z

added category

← Older revision		Revision as of 17:02, 5 December 2016
Line 47:		Line 47:

	[[Category:Enhancements]]		[[Category:Enhancements]]
			[[Category:Group Manager]]

JeffM2501: Remove TODO group, that is what the version planing pages are for

2013-02-10T08:20:06Z

Remove TODO group, that is what the version planing pages are for

← Older revision		Revision as of 08:20, 10 February 2013
Line 46:		Line 46:
	The second issue will be handling groups with multiple leaders, or organizations that don't have a consistent set of leaders (as in, ORG.GROUP1 and ORG.GROUP2 have leaders that do not overlap). This probably won't be a huge issue for most organizations, but it will still be something that has to be handled.		The second issue will be handling groups with multiple leaders, or organizations that don't have a consistent set of leaders (as in, ORG.GROUP1 and ORG.GROUP2 have leaders that do not overlap). This probably won't be a huge issue for most organizations, but it will still be something that has to be handled.

	~~[[Category:TODO]]~~
	[[Category:Enhancements]]		[[Category:Enhancements]]

Grans Remedy: /* Web Interface */

2011-04-03T07:33:02Z

Web Interface

← Older revision		Revision as of 07:33, 3 April 2011
Line 19:		Line 19:
	Organization administrator can create any number of user groups. User group names need to only be unique in the organization they belong to. User groups can have any number of members, pulled from the BZFlag user database. The group membership should store the BZID of the user to allow for name changes. Founders should be able to create, destroy, and rename user groups.		Organization administrator can create any number of user groups. User group names need to only be unique in the organization they belong to. User groups can have any number of members, pulled from the BZFlag user database. The group membership should store the BZID of the user to allow for name changes. Founders should be able to create, destroy, and rename user groups.

	Groups should also have a description field that can be edited by any founder, to identify the group. All members of the group should be able to see this description. When a user is added to a group they should be notified as well. Groups shall be either ''private'' or ''public''. A ''private'' group is one where only members of that group can see the group and its members.		Groups should also have a description field that can be edited by any founder, to identify the group. All members of the group should be able to see this description. When a user is added to a group they should be notified as well. Groups shall be either ''private'' or ''public''. A ''private'' group is one where only members of that group can see the group and its members. A ''public'' group is one in which the group and the names of its members are visible to all.

	Groups shall also have a membership policy setting which determines how new members can join the group. There will be three options for the membership policy. An Open group is one in which anyone can join, and a Closed group is one in which only the Founder or one of the groups managers can add new members. The third option is By Request, which means that any user can request to be a member of the group, and if they are a member then they can remove themselves at any time. A Founder or group manager must Approve or Deny ~~the~~ request.		Groups shall also have a 'membership policy' setting which determines how new members can join the group. There will be three options for the membership policy. An Open group is one in which anyone can join, and a Closed group is one in which only the Founder or one of the groups managers can add new members. The third option is 'By Request', which means that any user can request to be a member of the group, and if they are a member then they can remove themselves at any time. A Founder or group manager must Approve or Deny a request to join a 'By Request' group.

			For more details on the requirements of the Group Management System see [[Group management system functional requirements]]

	===Local Server Setup===		===Local Server Setup===

Grans Remedy: /* Web Interface */

2011-04-03T02:33:13Z

Web Interface

← Older revision		Revision as of 02:33, 3 April 2011
Line 19:		Line 19:
	Organization administrator can create any number of user groups. User group names need to only be unique in the organization they belong to. User groups can have any number of members, pulled from the BZFlag user database. The group membership should store the BZID of the user to allow for name changes. Founders should be able to create, destroy, and rename user groups.		Organization administrator can create any number of user groups. User group names need to only be unique in the organization they belong to. User groups can have any number of members, pulled from the BZFlag user database. The group membership should store the BZID of the user to allow for name changes. Founders should be able to create, destroy, and rename user groups.

	Groups should also have a description field that can be edited by any founder, to identify the group. All members of the group should be able to see this description. When a user is added to a group they should be notified as well.		Groups should also have a description field that can be edited by any founder, to identify the group. All members of the group should be able to see this description. When a user is added to a group they should be notified as well. Groups shall be either ''private'' or ''public''. A ''private'' group is one where only members of that group can see the group and its members.

			Groups shall also have a membership policy setting which determines how new members can join the group. There will be three options for the membership policy. An Open group is one in which anyone can join, and a Closed group is one in which only the Founder or one of the groups managers can add new members. The third option is By Request, which means that any user can request to be a member of the group, and if they are a member then they can remove themselves at any time. A Founder or group manager must Approve or Deny the request.

	===Local Server Setup===		===Local Server Setup===

Blast at 13:13, 12 August 2010

2010-08-12T13:13:07Z

← Older revision		Revision as of 13:13, 12 August 2010
Line 9:		Line 9:
	*'''Organization''': organizations are unique name spaces that are registered by a single user. The contain a number of user groups. An organization may be a game server, a group or network of servers, or a league.		*'''Organization''': organizations are unique name spaces that are registered by a single user. The contain a number of user groups. An organization may be a game server, a group or network of servers, or a league.
	*'''User Group''': user groups contain a list of users that are members of the group, they are managed by a group moderator.		*'''User Group''': user groups contain a list of users that are members of the group, they are managed by a group moderator.
	*'''~~Owner Group~~''': a user ~~group that is automatically created for each~~ organization and can ~~manage~~ and create ~~all user~~ groups in the ~~organization~~.		*'''Founder''': the user who registers an organization and can add co-founders and can create/change/delete groups
			*'''Managers''': the users that are assigned to a group and can add/remove/approve/deny users for that group.

	==Implementation==		==Implementation==
	This describes a desired implementation.		This describes a desired implementation.
	===Web Interface===		===Web Interface===
	A web page system should be created that allows users to create and manage organizations. Organization must have unique names. If an organization name exists at creation time, the user requesting the new organization should be notified that the name is unavailable. A user should not be able to create an organization that has the same name as any user other than himself. Organizations must keep a link to their ~~creator~~ account, so that we have a contact e-mail for the organization. ~~On creation the organization will create a owner group and~~ add ~~the creating user to~~ that ~~group. The owner group~~ can ~~fully administer~~ the ~~organization~~.		A web page system should be created that allows users to create and manage organizations. Organization must have unique names. If an organization name exists at creation time, the user requesting the new organization should be notified that the name is unavailable. A user should not be able to create an organization that has the same name as any user other than himself. Organizations must keep a link to their founder account, so that we have a contact e-mail for the organization. The founder can add additional co-founders that can do everything except add/remove the founder and other co-founders.

	Organization administrator can create any number of user groups. User group names need to only be unique in the organization they belong to. User groups can have any number of members, pulled from the BZFlag user database. The group membership should store the BZID of the user to allow for name changes. ~~Administrators~~ should be able to create, destroy, and rename user groups.		Organization administrator can create any number of user groups. User group names need to only be unique in the organization they belong to. User groups can have any number of members, pulled from the BZFlag user database. The group membership should store the BZID of the user to allow for name changes. Founders should be able to create, destroy, and rename user groups.

	Groups should also have a description field that can be edited by any ~~owner~~, to identify the group		Groups should also have a description field that can be edited by any founder, to identify the group. All members of the group should be able to see this description. When a user is added to a group they should be notified as well.
	. All members of the group should be able to see this description. When a user is added to a group they should be notified as well.

	===Local Server Setup===		===Local Server Setup===

Blast: /* Conversion From phpbb Groups */

2010-08-12T13:06:44Z

Conversion From phpbb Groups

← Older revision		Revision as of 13:06, 12 August 2010
Line 37:		Line 37:
	==Conversion From phpbb Groups==		==Conversion From phpbb Groups==
	The existing user groups on BZBB are already mostly in the SERVER.GROUP format. We should be able to convert each server into an organization and assign it an owner. The few groups that are left over should be able to be manually ported to the new system. Since the names of most groups will not change, game servers will still work with the new system.		The existing user groups on BZBB are already mostly in the SERVER.GROUP format. We should be able to convert each server into an organization and assign it an owner. The few groups that are left over should be able to be manually ported to the new system. Since the names of most groups will not change, game servers will still work with the new system.

			There will be a few difficulties in this process. First, there are already several groups using the BZFLAG organization. If that organization is intended to be reserved, that will need to be handled first.

			The second issue will be handling groups with multiple leaders, or organizations that don't have a consistent set of leaders (as in, ORG.GROUP1 and ORG.GROUP2 have leaders that do not overlap). This probably won't be a huge issue for most organizations, but it will still be something that has to be handled.

	[[Category:TODO]]		[[Category:TODO]]
	[[Category:Enhancements]]		[[Category:Enhancements]]

JeffM2501: group description and notification

2007-04-23T22:47:47Z

group description and notification

← Older revision		Revision as of 22:47, 23 April 2007
Line 17:		Line 17:

	Organization administrator can create any number of user groups. User group names need to only be unique in the organization they belong to. User groups can have any number of members, pulled from the BZFlag user database. The group membership should store the BZID of the user to allow for name changes. Administrators should be able to create, destroy, and rename user groups.		Organization administrator can create any number of user groups. User group names need to only be unique in the organization they belong to. User groups can have any number of members, pulled from the BZFlag user database. The group membership should store the BZID of the user to allow for name changes. Administrators should be able to create, destroy, and rename user groups.

			Groups should also have a description field that can be edited by any owner, to identify the group
			. All members of the group should be able to see this description. When a user is added to a group they should be notified as well.

	===Local Server Setup===		===Local Server Setup===

Mr Burns: gr. & sp.

2007-04-13T10:48:16Z

gr. & sp.

← Older revision		Revision as of 10:48, 13 April 2007
Line 1:		Line 1:
	{{DesignDocument}}		{{DesignDocument}}

	A need exists to let users manage ~~there~~ own user groups. At present a forum administrator is needed to add or modify groups. This is not optimal.		A need exists to let users manage their own user groups. At present a forum administrator is needed to add or modify groups. This is not optimal.

	==Overview==		==Overview==
Line 8:		Line 8:
	==Concepts==		==Concepts==
	*'''Organization''': organizations are unique name spaces that are registered by a single user. The contain a number of user groups. An organization may be a game server, a group or network of servers, or a league.		*'''Organization''': organizations are unique name spaces that are registered by a single user. The contain a number of user groups. An organization may be a game server, a group or network of servers, or a league.
	*'''User Group''': user groups contain a list of users that are members in the group, they are managed by a group moderator.		*'''User Group''': user groups contain a list of users that are members of the group, they are managed by a group moderator.
	*'''Owner Group''': a user group that is automatically created for each organization and can manage and create all user groups in the organization.		*'''Owner Group''': a user group that is automatically created for each organization and can manage and create all user groups in the organization.

Joevano: sp

2007-04-12T21:20:55Z

← Older revision		Revision as of 21:20, 12 April 2007
Line 25:		Line 25:

	===System Administration===		===System Administration===
	A reserved organization should have global administration ~~permisions~~, to manage all organizations and user groups if needed		A reserved organization should have global administration permissions, to manage all organizations and user groups if needed

	==Reserved Names==		==Reserved Names==

JeffM2501: they are user groups not sub groups

2007-04-12T17:59:23Z

they are user groups not sub groups

← Older revision		Revision as of 17:59, 12 April 2007
Line 16:		Line 16:
	A web page system should be created that allows users to create and manage organizations. Organization must have unique names. If an organization name exists at creation time, the user requesting the new organization should be notified that the name is unavailable. A user should not be able to create an organization that has the same name as any user other than himself. Organizations must keep a link to their creator account, so that we have a contact e-mail for the organization. On creation the organization will create a owner group and add the creating user to that group. The owner group can fully administer the organization.		A web page system should be created that allows users to create and manage organizations. Organization must have unique names. If an organization name exists at creation time, the user requesting the new organization should be notified that the name is unavailable. A user should not be able to create an organization that has the same name as any user other than himself. Organizations must keep a link to their creator account, so that we have a contact e-mail for the organization. On creation the organization will create a owner group and add the creating user to that group. The owner group can fully administer the organization.

	Organization administrator can create any number of user groups. ~~Sub~~ group names need to only be unique in the organization they belong to. User groups can have any number of members, pulled from the BZFlag user database. The group membership should store the BZID of the user to allow for name changes. Administrators should be able to create, destroy, and rename user groups.		Organization administrator can create any number of user groups. User group names need to only be unique in the organization they belong to. User groups can have any number of members, pulled from the BZFlag user database. The group membership should store the BZID of the user to allow for name changes. Administrators should be able to create, destroy, and rename user groups.

	===Local Server Setup===		===Local Server Setup===