-
Notifications
You must be signed in to change notification settings - Fork 48
Team Description 1
Governing Principles for cooperation among Pisi Linux teams and individuals
This document is to be read by anyone who currently contributes, or wishes to contribute to the Pisi Linux project.
To promote efficient and rewarding teamwork by having good overview and following protocol.
Pisi Linux teams are arranged according to other types of requests for collaboration should be conducted by the relevant team leader/s (where they exist). Team compositions with contact details are provided in this document.
Note: Due to limited manpower, individuals are likely to have several secondary roles and be members of several teams. However, where additional volunteers are found, then certain secondary roles can re-assigned.
Additionally, some teams may not yet have a team leader – or some teams may need to employ a revolving leadership system, depending on membership and their spare time.
Contact Information
- IRC or Slack: #pisi-devel or #board
- Mailing List: do we need one?
- Issue tracker: https://github.com/pisilinux/PisiLinux/issues
- Serdar Soytetir (obsoleteman) – Team Leader
- Marcin Bojara (marcin)
- Yusuf Aydemir (yusuf)
To decide all technical policy relating to the technical direction that Pisi Linux takes.
- Packaging policy and guidelines
- Technical decisions regarding installation system and process, toolchain, kernel, X server
- Develop ideas to further refine or extend PiSi, YALI, COMAR, MUDUR, KAPTAN, USER MANAGER and PANDA functionality
- Creation or incorporation of additional tools
See our procedures for details on ‘how we do things’ (Marcin to write this?). Most discussions regarding the Technical Board will happen in #pisi-devel or #board (IRC or Slack?). For requests please consult the contact above.
- The Technical Board holds regular meetings every ? at ? in #meetingroom on (IRC or Slack)
- Meetings agenda (URL)
- See our ticket queue for the things we are working on.
- See releases for information about Pisi Linux releases.
- Contact Info
Stefan Gronewold (groni) IRC or Slack: #pisi-devel or #board
The Project Coordinator will focus particularly on project overview and facilitation
- Maintain an overview on all aspects of the Project
- Maintain a project management calendar
- Coordinate and facilitate individual and team effort
- Process agenda item submissions
- Chair the Committee meetings
- Develop project strategies
- Work with Core to establish schedules for releases including freeze dates, final release, slips, etc. Ensure all other relevant interaction takes place between teams regarding these schedules and their requirements (eg: PR, docs, branding/artwork, websites/forums etc, etc.)
- IRC or Slack: #pisi-devel or #board
- Issue tracker: https://github.com/pisilinux/pisilinux-core/issues
- Serdar Soytetir – (obsoleteman) (Team Leader)
- Marcin Bojara - (marcin)
- Yusuf Aydemir - (yusuf)
The Core Team maintains the base repository. installation system and process, toolchain, kernel, X server, library versions and dependencies, and implements Technical Board directives.
- Pisi Linux code-base and core packages
- Manage the git Core repository packages and process requests for the Core repo
- Administrate the build system
- Provide guidance and support to the Extra-Packages Team
- Report progress towards release from Feature Freeze on
- Publish reports on changes to processes
- Remove unmaintained packages from Pisi Linux
- Core Team will implement all Technical Board directives, including the development of PISI, YALI, COMAR, MUDUR, KAPTAN, USER MANAGER
- Blog about important changes, and keep a log of new features on the wiki.
See our procedures for details on ‘how we do things’ (Marcin to write this?). Most discussions regarding the Core team will happen in #pisi-devel or #board (IRC or Slack?). For requests please consult the contact above.
If you want the to submit an issue or job request to the Core Team, please create a ticket in the issue tracker mentioned above. Please enter your Pisi Linux username or email address in the respective textbox, to make sure the team can contact you.
The Core team holds regular meetings every ? at ? in #meetingroom on (IRC or Slack) Meetings agenda (URL)
See our ticket queue for the things we are working on.
- IRC or Slack: #pisi-packaging
- Issue tracker: https://github.com/pisilinux/pisilinux-extra/issues
- Osman Erkan (Team Leader)
- Ayhan Yalçınsoy (ayhanyalcinsoy )
- Erkan Işık
- İlker Manap (ilkermanap)
- Kamil Atlı (suvari)
- Sencer Hamarat
- Sezai Yeniay (sezaiyeniay)
- Stefan Gronewold (groni)
- Vedat Demir (vedat)
- Ertuğrul Erata (ertugrul)
- Aydın Demirel (taurus)
- Burak Fazıl Ertürk (BlackSEA-)
- Ekin Dursun (onlined)
- Alihan Öztürk (alihanozturk)
- Varol Maksutoğlu (waroi)
- Ergün Salman (poyraz76)
The Extra-Packages team is responsible for the pisi-extra github repo. Extra Packages team is a sub team of the core team. Extra team head reports to the core team head.
- General responsibility of the Pisi Linux software selection
- Proposing new packages
- Updating existing packages
- Assuring that packages maintained do not break anything
- Use Github effectively for issue tracking, ensure that potential contributors can comprehend the latest status of the projects/issues.
- IRC or Slack: #qa-testing
- Stefan Gronewold (groni) (Team Leader)
- Ali Cengiz Kurt
- Ayhan Yalçınsoy (ayhanyalcinsoy)
- Berkay Yurdakul
- İlker Manap (ilkermanap)
- Kamil Atlı (suvari)
- Osman Erkan (namso-01)
- Sencer Hamarat
- sezai yeniay (sezaiyeniay)
- Süleyman Arıkan (slarikan)
- Vedat Demir (vedat)
The Quality Assurance Team ensures all of the software that makes up Pisi Linux receives adequate testing, is fit-for-purpose, and contains no major bugs. It's our goal to continually improve the quality of Pisi Linux releases and updates.
As a side note, every package maintainer is responsible for checking whether his/her package breaks something.
- Testing of software as it is released into the farm repo
- Developing and executing test plans to test important functionality in a systematic way
- Running test days for specific feature or component
- Working with the Core and Extra-Packages teams to maintain the release criteria
- Highlight any aspect of Pisi Linux which appears to be sub-standard (via Committee meeting agendas?)
- IRC or Slack: #
- Mehmet SÜTCÜ (Team Leader)
- Berkay Yurdakul
- Erkan Işık
- Stefan Gronewold (groni)
- Onur Aslan
- Osman Erkan (namso-01)
- Paula (sapphireGD)
- Sezai Yeniay (sezaiyeniay)
The Design Team is the design group of the Pisi Linux project. Our interests are not only in creating graphics for use by the Pisi Linux community, but also in advocating the use of the creative tools that are a part of Pisi Linux.
- Designing various user interface elements, icons, artwork, and branding material; ensuring consistency across all UI elements within Pisi Linux, respecting good typography and pleasant look without overusing skeumorphic or shiny materials.
- Ensuring that new or existing features respect general UX principles, and direct development process towards a UX-friendly one.
- Creating whiteboards, analyzing current elements, proposing new designs and guiding developers in implementation
- Follow and analyze current design trends, review current elements, and propose replacements
- Creating artwork, branding materials, and guidelines for these elements
- Migrate all available info to the wiki, assist Documentation team in this regard.
- IRC or Slack: #
- Sezai Yeniay (Team Leader)
- Ali Cengiz Kurt
- Erkan Işık
- Mehmet SÜTCÜ
- Stefan Gronewold (groni)
- Varol Maksutoğlu (waroi)
The Pisi Linux Website team aims to improve Pisi Linux image and to create the best possible online interface for users and contributors.
- Maintain the Pisi Linux and Pisi Linux World forum websites and forums
- Work in conjunction with Design/UX and QA teams for new features or changes to the existing parts. New features shall not be implemented without proper testing and confirmation from UX team.
- Migrate all available info to the wiki, assist Documentation team in this regard
- Bug fixing :) Keep the quality of the forum very good
- Update sections and items on the forum if needed
- Answer and give reaction on forum questions
- Follow web-design trends and use them
- IRC or Slack: #
- Stefan Gronewold (groni) (Team Leader)
- Berkay Yurdakul
- Erkan Işık
- Varol Maksutoğlu (waroi)
The PR/Marketing Team ensures that people in pisi Linux can consistently explain to everyone what Pisi Linux is, why the project can help them, and how they can help the project.
- Act as official point-of-contact with outside agencies (DW etc)
- Use G+, Twitter and Facebook as primary sources for news and communication about Pisi Linux
- Follow and analyze current social media trends and translate these to Pisi Linux
- Follow news about Pisi Linux in the media and other Linux news
- Answer/Reaction about Pisi Linux on G+, Twitter and Facebook
- IRC or Slack: #
- Necmettin Begiter (Team Leader)
- Ali Cengiz Kurt
- Ayhan Yalçınsoy (ayhanyalcinsoy)
- Berkay Yurdakul
- Stefan Gronewold (groni)
- Sezai Yeniay (sezaiyeniay)
The goal of the Pisi Linux Documentation team is to improve the overall experience of Pisi Linux users and contributors by providing clear and up to date documentation.
- Use wiki as primary information source available to everyone
- Make sure all the development related info is available on the wiki
- Use open file formats for documents (.html, .odf, .pdf, .md)
- Develop consistent document standards and templates
- Create “Introduction to Pisi Linux” documents and maintain them as version number progresses, make them available as printed copy
- Spell and grammar checking, ensure that the info available is in perfect shape
- Make use of old Pardus documentation, adapt for use within Pisi Linux
- IRC or Slack: #
- Necmettin Begiter (Team Leader)
- Ali Cengiz Kurt
- Ayhan Yalçınsoy (ayhanyalcinsoy)
- Erkan Işık
- İlker Manap (ilkermanap)
- Stefan Gronewold (groni)
- Sencer Hamarat
The goal of the Pisi Linux Localization team is to ensure that all aspects of Pisi Linux (the Software, Documentation, Websites and culture) are equally accessible to local communities (countries, languages).
- Use transifex as primary tool for translations https://www.transifex.com/projects/p/PiSiLinux/.
- Provide translations via PO files
- Keep focus on the quality of the translations.