Code Monkey home page Code Monkey logo

tasks's Introduction

tasks

Internal ticket tracker related to non-resource specific issues.

tasks's People

Contributors

jwflory avatar nolski avatar

Stargazers

 avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

tasks's Issues

Create initial branding resources

Overview

I think given the amount of work we are doing, it would be incredibly useful to have at least some branding resources that we can use with out documents and communications.

Ideally we would have a brand book

Submit article to Opensource.com about LibreCorps resources

Summary

Write and submit an article about LibreCorps and our resources to Opensource.com

Background

This summer was busy and we made advancements on our resources for UNICEF cohorts. We want to write an article about what we did and some of the general applicability of these resources for anyone building and developing free/open source software projects and communities.

Details

  1. Complete first draft of article (in progress here)
  2. Feedback rounds from LibreCorps team
  3. Submit to Opensource.com editor team for review
  4. Wait and see if it is accepted

Outcome

  • More publicity for our work and what we are doing (useful for building SEO presence leading up to FOSDEM)
  • Connect Opensource.com readers to some useful resources / tools we developed under LibreCorps; possibly invite more interested folks to add feedback and participate in some LibreCorps processes

Invite SJ to LibreCorps GitHub org, help him set up notifications

Summary

Help add SJ's GitHub account to this LibreCorps GitHub organization

Background

SJ is not a member of this GH organization, probably should do some follow-up to get him here since he is not seeing any of this discussion.

Details

  1. Log in, navigate to github.com/librecorps
  2. Accept invitation
  3. Publish membership

Outcome

SJ receives emails about new discussion / focus for GH task tracking / planning

Write abstract/description for BoF session at FOSDEM 2020 by 11 Oct

Summary

Write abstract and description for Birds of a Feather (BoF) session about transparent/ethical evaluations of AI in FOSDEM 2020 before 11 October CFP deadline

Background

@Nolski and I discussed the idea of splitting up into two sessions about a week ago.

A FOSDEM 2020 main track session gives our ideas on AI transparency and ethics a platform, but it is mostly unidirectional, i.e. we are talking to an audience. To better support our overall mission, combining the main track proposal with a โ‰ฅ60 minutes BoF session affords us bidirectional conversations with others at FOSDEM.

We also reach two different audiences: the main track session gives a general overview of our ideas for anyone, and the BoF session offers a deeper dive on AI transparency/ethics for those with deeper background and interest.

Details

Need to write abstract and description before 11 October CFP deadline.

In another issue, we can discuss a roadmap of how to facilitate the session and best engage a crowd of people with our ideas (maybe taking a page or two out of our MozFest facilitator handbook). But I figure it is best to wait for CFP status updates before investing too much time into planning an open-ended BoF session.

Outcome

  • Obtain unique and helpful feedback on our ideas from a wider community
  • Empower others to become leaders within their own organizations for more ethical and transparent ways to develop AI systems

cc: @itprofjacobs

Export AI ethics FOSDEM brainstorming into outline format

Summary

Export brainstorming notes / ideas into easy-to-read outline format

Background

Our brainstorming notes are in a shared Google Doc. We received a few rounds of feedback on our core ideas and thoughts. Now, we are in a position to frame them into an outline for the FOSDEM talk.

Details

  1. Review Questions to ask section in Google Doc as a starting point
  2. Create a new Google Doc in the shared folder with only outline and maybe abstract
  3. Start expanding feedback loops more widely on our more polished ideas

Outcome

Enable us to receive targeted feedback on our main ideas without overwhelming someone with the full contents of our brainstorming document

Google Docs vs Github, relations and workflows documented?

While skimming the opensource.com article today, I drilled down two levels deep from the provided links into the Google Docs reading list, and noticed a typo.

I've since done the usual: Forked and cloned the librecorps/resources repo, corrected it in my clone, pushed to my fork, and from my fork issued a pull request to upstream. Assuming that goes through well enough, that will correct the typo in the repo. (Maybe I should have saved it as an easy bug for HFOSS but alas sometimes I have to just do the thing.) So far so good.

