Difference between revisions of "Newsgroups Summaries"

From CDOT Wiki
Jump to: navigation, search
(Newsgroups)
(Newsgroups)
 
(26 intermediate revisions by 15 users not shown)
Line 1: Line 1:
 
The Mozilla Newsgroups provide a forum for discussions about topics related to key areas of the Mozilla products, processes, tools, and community.  However, while this breadth and depth is excellent in general, it becomes overwhelming for an individual wishing to follow all the currents.
 
The Mozilla Newsgroups provide a forum for discussions about topics related to key areas of the Mozilla products, processes, tools, and community.  However, while this breadth and depth is excellent in general, it becomes overwhelming for an individual wishing to follow all the currents.
  
Each week you and a partner are responsible for producing a Newsgroup Summary from the list of newsgroups below.  Create a link out of the newsgroup title below and make a page for your summaries; you'll create links each week for the summary.
+
Each week you and a partner are responsible for producing a '''Newsgroup Summary''' and '''FAQ''' from the list of newsgroups below.  Create a link out of the newsgroup title below and make a page (here is a [[Sample Summary|sample]]) for your summaries; you'll create links each week for the summary.
  
 
Your summaries should cover the Friday to Friday period each week, which means you'll have some overlap--that's ok.  Deb Richardson (dria) has produced an example summary and a document explaining how to do yours:
 
Your summaries should cover the Friday to Friday period each week, which means you'll have some overlap--that's ok.  Deb Richardson (dria) has produced an example summary and a document explaining how to do yours:
Line 7: Line 7:
 
* http://developer.mozilla.org/en/docs/Newsgroup_summaries
 
* http://developer.mozilla.org/en/docs/Newsgroup_summaries
 
* http://wiki.mozilla.org/MDC_newsgroup_summaries
 
* http://wiki.mozilla.org/MDC_newsgroup_summaries
 +
 +
Some of the these lists will be more question/answer than content to be summarized.  In this case you will put the good questions/answers into an FAQ format.  So, during the course of a week, if a technical question comes up and is answered on the newsgroup, write up a clear summarization of that discussion, including links to relevant documentation, bugs, etc.
 +
 +
These Summaries and FAQ lists are something the Mozilla project has never had before.  You are essentially working to launch a whole new aspect to the project that will continue on indefinitely on MDC.
  
 
== Newsgroups ==
 
== Newsgroups ==
Line 12: Line 16:
 
