Difference between revisions of "User:Callahanp/FlightgearWorkingGroups"

< User:Callahanp
(Tags: Mobile edit, Mobile web edit)
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
{{ WIP }}
  
===Independent Study===
+
While struggling to acquire knowledge of the Flightgear Codebase and Flightgear Community expectation and standards, I realized that I'm probably not alone and that others might be in a similar situation.
  
===Join a study group===
+
There's a lot to learn about FlightGear.  Much of it can be absorbed from reading posts to the flightgear-devel mailing lists, forum posts and entries in this wiki.  A lot can be gained by reading previously written documentation.  FlightGear is already a project with a long history. There is an ever increasing amount of supporting material available, some of it relevant, some not, some current, some seriously out of date.  
Work with others to master a specific area of Flightgear development.
+
  
While focusing in specific short term development goals, St groups go beyond just working in a specific problem or issue.  
+
While there is no single person with ultimate authority over the application, there is a small community of individuals with a measure of responsibility and control over the content and direction of the project.  These individuals have been involved with and have contributed heavily to Flightgear, some since it's inception.  Understanding their perspectives and motivations is key to becoming a successful contributor to Flightgear.
  
 +
Over the next few months, in co-operation with the developers, I intend to propose that steps be taken to recruit new participants to the Flightgear project, and provide them with a forum dedicated specifically to the needs of new or potential contributors.  '''This page is an attempt to say a bit about what might be needed.  It is in no way official or sanctioned by anyone associated with Flightgear.'''
  
Major study areas
+
So here's what I think would be needed:
Plug in and subsystem architecture
+
Build Process, Operating Systems and Distribution Packaging
+
  
Aircraft modeling
+
* A separate but open forum for learning about the Flightgear project from the standpoint of a new or potential contributor.  Possibly an irc channel, or other free and open collaboration space.
Scenery representation
+
* Regular online events for new or potential contributors
Data delivery
+
* Participation by long term Flightgear contributors would be welcomed but not required of them.
 +
* Deliberate and broad coverage of all areas of flightgear development without over-emphasis on any one area such as C++ code, Nasal, Scenery, Aircraft or Airports. 
 +
* Deliberate coverage of cross platform development.  Give individual participants support for working in and developing their expertise in more than one operating system, and for Linux, more than one linux distribution.
 +
* Emphasis on ensuring participant's knowledge of the extent of available flightgear materials such as scenery and aircraft external to the project itself.
 +
* Library Awareness: Knowledge of the extent and specific uses within Flightgear of various open source libraries on which flightgear depends.
 +
* Change Impact Awareness: Knowledge of the time investments in Aircraft, Airport, Scenery and Simulation materials and the impact of changes in one of these areas on the others.
 +
* Assistance with configuration of a suitable development environment with support for development of all aspects of Flightgear: C++ code, Nasal, Scenery, Aircraft and Airports.docFolders
  
Admission
+
===Independent Study===
Admission requirements are rigorous but for an individual with enthusiasm and dedication easy to satisfy.
+
  
Tuition
+
Independent study of specific topics by individuals or teams would be strongly encouraged.  Participants are encouraged to review all available material in a given area of the application and to propose, discuss and implement significant improvements with both the full cooperation of the overall flightgear community and the support and encouragement of a community of new contributors.
Tuition is paid in the standard open source volunteer project currencies: merge requests, forum posts, mailing list posts and contributions to wiki articles that move the project in a positive direction . Regular payments are required of all students.
+
  
 +
===Join a study group===
  
 +
Work with others to master a specific area of Flightgear development.
  
 +
While focusing in specific short term development goals, Study groups go beyond just working on a solution to a specific problem or issue. Their goal would be to develop an in-depth understanding of a specific part of Flightgear, and to improve both the application's source code materials and its the documentation.
  
 +
Major study areas
 +
* Plug in and subsystem architecture
 +
* Build Process, Operating Systems and Distribution Packaging
 +
