Changes

Jump to navigation Jump to search
Line 12: Line 12:  
</div>
 
</div>
   −
==Upcoming Agenda==
+
== Upcoming Agenda ==
 +
 
 +
* Settle down patch submitting workflow:
 +
** email based workflow as a primarily model (check other FOSS projects to gather all existed experience) [[User:Alsroot|alsroot]] 07:35, 27 October 2010 (EDT)
 +
** write an email-bot/trac-plugin to make an email<->trac sync. Will be useful, e.g., for non-developers who track bugs status and to let people know the current status in most convenient way. All emails, w/ ticket set, will be posted to bugs.sl.o and any comments(and patches) to bugs.sl.o, to tickets w/ previously sent patches, will be emailed. [[User:Alsroot|alsroot]] 07:35, 27 October 2010 (EDT)
   −
* Settle down patch submitting workflow [[User:Alsroot|alsroot]] 07:59, 25 October 2010 (EDT)
   
* Requirement to use [[Activity_Team/Sugar_Lint|sugar-lint]] (or so) in git pre-commit. [[User:Alsroot|alsroot]] 07:59, 25 October 2010 (EDT)
 
* Requirement to use [[Activity_Team/Sugar_Lint|sugar-lint]] (or so) in git pre-commit. [[User:Alsroot|alsroot]] 07:59, 25 October 2010 (EDT)
 +
 
* Increase a level of trust within core team, make patch reviewing workflow more clear:
 
* Increase a level of trust within core team, make patch reviewing workflow more clear:
 
** Any committer, to a particular core project, might be a reviewer (we either should trust all these people or drop them from committer list) [[User:Alsroot|alsroot]] 07:59, 25 October 2010 (EDT)
 
** Any committer, to a particular core project, might be a reviewer (we either should trust all these people or drop them from committer list) [[User:Alsroot|alsroot]] 07:59, 25 October 2010 (EDT)
Line 22: Line 26:  
** Review process should not include debates about coding style, if coding style conforms to lint checks and Hacking Policy (if it has unequivocal statements, needs to be rechecked), it should be applied [[User:Alsroot|alsroot]] 09:33, 25 October 2010 (EDT)
 
** Review process should not include debates about coding style, if coding style conforms to lint checks and Hacking Policy (if it has unequivocal statements, needs to be rechecked), it should be applied [[User:Alsroot|alsroot]] 09:33, 25 October 2010 (EDT)
 
** Purism is good but there is no need to achieve it by single patch, it might be changed in post-commit patches if second reviewer (e.g., looking to the patch thread on mailing list) found an issue in already commited code. [[User:Alsroot|alsroot]] 13:39, 25 October 2010 (EDT)
 
** Purism is good but there is no need to achieve it by single patch, it might be changed in post-commit patches if second reviewer (e.g., looking to the patch thread on mailing list) found an issue in already commited code. [[User:Alsroot|alsroot]] 13:39, 25 October 2010 (EDT)
 +
 
* officially dropping support for 0.86? (e.g. {{bug|1838}})
 
* officially dropping support for 0.86? (e.g. {{bug|1838}})
 
** do we need to discuss thing like that on Development Team meeting, is it a more appropriate task for Deployment and Platform teams? [[User:Alsroot|alsroot]] 07:59, 25 October 2010 (EDT)
 
** do we need to discuss thing like that on Development Team meeting, is it a more appropriate task for Deployment and Platform teams? [[User:Alsroot|alsroot]] 07:59, 25 October 2010 (EDT)
 +
 
* big (and small) ideas for 0.92  --[[User:Walter|Walter]] 13:17, 25 October 2010 (EDT)
 
* big (and small) ideas for 0.92  --[[User:Walter|Walter]] 13:17, 25 October 2010 (EDT)
  

Navigation menu