Dangerous Prototypes Open Source Hardware

V4 master to-do list wiki

December 14, 2011, 11:11:21 pm

Ian;

Can you compile a master todo list on the wiki? So there is one stable spot with everything needed. Perhaps make it a spreadsheet too so the person doing that specific change can put an estimated 100% done; whos doing it; and so on... And so everyone can add to it (ahve catagorys: Important; Wanted; Glitches and so on..)

I think that would be great, and every time I finish a fix or whatever. I can send you the required files with how to import them and attach the fix number to it or whatever so you know what its for, when you commit it with a note.

I have already found a few really easy fixes but no place to really post the fix so it can be seen and commited. because all todo forums always get flooded with other convos and stuff gets lost.

I think this would really help; or perhaps add all those things to the google code page (DP's?) but I think the wiki should be simpler to keep track of...

I think the got the STK500 done (not a great implementation; I coudlnt figure out a way to take over the already compiled SPI functions; so I just put the SPI functions into the STK500.c i added... You will see; I will test it once i get home from work in about 30 minutes..)

thanks.

Re: V4 master to-do list wiki

Reply #1 – December 15, 2011, 08:43:28 am

A wiki is a good idea. I will try to make a roudup when I finish v6, but you can also keep track of your progress if you like, your forum login gets you into the wiki too. I think what we really need is a public interface to our internal project management system.

For committing small changes, you need SVN access, welcome to the team :) Please send me a google code registered email and I'll add you.

Re: V4 master to-do list wiki

Reply #2 – December 15, 2011, 04:09:09 pm

shdfh

Re: V4 master to-do list wiki

Reply #3 – December 15, 2011, 05:02:45 pm

Have you ever considered using a GPL solution like Redmine for the projects?

Re: V4 master to-do list wiki

Reply #4 – December 16, 2011, 08:49:23 am

I looked at just about every project management and issue tracker out there (that is free, and php/mysql or java) and none of them really fit our work flow. We do the same process every time, more or less, and there is also a dependency to the steps in the process that no software seemed to address. I sat down and wrote something up in a few days (after spending 5 weeks working with a coder who just 'disappeared' one day and took his code with him).

Here are the shortcomings in other management systems that are specifically addressed in our internal system (of course it will be eventually released as GPL, but right now is full of hard-coded passwords and other poor coding):
1. Dependency - don't nag me about ordering a production run if we're just starting the design. Only tell me what i can do now.
2. Process management - most systems had really crappy copy functions. We use the same process for most projects and it's a pain to setup every one individually
3. Date certainty - many PM systems force you to choose a due date to help build a gantt chart. We don't work with that much certainty
4. Too many clicks - some PM systems took 10-20 clicks per task to setup, ours has bulk actions or individual stuff
5. Hours logging - not all systems include the ability to log hours, we're trying to get an idea how much projects cost to develop

There's more too. Sjaak thinks I'm nuts for writing my own instead of adapting to a program, but 3 days coding to get exactly the usability I wanted isn't too bad :)