Confirmed users
1,021
edits
Engagement/Developer Engagement/Hacks blog: Difference between revisions
Jump to navigation
Jump to search
Engagement/Developer Engagement/Hacks blog (view source)
Revision as of 23:22, 5 January 2015
, 5 January 2015updating the wiki to reflect editorial staff & other org changes
(updating the wiki to reflect editorial staff & other org changes) |
|||
| Line 1: | Line 1: | ||
==What Mozilla Hacks is - our vision== | ==What Mozilla Hacks is - our vision== | ||
Mozilla Hacks is one of Mozilla's most important channels for developer outreach and engagement. We want it to be | Mozilla Hacks is one of Mozilla's most important channels for developer outreach and engagement. We want it to be a key resource for people developing for the Open Web, providing news and in-depth descriptions of technologies and features. We will cover both development tips and tricks in general, but also look at features in Mozilla products from a technical perspective - to share our approach and line of thinking, and hopefully inspire other developers and companies to implement what we've built for the Web. | ||
Like [https://developer.mozilla.org/ MDN (Mozilla Developer Network)], Mozilla Hacks is a web browser-agnostic resource, focused on the Open Web and sharing knowledge with all web developers out there. | |||
Mozilla Hacks is not a press release channel and we don't reblog existing blog posts. We | Mozilla Hacks is not a press release channel and we don't reblog existing blog posts. We publish original content. If we find an interesting blog post, we might highlight it, but always with our own take. | ||
Our goal is also to make as much information as possible about the blog publicly available, such as number of readers, most popular posts and more. | Our goal is also to make as much information as possible about the blog publicly available, such as number of readers, most popular posts and more. | ||
| Line 19: | Line 19: | ||
==Writers/contributors== | ==Writers/contributors== | ||
Members of the Developer Engagement Team | Members of the Developer Engagement Team often write for Mozilla Hacks, but any other Mozillian is welcome to contribute! We are always seeking new technical contributors. If you know something interesting or are working on an interesting project that's ready to share with the readers of Mozilla Hacks, please let us know! We can be reached at mozhacks [at] mozilla [dot] com. We hope that the exposure you will get - both as an author and in the Mozilla context - will be good motivation for deciding to write for Mozilla Hacks - we will help promote your post! | ||
And if you have the technical expertise, but aren't sure about | |||
And if you have the technical expertise and a compelling topic, but aren't sure about your writing, we'd be happy to help put together an article together with you. | |||
We prefer original content, not reblogged, and if you want to blog in your own blog we would really like to see different versions/takes on the content. Additionally, we want to release things in Mozilla Hacks the same time as your possible personal blog post - otherwise, it's already on Twitter, Planet Mozilla and more, and some of the "oomph" factor and possibilities are missed. | We prefer original content, not reblogged, and if you want to blog in your own blog we would really like to see different versions/takes on the content. Additionally, we want to release things in Mozilla Hacks the same time as your possible personal blog post - otherwise, it's already on Twitter, Planet Mozilla and more, and some of the "oomph" factor and possibilities are missed. | ||
| Line 28: | Line 29: | ||
==Author responsibility== | ==Author responsibility== | ||
''Mozilla Hacks is not a billboard or announcement channel.'' It is a channel to educate, inform and engage in dialog with our readers, a place to listen for the opinions of developers, address their questions and concerns, and provide clarification regarding Mozilla products and positions. A blog post author is responsible for moderating and replying to comments. Not every comment needs a reply, but questions and similar should be addressed. People take the time to read and to comment, and they deserve the respect to have that communication. Also be aware that comments can be quoted in press, direct questions from journalists and similar, so please reach out to Mozilla press if you want/need to verify your statement. | |||
It is also a long term base for a good relations with developers based on mutual respect and communication. | It is also a long term base for a good relations with developers based on mutual respect and communication. | ||