Wiki source for Blog20101022MageiaInvolvementWithUpstream
What would be a distribution without upstream developers and contributors?
===Mageia should give the keys to involve oneself with upstream===
Well keys exist even when there's a lock :)
I'm sure people will love to be involved in a Mageia Game Team involving gamers, players, graphists, translators, packagers, developers... let's elaborate on how people can contribute upstream :-)
Each upstream project has at the minimum:
~- website to distribute the software
~- developers that can be contacted for patches or support (bugs) or discussion about new functionalities
~- users that talk together to suggest evolutions, documentation, provide translations
Some tools may be used, they can be documented for each and every package (and kept updated), teams on a specific domain can document and maintain this knowledge base, (re-)using what already exists and making known good practices ;-)
===Ideally teams include many competencies that work together===
For a list of packages, teams can mutualize efforts for testing and working with upstream to make the relevant information flowing
I would propose to provide generic templates based on a practical pilot, perhaps the gaming team involving:
~- users for bugs (package or upstream), documentation, promotion, support (be it upstream or distribution-wise)
~- translators (for package description, software content if needed, documentation)
~- packagers
~- testers
~- developers that can provide patches upstream
~- supporters that just follow the trend and will get involve when they can or decide it
===Desktop teams===
Well, one difference would be to have users involved in their desktop usage, day to day
~- with tips, use cases, preferences, suggestions to do it the right way, documentation on what exists and how it can be configured
~- graphists that make our desktop nice and looking modern and packagers to include their creations (think screensaver, background images, splash/boot screen...)
~- http://freedesktop.org initiatives sustained with user experience and as much as possible http://kde-look.org/ and http://gnome-look.org/ publicized for stable innovations
~- cross cooperation to identify what works with your hardware would be a plus: http://faq.tuxfamily.org/CommunicationLibreHardware/En
~~- dedicated teams around some peripherals (camera, smartphone/GPS, scanner...) can easily be identified, who is ready to contribute? Maybe OpenStreetMap and wikipedia can help :)
===Communication teams===
Communication is possible for everyone, though not everyone has the time or the fluency or the talent to write and analyze/follow what is being done
~- of course, there should be a planet, versatile, documented, promoted on news sites when subjects deserve it, analyzing trends and relevant subject in the (coming) forums
~- showing involvement and current initiatives once subjects are thoroughly worked on and with visible advancement for easy use
~- call to contribution when teams are being formed and have suficient backup and support with identified attainable goals
----
CategoryBlogMageia
===Mageia should give the keys to involve oneself with upstream===
Well keys exist even when there's a lock :)
I'm sure people will love to be involved in a Mageia Game Team involving gamers, players, graphists, translators, packagers, developers... let's elaborate on how people can contribute upstream :-)
Each upstream project has at the minimum:
~- website to distribute the software
~- developers that can be contacted for patches or support (bugs) or discussion about new functionalities
~- users that talk together to suggest evolutions, documentation, provide translations
Some tools may be used, they can be documented for each and every package (and kept updated), teams on a specific domain can document and maintain this knowledge base, (re-)using what already exists and making known good practices ;-)
===Ideally teams include many competencies that work together===
For a list of packages, teams can mutualize efforts for testing and working with upstream to make the relevant information flowing
I would propose to provide generic templates based on a practical pilot, perhaps the gaming team involving:
~- users for bugs (package or upstream), documentation, promotion, support (be it upstream or distribution-wise)
~- translators (for package description, software content if needed, documentation)
~- packagers
~- testers
~- developers that can provide patches upstream
~- supporters that just follow the trend and will get involve when they can or decide it
===Desktop teams===
Well, one difference would be to have users involved in their desktop usage, day to day
~- with tips, use cases, preferences, suggestions to do it the right way, documentation on what exists and how it can be configured
~- graphists that make our desktop nice and looking modern and packagers to include their creations (think screensaver, background images, splash/boot screen...)
~- http://freedesktop.org initiatives sustained with user experience and as much as possible http://kde-look.org/ and http://gnome-look.org/ publicized for stable innovations
~- cross cooperation to identify what works with your hardware would be a plus: http://faq.tuxfamily.org/CommunicationLibreHardware/En
~~- dedicated teams around some peripherals (camera, smartphone/GPS, scanner...) can easily be identified, who is ready to contribute? Maybe OpenStreetMap and wikipedia can help :)
===Communication teams===
Communication is possible for everyone, though not everyone has the time or the fluency or the talent to write and analyze/follow what is being done
~- of course, there should be a planet, versatile, documented, promoted on news sites when subjects deserve it, analyzing trends and relevant subject in the (coming) forums
~- showing involvement and current initiatives once subjects are thoroughly worked on and with visible advancement for easy use
~- call to contribution when teams are being formed and have suficient backup and support with identified attainable goals
----
CategoryBlogMageia
