Time Sheet Web App: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
No edit summary
(Redirected page to OSEDev)
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
=Time Tracker Web App Management=
#Redirect [[OSEDev]]
 
== OSE Developers ==
*Website - https://osedev.org
*Login - https://osedev.org/auth/login
*Graphs - https://osedev.org/graphs
*Public Profile - https://osedev.org/YOUR-OSEDEV-USERNAME
*Hour Log Widget for Wiki - https://osedev.org/wiki/YOUR-OSEDEV-USERNAME
 
 
== Admins ==
*Website - https://osedev.org/admin/
*Login - https://osedev.org/admin/login
*Users - for contributor transparency - the Dev should be listed under their name as it appears on their official log - such as [[Emmanouil Log]], [[Michael Log]], [[Marcin Log]], etc. In the log naming convention, first name is used when it is unique, but as soon as there are multiples of that first name, the last name is used. See [[Log Naming Convention]].
*Database dump -
*Entry correction - go to Notebook-> Log Entries
 
 
==Developer==
* github: https://github.com/damoti/osedev
* progress log: [[Lex_Log]]
 
 
=Rollout Sequence=
 
==Phase 1==
#Login is same as wiki (if someone is logged in, they can edit their hours)
#Contributors Input hours spent on tasks at any time, or all at once, through an inerface embeddable in the wiki
#Generates hours graph equivalent of [[Volunteer_Timesheet#Contributor_Graph]] (sum of all contributors'  hours, number of contributors). This is an overall graph over all of time since 2017.
 
==Phase 2==
#Generates the same contributor graph with hours broken down by every contributor (many contributors on same graph, contributor labeled by color and name
#Back end is editable to correct any errors in inputs
#Generates embeddable Contributor Graph (wiki, wordpress). This graph is a sum of all contributions
#Validates input (so it's a number)
#Generates graph by a single contributor for the last 90 days
#Generates overall graph by contributor (over all of their time), with x axis time, and hours on y graph
#Generates embed code for each contributor graph (to paste in Work Log)
#Graphs the number of wiki editors (is this possible?)
#Allows anyone to see a log of all contributions, and log of contributions by person. Log includes what task was done
 
==Phase 3==
*Emails follow up with 90 day cycle completion, and follow up with a mid-point survey.
*Integrates with phpList so Developees List can be used for dev team emails as needed
*Adds and removes emails from active Dev List automatically if people leave the team
*Contains emails of all contributors
*Automatic send of welcome email (to be written up)
*Automatic followup email if 2 weeks pass after Video Cover Letter, to see where a person is.
*Automatic followup email for people to create work log if they don't do so by 2 days.
*Automatic send of regret letter (for devs let go, or for applicants who do not create a work log)
:*Note that work log documents at which point people get stuck - for quality improvement purposes where OSE learns what of its procedures are adequate/clear
*Sends auto emails if logging has not occurred for 7 days (email to be written)
*Sends warning emails if a person is below 6.5 hours per week
*Sends auto email warning if 4 week average is trending below 6.5
*Kicks people off the team if 4 week average is below 6.5. This must be approved by HR admin.
 
==Advanced==
*Parses person's work log for key outputs of that week, and posts all those results automatically on a weekly Results Log (presented during Team Meetings, as automated Scrum Standup)
 
=Documentation Requirements=
*App is fully documented so anyone can manage its subsequent modification (coding level)
*Admin side is documented, including a 1 minute video
*User howto is documented, including a 1 minute video
 
=Other=
 
==Other Automation==
*Automates interview calendar
*Automates badge creation and update
*Automates sticker sending + swag sending
*Integrates with main website (WordPress) for automatic display via simple iframe or embed code
*integrates display to wiki with iframe or embed code, and is updated automatically on those pages
 
 
 
=Automation=
*App should encourage time logging on an ongoing basis, as it provides an automatic week tally.
*Sends notification - when person did not fill it out
*Sends notification to Developer if they are not filling their commitment at the absolute minimum level (6.5)
*Boots people off if they don't meet their average absolute minimum after 1 month
*Rewards with an Outstanding Badge for meeting 90% of their quota after 3 months
*Produces the graph that we use currently on an ongoing basis
*Graphs the number of wiki editors on an ongoing basis
*Graphs the total size of the dev team at one point
*Provides a stats dashboard with all contributors like current graph, agraph broken down by each contributor and labeled, a graph of wiki editors, number of wiki articles, number of edits
 
=Questions=
*Pull in alalytics from wiki to track overall Number of Editors, Number of Wiki Pages, Machines Documented '''Yes, already works.'''
*Create a burndown for each project. Burndown goes up to a successful enterprise. '''Would need to know the expected total hours in order to do burndown.'''
*Can app talk to Piwik? '''Probably yes.'''
*Can app query Mediawiki database? '''Yes.'''
*Can app query Wordpress database? '''Yes, already works.'''
 
 
 
 
=Other=
==Content Feed==
*Has auto feed from contributor logs to a single wiki page gallery,where Devs mark up their wiki for inclusion into weekly Results Gallery
*Results Gallery wiki page feed happens automatically, with new wiki pages created automatically
 
==Good Standing Algorithm==
*65% is our absolute minimum cutoff
*If 65% cutoff is not attained over a month duration, Dev is removed from Dev status and asked to rejoin if their time frees up
*Regular Track is defined as someone who just participates
*Advanced Track is defined. This means that a certain person is preparing for running workshops. This includes building a machine and then committing 2 weeks on site for a [[Dedicated Project Visit]].

Latest revision as of 04:53, 29 September 2017

Redirect to: