Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • C constitution
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 7
    • Issues 7
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • SRCT
  • constitution
  • Issues
  • #16

Closed
Open
Created Sep 07, 2014 by Renfred Harper@rharper2Developer

Add developer status guidelines

It is currently unclear to current members what constitutes other members worthy of developer status. The three criteria should be mentioned as guidelines:

  1. meeting attendance
  2. community involvement
  3. code contributions

It should be made clear these criteria are guidelines which should inform developers how to vote. The only criteria that matters is the faith of a majority of developers. It should be mentioned "developer" is a term symbolic in meaning and is not decided solely on technical skill.

Assignee
Assign to
Time tracking