The Mozilla Newsgroups are available via Google Groups and as as [https://lists.mozilla.org/listinfo mailing lists].
 
The Mozilla Newsgroups are available via Google Groups and as as [https://lists.mozilla.org/listinfo mailing lists].
  
# mozilla.dev.apps.firefox
+
# [[mozilla.dev.apps.firefox]]
# mozilla.dev.l10n
+
# [[mozilla.dev.l10n]]
# mozilla.dev.tech.js-engine
+
# [[mozilla.dev.tech.js-engine]]
# mozilla.dev.planning
+
# [[mozilla.dev.planning]]
# mozilla.dev.builds
+
# [[mozilla.dev.builds]]
# mozilla.dev.apps.thunderbird
+
# [[mozilla.dev.apps.thunderbird]]
# mozilla.dev.tech.layout
+
# [[mozilla.dev.tech.layout]]
# mozilla.dev.quality
+
# [[mozilla.dev.quality]]
# mozilla.dev.security
+
# [[mozilla.dev.security]]
# mozilla.dev.i18n
+
# [[mozilla.dev.i18n]]
# mozilla.dev.embedding
+
# [[mozilla.dev.embedding]]
# mozilla.dev.platform
+
# [[mozilla.dev.platform]]
# mozilla.dev.tech.xpcom
+
# [[mozilla.dev.tech.xpcom]]
# mozilla.dev.tech.xul
+
# [[mozilla.dev.tech.xul]]
# mozilla.dev.extensions
+
# [[mozilla.dev.extensions]]
 +
# [[mozilla.dev.apps.calendar]]
 +
# [[mozilla.dev.accessibility]]
  
 
== Grading ==
 
== Grading ==
  
Each weekly summary will be worth 2% of your final grade, to a maximum of 20%.  You will be graded on the completeness and quality of your summary:
+
Each weekly summary/faq will be worth 2% of your final grade, to a maximum of 20%.  You will be graded on the completeness and quality of your summary:
  
 
* 0/2 - incomplete
 
* 0/2 - incomplete
Line 36: Line 42:
 
* 2/2 - completed and good quality
 
* 2/2 - completed and good quality
  
In addition to being worth marks for the course, you should also be aware that newsgroups that are well done will be made available to the Mozilla community.  This is something the community is looking for, and will welcome.
+
== Publishing to MDC ==
 +
 
 +
I have now read all of your first summaries, and I'm impressed.  There are a few places for improvement (I've emailed you all), but generally, you've done a good job.
 +
 
 +
You can all begin posting directly to [http://developer.mozilla.org MDC].  Melissa and Eva have already done this, so you can follow their example:
 +
 
 +
# Find your newsgroup title [http://developer.mozilla.org/en/docs/Newsgroup_summaries here] and follow the link.
 +
# Create a page for your summaries by date ([http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird here is an example]).
 +
# Create your summary like [http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-09-29 this].  NOTE the page title format: http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-09-29
 +
# Provide a link on our wiki in your summary page (like [[Mozilla.dev.apps.thunderbird|this]])
 +
 +
All of this must be done each Friday so that it can be announced in the Mozilla community on [http://developer.mozilla.org MDC]If you have questions, please speak to me (dave).
 +
 
 +
Feel free to put your name(s) on your summary somewhere so that people get to know you as they read your work each week.
 +
 
 +
== FAQ vs. Summary ==
 +
 
 +
Some newsgroups are more FAQ than Summary.  If that is the case, you should follow the instructions on creating an [http://developer.mozilla.org/en/docs/Frequently_Asked_Questions FAQ on MDC] instead of, or in addition to, creating a summary as outlined above.
 +
 
 +
You can and should publish your FAQs to MDC just like the summaries.
 +
 
 +
== What if my newsgroup has no traffic this week? ==
 +
 
 +
Some newsgroups are very busy, and others have little or no traffic in a given week.  If you find that there is no activity in your newsgroup, you should dig through the group's archives and compile some FAQ questions, following the instructions [http://developer.mozilla.org/en/docs/Frequently_Asked_Questions here on MDC].

Latest revision as of 12:37, 18 October 2006

The Mozilla Newsgroups provide a forum for discussions about topics related to key areas of the Mozilla products, processes, tools, and community. However, while this breadth and depth is excellent in general, it becomes overwhelming for an individual wishing to follow all the currents.

Each week you and a partner are responsible for producing a Newsgroup Summary and FAQ from the list of newsgroups below. Create a link out of the newsgroup title below and make a page (here is a sample) for your summaries; you'll create links each week for the summary.

Your summaries should cover the Friday to Friday period each week, which means you'll have some overlap--that's ok. Deb Richardson (dria) has produced an example summary and a document explaining how to do yours:

Some of the these lists will be more question/answer than content to be summarized. In this case you will put the good questions/answers into an FAQ format. So, during the course of a week, if a technical question comes up and is answered on the newsgroup, write up a clear summarization of that discussion, including links to relevant documentation, bugs, etc.

These Summaries and FAQ lists are something the Mozilla project has never had before. You are essentially working to launch a whole new aspect to the project that will continue on indefinitely on MDC.

Newsgroups

The Mozilla Newsgroups are available via Google Groups and as as mailing lists.

  1. mozilla.dev.apps.firefox
  2. mozilla.dev.l10n
  3. mozilla.dev.tech.js-engine
  4. mozilla.dev.planning
  5. mozilla.dev.builds
  6. mozilla.dev.apps.thunderbird
  7. mozilla.dev.tech.layout
  8. mozilla.dev.quality
  9. mozilla.dev.security
  10. mozilla.dev.i18n
  11. mozilla.dev.embedding
  12. mozilla.dev.platform
  13. mozilla.dev.tech.xpcom
  14. mozilla.dev.tech.xul
  15. mozilla.dev.extensions
  16. mozilla.dev.apps.calendar
  17. mozilla.dev.accessibility

Grading

Each weekly summary/faq will be worth 2% of your final grade, to a maximum of 20%. You will be graded on the completeness and quality of your summary:

  • 0/2 - incomplete
  • 1/2 - completed
  • 2/2 - completed and good quality

Publishing to MDC

I have now read all of your first summaries, and I'm impressed. There are a few places for improvement (I've emailed you all), but generally, you've done a good job.

You can all begin posting directly to MDC. Melissa and Eva have already done this, so you can follow their example:

  1. Find your newsgroup title here and follow the link.
  2. Create a page for your summaries by date (here is an example).
  3. Create your summary like this. NOTE the page title format: http://developer.mozilla.org/en/docs/Newsgroup_summaries:mozilla-dev-apps-thunderbird:2006-09-29
  4. Provide a link on our wiki in your summary page (like this)

All of this must be done each Friday so that it can be announced in the Mozilla community on MDC. If you have questions, please speak to me (dave).

Feel free to put your name(s) on your summary somewhere so that people get to know you as they read your work each week.

FAQ vs. Summary

Some newsgroups are more FAQ than Summary. If that is the case, you should follow the instructions on creating an FAQ on MDC instead of, or in addition to, creating a summary as outlined above.

You can and should publish your FAQs to MDC just like the summaries.

What if my newsgroup has no traffic this week?

Some newsgroups are very busy, and others have little or no traffic in a given week. If you find that there is no activity in your newsgroup, you should dig through the group's archives and compile some FAQ questions, following the instructions here on MDC.