Re: [E-devel] Gitlab
On Thu, 16 Aug 2018 10:29:15 -0400 Mike Blumenkrantz said: > I am a bit curious where you think we need this much work with triaging? > > The biggest issue that we will have here is actually from our > passive-aggressive method of rejecting things we don't like. For example, > there are many, many patches that have been rejected and are idle for a > long time but not abandoned. These will not be closed using the current a lot of patches are rejected or have been asked for changes and the submitter never does it and they don't abandon. to forcibly kill it off you have to first commandeer then abandon as the new submitter. i got tired of doing that and just waited for submitters to do it. invariably many did not. this isn't passive-agreessive. it's submitters not ackowledging the patch should be abandoned. this is of course different to patches that were forgotten about. i think your characterization here is entirely wrong. > migration method. There are also unlimited tickets set to 'pending on user > input' which are dead; these also will not be closed. Most likely both of > these types of open items should just be closed during migration. probably. > On Sat, Aug 11, 2018 at 2:56 AM Jonathan Aquilina > wrote: > > > Guess then would be to migrate everything and I’ll work on triaging the > > bigs after > > > > Sent from my iPhone > > > > > On 11 Aug 2018, at 08:23, Pierre Couderc wrote: > > > > > >> On 08/11/2018 07:30 AM, jaquil...@eagleeyet.net wrote: > > >> If we are going to migrate I think we should migrate tickets slowly to > > see which ones are still valid and not pollute the new tracker with issues > > that are either moot or no longer valid. > > >> > > > Mmm, it is not logical. Migrate is a thing. Process tickets is another > > thing. Trying to do 2 independant things simulteaneoulsy? > > > > > > > > -- > > > 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 -- - Codito, ergo sum - "I code, therefore I am" -- Carsten Haitzler - ras...@rasterman.com -- 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
Re: [E-devel] EFL 1.22 Development and Features
On Mon, 13 Aug 2018 10:49:27 -0400 Mike Blumenkrantz said: > Nobody proposed it so it's not on the list. I'm slowly working on it anyway, proposals, votes or not. :) > On Mon, Aug 13, 2018 at 10:24 AM Stephen Houston > wrote: > > > I thought I had proposed this, but perhaps my mind has slipped. Where is > > theme? Because a new theme was desperately needed in the current release, > > much less the next. > > > > On Mon, Aug 13, 2018, 7:17 AM Al Poole wrote: > > > > > Hello all, > > > > > > With the 1.21 release of EFL coming to closure and its soon release, > > > now is the right time for us all to decide where to focus development > > > efforts in the EFL 1.22 release cycle. > > > > > > There will be 12 weeks of development time available for 1.22. > > > > > > There are two polls listing proposed changes in this new development > > cycle. > > > > > > You can keep track of them both here: > > > > > > https://phab.enlightenment.org/T7283 > > > > > > The two polls are at: https://phab.enlightenment.org/V36 and > > > https://phab.enlightenment.org/V37. > > > > > > Please can you spend some time looking at these proposals and express > > > your opinion on which of these proposals you oppose work being done on > > > in the EFL 1.22 development time. > > > > > > Thanks very much, > > > > > > Alastair (netstar) > > > > > > > > > > > -- > > > 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 > -- - Codito, ergo sum - "I code, therefore I am" -- Carsten Haitzler - ras...@rasterman.com -- 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
Re: [E-devel] Help with documentation
On Sat, 11 Aug 2018 12:53:41 -0700 Matthew Zamudio said: > If you want me to look over some of the HTML stuff you mentioned, I have > plenty of time to do that this weekend. our www is in: https://git.enlightenment.org/website/www-content.git/ https://git.enlightenment.org/website/www.git/ it's split. the content is the actual wiki content that the wiki will commit to using git when you edit on the wiki. we can revert bad changes easily enough then and get notifications of changes like everything else we get from code. the www core is a dokuwiki wiki engine. the css/styling is there. :) > M > > On Fri, Aug 10, 2018 at 5:30 PM, Matthew Zamudio > wrote: > > > Thank you! I will get busy on familiarizing myself with C and will install > > Enlightenment and some of the apps. In the meantime, if there is anything > > else you'd like me to get started on, please just let me know. > > > > In my book, immersion is always the best way to learn. > > > > Best, > > Matt > > > > On Thu, Aug 9, 2018 at 9:31 PM, Carsten Haitzler > > wrote: > > > >> On Thu, 9 Aug 2018 11:08:53 +0200 Xavi Artigas > >> said: > >> > >> > Hi, > >> > > >> > The API docs require both language polishing and a technical review for > >> > missing or unclear info. I generally think it is more efficient to do > >> both > >> > in one go, so I'd rather do these once you know some C at least. > >> > > >> > Putting yourself in the place of a user, installing Enlightenment and > >> some > >> > EFL apps, and then reviewing/writing their docs seems like an easy task > >> to > >> > begin with, and would give you a general overview of the project. > >> > > >> > Theming and Edje look like a nice progression from user docs to more > >> > technical stuff, although I don't know Edje yet, so I don't know how > >> hard > >> > that can be. > >> > > >> > Finally, not strictly technical writing, but I think we could use some > >> HTML > >> > expert on the website, specially with the changes *I* have in mind > >> > (separate sites for different types of users, multi-language code > >> > snippets...). > >> > >> indeed the above sounds sensible to me. > >> > >> > Xavi > >> > > >> > El jue., 9 ago. 2018 6:34 a. m., Carsten Haitzler >> > > >> > escribió: > >> > > >> > > On Wed, 8 Aug 2018 15:17:52 -0700 Matthew Zamudio < > >> > > mattzamudio...@gmail.com> > >> > > said: > >> > > > >> > > > Xavi, > >> > > > > >> > > > I will check out those resources. Thank you. > >> > > > > >> > > > As for code, I sadly can't do very much: I'm very experienced with > >> > > > HTML/CSS, and have some understanding of XML and JSON. Once I have > >> some > >> > > > defined tasks, however, I can learn what needs to be learned. I'm > >> coming > >> > > > mostly from a editorial background, but I'm ready to put in work to > >> learn > >> > > > the nuances of technical writing. > >> > > > >> > > Are you willing to learn C (our www has a primer on C too for people > >> that I > >> > > wrote assuming you know other programming langauges: > >> > > https://www.enlightenment.org/docs/c/start )? If you are then API > >> docs > >> > > could be > >> > > within reach. my take would to start making simple apps like hello > >> world > >> > > (samples already in our docs and then in our source trees etc. even > >> more). > >> > > if > >> > > you think that's not your cup of tea, or you will take a while to do > >> this > >> > > on > >> > > the side, then perhaps user documentation would be good as a start? > >> For > >> > > this > >> > > you still will need to get your hands dirty and start by downloading, > >> > > installing efl, enlightenment, terminology etc. so starting on our > >> existing > >> > > http://www.enlightenment.org is a good start. follow the docs there > >> and > >> > > ... > >> > > then contribute. if you think they are missing information, add it. > >> if you > >> > > think they should be reorganized, do that. it' is a wiki... you can > >> do it > >> > > just > >> > > by signing up. if you want to do major re-works. maybe a heads up > >> first on > >> > > the > >> > > idea here would be nice. > >> > > > >> > > this would maybe give you a soft landing and start on things. it'll be > >> > > necessary to compile and set up anyway if you want to contribute to > >> more > >> > > deeper > >> > > things and it's a good step along the way. i'm sure we have enough > >> typos > >> > > on our > >> > > pages too... > >> > > > >> > > note that phab.enlightenment.org is really about developers > >> > > sharing/communicating so it's more loose and typos etc. are less of an > >> > > issue. > >> > > .enlightenment.org is i guess the "official print" front end and > >> where > >> > > presentation is important. there is a wiki syntax sample page on > >> > > https://www.enlightenment.org/wiki/syntax ... > >> > > > >> > > maybe then get things compiled. installed etc. install some efl apps. > >> > > install > >> > > enlightenment and use it day to day. then get more curious. > >> > > > >> > >
[E-devel] Enlightenment Foundation Libraries 1.21 Release
After 12 months of development work we are proud to announce the release of version 1.21 of the Enlightenment Foundation Libraries. In these 12 months we got almost 5000 commits from 96 authors. Great job everyone! Some highlights are listed below. == Download == http://download.enlightenment.org/rel/libs/efl/efl-1.21.tar.xz 7e65be78a537aa67e447b945f01f4ecf9ddfa14d509bf6bbf53a60253ecbae4b == What's New == We only cover some highlights here. For the full list please look at the NEWS file, if you are interested in the details. As usual we have been working on fixing bugs, optimising our code for speed and memory footprint and adding new features. == Wayland, DRM and Input == The wayland protocol implementations still remains a highly active area in EFL. This cycle we have seen the addition of an EFL specific hints protocol for setting aspect on surfaces and the support of xdg-shell vfinal. Our drm2 and libinput usage gained support for setting pointer acceleration speed. == Edje == To aid the, sometimes very hard, debugging of edje files an embryo echo command was added. It is now also possible to reference images from other edje files. The biggest change however is the possibility to have edje_cc verify namespace usage during compilation . This also has been enabled in tree (with the whitelisting of some exceptions we can not change). We hope this will help to avoid these kind of problems for the future. == Evas == The Eavs subsystem added async canvas text layout functionality and improvements on font handling. A scale feature for embedded bitmap fonts and support for different H/V font DPI has been aded. Last but not least we added align=end in textblock for putting a text at the opposite side of LTR/RTL. == Elementary == A new text on patch widget was introduced this cycle together with a item pin feature in genlist. Additionally elm_entry was enhanced with a prediction hints API. == Eolian == Eolian improved its parsing in various areas. One being deferred parsing of inherits as well as better static checks of the given eo files. New API's have been added for part enumeration and to query information about objects. == Statistics == (git log --pretty=oneline v1.20.1..v1.21.0 | wc -l) Number of commits in 1.21: 4954 Number of commits in 1.20: 1665 (git shortlog -ns v1.20.1..v1.21.0 | wc -l) Number of authors in 1.21: 96 Number of authors in 1.20: 64 (git diff --stat v1.20.1..v1.21.0 | tail -1) 3217 files changed, 281935 insertions(+), 137611 deletions(-) in 1.21 1298 files changed, 69378 insertions(+), 31364 deletions(-) in 1.20 ==Building and Dependencies== If you have an existing EFL or Elementary install, you may wish to delete its header files and libraries before compiling and installing to avoid possible conflicts during compilation. Please refer to the README for a full list of dependencies, explanations on configure flags and other relevant information. Default dependencies are: * bullet * libpng * libjpeg * gstreamer (1.x, 0.10 support optional. Ensure all codecs you want are installed.) * zlib * luajit (lua 5.1 or 5.2 support optional) * libtiff * openssl * curl * dbus * libc * fontconfig * freetype2 * fribidi * libpulse * libsndfile * libx11 * libxau * libxcomposite * libxdamage * libxdmcp * libxext * libxfixes * libxinerama * libxrandr * libxrender * libxss * libxtst * libxcursor * libxp * libxi (2.2 or newer) * libgl (opengl/glx or opengl-es2/egl) * giflib * util-linux (limbount + libblkid) * systemd / libudev * poppler / poppler-cpp * libraw * libspectre * librsvg Recommended requirements (highly recommended): * harfbuzz * libwebp * libunwind (where available) Enable these with configure options: --enable-xinput22 \ --enable-systemd \ --enable-image-loader-webp \ --enable-harfbuzz \ --enable-multisense \ --enable-liblz4 On linux to get framebuffer support you may want to also do: --enable-fb --disable-tslib If you want wayland support also add: --enable-wayland \ --enable-elput \ --enable-drm At runtime if you want thumbnailing for DOC/PPT/XLS etc. files also provide: libreoffice -- 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
