MozillaWiki - User contributions [en]

Donate Bitcoin

2016-03-18T01:12:39Z

Alicoding: Broken link for bitcoin URL

<h2>Can I donate bitcoin?</h2>
Yes! To contribute via Bitcoin, please visit [https://donate.mozilla.org/give-bitcoin/ this link.]

<h5>Is Mozilla worried about the fluctuating value of bitcoin?</h5>
Mozilla will not actually be holding any bitcoins it receives through donations. Instead, we are partnering with Coinbase to convert them to United States dollars upon receipt. That means that the amount of the donation will remain entirely unaffected by changes in market value of bitcoin. In addition, Coinbase waives all transaction fees for nonprofits who use its service, including Mozilla. That means the amount in bitcoins that donors give in USD is what Mozilla will receive.
<br>
<h5>Is it tax-deductible to donate using bitcoin?</h5>
The Mozilla Foundation is a California non-profit corporation exempt from United States federal income taxation under IRC 501(c)(3) and a public charity classified under IRC sections 170(b)(1)(A) and 509(a)(1). Bitcoin donations Mozilla receives are considered charitable contributions under U.S. federal tax laws, to be used in its discretion for its charitable purposes.
<br>
<h5>Are there any special tax rules for contributions of bitcoin?</h5>
Because the IRS has indicated that it will treat bitcoin as property for U.S. tax purposes (see IRS Notice 2014-21), donations of bitcoin may be subject to special rules as to the amount of your charitable deduction, the documentation that must be provided to claim a tax deduction, or other matters. (See http://www.irs.gov/taxtopics/tc506.html for an overview.) Depending on your individual circumstance, a gift of bitcoin could have better or worse tax consequences than a cash gift. You may wish to consult your tax advisor about the tax consequences of giving bitcoins in your specific circumstances and about the documentation required in order to claim a deduction.
<br>
<h5>What documentation does Mozilla provide to donors?</h5>
We appreciate our donors and are happy to provide confirmation of their donation upon request. All bitcoin donors should automatically receive an acknowledgement of their donation for U.S. tax purposes, sent via email to the address they provide when they donate.
<br>
Depending on the amount of their non-cash contributions during the year, donors may also determine that they need Mozilla Foundation to sign a Form 8283 confirming its receipt of their donation (e.g., if their total bitcoin donations to all charities for the year exceed $5,000). Mozilla Foundation is happy to sign a donor’s Form 8283 upon request, but it is the donor’s sole responsibility to determine whether this is necessary and, if so, to provide the form for signature at least 10 business days in advance. PDF copies of the form may be sent to donate@mozilla.org for signature. Any other documentation (e.g., an appraisal) remains the donor’s sole responsibility.
<br>
<h5>What personal information does Mozilla require Bitcoin donors to provide?</h5>
In most cases, Mozilla requires only an email address, which is necessary so that Mozilla can send them an acknowledgment letter for tax purposes.
<br>
For bitcoin contributions of more than $5,000, and other contributions for which the donor provides Form 8283 to Mozilla for signature, Mozilla expects to file a Form 8282 with the IRS in connection with its disposition of the bitcoins it receives. In such cases, we will request the donor’s name, address, and U.S. tax identification number so that we can properly complete our tax forms. Typically, the donor is required to provide that information to Mozilla on a Form 8283 in any event, in order to secure his or her own tax deduction (see above). If we do not hear from a donor within 90 calendar days from the date of his or her donation, we reserve the right to file the Form 8282 using our best available information.
<br>
<h5>How secure is Coinbase?</h5>
Coinbase is committed to keeping its platform secure by encrypting all sensitive customer information and storing 97% of funds offline to protect against theft. Coinbase also utilizes an active community of security researchers to encourage the continuous auditing of their platform. For more information on the measures Coinbase takes to protect your funds and information, visit their Security page:
https://www.coinbase.com/security

Webmaker/Textbook

2014-05-09T14:08:28Z

Alicoding: /* Competency Page directory */

__NOTOC__
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/v0h9d5rl.png
=Toward Web Lit Textbook 1.0=
* '''Schedule & Logistics''': https://etherpad.mozilla.org/book-sprint

==Links==
* '''Notes''': https://etherpad.mozilla.org/Textbook

'''Prototypes'''
* '''Sample page copy''': The "Credibility" page. 2nd draft copy: https://etherpad.mozilla.org/credibility
* <b>Webmaker.org "Explore" prototype</b>: https://webmaker.mofostaging.net/explore

'''Good sources for activities and kits'''
* <b>Web Lit Mapper</b>. A good source of resources and activities, tagged by competency http://weblitmapper.webmakerprototypes.org/
* <b>Top 100 resources</b> (many are outside OERs). http://mzl.la/top100
* <b>"Best in Show"</b> -- our most updated list of OERs/Kits per competency. https://teach.etherpad.mozilla.org/best-in-show
* <b>Teaching Kit production queue</b>. Kits in progress. Burn down list: http://mzl.la/kit_list

'''Documentation'''
* "<b>How to create a good teaching kit</b>." Documentation on SUMO [link] (needs to be updated, using copy here https://wiki.mozilla.org/Webmaker/Teaching_Kits and the SUMO page)
* <b>Style guide for writing these pages</b>. Starting a draft here: https://etherpad.mozilla.org/style_guide
* <b>Community engagement plan</b>. https://teach.etherpad.mozilla.org/featureseries
* <b>Quarterly Curation Sprint Plan</b> https://etherpad.mozilla.org/style-guide-editorial

<b>Experimental</b>
** '''Kit Builder'''. Fuzzy's new [http://fuzzyfox.github.io/webmaker-kits-builder kit builder prototype] + [https://fuzzyfox.github.io/webmaker-kits-builder/README.md documentation]
** '''Gallery Maker.''' aka Cade's "makeLister." New tool for creating Webmaker.org galleries. [https://bugzilla.mozilla.org/show_bug.cgi?id=1005905 Blocked on this]
** '''Web Lit Map visual redesign ideas '''[https://www.dropbox.com/s/kzl0xa0rj3yoe1c/webliteracymap_sngconcepts.pdf A few basic sketches from Sabrina ]

<b>Notes for Web Literacy Map</b>
* Suggested changes for next version of Web Lit Map https://etherpad.mozilla.org/Web-Lit-Map
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/qur82k-2.png

= Competency Page directory=
*[https://etherpad.mozilla.org/composing Composing]
*[https://etherpad.mozilla.org/codingscripting Coding/Scripting]
*[https://etherpad.mozilla.org/remix Remix]
*[https://etherpad.mozilla.org/credibility Credibility]
*[https://etherpad.mozilla.org/Collaborating Collaborating]
*[https://etherpad.mozilla.org/security Security]
*[https://etherpad.mozilla.org/privacy Privacy]
*[https://etherpad.mozilla.org/search Search]
*[https://etherpad.mozilla.org/sharing Sharing]
*[https://etherpad.mozilla.org/navigation Navigation]
*[https://etherpad.mozilla.org/webmechanics Web Mechanics]
* [http://etherpad.mozilla.org/designaccessibility Design and Accessibility]
* [https://etherpad.mozilla.org/infrastructure Infrastructure]
* [https://etherpad.mozilla.org/openpractices Open Practices]

=Sprint=
===Wed Morning===
* '''GOAL: ship a mock-up of the "Credibility" page'''. To model and discuss Wed. Show how a new template could work for the page. Experiment with look and feel, etc.
* '''[http://mzl.la/1fMCbXj Ticket Tag]''': [wedam]
<div>
<onlyinclude>
<bugzilla>
{
"product": "Webmaker",
"whiteboard": "[wedam]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "last_change_time"
}
</bugzilla>
</onlyinclude>
</div>

===Wed Afternoon===
* '''GOAL: get started on three high-priority pages together''': Privacy, Remix, Coding & Scripting.
* '''Who's focusing on what?''' (please hack)
** '''Cassie''': design. icons + make the new pages layout look awesome.
** '''Kate''': design, coding. Technical review where needed
** '''Kat & Drushka''': review "staff pick" teaching kits for each page. Ensure the titles are clear.
** '''Brett''': Remix. Draft a team to draft the "remix" page.
** '''Matt / Claw:''' divide up privacy + coding & scripting.
** '''Humph''': joining Thurs & Fri. Question: Humph, where do you want to focus?
** '''Ali''': Localization / Translation

* '''Tag''': [wed] [aft]
<div>
<onlyinclude>
<bugzilla>
{
"product": "Webmaker",
"whiteboard": "[wed] [aft]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</onlyinclude>
</div>

===Thursday===
* '''GOAL: ship three more pages'''. To be decided together.
* [http://mzl.la/1iTNz4w '''Tag''']: [thurs]
<div>
<onlyinclude>
<bugzilla>
{
"product": "Webmaker",
"whiteboard": "[thurs]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "last_change_time"
}
</bugzilla>
</onlyinclude>
</div>

===Friday===
* '''GOAL: ship how many more?'''. Plus: ship a draft style guide. Documenting best practices we learned from working together over the week.
* '''[http://mzl.la/1kHDUtn Tag]''': [fri]
<div>
<onlyinclude>
<bugzilla>
{
"product": "Webmaker",
"whiteboard": "[fri]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "last_change_time"
}
</bugzilla>
</onlyinclude>
</div>
[https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&list_id=10102809&o1=substring&query_format=advanced&component=Teaching%20Kits%20%2F%20Curriculum&product=Webmaker All Webmaker curriculum tickets]
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/hirpw_mt.png

Webmaker/Textbook

2014-05-07T16:38:52Z

Alicoding: /* Wed Afternoon */

__NOTOC__
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/v0h9d5rl.png
=Toward Web Lit Textbook 1.0=
* '''Schedule & Logistics''': https://etherpad.mozilla.org/book-sprint

==Links==
* '''Notes''': https://etherpad.mozilla.org/Textbook

'''Prototypes'''
* '''Sample page copy''': The "Credibility" page. 2nd draft copy: https://etherpad.mozilla.org/credibility
* <b>Webmaker.org "Explore" prototype</b>: https://webmaker.mofostaging.net/explore

'''Good sources for activities and kits'''
* <b>Web Lit Mapper</b>. A good source of resources and activities, tagged by competency http://weblitmapper.webmakerprototypes.org/
* <b>Top 100 resources</b> (many are outside OERs). http://mzl.la/top100
* <b>"Best in Show"</b> -- our most updated list of OERs/Kits per competency. https://teach.etherpad.mozilla.org/best-in-show
* <b>Teaching Kit production queue</b>. Kits in progress. Burn down list: http://mzl.la/kit_list
* <b>Community engagement plan</b>. https://teach.etherpad.mozilla.org/featureseries

'''Documentation'''
* "<b>How to create a good teaching kit</b>." Documentation on SUMO [link] (needs to be updated, using copy here https://wiki.mozilla.org/Webmaker/Teaching_Kits and the SUMO page)
* <b>Style guide for writing these pages</b>. Starting a draft here: https://etherpad.mozilla.org/style_guide
* <b>Quarterly Curation Sprint Plan</b> https://etherpad.mozilla.org/style-guide-editorial

<b>Experimental</b>:
** '''Kit Builder'''. Fuzzy's new [http://fuzzyfox.github.io/webmaker-kits-builder kit builder prototype] + [https://fuzzyfox.github.io/webmaker-kits-builder/README.md documentation]
** '''Gallery Maker.''' aka Cade's "makeLister." New tool for creating Webmaker.org galleries. [https://bugzilla.mozilla.org/show_bug.cgi?id=1005905 Blocked on this]

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/qur82k-2.png

=Sprint=
===Wed Morning===
* '''GOAL: ship a mock-up of the "Credibility" page'''. To model and discuss Wed. Show how a new template could work for the page. Experiment with look and feel, etc.
* '''[http://mzl.la/1fMCbXj Ticket Tag]''': [wedam]
<div>
<onlyinclude>
<bugzilla>
{
"product": "Webmaker",
"whiteboard": "[wedam]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "last_change_time"
}
</bugzilla>
</onlyinclude>
</div>

===Wed Afternoon===
* '''GOAL: get started on three high-priority pages together''': Privacy, Remix, Coding & Scripting.
* '''Who's focusing on what?''' (please hack)
** '''Cassie''': design. icons + make the new pages layout look awesome.
** '''Kate''': design, coding. Technical review where needed
** '''Kat & Drushka''': review "staff pick" teaching kits for each page. Ensure the titles are clear.
** '''Brett''': Remix. Draft a team to draft the "remix" page.
** '''Matt / Claw:''' divide up privacy + coding & scripting.
** '''Humph''': joining Thurs & Fri. Question: Humph, where do you want to focus?
** '''Ali''': Localization / Translation

* '''Tag''': [wed] [aft]
<div>
<onlyinclude>
<bugzilla>
{
"product": "Webmaker",
"whiteboard": "[wed] [aft]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</onlyinclude>
</div>

===Thursday===
* '''GOAL: ship three more pages'''. To be decided together.
* [http://mzl.la/1iTNz4w '''Tag''']: [thurs]
<div>
<onlyinclude>
<bugzilla>
{
"product": "Webmaker",
"whiteboard": "[thurs]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "last_change_time"
}
</bugzilla>
</onlyinclude>
</div>

===Friday===
* '''GOAL: ship how many more?'''. Plus: ship a draft style guide. Documenting best practices we learned from working together over the week.
* '''[http://mzl.la/1kHDUtn Tag]''': [fri]
<div>
<onlyinclude>
<bugzilla>
{
"product": "Webmaker",
"whiteboard": "[fri]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "last_change_time"
}
</bugzilla>
</onlyinclude>
</div>
[https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&list_id=10102809&o1=substring&query_format=advanced&component=Teaching%20Kits%20%2F%20Curriculum&product=Webmaker All Webmaker curriculum tickets]
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/hirpw_mt.png

Webmaker/Triage

2014-04-16T18:16:51Z

Alicoding:

Every week we look at all of the unassigned and unmentored bugs in the Webmaker product on Bugzilla. The goal is to get to zero unowned bugs.

* Time: Every Wednesday at 11AM Pacific / 2PM Eastern for 1 hour
* Location: MoFoDev Vidyo room
* Bugzilla search: [https://bugzilla.mozilla.org/buglist.cgi?order=Last%20Changed&list_id=9911651&resolution=---&emailtype1=exact&status_whiteboard_type=notregexp&emailassigned_to1=1&query_format=advanced&status_whiteboard=%28mentor%3D%7Cicebox%7Cdiscussion%29&email1=nobody%40mozilla.org&product=Webmaker https://bugzilla.mozilla.org/buglist.cgi?order=Last%20Changed&list_id=9911651&resolution=---&emailtype1=exact&status_whiteboard_type=notregexp&emailassigned_to1=1&query_format=advanced&status_whiteboard=%28mentor%3D%7Cicebox%7Cdiscussion%29&email1=nobody%40mozilla.org&product=Webmaker]

Note that during this triage call we do not focus on getting the bugs assigned to the person responsible for resolving them, but rather on getting bugs assigned to the person who is best suited to make sure it ends up in the hands of the person who ultimately works on resolving them. The triage session is to ensure no bug remains unseen.

Webmaker/Triage

2014-04-16T18:09:42Z

Alicoding:

Every week we look at all of the unassigned and unmentored bugs in the Webmaker product on Bugzilla. The goal is to get to zero unowned bugs.

* Time: Every Wednesday at 11AM Pacific / 2PM Eastern for 1 hour
* Location: MoFoDev Vidyo room
* Bugzilla search: [https://bugzilla.mozilla.org/buglist.cgi?list_id=9911588&emailtype1=exact&status_whiteboard_type=notregexp&emailassigned_to1=1&status_whiteboard=%28mentor%3D%7Cicebox%7Cdiscussion%29&email1=nobody%40mozilla.org&resolution=---&query_format=advanced&product=Webmaker https://bugzilla.mozilla.org/buglist.cgi?list_id=9911588&emailtype1=exact&status_whiteboard_type=notregexp&emailassigned_to1=1&status_whiteboard=%28mentor%3D%7Cicebox%7Cdiscussion%29&email1=nobody%40mozilla.org&resolution=---&query_format=advanced&product=Webmaker]

Note that during this triage call we do not focus on getting the bugs assigned to the person responsible for resolving them, but rather on getting bugs assigned to the person who is best suited to make sure it ends up in the hands of the person who ultimately works on resolving them. The triage session is to ensure no bug remains unseen.

Webmaker/GitHub/Copy

2014-04-14T16:33:31Z

Alicoding: /* How to add or update copy on Webmaker.org */

= How to add or update copy on Webmaker.org =

* You'll need a GitHub account.

'''Instructions:'''
* 1. Log into your GitHub account.
* 2. Visit the code repository that you would like to make changes to. For example: https://github.com/mozilla/webmaker.org

https://dl.dropboxusercontent.com/spa/n5v3bx9nnjkdpzf/48qefzvs.png

* 3. Click the "Fork" button
https://dl.dropboxusercontent.com/spa/n5v3bx9nnjkdpzf/qle67plf.png
* 4. You will now have a copy of the repo on your own user account. e.g. https://github.com/alicoding/webmaker.org
* 5. To change existing copy on Webmaker.org, go to: locale/en_US/webmaker.org https://dl.dropboxusercontent.com/spa/n5v3bx9nnjkdpzf/0kp9v1nl.png
* 6. Click "Edit"
https://dl.dropboxusercontent.com/spa/n5v3bx9nnjkdpzf/2bhkipdj.png
* 7. Find and change the text you want.
* 8. Add a message to the "Commit field." (What kinds of messages are useful. What's the best practise?)
* 9. Add a message to the "description field" (What kinds of messages are useful. What's the best practise?)
* 10. Click on "Commit changes"
https://dl.dropboxusercontent.com/spa/n5v3bx9nnjkdpzf/26u9hcxx.png
* 11. Go back to the your forked repo. e.g. https://github.com/alicoding/webmaker.org
* 12. Click on green button "Compare, review, create pull request"
https://dl.dropboxusercontent.com/spa/n5v3bx9nnjkdpzf/moz70d8-.png
* 13. Review your changes and click on "Create pull request"
https://dl.dropboxusercontent.com/spa/n5v3bx9nnjkdpzf/71qxqd_w.png
* 14. Finally, click on "Send pull request."
https://dl.dropboxusercontent.com/spa/n5v3bx9nnjkdpzf/m8wzcrxg.png
* 15. That's it! You're done.

Webmaker/GitHub/Copy

2014-04-14T16:26:57Z

Alicoding: /* How to add or update copy on Webmaker.org */

= How to add or update copy on Webmaker.org =

* You'll need a GitHub account.

'''Instructions:'''
* 1. Log into your GitHub account.
* 2. Visit the code repository that you would like to make changes to. For example: https://github.com/mozilla/webmaker.org
[[image:https://dl.dropboxusercontent.com/spa/n5v3bx9nnjkdpzf/48qefzvs.png|350px|]]
* 3. Click the "Fork" button
[[image:https://dl.dropboxusercontent.com/spa/n5v3bx9nnjkdpzf/qle67plf.png|350px|]]
* 4. You will now have a copy of the repo on your own user account. e.g. https://github.com/alicoding/webmaker.org
* 5. To change existing copy on Webmaker.org, go to: locale/en_US/webmaker.org [[image:https://dl.dropboxusercontent.com/spa/n5v3bx9nnjkdpzf/0kp9v1nl.png|350px|]]
* 6. Click "Edit"
[[image:https://dl.dropboxusercontent.com/spa/n5v3bx9nnjkdpzf/2bhkipdj.png|350px|]]
* 7. Find and change the text you want.
* 8. Add a message to the "Commit field." (What kinds of messages are useful. What's the best practise?)
* 9. Add a message to the "description field" (What kinds of messages are useful. What's the best practise?)
* 10. Click on "Commit changes"
[[image:https://dl.dropboxusercontent.com/spa/n5v3bx9nnjkdpzf/26u9hcxx.png|350px|]]
* 11. Go back to the your forked repo. e.g. https://github.com/alicoding/webmaker.org
* 12. Click on green button "Compare, review, create pull request"
[[image:https://dl.dropboxusercontent.com/spa/n5v3bx9nnjkdpzf/moz70d8-.png|350px|]]
* 13. Review your changes and click on "Create pull request"
[[image:https://dl.dropboxusercontent.com/spa/n5v3bx9nnjkdpzf/71qxqd_w.png|350px|]]
* 14. Finally, click on "Send pull request."
[[image:https://dl.dropboxusercontent.com/spa/n5v3bx9nnjkdpzf/m8wzcrxg.png|350px|]]
* 15. That's it! You're done.