Media Technology News
The biggest issues pointed out by the community had to do with the tone of the language in the documents. Many pointed out that it did not match the values of our community. We took a closer look at organizations such as the Wikimedia Foundation and Mozilla, incorporating some of the approaches they took to make our terms a bit more human. We trimmed and shortened what we could. We clarified where things were ambiguous. The end result is much more in line with our community values.
Some examples of changes include the following:
- When possible, we changed the tone of both documents to make them more friendly.
- We removed capital letters and used other means to make specific parts of the document noticeable.
- We deleted a couple of references to collecting data that we do not actually collect.
- We clarified that we won’t block accounts “for any and no reason”, but only in cases of Terms of Service, Code of Conduct and Git access policy violations.
- We clarified active notification of users about material changes to policy. We will send an email at least 72 hours prior to changes going into effect. This will give users time to delete their accounts if they don’t want to accept new policies.
- We added contact info and updated all phone numbers, addresses etc. to be formatted according to international standards.
- We clarified that you don’t need to create an account to access the Website, just some parts of it.
- We clarified how to notify us in case of unauthorized access to user account.
- We clarified how long do we store data after it has been removed from user profile.
We did leave some things from the previous draft without major changes, such as bullet points under section C, for example. And we did it for a reason. One of our goals is to make Drupal.org a place where everyone feels comfortable. Additionally, we have to ensure that Drupal.org is protected if a legal issue does arise. Those bullet points are there not because we want to be able to police or censor the activity on the site. This language exists because it protects Drupal.org if one user takes issue with content from another user. We will still use the process outlined in the Drupal Code of Conduct to resolve any issues whenever we can.
With that in mind, please take a look at the latest drafts:
Thank you for all your help in building these documents.
I’m excited to announce (although a little late) that my responsive design extension for Brackets, known as Response, has been updated to work in the latest version of the tool. Now before I go on I have to give the full credit for this update to Chen-Heng Chang. Make sure you give him some love on Twitter (@kidwm). Go on over to his fork of the project to get the code.
Until I can get his changes merged over you can consider his fork as the official repository for the project for the time being.
There are detailed instructions for how to setup and install the extension in the latest version of Brackets on the repository’s main page. The final step (installing the extension) only has instructions for Windows. For those on a Mac here is the path you need:
Important: there are still many bugs remaining so I will be doing an updated video tutorial in the next couple of days. Until then please refer to this video.
New video tutorial explaining how to use Core Image filters on iOS using Swift.
New video tutorial explaining how to create menubar applications for OS X using Swift.
New video tutorial explaining how to create class extensions in Swift that allow you to easily extend the functionality of framework classes.
New video tutorial showing you how to use storyboards to visually lay out and connect the views in your Mac app.