Ushahidi Mailing Lists

I am not sure what Max means with his phrase, but I do think we need to do a
feature freeze and work on making sure that we have core functionality
working properly, some examples are the "Import incidents" (from CSV), and
the sharing of incidents between different instances. 

Currently we have many cases when one update to the master code breaks other
stuff, ie. by uploading files that should not be uploaded (ie. config.php).
My view is that many of these things came post-Haiti (which is
understandable).

At any rate, the clean up effort does not need to prevent others from
contributing to the project, but should allow Ushahidi to have a "stable"
version. This will become more relevant as we have more projects using the
application (as in "depending"); my view is that they will be more inclined
to stability over cutting edge features.

Again, my 0,02, I know that I'm seeing this more from the implementer's
point of view rather than the developer's, that's why I am trying to find a
way that serves both.

Cheers,

Pablo

> -----Original Message-----
> From: Max Froumentin [mailto:max@...]
> Sent: Tuesday, March 16, 2010 15:55
> To: developers@...
> Subject: Re: [ushahidi developers] Clean Up Time!
> 
> On 15 March 2010 15:51, David Kobia <david@...> wrote:
> 
> > ~~~~~~~~~~~~~~~~~~
> > Cleaning up our User Interface involves the following:
> > * Making sure our HTML is XHTML Compliant
> 
> I don't think that's fixing any problem we have. I'm more than happy
> to be convinced otherwise, but in the meantime I think I'll spend time
> on cleaning up HTML and CSS, simplifying, optimising and making the
> main site as mobile-friendly as possible.
> 
> ...as opposed to the mobile site Caleb and I have been spending some
> time on, which is moving to the backburner for now. (I'm still hopeful
> for a discussion about requirements and use cases, btw)
> 
> Max.
> 
> 
> 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~
> List Archive: http://list.ushahidi.com/
> 
> Would you like to receive list mail batched in a daily digest instead?
Send a
> message to:
> developers-digest-subscribe@...
> 
> To remove your address from the list, just send a message to
> the address in the "List-Unsubscribe" header of any list
> message. If you haven't changed addresses since subscribing,
> you can also send a message to:
> developers-unsubscribe@...
> 
> For addition or removal of addresses, we'll send a confirmation
> message to that address. When you receive it, simply reply to it
> to complete the transaction.
> 
> If you need to get in touch with the human owner of this list,
> please send a message to:
> developers-owner@...