Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Browser policy #61

Merged
merged 4 commits into from
Jan 17, 2013
Merged

Browser policy #61

merged 4 commits into from
Jan 17, 2013

Conversation

bear454
Copy link
Member

@bear454 bear454 commented Jan 11, 2013

@cassiolupifieri is going to add the browser support policy; this is just prep work so he can add it.

@roman-neuhauser
Copy link

please keep line length at 72 characters max. and the html table is barely readable in the text file, can you use markdown syntax for it instead?

</tr>
</table>

**_The complete table was last update on 14 January 2013._**
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo: it has to be "updated", not "update".

@cornelius
Copy link
Member

In a discussion with @dmajda, we came to the conclusion that we would introduce a top level section "Support", where we collect the different aspects of what we support. The browser policy should go there as well as the policy about supported base systems or supported hypervisors.

@cassiux
Copy link
Contributor

cassiux commented Jan 15, 2013

@roman-neuhauser not is not possible use markdown for the table, I discussed that before with @cornelius and @jamestyj,

@cassiux
Copy link
Contributor

cassiux commented Jan 15, 2013

@cornelius Fixed the text. I agree in create a top level "support".

@roman-neuhauser
Copy link

@dmajda, @cornelius: in a Support section, i would expect to find information on Support I can get as a user, not information on base systems and client software. would you expect to find a listing of file formats under a word processor's manual section called Support?

@roman-neuhauser
Copy link

@cassiolupifieri what are the obstacles?

@cornelius
Copy link
Member

@roman-neuhauser How to get support as a user should go there as well. But knowing which scenarios are eligible to get supported is part of that, isn't that?

@cassiux
Copy link
Contributor

cassiux commented Jan 15, 2013

@roman-neuhauser the markdown doesn't support "colspan" attributes.

@cornelius
Copy link
Member

Let's merge this now, and than go forward from there.

cornelius added a commit that referenced this pull request Jan 17, 2013
@cornelius cornelius merged commit 9ee4e22 into master Jan 17, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants