Category:Feature Requests - Revision history

Oz Linden: Redirected page to Feature Contributions

2014-08-25T21:12:49Z

Redirected page to Feature Contributions

← Older revision		Revision as of 14:12, 25 August 2014
Line 1:		Line 1:
	~~{{Languages\|Category Feature Requests}}~~		#REDIRECT [[Feature Contributions]]
	~~{{OSWikiContribBox}}~~

	~~== Filing Feature Requests==~~
	~~We're always looking for new ideas. Please let us know what you would like to see done.~~

	~~The best place for your feature requests to get noticed is in [http://jira.secondlife.com JIRA Bug Tracker].~~

	~~== Implementing Feature Requests==~~
	~~If you are a developer looking for ways to contribute, you can find ideas on~~ [http://jira.secondlife.com/browse/VWR-1577 a JIRA Meta Issue VWR-1577] which is intended to collect issues that lend themselves to be solved through open source contributions. Another source of inspiration would be the JIRA report [~~http://jira.secondlife.com/secure/IssueNavigator.jspa?requestId=10362 Unresolved~~ Feature ~~Requests] .~~

	Whenever you are planning to work on a feature, make sure you bring it up on [[SLDev\|the SLDev mailing list]]. By engaging with the community, you'll get a better idea about whether your feature implementation will be accepted into the main codebase, you'll get ideas about how to make it more likely that your code will be accepted, and you might find developers willing to collaborate with you on the implementation.

	~~See [[Submitting code]] for much more detail on this topic.~~

	~~== Refining Feature Requests ==~~

	Features are more likely to get implemented if the description of the feature is clear. For a complicated feature, a link to a specification on the wiki is a great way to help flesh out the idea. Articles in this category should be well developed and should be a secondary resource for feature requests already in JIRA. Make sure that after you create a feature request article, you add the <nowiki>[[Category:Feature Requests]]</nowiki> to the article so that it displays on this page.

	~~== Tracking New Features that you are working on ==~~

	Linden Lab allows developers who have signed a [http://secondlifegrid.net/programs/open_source/submission contribution agreement] to assign tasks in the [http://jira.secondlife.com public JIRA], so if you are working on a new feature and have signed an agreement, put it out on the JIRA and set its status to "In Progress" so others can keep track of what is being worked on. Feel free to pick up any Open requests or issues as well.

	~~You don't automatically get permissions on the public JIRA when you sign the agreement.~~

	* The Contrib-Agreement group in the public JIRA entitles you to certain permissions. The main permission you are granted is the power to assign a JIRA task. Please note the following about your permissions:
	** These permissions were introduced so that Open Source Contributors could assign JIRA tasks to themselves in order to show that work is in progress. Assigning an issue to yourself will inform Lindens and your peers of that work in progress or your forthcoming contribution.
	** Don't assign tasks to anyone without their consent.
	** These permissions would allow you to assign tasks to Lindens.
	** Please don't assign things directly to Lindens unless the person in question has specifically requested it.
	** To get added to the group: [http://secondlifegrid.net/technology-programs/virtual-world-open-source/submission sign a contribution agreement], then file a request in JIRA under WEB/jira.secondlife.com to be added to the dropdown list.

	~~== More info ==~~

	~~See also: [[Submitting code]], [[:Category:Design Discussions]], [[:Category:Bounties]] , [[LSL_Useful_Function_WishList~~]] .

Mako Nozaki: /* Refining Feature Requests */

2010-04-26T14:50:48Z

Refining Feature Requests

← Older revision		Revision as of 07:50, 26 April 2010
Line 16:		Line 16:
	== Refining Feature Requests ==		== Refining Feature Requests ==

	Features are more likely to get implemented if the description of the feature is clear. For a complicated feature, a link to a specification on the wiki is a great way to help flesh out the idea. Articles in this category should be well developed and should be a secondary resource for feature requests already in JIRA. Make sure that after you create a feature request article, you add the Category:Feature Requests to the article so that it displays on this page.		Features are more likely to get implemented if the description of the feature is clear. For a complicated feature, a link to a specification on the wiki is a great way to help flesh out the idea. Articles in this category should be well developed and should be a secondary resource for feature requests already in JIRA. Make sure that after you create a feature request article, you add the <nowiki>[[Category:Feature Requests]]</nowiki> to the article so that it displays on this page.

	== Tracking New Features that you are working on ==		== Tracking New Features that you are working on ==

Rob Linden: "more info" section

2009-03-13T23:39:23Z

"more info" section

← Older revision		Revision as of 16:39, 13 March 2009
Line 30:		Line 30:
	** Please don't assign things directly to Lindens unless the person in question has specifically requested it.		** Please don't assign things directly to Lindens unless the person in question has specifically requested it.
	** To get added to the group: [http://secondlifegrid.net/technology-programs/virtual-world-open-source/submission sign a contribution agreement], then file a request in JIRA under WEB/jira.secondlife.com to be added to the dropdown list.		** To get added to the group: [http://secondlifegrid.net/technology-programs/virtual-world-open-source/submission sign a contribution agreement], then file a request in JIRA under WEB/jira.secondlife.com to be added to the dropdown list.

			== More info ==

			See also: [[Submitting code]], [[:Category:Design Discussions]], [[:Category:Bounties]] , [[LSL_Useful_Function_WishList]] .

Rob Linden: /* Implementing Feature Requests */ - temporarily deleting some links, adding new one

2009-03-13T23:38:26Z

Implementing Feature Requests: - temporarily deleting some links, adding new one

← Older revision		Revision as of 16:38, 13 March 2009
Line 12:		Line 12:
	Whenever you are planning to work on a feature, make sure you bring it up on [[SLDev\|the SLDev mailing list]]. By engaging with the community, you'll get a better idea about whether your feature implementation will be accepted into the main codebase, you'll get ideas about how to make it more likely that your code will be accepted, and you might find developers willing to collaborate with you on the implementation.		Whenever you are planning to work on a feature, make sure you bring it up on [[SLDev\|the SLDev mailing list]]. By engaging with the community, you'll get a better idea about whether your feature implementation will be accepted into the main codebase, you'll get ideas about how to make it more likely that your code will be accepted, and you might find developers willing to collaborate with you on the implementation.

	See ~~also:~~ [[~~:Category:Design Discussions]], [[:Category:Bounties]] , [[LSL_Useful_Function_WishList~~]] .		See [[Submitting code]] for much more detail on this topic.

	== Refining Feature Requests ==		== Refining Feature Requests ==

Rob Linden: updating contrib language and adding links

2009-03-13T23:37:07Z

updating contrib language and adding links

← Older revision		Revision as of 16:37, 13 March 2009
Line 10:		Line 10:
	If you are a developer looking for ways to contribute, you can find ideas on [http://jira.secondlife.com/browse/VWR-1577 a JIRA Meta Issue VWR-1577] which is intended to collect issues that lend themselves to be solved through open source contributions. Another source of inspiration would be the JIRA report [http://jira.secondlife.com/secure/IssueNavigator.jspa?requestId=10362 Unresolved Feature Requests] .		If you are a developer looking for ways to contribute, you can find ideas on [http://jira.secondlife.com/browse/VWR-1577 a JIRA Meta Issue VWR-1577] which is intended to collect issues that lend themselves to be solved through open source contributions. Another source of inspiration would be the JIRA report [http://jira.secondlife.com/secure/IssueNavigator.jspa?requestId=10362 Unresolved Feature Requests] .

	~~<br />~~		Whenever you are planning to work on a feature, make sure you bring it up on [[SLDev\|the SLDev mailing list]]. By engaging with the community, you'll get a better idea about whether your feature implementation will be accepted into the main codebase, you'll get ideas about how to make it more likely that your code will be accepted, and you might find developers willing to collaborate with you on the implementation.

	See also: [[:Category:Design Discussions]], [[:Category:Bounties]] , [[LSL_Useful_Function_WishList]] .		See also: [[:Category:Design Discussions]], [[:Category:Bounties]] , [[LSL_Useful_Function_WishList]] .

Line 19:		Line 20:
	== Tracking New Features that you are working on ==		== Tracking New Features that you are working on ==

	Linden ~~Labs~~ allows developers who have signed a [http://secondlifegrid.net/programs/open_source/submission contribution agreement] to assign tasks in the [http://jira.secondlife.com public JIRA], so if you are working on a new feature and have signed an agreement, put it out on the JIRA and set its status to "In Progress" so others can keep track of what is being worked on. Feel free to pick up any Open requests or issues as well.		Linden Lab allows developers who have signed a [http://secondlifegrid.net/programs/open_source/submission contribution agreement] to assign tasks in the [http://jira.secondlife.com public JIRA], so if you are working on a new feature and have signed an agreement, put it out on the JIRA and set its status to "In Progress" so others can keep track of what is being worked on. Feel free to pick up any Open requests or issues as well.

	You don't automatically get permissions on the public JIRA when you sign the agreement~~. Here is an edited excerpt of a post to the [[SLDev]] mailing list by [[User:Iridium Linden\|Iridium Linden]]~~.		You don't automatically get permissions on the public JIRA when you sign the agreement.

	* The Contrib-Agreement group in the public JIRA entitles you to certain permissions. The main permission you are granted is the power to assign a JIRA task. Please note the following about your permissions:		* The Contrib-Agreement group in the public JIRA entitles you to certain permissions. The main permission you are granted is the power to assign a JIRA task. Please note the following about your permissions:
Line 27:		Line 28:
	** Don't assign tasks to anyone without their consent.		** Don't assign tasks to anyone without their consent.
	** These permissions would allow you to assign tasks to Lindens.		** These permissions would allow you to assign tasks to Lindens.
	** '~~''If you~~ assign ~~a JIRA task~~ to ~~a Linden without~~ the ~~explicit consent of that Linden, you will immediately be ejected from the group and your permissions thusly lost~~.~~'''~~		** Please don't assign things directly to Lindens unless the person in question has specifically requested it.
	** ~~If you require~~ a ~~copy of the~~ agreement, ~~follow the instructions on the wiki~~. ~~Add your name~~ to ~~the contributor wiki, contact me, and I will add you~~ to the ~~group.~~		** To get added to the group: [http://secondlifegrid.net/technology-programs/virtual-world-open-source/submission sign a contribution agreement], then file a request in JIRA under WEB/jira.secondlife.com to be added to the dropdown list.
	** Questions? Email me.
	** Iridium

Alissa Sabre: Added a _slightly_tricky_ Template:Languages at the top because Japanese translation is available.

2007-10-07T05:54:32Z

Added a _slightly_tricky_ Template:Languages at the top because Japanese translation is available.

← Older revision		Revision as of 22:54, 6 October 2007
Line 1:		Line 1:
			{{Languages\|Category Feature Requests}}
	{{OSWikiContribBox}}		{{OSWikiContribBox}}

Tjako Schumann at 22:36, 24 September 2007

2007-09-24T22:36:23Z

← Older revision		Revision as of 15:36, 24 September 2007
Line 7:		Line 7:

	== Implementing Feature Requests==		== Implementing Feature Requests==
	If you are a developer looking for ways to contribute, you can find ideas on [http://jira.secondlife.com/browse/VWR-1577 a JIRA Meta Issue VWR-1577] which is intended to collect issues that lend themselves to be solved through open source contributions. Another source of inspiration would be the JIRA report [http://jira.secondlife.com/secure/IssueNavigator.jspa?requestId=10362 Unresolved Feature Requests]		If you are a developer looking for ways to contribute, you can find ideas on [http://jira.secondlife.com/browse/VWR-1577 a JIRA Meta Issue VWR-1577] which is intended to collect issues that lend themselves to be solved through open source contributions. Another source of inspiration would be the JIRA report [http://jira.secondlife.com/secure/IssueNavigator.jspa?requestId=10362 Unresolved Feature Requests] .


	<br />		<br />
	See also: [[:Category:Design Discussions]], [[:Category:Bounties]].		See also: [[:Category:Design Discussions]], [[:Category:Bounties]] , [[LSL_Useful_Function_WishList]] .

	== Refining Feature Requests ==		== Refining Feature Requests ==

Mm Alder: /* Tracking New Features that you are working on */ more clarification

2007-09-06T19:32:30Z

Tracking New Features that you are working on: more clarification

← Older revision		Revision as of 12:32, 6 September 2007
Line 19:		Line 19:
	== Tracking New Features that you are working on ==		== Tracking New Features that you are working on ==

	Linden Labs allows developers who have signed a [http://secondlifegrid.net/programs/open_source/submission contribution agreement] to assign tasks in the [http://jira.secondlife.com public JIRA], so if you are working on a new feature and have signed an agreement, put it out on the JIRA and set its status to "In Progress" so others can keep track of what is being worked on. Feel free to pick up any Open requests as well.		Linden Labs allows developers who have signed a [http://secondlifegrid.net/programs/open_source/submission contribution agreement] to assign tasks in the [http://jira.secondlife.com public JIRA], so if you are working on a new feature and have signed an agreement, put it out on the JIRA and set its status to "In Progress" so others can keep track of what is being worked on. Feel free to pick up any Open requests or issues as well.

	You don't automatically get permissions on the public JIRA when you sign the agreement. Here is an edited excerpt of a post to the [[SLDev]] mailing list by [[User:Iridium Linden\|Iridium Linden]].		You don't automatically get permissions on the public JIRA when you sign the agreement. Here is an edited excerpt of a post to the [[SLDev]] mailing list by [[User:Iridium Linden\|Iridium Linden]].

	* The Contrib-Agreement group in the public JIRA entitles you to certain permissions. The main permission you are granted is the power to assign a JIRA task. Please note the following about your permissions:		* The Contrib-Agreement group in the public JIRA entitles you to certain permissions. The main permission you are granted is the power to assign a JIRA task. Please note the following about your permissions:
	** These permissions were introduced so that Open Source Contributors could assign JIRA tasks to themselves in order to show that work is in progress.		** These permissions were introduced so that Open Source Contributors could assign JIRA tasks to themselves in order to show that work is in progress. Assigning an issue to yourself will inform Lindens and your peers of that work in progress or your forthcoming contribution.
	** Don't assign tasks to anyone without their consent.		** Don't assign tasks to anyone without their consent.
	** These permissions would allow you to assign tasks to Lindens.		** These permissions would allow you to assign tasks to Lindens.

Mm Alder: /* Tracking New Features that you are working on */ clarification

2007-09-06T19:24:56Z

Tracking New Features that you are working on: clarification

← Older revision		Revision as of 12:24, 6 September 2007
Line 25:		Line 25:
	* The Contrib-Agreement group in the public JIRA entitles you to certain permissions. The main permission you are granted is the power to assign a JIRA task. Please note the following about your permissions:		* The Contrib-Agreement group in the public JIRA entitles you to certain permissions. The main permission you are granted is the power to assign a JIRA task. Please note the following about your permissions:
	** These permissions were introduced so that Open Source Contributors could assign JIRA tasks to themselves in order to show that work is in progress.		** These permissions were introduced so that Open Source Contributors could assign JIRA tasks to themselves in order to show that work is in progress.
	** These permissions ~~also~~ allow you to assign tasks to Lindens.		** Don't assign tasks to anyone without their consent.
			** These permissions would allow you to assign tasks to Lindens.
	** '''If you assign a JIRA task to a Linden without the explicit consent of that Linden, you will immediately be ejected from the group and your permissions thusly lost.'''		** '''If you assign a JIRA task to a Linden without the explicit consent of that Linden, you will immediately be ejected from the group and your permissions thusly lost.'''
	** If you require a copy of the agreement, follow the instructions on the wiki. Add your name to the contributor wiki, contact me, and I will add you to the group.		** If you require a copy of the agreement, follow the instructions on the wiki. Add your name to the contributor wiki, contact me, and I will add you to the group.
	** Questions? Email me.		** Questions? Email me.
	** Iridium		** Iridium

Mm Alder at 15:57, 6 September 2007

2007-09-06T15:57:55Z

← Older revision		Revision as of 08:57, 6 September 2007
Line 4:		Line 4:
	We're always looking for new ideas. Please let us know what you would like to see done.		We're always looking for new ideas. Please let us know what you would like to see done.

	The best place for your feature requests to get noticed is in [~~https~~://jira.secondlife.com JIRA Bug Tracker].		The best place for your feature requests to get noticed is in [http://jira.secondlife.com JIRA Bug Tracker].

	== Implementing Feature Requests==		== Implementing Feature Requests==
	If you are a developer looking for ways to contribute, you can find ideas on [~~https~~://jira.secondlife.com/browse/VWR-1577 a JIRA Meta Issue VWR-1577] which is intended to collect issues that lend themselves to be solved through open source contributions. Another source of inspiration would be the JIRA report [~~https~~://jira.secondlife.com/secure/IssueNavigator.jspa?requestId=10362 Unresolved Feature Requests]		If you are a developer looking for ways to contribute, you can find ideas on [http://jira.secondlife.com/browse/VWR-1577 a JIRA Meta Issue VWR-1577] which is intended to collect issues that lend themselves to be solved through open source contributions. Another source of inspiration would be the JIRA report [http://jira.secondlife.com/secure/IssueNavigator.jspa?requestId=10362 Unresolved Feature Requests]


Line 16:		Line 16:

	Features are more likely to get implemented if the description of the feature is clear. For a complicated feature, a link to a specification on the wiki is a great way to help flesh out the idea. Articles in this category should be well developed and should be a secondary resource for feature requests already in JIRA. Make sure that after you create a feature request article, you add the Category:Feature Requests to the article so that it displays on this page.		Features are more likely to get implemented if the description of the feature is clear. For a complicated feature, a link to a specification on the wiki is a great way to help flesh out the idea. Articles in this category should be well developed and should be a secondary resource for feature requests already in JIRA. Make sure that after you create a feature request article, you add the Category:Feature Requests to the article so that it displays on this page.

			== Tracking New Features that you are working on ==

			Linden Labs allows developers who have signed a [http://secondlifegrid.net/programs/open_source/submission contribution agreement] to assign tasks in the [http://jira.secondlife.com public JIRA], so if you are working on a new feature and have signed an agreement, put it out on the JIRA and set its status to "In Progress" so others can keep track of what is being worked on. Feel free to pick up any Open requests as well.

			You don't automatically get permissions on the public JIRA when you sign the agreement. Here is an edited excerpt of a post to the [[SLDev]] mailing list by [[User:Iridium Linden\|Iridium Linden]].

			* The Contrib-Agreement group in the public JIRA entitles you to certain permissions. The main permission you are granted is the power to assign a JIRA task. Please note the following about your permissions:
			** These permissions were introduced so that Open Source Contributors could assign JIRA tasks to themselves in order to show that work is in progress.
			** These permissions also allow you to assign tasks to Lindens.
			** '''If you assign a JIRA task to a Linden without the explicit consent of that Linden, you will immediately be ejected from the group and your permissions thusly lost.'''
			** If you require a copy of the agreement, follow the instructions on the wiki. Add your name to the contributor wiki, contact me, and I will add you to the group.
			** Questions? Email me.
			** Iridium