public inbox for gentoo-soc@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-soc] Council Webapp Progress Report
@ 2010-07-27  1:56 Wei Xie
  2010-07-27  3:33 ` [gentoo-soc] ventoo weekly report Christopher Harvey
  0 siblings, 1 reply; 3+ messages in thread
From: Wei Xie @ 2010-07-27  1:56 UTC (permalink / raw
  To: gentoo-soc

The past weeks have been mainly about code review and fixing.

[What we did]
* Run both spec and cuucmber by default (committed by mentor Hans de Graaff)
* Add role to User and related permission control facility
* Ignored db/schema.rb and track db/migrations for schema-related stuff
* Seed the dev database with db/seed.rb instead of rake db:bootstrap
(avoided re-inventing wheels)
* Fixed Agenda related bugs
* gave credits to the original authors of some code lines
* Found two bugs of Hobo and fixed them. Mentors have submitted
patches upstream.
* Adjust indention in all other files.

* I worked on other tasks as well. But since they are not reviewed by
mentors yet. I will write about them later. These tasks include:
  * GLEP work flow support in the application
  * Sending email notifications for new agenda item or approaching agenda


[What to do]
* Continue code review and fix any comments by mentors.
* Self-check my previous code and try to fix any potential bugs

[Problems]
* The fixing progress has been very slow. I adopted a different editor
configuration and many source code files have been affected (mainly
indention related). I have to rebase to each commit and try to get it
right.


[Conclusion]
The fixing stuff consumes much more time than I have expected. I will
do some self-checking before pushing to remote repository as well in
order to speed up the code review process.

-- 
Xie, Wei



^ permalink raw reply	[flat|nested] 3+ messages in thread
* [gentoo-soc] ventoo weekly report
@ 2010-08-02  5:54 Christopher Harvey
  0 siblings, 0 replies; 3+ messages in thread
From: Christopher Harvey @ 2010-08-02  5:54 UTC (permalink / raw
  To: gentoo-soc, Luis Araujo

This week I added a system to ventoo that highlights parts of a file 
when ventoo thinks they are invalid and should not be saved back into 
the file. The code that does the checking are external python scripts 
that users can easily add to ventoo without changing any other code. The 
reason this was added is that up until now as the user is editing a file 
he/she had no idea if the file was valid until a diff or a save was 
requested. Now SOME (or even most) errors can be caught with a python 
script that validates user input in the background. Even nicer is that 
well written scripts can catch errors that augeas can't. (augeas is the 
library I use to move the files in and out of memory and manipulate the 
file structure) For example, if the user enters /dev/sdf12, but that 
device doesn't exist, the cell lights up bright red. The user can still 
save, so it's really only a warning. Warnings like this can typically be 
checked in about 2-4 lines of python. Augeas already did a pretty good 
job of catching a lot of invalid config files, but this system makes it 
easier for the user and can catch errors that augeas wasn't designed to 
catch.

Next week:
Remote editing of other computers.



^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2010-08-02  8:54 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-07-27  1:56 [gentoo-soc] Council Webapp Progress Report Wei Xie
2010-07-27  3:33 ` [gentoo-soc] ventoo weekly report Christopher Harvey
  -- strict thread matches above, loose matches on Subject: below --
2010-08-02  5:54 Christopher Harvey

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox