Hello.

Mike requested me to let you know that he also explains things in his 
second reply (16.10.2013) which you seem to ignore.

On 10/29/2013 12:20 PM, Ulisses Furquim wrote:

[snap]

> I was trying to understand the bug being fixed and yes, it's minor and
> I can just leave it as that. However, we need to improve the way we do
> development as an open source project. It's kind of embarrassing that
> we don't have proper usage of version control, good commit messages,
> reviews, release schedule and so on. :-/

And you thing that will improve just by complaining about it? It will 
definitely not. It only improves if you actively work on changing 
things. I few examples for you what did improve over the last 1.5 years:

o Daniel and Tom migrated us over to git and helped people with using is 
as well as bringing in best practices piece by piece (developer repos 
and branches, possible merge work flows, complains about commit messages)

o Daniel and I did a lot of work to get CI up to speed and improved it 
in various ways

o I started to do coverity builds and other QA stuff to raise awareness

o During the latest dev day we discussed about release and raster 
suggested a time based schedule (just think about this. I would never 
seen that coming some time ago). I signed up for doing the first trial 
of this for the 1.9 efl release.

That are just a few things. I actually think we improved a lot over the 
last 1.5 years. Still not where I want us to be but we are making more 
progress than I hoped for.

All things only works if someone steps up and ACTIVELY does something. 
You want more review? Great! There has been a chance with the cserv2 
branch just recently but nobody really did a public review. I see you 
doing reviews on the async stuff which is good but if you want more 
people doing it you need to lead by doing so yourself even on other patches.

Don't complain about everything is shitty just because you don't like 
how this one patch was handled. Look at the whole picture and improve by 
actively helping out where help is needed. And yes, we should discuss 
this in a different thread

regards
Stefan Schmidt

------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to