Search results
Jump to navigation
Jump to search
Page title matches
- ...s manual]] provides more comprehensive and up-to-date introductions to the issues described here. Here are a few of the most obvious development issues/questions/comments:10 KB (1,624 words) - 21:33, 23 February 2010
Page text matches
- <noinclude>[[Category:Development Team]] :Bug Tracking: [https://github.com/sugarlabs/chat/issues Github Issues]5 KB (643 words) - 09:04, 18 October 2022
- | source = Development Team/Manual ...project. Although this Developer's Manual focuses mostly on the software development side of the process, we are also very interested in encouraging the contrib2 KB (343 words) - 21:33, 23 February 2010
- == Common issues == ''If your activity is part of Fructose follow [[Development Team/Release#Module_release|Module Release]] instead.''2 KB (316 words) - 20:49, 16 January 2018
- ...ansion of this wiki will enable a coordinated approach to fixing the known issues. It will also allow contributors, from inside and outside the Sugar communi * Please add issues you think are relevant for the workshop in the headings below2 KB (308 words) - 21:33, 23 February 2010
- {{:Development Team/Mission}} ...d find out more about the meeting time and upcoming and earlier meetings [[Development Team/Meetings|here]]. Help: [[Sugar_Labs/Communication channels#IRC.2C_Inte3 KB (497 words) - 19:13, 27 November 2019
- ...isting projects or starting your own. Although it focuses on the software development side of the process, we are also very interested in encouraging [[Sugar_Lab * [[Development Team/Manual/Setup]]3 KB (431 words) - 14:11, 3 July 2012
- ...ks to many ideas and development resources. Your may also propose your own development ideas—show your creativity—combine the best aspects from the po We're currently in the "get ideas" phase; please see [[Development Team/Project Ideas]] for a list of potential projects, and add your own. (T2 KB (309 words) - 20:30, 10 March 2010
- ...us possibilities. The idea of helping external groups form to share in the development and support burden was seen as a favorable strategy. Raising money for "eve === Key issues ===3 KB (364 words) - 09:36, 1 March 2011
- ...of possible scheme and resource-path implementations are possible, pending development time to implement them. The URLs will need to conform to certain constraint ===Implementation Issues===4 KB (614 words) - 17:36, 12 May 2009
- There are several options for setting up the Sugar desktop environment for development, depending on what equipment you have; ! Good for Sugar activity development5 KB (803 words) - 18:13, 1 December 2017
- * Still having Git repository issues ''(might have just been fixed...)'' * To follow good software engineering practices during development3 KB (457 words) - 22:19, 5 September 2010
- * Sugar distributions: what are the issues? ...are in line with the Sugar Labs vision. It is extremely important to push development and support into the hands of local organizations because: (1) it scales; (4 KB (655 words) - 09:33, 19 December 2016
- Fractionator was made in the IGME.582 ( Humanitarian FOSS Development ) class at Rochester Institute of Technology. * Active development still in progress2 KB (345 words) - 11:26, 10 May 2017
- # What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - A ...ht|An example of the kind of screenshot of your first modification to your development environment which you should include in your application. Note that the dro6 KB (944 words) - 00:20, 29 April 2013
- ...re team which does all this great work in the background without which the development would not be possible at all, *the deployments that provide the development team with feedback from the field,3 KB (496 words) - 13:26, 13 February 2016
- * Current affiliation with Sugar Labs: maintainer of the [[Development Team/Buildbot|build infrastructure]] * Name of project: Version support for [[Development Team/Datastore Rewrite|data store]] / [[Design_Team/Designs/Journal|Journal8 KB (1,277 words) - 12:07, 26 April 2009
- {{Translation | lang = ko | source = Development Team/Manual | version = 93961}} * [[Developers/Issues|개발자/쟁점]]3 KB (76 words) - 21:33, 23 February 2010
- ...n the @dx mailing list that tch sent some time ago. Those will close a few issues from above. =Development goals=6 KB (1,105 words) - 00:37, 17 May 2016
- ...Translations | [[0.92/Notes|english]] }}{{TeamHeader|Development Team|home=Development Team|roadmap_link={{Upcoming Stable Release}}/Roadmap}}</noinclude>[[Catego You can browse the notes of each development release in [[0.92/Roadmap#Schedule]]. Their respective sources are listed t7 KB (914 words) - 13:04, 5 March 2012
- ...re team which does all this great work in the background without which the development would not be possible at all, * the deployments that provide the development team with feedback from the field,5 KB (721 words) - 12:10, 3 November 2015