Along the way of doing that though I noticed a few things that aren't clear to me but that might be documented somewhere if only I can get some pointers and which might help other potential contributors less familiar with LibreCorps day-to-day:

  • What is the relationship between the resources repo and the Google docs?

  • How does content flow from one to the other, and in which direction?

  • Since the Google docs versions are the published ones but are not generally editable (I cannot, for instance, edit them from my non-RIT Google account), how might someone who is less familiar than me with our idiosyncratic use of tasks repos meant to channel their contributions? Any chance we can eventually replace each of the Google docs with some short text redirecting to their counterparts on the web site?

  • I noticed that the config.toml file makes reference to https://librecorps.github.io/resources which is fine. but the base URL (https://librecorps.github.io/) is 404, which I found disorienting.

๐Ÿ†• UNICEF open source metrics article for Opensource.com

Summary

Write article describing the open source metrics UNICEF Innovation is using to evaluate projects

Background

This is a <1000 word write-up about what metrics UNICEF is collecting, the KPIs the metrics connect to, and a high-level overview of how the formulas work. The scoring system devised by the UNICEF Innovation team (currently living in an offline spreadsheet) is really cool, and serves as an interesting application of the criteria we evaluate on to a mathematically-sound evaluation system.

Writing this article is a win-win for LibreCorps and UNICEF for the following reasons:

  • Expose UNICEF team's work into the open and motivates them to share their work more widely with others
  • Great feedback / use case to help us develop GrimoireLab dashboards (i.e. once we actually get it online, what do we build?)
  • Helps us connect UNICEF Innovation to CHAOSScon, which is a niche event right up the ally of this team and can help the UNICEF Innovation team get feedback on the KPIs they are evaluating cohorts / teams on (i.e. "does Metric X over Metric Y really matter?")

Details

I'm waiting on a high-level overview of the formulas from Cecilia. Once I have it, I'll start working through their scoring system to craft an article sometime in December 2019. We'll work on publishing in January 2020, leading up to CHAOSScon on January 31st.

Outcome

  • Share more interesting work from our engagement with UNICEF
  • Move the needle slightly for UNICEF Innovation team to practice Working Open

Evaluate GrimoireLab for open source community metrics

Summary

Evaluate whether GrimoireLab is a useful metrics tool for LibreCorps to set up for managing current / future contracts

Background

Grimoire is a visual dashboard presenting open source community/people metrics. It integrates with existing open source tools and platforms to give an approximation of changes in an open source project. It includes monitoring areas like source code, issue/task management, mailing lists/forums, documentation, continuous integration (CI), and more.

This could be a useful service for LibreCorps to provide. If we set up Grimoire, we could create visual dashboards for each team and/or cohort. The dashboards would include graphs and charts for pieces of what we already evaluate on with our rubrics. We could provide links to the dashboards both for individual teams/cohorts and also the UNICEF fund managers to periodically check-in and quickly see the state of a team's open source engagement.

It also gives us a more helpful and intuitive way to monitor progress by an individual team in small, gradual steps versus a team that is not engaging with our resources at all.

Details

@Nolski and I didn't yet come to an agreement on what this looks like or how it should be presented, so we decided to start with an experiment and see where it goes. Steps to bring a proof-of-concept experiment might look like the following:

  1. Spin up new DigitalOcean droplet under FOSS@MAGIC account
  2. Install Grimoire onto droplet
  3. Choose one team (preferably one doing well) to build a mock dashboard for, try out different data collection plugins to see what is useful or not
  4. Tweak internally based on feedback
  5. If we like it, present to UNICEF and get their feedback

Outcome

  • Us:
    • Easier to track small gains / community changes in a team's project
    • Helps us work across multiple repos / platforms (i.e. for example, easy to combine two GitHub repos and a GitLab repo)
    • Monitor cohort progress in a convenient-to-use web interface (i.e. easier for us to on-board new students / people to help with LibreCorps program)
    • Helps make LibreCorps work more indispensable to evaluating success of an open source project
  • Clients:
    • Move towards producing meaningful quantifiable metrics (these will get produced with or without us, do we want to influence these for the better?)
    • At-a-glance picture of how a project, team, or cohort is doing
    • Potential to reuse and repeat across future clients

cc: @itprofjacobs

Develop Roadmap for AI Transparency & Ethics Plans

