Kōrero Māori

[kmahelona]

Project Lead: @kmahelona

Mentor: @GuteMonik

Welcome to OL6, Cohort A! This issue will be used to track your project and progress during the program. Please use this checklist over the next few weeks as you start Open Leadership Training 🎉.

---

Before Week 1 (Sept 11): Your first mentorship call

• Complete the OLF self-assessment (online, printable). If you're a group, each teammate should complete this assessment individually. This is here to help you set your own personal goals during the program. No need to share your results, but be ready to share your thoughts with your mentor.
• Make sure you know when and how you'll be meeting with your mentor.

Before Week 2 (Sept 18): First Cohort Call (Open by Design)

• Complete Assignment 'Write Your Vision or Mission Statement'. Leave a comment on this issue with your draft vision statement & be ready to share this on the call.
• Watch 'Mozilla & Working Open'.
• Check the Syllabus for notes and connection info for all the cohort calls.

Before Week 3 (Sept 25): Mentorship call

• Look up two other projects and comment on their issues with feedback on their vision statement.
• Complete your Open Canvas (instructions, canvas). Comment on this issue with a link to your canvas.
• Start your Roadmap. Comment on this issue with your draft Roadmap.

Before Week 4 (Oct 2): Cohort Call (Build for Understanding)

• Look up two other projects and comment on their issues with feedback on their open canvas.
• Pick an open license for the work you're doing during the program.
• Use your canvas to start writing a README, or landing page, for your project. Link to your README in a comment on this issue.

This issue is here to help you keep track of work during the first month of the program. Please refer to the OL6 Syllabus for more detailed weekly notes and assignments past week 4.

[kmahelona]

Draft Vision Statement

We’re building tools to assist indigenous language communities with gathering corpus so they can create applications to help accelerate the documentation and revitalisation of their indigenous languages. We want to open source this project so we can empower indigenous communities to lead their own initiatives and maintain sovereignty over their data.

Links

• Open Canvas
• Roadmap
• Readme

License

We're in the process of developing our own license for this project. It's called the Kaitiakitanga License and a draft of it is available here. Needed a license for the project is a known issue https://github.com/TeHikuMedia/corpora/issues/6.

[fraguada]

Strong statement. Beyond liking the vision, I particularly like the

We’re building tools to ...

start to the statement. Looking forward to seeing this develop.

[gorlapraveen]

Hey @kmahelona , projects looks interesting on assisting the people to develop indigenous innovations!

[fraguada]

Nice to see this translated into the open canvas. The key metrics is a challenge for this project in particular since a quantitative value, for example, number of languages supported, number of groups, hours, etc, doesn't seem to represent true success. What about extending the key metrics to include languages on certain platforms? Is there a firefox add-on language for this group/language? Can wikipedia articles be translated to this language? Are there wikipedia articles specifically in this language that will need to be translated into other languages. I find that this metric, lets call it, 'translation pressure': the demand for a language in relation to content, might be something to explore.

Note: I have no clue about linguistics nor the preservation of culture or languages and what I have just mentioned either probably exists, or is completely irrelevant and should be ignored!

[kmahelona]

@fraguada those are all good points. I'm used to reporting to funders on those types of quantitative values. I think hours is definitely a good measure of success but perhaps more so for the group collecting the corpus and not necessarily this project. The thing with platforms is there's heaps of work that happens between data collection (which this app does) and trained model (which doesn't happen here) in this project so does "# apps using transcription API" apply?

And maybe there's another issue here in that the scope of the project is growing too much. For example we've more or less built a captioning tool into the project not only to solve the data problem but also to offer transcriptions and captioning as a service...