Difference between revisions of "Funded Project System Development"

From Inkscape Wiki
Jump to navigation Jump to search
 
(14 intermediate revisions by 3 users not shown)
Line 24: Line 24:
* Can't change "Proposer". The initial projects should have "Inkscape" as the proposer.
* 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.
* 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.
* "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]


* 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.
* 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]


* How are the project fund raising goals set? I didn't see that in the interface.
* 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".
* 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?
* 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?
* 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 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?
* 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.]
<!-- 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.
* 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.


== Dialog Pages ==
* Update users about progress (Hook up to mailing system).


**WorkerApplicationForm** - Apply for a project.  Creates a Job Proposal entry.
* Keep track of edits of the respective items (wishlist)
 
**WorkerList** - List applications.  Can display All, Pending, Approved, or Denied applications.  Sort/filter based on ones requiring vetting.  Administrative.
 
**WorkerView** - Vet applicant.  To be used by the board member charged with vetting applicants.  Administrative.  Displays the application and allows specifying yea or nay or to request clarification by the applicant.
 
**ProjecSuggestionForm** - Simple form for adding one or more ideas for projects.  Fields kept to a minimum - Name, brief 1-2 sentence description of the name, and (optionally) a category.  (Will need some mechanism to detect and merge/review dupes.)
 
**ProjectDefinitionForm** - Detailed form for modifying and entering additional data about the project, including deliverables.
 
**ProjectUpdateForm** - Used by the project's worker to enter status reports and provide a % complete.
 
**GSoCProjectIdeasList** - Listing of project ideas for Google Summer of Code.  Categorize them by GSoC Status:  Pending/Active/Completed/Failed at top (labelled Accepted), Open in middle (labelled Suggestions), Draft at bottom (labelled More Ideas).
 
**OpenProjectList** - List of all projects available for anyone to do regardless of funding.  If the project is eligible to be funded, allows creation of a Job record.  If it fits the requirements for GSoC, allows creation of a GSoC job record in Draft mode.  Includes a search/sort mechanism by various parameters including what conditions they fail to meet (e.g. need to be seconded; have reached 6 months but lack certain details; etc.)
 
**FundedProjectJobsList** - List of Approved Jobs for applicants to apply for.  Eligible projects must be >= 6 months, has a deliverable, has acceptance criteria defined, has a time limit defined, and proposal has been seconded.  Should be possible to filter/sort based on the allocated funds amounts.
 
**MyProjectsList** - List my projects.  Both projects I've proposed, and ones I've applied for.  Includes GSoC, Open, and Funded projects.  Indicate status and provide modify links.  E.g. projects that need a status report are flagged as such, etc.
 
Fundraising Coordinator registration page
 
Fund Allocation Page.  List fundable/funded projects.  For fundraiser coordinators to browse through and 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.)
 
Register a fundraiser record.  Set the development projects that the fundraiser's money will be allocated to.  Indicate the keyword for flagging incoming donations, or else allow manually specifying the amount that was raised.  Also allows marking a fundraiser finished.  Initial coordinator for the fundraiser is the person who creates it.
 
Allocate funds to fundable projects.  Allow fundraiser coordinators to allocate money from the funds they raised to specific fundable projects.
 
Signoff page for completed projects


* Allow for discussion on a project (wishlist)


== Data Fields ==
== Data Fields ==


Project
Project
   + Description
   - 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
   + 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
  + 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
   + fundraiser_id
   - fundraiser_id
   + Fundraising Coordinator
   - Fundraising Coordinator


Fund Allocations
Fund Allocations
   + job_id
   - job_id
   + fundraiser_id
   - fundraiser_id
   + Amount
   - Amount


Application
== Potential Sources of Project Ideas ==
  + person_id
* [[Projects]]
  + job_id
* [[Google_Summer_of_Code]]
  + Job Qualifications
* [[Roadmap]]
  + Implementation Plan
* [[Extension architecture proposals]]
  + Date Vetted
* [[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