Summary

As per my arrangements with UNICEF I am to develop a set of resources, tools, and guidance documents to assist machine learning focused cohorts can develop their technology in a way that is open, responsible, and ethical.

Outcome

A document with my plans in priority order of which tasks I would like to complete.

Machine learning model template

Summary

Teams are hesitant to release their machine learning code open source as they feel it's not as simple as other application code. It would be nice if we had a succinct template to

Background

This stems from my talks with MacroEyes and Har Zindagi. They both are wary about releasing their machine learning models as they might be used improperly or not understood correctly. I think we could really provide a useful resource that hasn't been used beyond more than one project yet.

I was reading a white paper a while back which researched this quite a bit. Perhaps we could also adapt the publiccode.yml document created by the public code network?

Outcome

I think a great outcome for this would be a README template or at very least a how to use document you can embed in the repository/documentation. Something easily accessible like a markdown file

Create Mission Statement Guide

>>> Link to Guide <<<

Overview

We want to create a comprehensive guide on developing a FOSS mission statement using the best resources out there on making these decisions in a way that's transparent and inclusive

Output

Mission statement document

Create Template for Milestones

>>> Working Draft of Template <<<

Summary

Create a draft template to use when delivering Milestone plans for our companies

Background

Our companies need a detailed plan of action when it comes to developing their FOSS strategy. This milestone tracker will have specific points of actions, deliverables, and resources needed to progress from one step to the next.

Outcome

A finished milestone tracker template

Collect feedback on FOSDEM abstract and outline before CFP deadline

Summary

Reach out to others in problem space and collect feedback on our polished ideas / proposal

Background

For the last month, we developed resources around the AI ethics / transparency / freedom idea and worked closely with a few folks to develop our thoughts further. Now, we want to polish our ideas more from the feedback we collected and broaden the feedback loop more widely leading up to the first FOSDEM CFP deadline: Friday, 11 October 2019.

Details

Cross-reference #8.

  1. Add polished ideas (abstract + outline) to new Google Doc, link to it in this GitHub issue
  2. Identify others in the AI problem space to invite for sharing feedback
  3. Timebox final feedback on abstract/outline to Friday, Oct. 4th (one week before deadline)

Outcome

  • Condense our brainstorming ideas into a more easily consumable format
  • Receive feedback from folks coming from different backgrounds / perspectives
  • Continue to polish our ideas leading up to FOSDEM CFP deadline

Review BMGF Phase II Funding Document

Summary

>>> DOCUMENT <<<

Ibrahim has asked for a review on their phase II funding document for the Gates Foundation.

Background

UNICEF's Gates cohorts applying for a second round of funding.

Details

Review should focus on how FOSS consulting can help them achieve this second round of funding.

Outcome

Written report on document as well as updates to BMGF team milestone plans

Create spreadsheet of all public repositories / resources for all UNICEF IF cohort teams

Summary

Create a shared spreadsheet with URLs for where each team is maintaining their open source project and portfolio

Background

Each UNICEF Innovation Fund (IF) cohort uses different git forges or project-hosting tools for their projects. There is not a single resource to look at to find where each team is doing their open source development.

Our task is to help the UNICEF IF managers monitor progress of each cohort and help make the open source efforts of each cohort easier to measure and track. This also helps us because it gives us a resource to use when we want to check in on a project or if a cohort asks us for help (i.e. we can find out where their open source activity is).

Details

This will be an iterative process and may take a month to make it a comprehensive resource. I suggest this approach:

  1. Create Google Form survey with questions for each cohort that ask:
  • List all public repositories
  • Explain the role of each repository in their project (i.e. front-end? back-end? blockchain component? plug-in for another FOSS project?)
  1. Send out to each cohort + UNICEF IF managers
  2. Follow up with specific teams to fill the form where necessary

Outcome

  • Easier to locate open source progress and activity of a UNICEF IF cohort
  • Assists UNICEF IF managers in monitoring cohort activity (separate from the work we are doing)
  • Less confusion over where open source development is done, if it is being done

Migrated from FOSSRIT/tasks#92.

Create travel budget and itinerary for JFlory at FOSDEM 2020

Summary

Budget and plan out expenses for @jwflory to attend SustainOSS / CHAOSSCon / FOSDEM 2020

Background

To help get a leg on cheaper airfare prices, I need to prepare a budget of estimated expenses for traveling for the trio of FOSS conferences centered around LibreCorps outreach and networking.

Details

  • Round-trip airfare from Atlanta
  • Lodging / accommodation in Brussels
  • Food
  • Public transit

Outcome

Save money by booking travel ahead of time for FOSDEM 2020

Connect High Level Rubric with Topic Rubric

Summary

This is a detailing of the relation between issues #86 and #96.

Background

The High Level Rubric needs access to higher detail from the topics listed for each team. This issue explains how this will be done.

Details

  • Get issues #86 and #96 done in their own right.
  • Send the rubrics to the teams
  • Once the teams start self-evaluating we will start to inform the High Level Rubric, factoring in our own evaluations as well.
  • We link to the topic rubrics from the high level rubric

Outcome

We will have an easy-to-access overview of the team's progress as well as an easy way to get more detailed information.


Migrated from FOSSRIT/tasks#97.

Come up with labeling scheme to keep things organized

Summary

Add more issue labels to better include other types of tasks added to this repository

Background

We have a few labels already for different UNICEF cohorts and meetings, but there are some tasks in this repo that do not fit into the existing labels. Adding useful labels for things we could quickly highlight to someone in a passing conversation (e.g. issues about resources, talks we've given, etc.) helps us identify our areas of specialization.

It also makes it easier to write articles about some of our work too. ๐Ÿ˜…

Details

I haven't thought about this in depth yet. Next step for me is come up with a list of labels, get feedback from others if they are actually useful / serve a purpose, and add them.

Outcome

  • Easier to navigate issues in this repo
  • Easier to highlight some of our key focus areas, both internally and externally

Data Responsibility & Sharing Guidelines

Summary

Many of our AI focused cohorts are unsure as to how/whether they should release their training datasets along-side their machine learning code.

Details

The UN OCHA has provided great guidance on releasing data, determining sensitivity, etc. The main guidance document can be found here:

https://centre.humdata.org/wp-content/uploads/2019/03/OCHA-DR-Guidelines-working-draft-032019.pdf

I have contacts at HDX which might serve as a the perfect platform to release their data on.

Outcome

An initial document or perhaps roadmap template for assessing & releasing a data set online.

Research outreach opportunities for ICT4D 2020

Summary

Research more about a LibreCorps presence at the ICT4D conference

Background

The ICT4D conference is potentially a great venue for us to do LibreCorps outreach and seek out new partnerships. There are two options for us to participate: by speaking or by exhibiting.

Questions to answer:

  • What do we want to pitch for a CFP?
  • When does the CFP close?

Details

Once we discuss the above questions, we can figure out a new blueprint with deadlines, content goals, etc.

Outcome

Continuing to share and promote the LibreCorps work and mission to seek new partnerships abroad

Create presentation outline for MozFest + LibreCorps

Summary

Create first draft of presentation/session outline for LibreCorps MozFest 2019 session

Background

Earlier this year, we applied to run an interactive session at Mozilla Festival 2019 with our LibreCorps resources and assets. The session was recently accepted. Now, we need to begin planning the session and coming up with an interactive format to include a live audience in using our resources.

Details

For now, a first step is to organize details into a document outline. Then I can collect some feedback from others and begin building out further steps to improve on what we present there at MozFest.

Outcome

Initial path forward on what we take to MozFest 2019

Set up follow up calls with milestone plans

Summary

Set up walk through calls for UNICEF teams based on our new milestone planning documents

Blocked by #2

Outcome

Follow up calls based on our new milestone planning document

DISCUSSION: Resources for cohorts

Overview

I wanted to start a discussion about where we will be spending out effort when delivering physical/digital resources beyond specific guidance among the companies and organizations we are working with.

Details

I think each resource we propose should hit a few qualities

  • They should come from a specific need that we have identified from our intro calls or follow up meetings
  • They should have a measurable impact on our grading rubric
  • They should be generalizable that new organizations should be able to use them.

Outcome

We want to have a set of ideas for resources that can branch out into their own tickets for us to begin creating.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.