Voting is now ended for this proposal period.

this is a bit of a problem as you can vote only for 1 item...

You cannot. The proposal window is closed for this round of voting. 5 weeks from now there will be a second round of voting to include additional features which are proposed at that time.

How do I add items to the voting?

The difference in perspective shapes how people will respond. With this approach we are by default assuming that all proposals are good and will be accepted, and people must put work into rejecting them if they have strong feelings.

Also, maybe it's too late for asking this but, why is the polling in negative form (what features are you opposed to)?
I know very little about most of the features in the list, so I do not feel inclined to vote against somebody else's work :/

Core developers is imo anyone who is significantly active in the project, not necessarily limted to committers.

I already have this working at present in my citest branch; running make examples in the efl tree automatically updates the submodule and builds all the examples using the (provided) raw makefiles. The examples build is roughly 30x faster on my local machine now.

Note: src/bin/ethumb/* is just a example.

Who is supposed to vote? In T7169 (bullet point 2) it is said that only core developers vote. Does that mean committers , probies, or who?

Turns out the render2/region.c code is also being used by Eina_Tiler (for region_new function). Before this ticket happens, the region code will likely need to be relocated (perhaps made into Eina_Region??)

Something is wrong :-(

@kimcinoo can you help verify that that user is actually using render2? As I mentioned on D6696, I don't see how render2 can be activated except by using X11 and setting an env var.