Editing Brainstorm 2010/Garage and developer services

Warning: You are not logged in. Your IP address will be recorded in this page's edit history.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 6: Line 6:
Garage, subversion and git repositories, autobuilders, issue trackers, mailing lists... what can be done to improve the Maemo application developer experience by the community?
Garage, subversion and git repositories, autobuilders, issue trackers, mailing lists... what can be done to improve the Maemo application developer experience by the community?
-
 
+
* Item 1
-
* requests for improvements
+
** Sub-item 1
-
** do not auto-upload to public repo on succeeding build, give developer a method to check the actual result prior to "publishing" the package (gri)
+
** Sub-item 2
-
** have a purge button, so a successfully built package that doesn't look like intended, can be removed/overwritten by a modified version, without need for incrementing version number (synt: bundyo, nicolai)
+
* Item 2
-
 
+
*: Indented paragraph belonging to item 2
-
* debate about alternatives
+
*# Numbered sublist
-
** qgil says there are better alternatives nowadays, so why put effort into improvements of the current service
+
*# Numbered sublist
-
** Ferenc Szekely points to functions of garage that are hard to implement in any of the alternative services, like upload privileges to extras
+
-
** Jaffa about the current setup:
+
-
*** #advantages:
+
-
*** familiarity between projects
+
-
*** cross-project collaboration
+
-
*** streamlined tools for Maemo
+
-
*** single authentication/authorisation point
+
-
*** svn
+
-
*** #disadvantages / requests for improvement:
+
-
*** poor communication in the past (move to vcs.maemo.org and drop.maemo.org)
+
-
*** concerns about qgil's suggestion to go into "maintenance mode" might cause bit rot
+
-
** qgil calls for staying on topic, which is "what are the top priority tasks at maemo for the next 6 months". Then he claims maemo developer services has pretty much all it needs, and most of the developers will migrate to meego in a short while, so we shouldn't waste effort on improving maemo developer services
+
-
** Jaffa (and Tekojo) disagrees on the meego part of qgil. In the scope of this brainstorm impact of meego on maemo still unclear.
+
-
** Tekojo nicely summarizes: "''What it needs to do it does it already.'' Here I agree. Garage has been a fairly low maintenance, reliable service for a long time. Don't poke at it without a good reason. And if such reasons come up, Ferenc knows where to poke"
+

Learn more about Contributing to the wiki.


Please note that all contributions to maemo.org wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see maemo.org wiki:Copyrights for details). Do not submit copyrighted work without permission!


Cancel | Editing help (opens in new window)

Templates used on this page: