Re: [Minibits-general] CVS Usage, Skills, Etc

[d <par...@co...>]

hey minders;

first, i've posted new code and due to a minor problem with the cvs 
mailing list nobody received the notice.  fixed now but check the cvs 
change log for more details.  if you can't find it let me know and i'll 
fwd the returned notices to the minibits-general list.

i too have an icq and would rather email the number directly to you than 
post it in the list.  sorry, i'm a little paranoid when it comes to 
exposing my info for spammers, etc.  i'll send that soon.

my skills;
	VB Programming (goes way back to BASICA) -- 10yrs
	SQL (of various flavors) -- 5yrs
	Access DB development -- 7yrs
	PHP -- 2yrs
	Web Authoring/Admin -- 8yrs
	Network/System Admin -- 7yrs (pro)
	Shell Scripting/Automation (UNIX / Windows) -- 6 yrs
	Numerous envs that are now dead
	etc, etc, etc,... (don't want to go all out)

what i do for minibits;
i've worked extensively, and against my will, on m$ code standards and 
compliance.  yep, pretty familiar with the way ol' bill does things and 
i'm sure it doesn't reflect in my coding style.  i'd like to start by 
working on this area with the application.  i see software compliance as 
very important to compatibility, usability, coordinated group 
development, etc.  After that i'd like to move to the db dev side as 
that's where i've been professionally in the recent years.

now the fun stuff;  (sorry for the epic)

Command Line Arguments -- about to be committed to cvs.  right now it's 
not very proficient on detailed arguments with options but can take 
simple /ARGs.  i don't want to add detailed arguments cause i don't see 
them being used in the app.  best to think of them as simple switches, 
no options.  i.e /DEBUG:MODE=2 is not supported but /DEBUG is.  if you 
have an argument that you need called tell me the switch name and it's 
basic operating principle.  i.e. the /DEBUG option simply sets a global 
variable DEBUG_MODE to true.  i'm trying not to over complicate this.

frmMainMenu/vbp Project file -- if you have any modifications to the 
frmMain or need something set in the VB project itself, such as an 
additional form, just add the new frm and mod files to the cvs.  then 
create a new tracker item under the dev activities section, include 
details then assign it to me.  that way we're all informed when it's 
completed and operational.

ok, that's all the emailin` i can take now.  'till later,
d.




Rob Walters wrote:

> Hi all,
> A number of developments since last I emailed.
> To aid communication it would help immensely if we could use some common 
> form of instant messaging. It is sometimes very slow to get info by 
> email. I suggest ICQ. For the benefit of this, my number is 231229701.
>  
> I think we also need to develop a better ide of what each of us see 
> their role within the project as being, and also skills. This will 
> aid me to work out what skill areas we need to strengthen to allow the 
> project to grow. I'll kick this off:
> My skills:     VB programming for 4 years or so
>                    Database experience in Access
>                    Experience in Java (6 months) and C/C++ (1 yr).
>                    Business experience mainly from a Repair & Overhaul 
> point of view
>                    Experience in web authoring (3 years)
>                    Training in software engineering
>                    UML (2 yrs)
>  
> My role within the project: Primarily as a coder
>                                       Providing ideas for direction
>                                       Administration of the project
>                                       Design
>  
> Following neatly on from this, I think we need someone to take care of 
> the website and documentation side of things, to allow the coders to 
> code, so to speak. So I shall be trying to find someone over the next 
> few days.
>  
> d and I have been discussing some of the settings. Some 
> implementation-specific settings will be kept in the database, 
> workstation-specific settings will be kept in the registry.
>  
> It has been agreed that it is necessary to develop some usage methods 
> for the CVS. d will be putting together some notes, but in brief, it is 
> necessary to limit developer changes to frmMainMenu and MiniBits.vbp. 
> This is because the code is frequently changing for these forms. All 
> changes required for these forms should take place through d. I'll leave 
> it to him to notify you of how such changes should be communicated.
>  
> It is also necessary to maintain a list of versions of MiniBits. I will 
> add a file to CVS over the next few days. The revision number should be 
> incremented whenever a change is made to the source code that will 
> either remove a bug or provide an improvement. It will be within the 
> MiniBits module, named Version.txt.
>  
> Any thoughts, reply to the list.
> Rob