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 ...
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... anyway, good to go! On Mon, Jun 11, 2018 at 4:26 PM, Marcel Hollerbach <[email protected]> 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 < >> [email protected]> 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 <[email protected]> >>> 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 >>>> [email protected] >>>> 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 >>> [email protected] >>> 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 > [email protected] > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- Regards, Hermet ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