* Aircraft modeling
 +
* Scenery
 +
* Airports
  
 +
Admission
 +
Admission requirements would be rigorous but for an individual with enthusiasm and dedication easy to satisfy.
  
 +
Tuition:
 +
Tuition would be paid in standard open source volunteer project currencies: merge requests, forum posts, mailing list posts and contributions to wiki articles that move the project in a positive direction. Regular payments are required of all students.
  
  
Tuition
+
Faculty- what Faculty.  This is self directed study...
Faculty
+

Latest revision as of 14:08, 18 April 2020

WIP.png Work in progress
This article or section will be worked on in the upcoming hours or days.
See history for the latest developments.

While struggling to acquire knowledge of the Flightgear Codebase and Flightgear Community expectation and standards, I realized that I'm probably not alone and that others might be in a similar situation.

There's a lot to learn about FlightGear. Much of it can be absorbed from reading posts to the flightgear-devel mailing lists, forum posts and entries in this wiki. A lot can be gained by reading previously written documentation. FlightGear is already a project with a long history. There is an ever increasing amount of supporting material available, some of it relevant, some not, some current, some seriously out of date.

While there is no single person with ultimate authority over the application, there is a small community of individuals with a measure of responsibility and control over the content and direction of the project. These individuals have been involved with and have contributed heavily to Flightgear, some since it's inception. Understanding their perspectives and motivations is key to becoming a successful contributor to Flightgear.

Over the next few months, in co-operation with the developers, I intend to propose that steps be taken to recruit new participants to the Flightgear project, and provide them with a forum dedicated specifically to the needs of new or potential contributors. This page is an attempt to say a bit about what might be needed. It is in no way official or sanctioned by anyone associated with Flightgear.

So here's what I think would be needed:

  • A separate but open forum for learning about the Flightgear project from the standpoint of a new or potential contributor. Possibly an irc channel, or other free and open collaboration space.
  • Regular online events for new or potential contributors
  • Participation by long term Flightgear contributors would be welcomed but not required of them.
  • Deliberate and broad coverage of all areas of flightgear development without over-emphasis on any one area such as C++ code, Nasal, Scenery, Aircraft or Airports.
  • Deliberate coverage of cross platform development. Give individual participants support for working in and developing their expertise in more than one operating system, and for Linux, more than one linux distribution.
  • Emphasis on ensuring participant's knowledge of the extent of available flightgear materials such as scenery and aircraft external to the project itself.
  • Library Awareness: Knowledge of the extent and specific uses within Flightgear of various open source libraries on which flightgear depends.
  • Change Impact Awareness: Knowledge of the time investments in Aircraft, Airport, Scenery and Simulation materials and the impact of changes in one of these areas on the others.
  • Assistance with configuration of a suitable development environment with support for development of all aspects of Flightgear: C++ code, Nasal, Scenery, Aircraft and Airports.docFolders

Independent Study

Independent study of specific topics by individuals or teams would be strongly encouraged. Participants are encouraged to review all available material in a given area of the application and to propose, discuss and implement significant improvements with both the full cooperation of the overall flightgear community and the support and encouragement of a community of new contributors.

Join a study group

Work with others to master a specific area of Flightgear development.

While focusing in specific short term development goals, Study groups go beyond just working on a solution to a specific problem or issue. Their goal would be to develop an in-depth understanding of a specific part of Flightgear, and to improve both the application's source code materials and its the documentation.

Major study areas

  • Plug in and subsystem architecture
  • Build Process, Operating Systems and Distribution Packaging
  • Aircraft modeling
  • Scenery
  • Airports

Admission Admission requirements would be rigorous but for an individual with enthusiasm and dedication easy to satisfy.

Tuition: Tuition would be paid in standard open source volunteer project currencies: merge requests, forum posts, mailing list posts and contributions to wiki articles that move the project in a positive direction. Regular payments are required of all students.


Faculty- what Faculty. This is self directed study...