Bugmark

[andyl]

Project Lead: andyl

Mentor: Rob Schaefer GitHub: @schae234

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 :tada:.

---

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

• [x] 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.
• [x] 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)

• [x] 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.
• [x] Watch 'Mozilla & Working Open'.
• [x] Check the Syllabus for notes and connection info for all the cohort calls.

Before Week 3 (Sept 25): Mentorship call

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

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

• [x] Look up two other projects and comment on their issues with feedback on their open canvas.
• [x] Pick an open license for the work you're doing during the program.
• [x] 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.

[andyl]

I’m working with Large Enterprise who publish Open Source Software to provide a market-driven development tools and services so that they can use price signals to compensate and incentivize a distributed workforce.

[andyl]

Draft roadmap at https://github.com/bugmark/mozleaders/blob/master/roadmap.md

[andyl]

Canvas at https://github.com/bugmark/mozleaders/blob/master/canvas.md

[GeorgLink]

Hi @andyl, good to see you on board here at the Open Leaders :-)

We are in the same cohort.

[andyl]

@GeorgLink LOL that is great. What is your project?? Will be great to compare notes.

[GeorgLink]

I signed up with CHAOSS/Bugmark but decided to focus on CHAOSS. Now that I see you here, I think we can leverage our both engagement in Open Leaders for Bugmark.

On Mon, Sep 10, 2018 at 8:20 AM andyl notifications@github.com wrote:

@GeorgLink https://github.com/GeorgLink LOL that is great. What is your project?? Will be great to compare notes.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/MozillaFestival/open-leaders-6/issues/65#issuecomment-419909163, or mute the thread https://github.com/notifications/unsubscribe-auth/AIc5ReDiUi18TGniSXvfPvBJOLjXdaHEks5uZmcRgaJpZM4WgbwN .

[andyl]

Bugmark is a new application that allows any open-source project to use Market-Driven Development. Bugmark works with issue trackers, allowing project maintainers and community members to fund offers to fix issues. Workers can post counter-offers, and matches are generated auction style. Our goal is to generate price signals that identify high-value issues, to increase the quality of the open-source ecosystems, and to provide a way for developers to make a living wage in open-source.

At Mozfest we hope to launch a new version of our system that is packaged for easy installation, and would like to recruit early-adopter developers to build their own trading applications on the Bugmark exchange.