Vinux does use git for all of it's original content. We are currently getting burned in two areas. Rather than an outdated issues list, I am attempting to get a bug tracking system in place. However, for Vinux we need to track the progress of a bug / patch through the project, such as orca, and the distribution, such as Ubuntu. We need to track the status of when / if the bug gets resolved or a patch gets incorporated. Just this week, some patches have been incorporated into orca and Ubuntu Natty. That is one of our goals. A few others have been overlooked and need us to push them again.
The second area we have gotten burned is with Ubuntu changes wiping out speech and stability. We are considering ways to adapt our infrastructure and repositories to prevent this. Without becoming a major distribution and having all source code for every package and have an approval process for every Ubuntu package. We just do not have that amount of manpower. Tyler has been verbal against warnings on the Vinux list about applying each update, which is against Tony's recommendations because it can result in an unstable system.
Tyler, I have given you several suggestions about programming tasks you might want to consider. I even asked if you would assist in getting a bug tracking system in place. I will not be a dictator to volunteers. If you need that amount of direction, work as an entry level job at a comercial company. Tyler, I know you have a lot of programming knowledge, but I have never heard of any examples of your work other than making trouble on every list you are on. Do you actually program? Because your team skills need a lot of work!
*Don Marang *Vinux Software Development Coordinator - vinuxproject.org <http://www.vinuxproject.org/> There is just so much stuff in the world that, to me, is devoid of any real substance, value, and content that I just try to make sure that I am working on things that matter.
-- Dean Kamen On 4/8/2011 12:28 PM, DaShiell, Jude T. CIV NAVAIR 1490, 1, 26 wrote:
I mean both a piece of software and a person tasked first with a project freeze. The person would go through the to do list and find out how each item got on it and fix anything needing fixing based on current project status. Once done a far clearer and more accurate to do list becomes available. Then as many versions of project components will have to be checked to learn if versioning was done on those components consistently and where that has been done the manager can start building a repository based on consistent versioning information. That will organize all of the components and locate components with incomplete or missing versioning information. Those who wrote that stuff are going to be asked for versioning information for those components which will be edited into those components and those components will then join what's in the repository. If what I read is correct, the project now is too disorganized to use revision control software on it for now. Once organization has been established and everybody is given a commit url to the revision control system the freeze can then be lifted and development resume. However the revision control manager's responsibility from that point forward in the project is to make sure all log entries are filled out for commits in future and to be able to check out existing previous versions of software when coders make mistakes and perhaps had a computer accident of some kind and lost what they were writing. During a freeze, revision control managers report to project owners both on progress and copy project owners on inquiry messages sent to project members about project components with revision control projects. Probably just before the freeze is lifted, a thorough check of the to do list needs to be done to correct any entries based on information gained during the freeze process. Missing documentation connected to customizations made by Vinux probably will be another problem which can be written and updated during the freeze and checked in along with associated project components like programs and configuration files. -----Original Message----- From: programmingblind-bounce@xxxxxxxxxxxxx [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Homme, James Sent: Friday, April 08, 2011 11:03 To: programmingblind@xxxxxxxxxxxxx Subject: RE: Shell Programming Was RE: Searching for blind programmer to start a school for blind programmers Hi, You mean a piece of software, not a person, right? Or do you mean a person? Jim Jim Homme, Usability Services, Phone: 412-544-1810. Skype: jim.homme Highmark recipients, Read my accessibility blog. Discuss accessibility here. Accessibility Wiki: Breaking news and accessibility advice -----Original Message----- From: programmingblind-bounce@xxxxxxxxxxxxx [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of DaShiell, Jude T. CIV NAVAIR 1490, 1, 26 Sent: Friday, April 08, 2011 10:45 AM To: programmingblind@xxxxxxxxxxxxx Subject: RE: Shell Programming Was RE: Searching for blind programmer to start a school for blind programmers Ouch! Apparently the Vinux Project also needs a revision control manager too. I hope the project gets one in time to prevent the train wreck which is very probably fast approaching otherwise. -----Original Message----- From: programmingblind-bounce@xxxxxxxxxxxxx [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Littlefield, Tyler Sent: Friday, April 08, 2011 10:07 To: programmingblind@xxxxxxxxxxxxx Subject: Re: Shell Programming Was RE: Searching for blind programmer to start a school for blind programmers Vinux needs people to work with the script, but right now development is really unorganized. There is a sort of to-do list which has a lot of invalid points, and apparently a "tutorial" has to be written for people to read the scripts taht are there. I'd love to contribute to that, but it seems a bit of a pain since no one knows what actually needs to be done. On 4/8/2011 5:23 AM, Homme, James wrote: Hay Storm, I thought I read that the Blinux project needs shell programmers. Is that correct? Jim Jim Homme, Usability Services, Phone: 412-544-1810. Skype: jim.homme Highmark recipients, Read my accessibility blog<http://mysites.highmark.com/personal/lidikki/Blog/default.aspx> . Discuss accessibility here<http://collaborate.highmark.com/COP/technical/accessibility/default.aspx> . Accessibility Wiki: Breaking news and accessibility advice<http://collaborate.highmark.com/COP/technical/accessibility/Accessibility%20Wiki/Forms/AllPages.aspx> From: programmingblind-bounce@xxxxxxxxxxxxx [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Storm Dragon Sent: Thursday, April 07, 2011 3:30 PM To: programmingblind@xxxxxxxxxxxxx Subject: Re: Searching for blind programmer to start a school for blind programmers Hi, If this gets going I would like to teach. Maybe entry level shell programming (Bash). sounds like a great idea. Thanks Storm
