Menu
▾
▴
usbk-devel — usbk development list
You can subscribe to this list here.
| 2011 |
Jan
(9) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|
|
From: Mehmet E. A. <me...@pa...> - 2011-01-26 22:37:37
|
On Tue, 25 Jan 2011 22:51:52 +0200 Mehmet Emre Atasever <me...@pa...> wrote: > [ Because of some mischanges, some developers may not get this mail. So I'm sending again. ] > > Hi all, > > Before big changes with USB-K, lets decide about coding style, skeleton of sources, commits etc. These decisions provide us more readable codes, and help us managing sources better. > > I made a short list. Day by day we will make enhancements with these items. > > 1.) Make commits atomic [1]. I mean, if you make changes with one porpose do it and commit. Do NOT do other works with that commit. For example, you need a bug-fix. Then fix it and commit with this message: > "Bug Fixed #2341241 > > - SCSI device broken error is handled which causes SEGFAULT" > > Commit this and make other changes with another commit. > > 2.) Every source file must contain license header. There are too many different style with writing the license header. I offer this: > > <COMMENT START> > @file <FILENAME> > > Copyright (C) <YEAR> <PERSON/PEOPLE> > > <LICENSE TEXT> > > -------<SEPERATOR>--------- > What does this file for. > > <COMMENT END> > > Example: > > /* > * @file general.h > * > * Copyright (C) 2010 > * > * This program is free software: you can redistribute it and/or modify > * it under the terms of the GNU General Public License as published by > * the Free Software Foundation, either version 3 of the License, or > * (at your option) any later version. > * > * See http://www.gnu.org/licenses/ for more information > * > **************************************************************************** > * General headers and definitions of usbk. > * > */ > > 3. Use spaces instead of tabulators. This provides us beautiful code :) > > 4. I have been looking for coding styles at web and I found this style [2]. It seemed me very good. We don't have to accept every method one to one, we can change some. > > 5. We should use code documentation with a tool, for example Doxygen. I offer Qt-Style Doxygen documenting [3]. > > 6. Language of the project should fully written in English. I offer use gettext for language support. > > This list might be extended. > > Any suggestions are welcome. > > [1] http://en.wikipedia.org/wiki/Atomic_commit#Revision_Control > [2] C Sources : http://maultech.com/chrislott/resources/cstyle/indhill-cstyle.html > C++ Sources: http://doc.trolltech.com/qq/qq13-apis.html > [3] http://www.stack.nl/~dimitri/doxygen/docblocks.html > http://doc.trolltech.com/qq/qq28-qthelp.html#htmlfilesandhelpprojects > > -- > > ~ @memre <Mehmet Emre Atasever> > __EOM This mail is not read-only :P -- ~ @memre <Mehmet Emre Atasever> __EOM |
|
From: Murat K. <mur...@gm...> - 2011-01-26 22:37:11
|
It is still same. We will start this tree step after apply new version of SCSI command interface to current source. -Murat On Tue, Jan 25, 2011 at 10:46 PM, Mehmet Emre Atasever <me...@pa...>wrote: > Hi there.. > > It's time to make plan something about USB-K Software. > > At the first meeting at Tamara Electronics office, we decided these items: > - Project will be splitted into libusbk and lsusbk. Compatibility support > is important, so some enhanement may required. > - udev support will be applied to libusbk. > - A Qt GUI will be written which uses libusbk. > > Are there any changes with these steps? > > -- > ~ @memre <Mehmet Emre Atasever> > __EOM > > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better > price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > Usbk-devel mailing list > Usb...@li... > https://lists.sourceforge.net/lists/listinfo/usbk-devel > > |
|
From: Mehmet E. A. <me...@pa...> - 2011-01-25 20:53:02
|
[ Because of some mischanges, some developers may not get this mail. So I'm sending again. ] Hi all, Before big changes with USB-K, lets decide about coding style, skeleton of sources, commits etc. These decisions provide us more readable codes, and help us managing sources better. I made a short list. Day by day we will make enhancements with these items. 1.) Make commits atomic [1]. I mean, if you make changes with one porpose do it and commit. Do NOT do other works with that commit. For example, you need a bug-fix. Then fix it and commit with this message: "Bug Fixed #2341241 - SCSI device broken error is handled which causes SEGFAULT" Commit this and make other changes with another commit. 2.) Every source file must contain license header. There are too many different style with writing the license header. I offer this: <COMMENT START> @file <FILENAME> Copyright (C) <YEAR> <PERSON/PEOPLE> <LICENSE TEXT> -------<SEPERATOR>--------- What does this file for. <COMMENT END> Example: /* * @file general.h * * Copyright (C) 2010 * * This program is free software: you can redistribute it and/or modify * it under the terms of the GNU General Public License as published by * the Free Software Foundation, either version 3 of the License, or * (at your option) any later version. * * See http://www.gnu.org/licenses/ for more information * **************************************************************************** * General headers and definitions of usbk. * */ 3. Use spaces instead of tabulators. This provides us beautiful code :) 4. I have been looking for coding styles at web and I found this style [2]. It seemed me very good. We don't have to accept every method one to one, we can change some. 5. We should use code documentation with a tool, for example Doxygen. I offer Qt-Style Doxygen documenting [3]. 6. Language of the project should fully written in English. I offer use gettext for language support. This list might be extended. Any suggestions are welcome. [1] http://en.wikipedia.org/wiki/Atomic_commit#Revision_Control [2] C Sources : http://maultech.com/chrislott/resources/cstyle/indhill-cstyle.html C++ Sources: http://doc.trolltech.com/qq/qq13-apis.html [3] http://www.stack.nl/~dimitri/doxygen/docblocks.html http://doc.trolltech.com/qq/qq28-qthelp.html#htmlfilesandhelpprojects -- ~ @memre <Mehmet Emre Atasever> __EOM |
|
From: Mehmet E. A. <me...@pa...> - 2011-01-25 20:47:21
|
Hi there.. It's time to make plan something about USB-K Software. At the first meeting at Tamara Electronics office, we decided these items: - Project will be splitted into libusbk and lsusbk. Compatibility support is important, so some enhanement may required. - udev support will be applied to libusbk. - A Qt GUI will be written which uses libusbk. Are there any changes with these steps? -- ~ @memre <Mehmet Emre Atasever> __EOM |
|
From: Mehmet E. A. <me...@pa...> - 2011-01-25 20:28:20
|
I wish my settings are true.. -- ~ @memre <Mehmet Emre Atasever> __EOM |
|
From: Mehmet E. A. <me...@pa...> - 2011-01-25 14:55:13
|
mail list settings are changing, you may get test mails, sorry for disturbing. -- ~ @memre <Mehmet Emre Atasever> __EOM |
|
From: Mehmet E. A. <me...@pa...> - 2011-01-25 14:40:00
|
Hi dear Tamara developers, I hope Tamara will glad to open USB-K source codes with GPL license. Welcome to opensource world. -- ~ @memre <Mehmet Emre Atasever> __EOM |
|
From: Mehmet E. A. <me...@pa...> - 2011-01-25 14:31:07
|
Hi dear Tamara developers, I hope Tamara will glad to open USB-K source codes with GPL license. Welcome to opensource world. -- ~ @memre <Mehmet Emre Atasever> __EOM |
|
From: Mehmet E. A. <me...@pa...> - 2011-01-20 14:53:06
|
Hi all, Before big changes with USB-K, lets decide about coding style, skeleton of sources, commits etc. These decisions provide us more readable codes, and help us managing sources better. I made a short list. Day by day we will make enhancements with these items. 1.) Make commits atomic [1]. I mean, if you make changes with one porpose do it and commit. Do NOT do other works with that commit. For example, you need a bug-fix. Then fix it and commit with this message: "Bug Fixed #2341241 - SCSI device broken error is handled which causes SEGFAULT" Commit this and make other changes with another commit. 2.) Every source file must contain license header. There are too many different style with writing the license header. I offer this: <COMMENT START> @file <FILENAME> Copyright (C) <YEAR> <PERSON/PEOPLE> <LICENSE TEXT> -------<SEPERATOR>--------- What does this file for. <COMMENT END> Example: /* * @file general.h * * Copyright (C) 2010 * * This program is free software: you can redistribute it and/or modify * it under the terms of the GNU General Public License as published by * the Free Software Foundation, either version 3 of the License, or * (at your option) any later version. * * See http://www.gnu.org/licenses/ for more information * **************************************************************************** * General headers and definitions of usbk. * */ 3. Use spaces instead of tabulators. This provides us beautiful code :) 4. I have been looking for coding styles at web and I found this style [2]. It seemed me very good. We don't have to accept every method one to one, we can change some. 5. We should use code documentation with a tool, for example Doxygen. I offer Qt-Style Doxygen documenting [3]. 6. Language of the project should fully written in English. I offer use gettext for language support. This list might be extended. [1] http://en.wikipedia.org/wiki/Atomic_commit#Revision_Control [2] C Sources : http://maultech.com/chrislott/resources/cstyle/indhill-cstyle.html C++ Sources: http://doc.trolltech.com/qq/qq13-apis.html [3] http://www.stack.nl/~dimitri/doxygen/docblocks.html http://doc.trolltech.com/qq/qq28-qthelp.html#htmlfilesandhelpprojects -- ~ @memre <Mehmet Emre Atasever> __EOM |
