samking / code-the-change-projects Goto Github PK

Interface with the docs api and post the link.

I'm afraid that if we ask projects to do this, they'll get the permissions wrong.

Some thoughts of different fields to have:

• a link to a Google doc where anyone with the link can edit so that engineers and volunteers can coordinate
• a link to the public code repo
• check out sc4g and ctc project listings or ctc project form for guidelines on what to ask.
• who's behind the project?
• what problem is the project solving?
• what is the project?
• how can i help?

Do we want there to be one 'description' field, or do we want specific sub-fields?

• lint script to lint all python files (and fix imports, similar to https://chromium.googlesource.com/chromiumos/chromite/+/master%5E/appengine/ae_pylint)
• script to run the server
• script to clean annoying .pyc files
• script to run unit tests

Title
Description (potentially several fields if we want to force orgs to ask specific questions)
Tag keys
Owner key
Created date
Updated date
Completed
Page views

• name (key)
• description
• category [technical, focus area]

Potentially create a WorkingOn model with a project key and user key.

Project page will have a button that lets a user sign up or un-sign-up.

Project page will display all users working on it.

User page will display projects signed up for.

The user page should list the projects I posted and the projects I'm signed up for.

I should be able to filter the project page by tags.

I should be able to filter the project page by number of people signed up for the project.

The project page should be sorted by recently-updated.

• name
• email
• free text: other contact? development history?

• Landing page?
• Description of CtC?
• Description of the db for nonprofits?
• Description of the db for engineers?
• Guidelines for a good project (including a description of what orgs are allowed to use the site)
• Guidelines on licensing, a description of Apache v GPL
• Disclaimer of liability, privacy policy, etc.

There should be a list of pre-populated tags (or a tooltip for good tags?). Maybe tag autocomplete. Maybe a series of checkboxes (with an other field that accepts comma separated input) on the edit page would work?

Do this for both focus area and technical skills.

Have some engineers and a nonprofits run through the workflow. Observe their pain points.