Difference between revisions of "Funded Project System Development"

From Inkscape Wiki
Jump to navigation Jump to search
 
(23 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Finished ==
√ Verify the following Project Types are defined in the database:
      Administration,
      Bug Triaging,
      Bug Fixing,
      Refactoring,
      Feature Development,
      Documentation,
      Website,
      Tool Development,
      Other
√ It's time to get rid of the tripling of projects on the Projects page.
== Tasks ==
== Tasks ==


1. The interface is very slow. It makes it difficult to figure out how the site works. Clicking on one of the project name takes so long to bring up that project's information that one wonders if that was the correct way to do it. If the interface cannot be sped up then at least some instructions should be added to the web page. (e.g. "Click on project name to edit that project's parameters.")
* The interface is very slow. It makes it difficult to figure out how the site works. Clicking on one of the project name takes so long to bring up that project's information that one wonders if that was the correct way to do it. If the interface cannot be sped up then at least some instructions should be added to the web page. (e.g. "Click on project name to edit that project's parameters.")
 
* SVG's are not allowed for the Banner and Logo!! I've heard that there is some great Libre Graphics program that can produce SVGs that scale better than PNGs on the web...
 
* The Logo is required to be 150x150 px but it is displayed at a different resolution leading to blurring. (See #2 for solution.)
 
* Can't change "Proposer". The initial projects should have "Inkscape" as the proposer.
 
* Can't format the "Project Updates". We should be able to use at least a limited set of HTML tags. [Markdown is available in https://code.launchpad.net/~marenhachmann/inkscape-web/projects-pages, but there's no way currently to limit the kind of markup we want to allow. Not sure if it's enough to limit design by CSS alone...]
 
* "Project Update" is not a good title for the initial project description. We should have "Project Description" (or something similar) followed by a "Project Update" section. [These are now separate items in https://code.launchpad.net/~marenhachmann/inkscape-web/projects-pages]


2. SVG's are not allowed for the Banner and Logo!! I've heard that there is some great Libre Graphics program that can produce SVGs that scale better than PNGs on the web...
* What does "Importance" mean. It is not clear what the input should be (text or number), what the numbers mean (low number more important than high number?), and what is the range of acceptable numbers. A drop-down menu might be better here. [Implemented in https://code.launchpad.net/~marenhachmann/inkscape-web/projects-pages]


3. The Logo is required to be 150x150 px but it is displayed at a different resolution leading to blurring. (See #2 for solution.)
* How are the project fund raising goals set? I didn't see that in the interface.


4. Can't change "Proposer". The initial projects should have "Inkscape" as the proposer.
* The project summaries on "https://inkscape.org/en/project/" should be customizable and not just first few lines of the "Project Update". [Bryce asked for an 'elevator pitch']


5. Can't format the "Project Updates". We should be able to use at least a limited set of HTML tags.
* Decide where in the site to link to the Add a Project form. Maybe under Contribute? [We can add that link to several places, I think. I'd also like to see it on the Funded Projects page itself.]


6. "Project Update" is not a good title for the initial project description. We should have "Project Description" (or something similar) followed by a "Project Update" section.
* How should we hook in the ui/mockups gallery category to the projects? We could tie specific items or a single gallery so we can attach files to the project? [Easiest way: by linking from a text, maybe?]


7. What does "Importance" mean. It is not clear what the input should be (text or number), what the numbers mean (low number more important than high number?), and what is the range of acceptable numbers. A drop-down menu might be better here.
* How should we vote or +1 various projects? Should we have separate +1 Concept (in an ideal world) +1 Design (I like the design for this project) +1 Technical (It's technically well spec'd)? Or just a single thumbs up?


8. How are the project fund raising goals set? I didn't see that in the interface.
* How do we identify that a given applicant is valid? (I.e. that they are in the AUTHORS file)  Perhaps look at what was done for the voting system since it has the same requirement.  Maybe the users table needs to have a field or flag added to indicate people who are official Inkscape contributors? [We could use the team functionality for this. There will be a group/team for developers.]


9. The project summaries on "https://inkscape.org/en/project/" should be customizable and not just first few lines of the "Project Update".
* State update. A process is periodically invoked to calculate the state of projects. Most state changes are time-based, but there are exceptions that allow adjusting states manually.


10. It's time to get rid of the tripling of projects on the Projects page.
* Update users about progress (Hook up to mailing system).


== Pages to create ==
* Keep track of edits of the respective items (wishlist)


* Fundraising Coordinator registration page
* Allow for discussion on a project (wishlist)
* Fund allocation page for FC's to put money towards particular projects, either in absolute amounts or proportionally, or according to a programmatic rule (4 oldest projects, evenly across all projects of a given type, etc.)
* Fundraiser definition page.  Indicate the keyword for flagging incoming donations.  Also allows marking a fundraiser finished.  Initial coordinator for the fundraiser is the person who creates it.  The fundrais
* Signoff page for completed projects
*


  + Projects
== Data Fields ==
  + job_id
 
  + Project Name
Project
   + Date Proposed
   - Description (not in trunk, but exists in https://code.launchpad.net/~marenhachmann/inkscape-web/projects-pages)
   + Type: [
   - Progress Reporting URL (not in trunk, what is this for?)
      Administration,
      Bug Triaging,
      Bug Fixing,
      Refactoring,
      Feature Development,
      Documentation,
      Website,
      Tool Development,
      Other
      ]
  + Description
   + Deliverables
   + Deliverables
   + Acceptance Criteria
   + Acceptance Criteria
  + Progress Reporting URL
   + Expected Duration
   + Expected Duration
   + Date Started    # Implies is_assigned
   + Date Started    # Implies is_assigned
   + Date Completed
   + Date Completed
   + Proposer
   + Proposer
   + Supporter
   + Supporter ('Second')
   + Reviewer
   + Reviewer
   + is_fundable
   + is_fundable
   + is_pre_approved
   + is_pre_approved
Fundraiser
  + Importance
   + fundraiser_id
  + Logo
   + Fundraising Coordinator
  + Banner
  + Title
  + Slug (for url)
  + Date created
  + Date edited
   + Manager
   + Project Type


Fund Allocations
ProjectUpdate
   + job_id
   + Project
   + fundraiser_id
   + Description
   + Amount
   + Image
  + Creator
  + Date created
  + Date edited


Application
Criteria
   + person_id
   + Content
   + job_id
   + Detail
  + Job Qualifications
  + Implementation Plan
  + Date Vetted


Dialog Interfaces
class Deliverable(Model):
=================
    (A single deliverable item)
Propose a project - Keep it simple, one text field to fill out.
    + For Project
(We'll need some mechanism to detect and merge/remve dupes.)
    + Name
    + sort order
    + Date targeted
    + Date finished


List my projects.  Both projects I've proposed, and ones I've applied
Task
for.  Indicate status and provide modify links.
  (A task or sub-task of a deliverable stage)
  + For Deliverable (= delive)
  + Name
  + Date targeted
  + Date finished


Modify project definition - Allows addition of detailed description,
Application (= Worker)
deliverables, and so on.  Perhaps give a % complete?
  - Job Qualifications (not in trunk, needed? Could also live inside 'plan')
  + person_id (= user)
  + job_id (= project)
  + Implementation Plan (= plan)
  + Date Vetted
  + Assigned


List fundable/funded projects.  For fundraiser coordinators to brwse
Fundraiser
through, and for applicants to apply for.
  - fundraiser_id
  - Fundraising Coordinator


Add a fundraiser
Fund Allocations
 
  - job_id
Allocate funds to fundable projects.  Allow fundraiser coordinators to
  - fundraiser_id
allocate money from the funds they raised to specific fundable
  - Amount
projects.
 
Apply for project
 
List applications.  Can display All, Pending, Approved, or Denied
applications.
 
Vet applicant.  To be used by the board member charged with vetting
applicants.  Displays the application and allows specifying yea or nay
or to request clarification by the applicant.
 
So for example, we should be able to submit an entry, but where? Have
a page under contribute for designs?
 
How should we hook in the ui/mockups gallery category to the projects?
We could tie specific items or a single gallery so we can attach files
to the project?


How should we vote or +1 various projects? Should we have seperate +1
== Potential Sources of Project Ideas ==
Concept (in an ideal world) +1 Design (I like the design for this
* [[Projects]]
project) +1 Technical (It's technically well spec'd)? Or just a sinlge
* [[Google_Summer_of_Code]]
thumbs up?
* [[Roadmap]]
* [[Extension architecture proposals]]
* [[GtkMMification]]
* [[FeatureNotePad]]

Latest revision as of 16:46, 2 April 2018

Finished

√ Verify the following Project Types are defined in the database:

     Administration,
     Bug Triaging,
     Bug Fixing,
     Refactoring,
     Feature Development,
     Documentation,
     Website,
     Tool Development,
     Other

√ It's time to get rid of the tripling of projects on the Projects page.


Tasks

  • The interface is very slow. It makes it difficult to figure out how the site works. Clicking on one of the project name takes so long to bring up that project's information that one wonders if that was the correct way to do it. If the interface cannot be sped up then at least some instructions should be added to the web page. (e.g. "Click on project name to edit that project's parameters.")
  • SVG's are not allowed for the Banner and Logo!! I've heard that there is some great Libre Graphics program that can produce SVGs that scale better than PNGs on the web...
  • The Logo is required to be 150x150 px but it is displayed at a different resolution leading to blurring. (See #2 for solution.)
  • Can't change "Proposer". The initial projects should have "Inkscape" as the proposer.
  • How are the project fund raising goals set? I didn't see that in the interface.
  • The project summaries on "https://inkscape.org/en/project/" should be customizable and not just first few lines of the "Project Update". [Bryce asked for an 'elevator pitch']
  • Decide where in the site to link to the Add a Project form. Maybe under Contribute? [We can add that link to several places, I think. I'd also like to see it on the Funded Projects page itself.]
  • How should we hook in the ui/mockups gallery category to the projects? We could tie specific items or a single gallery so we can attach files to the project? [Easiest way: by linking from a text, maybe?]
  • How should we vote or +1 various projects? Should we have separate +1 Concept (in an ideal world) +1 Design (I like the design for this project) +1 Technical (It's technically well spec'd)? Or just a single thumbs up?
  • How do we identify that a given applicant is valid? (I.e. that they are in the AUTHORS file) Perhaps look at what was done for the voting system since it has the same requirement. Maybe the users table needs to have a field or flag added to indicate people who are official Inkscape contributors? [We could use the team functionality for this. There will be a group/team for developers.]
  • State update. A process is periodically invoked to calculate the state of projects. Most state changes are time-based, but there are exceptions that allow adjusting states manually.
  • Update users about progress (Hook up to mailing system).
  • Keep track of edits of the respective items (wishlist)
  • Allow for discussion on a project (wishlist)

Data Fields

Project

 - Description (not in trunk, but exists in https://code.launchpad.net/~marenhachmann/inkscape-web/projects-pages)
 - Progress Reporting URL (not in trunk, what is this for?)
 + Deliverables
 + Acceptance Criteria
 + Expected Duration
 + Date Started    # Implies is_assigned
 + Date Completed
 + Proposer
 + Supporter ('Second')
 + Reviewer
 + is_fundable
 + is_pre_approved
 + Importance
 + Logo
 + Banner
 + Title
 + Slug (for url)
 + Date created
 + Date edited
 + Manager
 + Project Type

ProjectUpdate

 + Project
 + Description
 + Image
 + Creator
 + Date created
 + Date edited

Criteria

 + Content
 + Detail

class Deliverable(Model):

   (A single deliverable item)
   + For Project
   + Name
   + sort order
   + Date targeted
   + Date finished

Task

  (A task or sub-task of a deliverable stage)
 + For Deliverable (= delive)
 + Name
 + Date targeted
 + Date finished

Application (= Worker)

 - Job Qualifications (not in trunk, needed? Could also live inside 'plan')
 + person_id (= user)
 + job_id (= project)
 + Implementation Plan (= plan)
 + Date Vetted
 + Assigned

Fundraiser

 - fundraiser_id
 - Fundraising Coordinator

Fund Allocations

 - job_id
 - fundraiser_id
 - Amount

Potential Sources of Project Ideas