Skip to content
This repository has been archived by the owner on Nov 21, 2018. It is now read-only.

Commit

Permalink
emoved duplicating markdown
Browse files Browse the repository at this point in the history
  • Loading branch information
@therebelrobot
therebelrobot committed Mar 3, 2015
1 parent f7598c0 commit 49f192c
Showing 1 changed file with 0 additions and 26 deletions.
26 changes: 0 additions & 26 deletions wg-meetings/2015-03-02.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -55,32 +55,6 @@ Provide an option for localization teams to redirect their custom local domains

Do a full design pass. Use what we have and iterate over it. Adapt to the current design of the website. Issue using markdown for more complicated stuff such as version-stuff. Suggest to move to an html-markdown hybrid for the content to be translated.

* #195 - use jade templates (added by @Fishrock123)ideration. Discussion will continue in the issue on Github. WG want to start by adding new people as collaborators, before consider them for a WG membership.

* #246 - Remove/flag stale i18n articles (added by @snostorm)

This comment has been minimized.

Sign in to view

Copy link
@bnb

bnb Mar 4, 2015

Did you mean to remove everything from here down? I don't see duplicate content for it anywhere, and there's not much left over when all this is removed.

This comment has been minimized.

Sign in to view

Copy link
@therebelrobot

therebelrobot Mar 7, 2015

Author Contributor

It is duplicate content, #195 - use jade templates starts again below this removal. This was an issue with how my local vim has handling clipboard pastes.

This comment has been minimized.

Sign in to view

Copy link
@therebelrobot

therebelrobot Mar 7, 2015

Author Contributor

I take that back. I think the next one is action items. I'll make the adjustment.

This comment has been minimized.

Sign in to view

Copy link
@therebelrobot

therebelrobot Mar 7, 2015

Author Contributor

Oh, good laws. Yeah, it is stupid duplication. Nevermind. This removal was for vim issues.

Remove untranslated content from the repo before starting to link to the translated versions of the website. Keep placeholders for languages that has started translation.

* #153 - translation "policy" (loose translation, etc.) (added by @snostorm)

Danish localization team brought up this issue. Should they translate the technical terms, or keep them in English? Whom is the target audience? If the audience has an understanding of the English terminology then it should be up to the translation team to decide. WG don’t want to restrict teams to a direct translation as long as the translation conveys the same content.

* #136 - subtrees / how do sub-groups publish (added by @snostorm)

Norwegian team will be used as an experiment for implementation subtrees into the iojs/website repo. We will point the content/no directory to the iojs/iojs-no website branch. Pull-requests and changes will have to go to the localized repo’s website branch in order to avoid conflicts. This will need to be documented, and training may be required in order to get this working. Hopefully this will end up making things cleaner for the localization teams.

* #254 - SSL all things (as relating to #136 above) (added by @snostorm)

<all-the-things.gif>

The WG is here to aid their (localization groups) workflow. WG should be working to providing reasons for the localization teams to use the iojs.org website and not make their own, duplicated, processes and workflows.

Provide an option for localization teams to redirect their custom local domains to the iojs.org website.

* #181 - Website Design Pass and possible dedicated lead for build (added by @snostorm)

Do a full design pass. Use what we have and iterate over it. Adapt to the current design of the website. Issue using markdown for more complicated stuff such as version-stuff. Suggest to move to an html-markdown hybrid for the content to be translated.

* #195 - use jade templates (added by @Fishrock123)

Avoid adding additional tech, our current stack should do what we need.

0 comments on commit 49f192c

Please sign in to comment.