process - Revision history

Tantek: /* Exploratory Discussions */ de-dup text from what gets expanded from the irc link

2022-11-29T19:10:11Z

Exploratory Discussions: de-dup text from what gets expanded from the irc link

← Older revision		Revision as of 19:10, 29 November 2022
Line 189:		Line 189:
	You should do it on this wiki using current items under exploratory discussion as a guide.		You should do it on this wiki using current items under exploratory discussion as a guide.

	Then send a note to ~~the #microformats~~ [[irc]] ~~chat~~ to get the attention of others who are interested in microformats. This is probably a good chance to pull in people from outside the current microformats community who may also be experiencing the same issue.		Then send a note to [[irc]] to get the attention of others who are interested in microformats. This is probably a good chance to pull in people from outside the current microformats community who may also be experiencing the same issue.

	Feedback will probably range the gamut. Others may challenge your problem statement, the need for a microformat, concur, or add. All constructive feedback is good.		Feedback will probably range the gamut. Others may challenge your problem statement, the need for a microformat, concur, or add. All constructive feedback is good.

Tantek: /* Exploratory Discussions */ use chat not email

2022-11-29T19:09:35Z

Exploratory Discussions: use chat not email

← Older revision		Revision as of 19:09, 29 November 2022
Line 189:		Line 189:
	You should do it on this wiki using current items under exploratory discussion as a guide.		You should do it on this wiki using current items under exploratory discussion as a guide.

	Then send a note to the microformats~~-new list~~ to get the attention of others who are interested in microformats. This is probably a good chance to pull in people from outside the current microformats community who may also be experiencing the same issue.		Then send a note to the #microformats [[irc]] chat to get the attention of others who are interested in microformats. This is probably a good chance to pull in people from outside the current microformats community who may also be experiencing the same issue.

	Feedback will probably range the gamut. Others may challenge your problem statement, the need for a microformat, concur, or add. All constructive feedback is good.		Feedback will probably range the gamut. Others may challenge your problem statement, the need for a microformat, concur, or add. All constructive feedback is good.

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:31:14Z

Replace <entry-title> with {{DISPLAYTITLE:}}

← Older revision		Revision as of 16:31, 18 July 2020
Line 1:		Line 1:
	If this is your first visit, please see the [[introduction]] page first.		If this is your first visit, please see the [[introduction]] page first.

	~~<entry-title>~~The microformats process~~</entry-title>~~		{{DISPLAYTITLE:The microformats process}}

	'''So you wanna develop a new microformat?'''		'''So you wanna develop a new microformat?'''

Tantek: make sure of POSH, mf2 direct links

2018-05-08T03:54:15Z

make sure of POSH, mf2 direct links

← Older revision		Revision as of 03:54, 8 May 2018
Line 21:		Line 21:
	Before even considering pursuing a new microformat, first:		Before even considering pursuing a new microformat, first:

	# Make your site [[POSH]].		# Make sure your site uses [[POSH]].
	# Add <em>existing</em> microformats to your sites like [[~~hcard\|hCard~~]] for your contact info, [[~~hcalendar\|hCalendar~~]] for your events, [[~~hatom\|hAtom~~]] for your episodic content (e.g. blogs). See [[get-started]] for more specific examples of adding microformats to your sites.		# Add <em>existing</em> microformats to your sites like [[h-card]] for your contact info, [[h-event]] for your events, [[h-entry]] for your episodic content (e.g. blogs). See [[get-started]] for more specific examples of adding microformats to your sites.
	#* In particular, start adding '''[[microformats2]]''' markup for all your microformats. Any new microformats must use [[microformats2]] - using it will help you become familiar with it.		#* In particular, start adding '''[[microformats2]]''' markup for all your microformats. Any new microformats must use [[microformats2]] - using it will help you become familiar with it.

Tantek: have not been using mailing lists for years now

2016-10-24T22:25:17Z

have not been using mailing lists for years now

← Older revision		Revision as of 22:25, 24 October 2016
Line 38:		Line 38:
	Check the [[exploratory-discussion]] page, and search around on the web. Chances are that someone else has encountered the same problem as you. There are very few truly new problems.		Check the [[exploratory-discussion]] page, and search around on the web. Chances are that someone else has encountered the same problem as you. There are very few truly new problems.

	If you still believe that you have a new and unsolved problem, post a one sentence summary of the problem to the [[irc]] channel~~, and if~~ no one ~~is around~~, then ~~the [http://microformats.org/mailman/listinfo/microformats-new/ microformats-new] mailing list~~.		If you still believe that you have a new and unsolved problem, post a one sentence summary of the problem to the [[irc]] channel. If no one answers, perhaps start a page documenting the problem you're solving, then ask again.

	It's better to get the community involved in the discussion as the community can help find previous attempts at describing or solving the problem.		It's better to get the community involved in the discussion as the community can help find previous attempts at describing or solving the problem.
Line 46:		Line 46:
	We're not using the wiki as a general "scratch pad".		We're not using the wiki as a general "scratch pad".

	If you can't summarize the problem you are trying to solve in a short ~~email~~, and feel like you need a long document, you're probably trying to solve too big of a problem - see previous point about 'is there a simpler problem here?' and simplify until you describe your problem and real world use case in a short paragraph.		If you can't summarize the problem you are trying to solve in a short message on IRC (think tweetsized), and feel like you need a long document, you're probably trying to solve too big of a problem - see previous point about 'is there a simpler problem here?' and simplify until you describe your problem and real world use case in a short paragraph.

	== What is the use case ==		== What is the use case ==
Line 96:		Line 96:
	It's quite possible during this step that you'll find someone else who has dealt with the problem(s) you're addressing. Perhaps even solved it/them. Do your best to open a dialog with others who have encountered the same problem(s). We don't want to build walls between competing communities - we want people to work together to develop a good solution which will cover the majority of cases.		It's quite possible during this step that you'll find someone else who has dealt with the problem(s) you're addressing. Perhaps even solved it/them. Do your best to open a dialog with others who have encountered the same problem(s). We don't want to build walls between competing communities - we want people to work together to develop a good solution which will cover the majority of cases.

	If you can't find previous efforts at formats for the data you want to microformat, ask in [[IRC~~]] and on the [[mailing-lists~~]].		If you can't find previous efforts at formats for the data you want to microformat, ask in [[IRC]].

	==Brainstorm Proposals==		==Brainstorm Proposals==
Line 219:		Line 219:
	*** e.g. add/drop/rename arbitrary features (per research/feedback from publishers/consumers)		*** e.g. add/drop/rename arbitrary features (per research/feedback from publishers/consumers)

	Drafts are written up on the wiki using the draft template. Upon writing up a draft, send a note to ~~the microformats-new mailing list~~ to alert people that something new has happened. Continue encouraging feedback from relevant resources both inside and outside the community. Drafts need to include at least the following:		Drafts are written up on the wiki using the draft template. Upon writing up a draft, send a note to IRC channel with URL to alert people that something new has happened. Continue encouraging feedback from relevant resources both inside and outside the community. Drafts need to include at least the following:

	* Statements regarding the fact that you will not patent and are adopting appropriate copyright (preferably PUBLIC DOMAIN) as illustrated by current drafts.		* Statements regarding the fact that you will not patent and are adopting appropriate copyright (preferably PUBLIC DOMAIN) as illustrated by current drafts.

TomMorris: /* Related */ adding link to free-specifications

2014-11-09T12:57:01Z

Related: adding link to free-specifications

← Older revision		Revision as of 12:57, 9 November 2014
Line 353:		Line 353:

	== Related ==		== Related ==
			* [[free-specifications]]
	* [[process-faq]]		* [[process-faq]]
	* [[process-issues]]		* [[process-issues]]
	* [[process-brainstorming]]		* [[process-brainstorming]]

Tantek: /* Get some experience first */ use microformats2 to learn it

2013-04-28T15:20:45Z

Get some experience first: use microformats2 to learn it

← Older revision		Revision as of 15:20, 28 April 2013
Line 22:		Line 22:

	# Make your site [[POSH]].		# Make your site [[POSH]].
	# Add <em>existing</em> microformats to your sites like [[hcard\|hCard]] for your contact info ~~etc.~~, [[hcalendar\|hCalendar]] for your events, [[hatom\|hAtom]] for your episodic content (e.g. blogs). See [[get-started]] for more specific examples of adding microformats to your sites.		# Add <em>existing</em> microformats to your sites like [[hcard\|hCard]] for your contact info, [[hcalendar\|hCalendar]] for your events, [[hatom\|hAtom]] for your episodic content (e.g. blogs). See [[get-started]] for more specific examples of adding microformats to your sites.
			#* In particular, start adding '''[[microformats2]]''' markup for all your microformats. Any new microformats must use [[microformats2]] - using it will help you become familiar with it.

	This will help familiarize you with how [[POSH]] and [[microformats]] currently work. Such "real world" experience will greatly help you with the development of a new microformat. For more on this see [[why-using-existing-microformats-matters]].		This will help familiarize you with how [[POSH]] and [[microformats]] currently work. Such "real world" experience will greatly help you with the development of a new microformat. For more on this see [[why-using-existing-microformats-matters]].

Tantek: Changed protection level for "process" [edit=sysop:move=sysop]

2013-04-07T08:39:45Z

Changed protection level for "process" [edit=sysop:move=sysop]

← Older revision	Revision as of 08:39, 7 April 2013
(No difference)

Tantek: Reverted edits by ABIDEEN10 (Talk) to last version by Tantek

2013-04-07T04:58:52Z

Reverted edits by ABIDEEN10 (Talk) to last version by Tantek

Show changes

ABIDEEN10 at 02:37, 7 April 2013

2013-04-07T02:37:46Z

Show changes