-
Notifications
You must be signed in to change notification settings - Fork 0
V2 Roadmap
WORK IN PROGRESS
Wordset is our baby. We've built it to a point that it's actually currently the most full featured collaborative data project out there. It's a project that we really believe in and what makes us love it is that it has so many things we could do, that it's mind boggling. Deciding what we are actually going to end up doing is the hardest task of all. What are we going to focus on?
This is an attempt to write up the goals of the project over the coming months (I almost wrote "couple of months", but public documents aren't a place to be too eager). There are lists of things that need to get done to match the goal above, and they are tagged as Project, Community, API, or UI.
See this longer discussion of Seqs
Switching to this much more freeform system we think is important for building out the future of Wordset.
- API- Words split into Seqs -> Words API#9
- API- Words changed to be Wordsets
- API- Change the API to include seq searching API#10
- UI- Loading a page "/word/sushi" should load the Seq "sushi" and then grab it's associated wordset (note: the example path there will change with multi-language) UI#20
- API- Create merger proposal API#11
- API- Create merger project, where we have multiple Seqs per words API#12
One of the things we're most excited about is to help organize the languages that we are documenting. Part of that is definitely fleshing out a far richer dialectal / regional notation and searching system than anyone else. Every language has lots of variety and we want to express that and help notate that. In fact, Hampton and Michael both write/speak a merged version of UK and American English, since their native dialects were different. Expressing this kind of stuff has been one of the hardest things to wrap our brains around, but we have a pretty solid idea at this point and think we are ready starting to implement it.
A region is a subset of a dialect which is a subset of a language.
Both meanings and Seqs can be tagged with regionality. For example, the seq "color" is chiefly used in the US. The seq for "scheme" is the same in all regions, but the meaning of "scheme" as a positive (governmental) plan is chiefly used in the UK.
- API- Build out basic Dialect/Region data objects API#13
- API- Pick initial english dialects / regions API#14, see also the language progress wiki page
- API- Add concern to Seqs and Meanings API#15
- UI- display regionality next to the seq or the meaning. UI#23
We can't claim to revolutionize language and only do it for English. It's absolutely critical that we expand out into at least one other language in the coming months. In order to do this, we'll need to do some things first..
- API- change the data models, mostly POS-per-language, proposals-per-language, wordlist-per-language, etc. API#17
- API- change the API to accept a lang parameter API#8
- API- add options for e.g. gender, etc. on a per-language basis API#7
- UI- integrate with a localization engine for the front end.. the buttons can't be in English! UI#15
- UI- teach the Ember-Data models to know about languages UI#21
- UI- update the app to not use the static POS system, and learn to dynamically load the list UI#18
- UI- update paths from "word/sushi" to "en/sushi", etc. UI#16
- UI– display other aspects of a word not present in EN (e.g. in DE, the case or gender; in NO, Bokmål or Nynorsk) UI#17
- Project- find a good starting dictionary for a particular language (see separate page on language options)
- Project- select which language we are going to expand into first (see separate page on language options)
- Community- put up a "sign up to help" link to start collecting people who can help in each language
- Community- select a set of founding editors for another language (the last 3 kind of go together)
- UI- Make removal proposals more obviously a removal using visual clues.UI#19
- UI- Clean up Proposal code... it's pretty fugly with partials and stuff right now UI#14
- UI- Fix bug where validations don't work correctly during a Proposal Edit. UI#12
- API- Build in OAuth support API#5
- UI- (SKIPPED) Switch from not-so-good "ember-auth" implementation to Torii UI#13