Okay, after another discussion on ml, we start with those groups:
- data types: Everything related to defined data types and the functions
therefore, (includes Eos base object)
- main loop: loop, idlers, jobs,
- rendering: engine related things
- layout: edje objects, boxes, tables, everything that positions child
objects for you.
- display system: cocoa, xserver, wayland, windows engine, drm, fb
related things
- widgets: Bugs in widgets
- system integration: dbus, files, session variables, process execution
things
- language bindings: I think this is self explaining
- networking: ecore_con and file download things
- input: input methods and everything where input can come from.
Greetings,
bu5hm4n
On 06/11/2018 02:46 PM, Mike Blumenkrantz wrote:
As said in discussion on IRC, grouping by library does nothing to reduce
the bucket size here, so this is a false premise. Grouping by overall
functional component, as proposed by Hermet, will provide better workflows,
and we can create sub-projects for these components (effectively sub
sub-projects) to further pare down the number of tickets per bucket.
On Mon, Jun 11, 2018 at 6:18 AM Marcel Hollerbach <m...@bu5hm4n.de> wrote:
Mike came up with the idea of sub projects, which sounds very good to me.
On 06/11/2018 10:17 AM, Hermet Park wrote:
Imho, base infrastructure (eo/eina/efl) / rendering (evas, ector) /
layout
(edje, eet) / core system (ecore family) / window system / widgets
(elm) /
sys-helpers (efreet, eldbus, eeze... ) is enough ...
Probably true, however, i would like to have them in even smaller
projects, so its easier to find relevant tickets for one specific
subsystem ... :) I think a project with 10 tickets is easier to maintain
and look at instead of 100 tickets ... :)
But, your proposal is not arguable neither. I agree on it.
The problem is, sometimes issues aren't independent by modules nor clear
to
list up...
That is the reason i want to use projects tags now, you can add multiple
projects (like efl-ecore efl-evas efl-elementary).
anyway, good to go!
Waiting until this evening, but i am going to prepare things ... :)
Thank for your feedback!
Greetings,
bu5hm4n
On Mon, Jun 11, 2018 at 4:26 PM, Marcel Hollerbach <m...@bu5hm4n.de>
wrote:
Okay, we need to step back with this a bit.
The problem is, workboards are quite unmanagable, and clearly not made
for
the amount of tickets we are having.
So here a new proposal:
I create the following projects:
efl-ecore (additionally: elput & ecore_*)
efl-eina (additionally: evil emile)
efl-eo
efl-eolian
efl-edje (additionally: ephysics embryo)
efl-evas (additionally ector)
efl-elementary (additionally: ethumb, emotion & elocation)
efl-eldbus
efl-eio
efl-efreet
efl-sys (additionally: eeze)
efl-eet
Each project gets automatically added efl to it. The tags can be added
to
each ticket.
Opinions?
Greetings,
bu5hm4n
On 06/11/2018 05:54 AM, Hermet Park wrote:
good to go.
On Sat, Jun 9, 2018 at 12:47 AM, Mike Blumenkrantz <
michael.blumenkra...@gmail.com> wrote:
This seems like something which would help people more easily find
issues
that they can contribute to. Perhaps a 5th workboard for something
like
'main loop' could also be added?
On Fri, Jun 8, 2018 at 11:32 AM Marcel Hollerbach <m...@bu5hm4n.de>
wrote:
Hello,
as Mike said, here my proposal for handling bugs for the upcoming
release:
i) Every bug will get a difficulty assigned either Easy, Difficult,
or
Impossible, this is to ensure that new people, and people that don't
know the subsystem or context very well can also help bugfixing.
ii) I am going to create 4 new workboards:
- primitives: Stuff that has its root problems in eina, eo, (low in
our
software stack)
- interfaces: A Bug is caused due to the movement to a different
namespace, refactoring into new classes, or changes related to new
efl_*
code / classes.
- rendering: A Bug is located in the engine code for some
protocol/platform
- widgets: Your usage of elm widgets broke somewhere between efl-1.20
and the current state.
iii) If you work on a bug, claim it for you. If a other bug sneaks in
between, or there is no time in the next week or so: Document your
findings, and remove your name from the assignee field on
phabricator,
so someone else might work on the bug.
Any objections ? For Monday I am planning to go through the
bugtracker
trying to assign difficulities, and workboards.
Greetings,
bu5hm4n
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
