Re: [E-devel] [RFC] Ticket Tagging
On Thu, 03 Dec 2015 22:29:14 + Mike Blumenkrantz said: actually i was thinking. this isn't the right way to do this. actually wishlist priority is not the right way either. this kind of screws phab's ability to drill down to actual bigs when we release. the burn rate stuff doesn't work nicely because todo and wishlist items are included in bug count. https://phab.enlightenment.org/maniphest/report/burn/ this specifically when you filter by project you get wishlist and now todo included. i dont think we want that. what i think we want is something like projectname projectname-todo projectname-wishlist where we assign the todo and wishlist bugs TO a specific project that is the project todo and wishlist "list". this should work much better imho. ... ? > In other projects that I've worked on, bug trackers sometimes tag tickets > based on various attributes. An example of this is the Servo project on > github: > > https://github.com/servo/servo/issues > > Tickets here are tagged by component, type of ticket (bug, refactoring, > enhancement, ...), and difficulty. > > We've been getting some newer developers recently, both corporate and > hobbyist, and I think some of this tagging could be useful to our > workflow--specifically tagging tickets for difficulty. > > What this would require is the creation of projects like "Trivial", "Easy", > "Hard", "Wizards Only", etc, and then adding these projects to tickets. In > this way, someone with knowledge of the related area for a ticket could > mark some tickets out which could then be handled by people with the > related level of expertise/stubbornness. > > Ideally, this would somewhat reduce work for our more senior developers by > making easier tasks more visible. It would also enable new developers to > find tickets which they could make progress with while avoiding falling > into evas_map and other bug abysses. > > If this goes well, it may be worthwhile to also start tagging/creating > tickets for "todo" items using the same methods. > -- > Go from Idea to Many App Stores Faster with Intel(R) XDK > Give your users amazing mobile app experiences with Intel(R) XDK. > Use one codebase in this all-in-one HTML5 development environment. > Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs. > http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140 > ___ > 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" -- The Rasterman (Carsten Haitzler)ras...@rasterman.com -- Go from Idea to Many App Stores Faster with Intel(R) XDK Give your users amazing mobile app experiences with Intel(R) XDK. Use one codebase in this all-in-one HTML5 development environment. Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs. http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140 ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Regarding Min/Max filter addition in Elm_Spinner
On 4 December 2015 at 23:32, SHILPA ONKAR SINGH wrote: > Hi All, > > I am working on this requirement of adding a min/max filter in elm_spinner. > so If applications have set min/max value to spinner or have added a set of > special values to spinner. > and If The values being entered in spinner are beyond the range of min/max > values those values will not even > be allowed to enter. > > Does this make sense? Can I go ahead and complete the patch? > > or a filter which restricts it self to the formats of spinner only is enough > for e.g. do not allow to enter "." if its not a floating point spinner but > will let you enter any value, only thing the value entered will be reset to > min/max value after entry looses focus. - current working Do you really need to filter the input? I think it is enough to let the user type anything and just *fix* the final value for him. -- http://indefini.org -- Go from Idea to Many App Stores Faster with Intel(R) XDK Give your users amazing mobile app experiences with Intel(R) XDK. Use one codebase in this all-in-one HTML5 development environment. Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs. http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140 ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
[E-devel] Phab update
I've recently added a new priority "TODO" for tickets and created a number of them for pending Enlightenment/Wayland work that is underway. TODO tickets should be used for the case where a developer has a todo list of things to work on and is open to collaborating with others who might be interested in helping out, or just for tracking the work in a public space. Ideally these tickets should be assigned to the related projects and the summary should include at least a vague description of how to complete the todo item. TODO tickets are not wishlist tickets. A wishlist ticket is for an idea that would be "nice to have" and can be created by anyone. A TODO ticket is for something which is definitely going to get done and should only be created by the person who is going to be doing it. Some examples of TODO tickets can be found here: https://phab.enlightenment.org/maniphest/query/CM4GUI2g3L_d/#R -- Go from Idea to Many App Stores Faster with Intel(R) XDK Give your users amazing mobile app experiences with Intel(R) XDK. Use one codebase in this all-in-one HTML5 development environment. Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs. http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140 ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] [RFC] Ticket Tagging
Hello, On 12/04/2015 12:29 AM, Mike Blumenkrantz wrote: > In other projects that I've worked on, bug trackers sometimes tag tickets > based on various attributes. An example of this is the Servo project on > github: > > https://github.com/servo/servo/issues > > Tickets here are tagged by component, type of ticket (bug, refactoring, > enhancement, ...), and difficulty. > > We've been getting some newer developers recently, both corporate and > hobbyist, and I think some of this tagging could be useful to our > workflow--specifically tagging tickets for difficulty. > > What this would require is the creation of projects like "Trivial", "Easy", > "Hard", "Wizards Only", etc, and then adding these projects to tickets. In > this way, someone with knowledge of the related area for a ticket could > mark some tickets out which could then be handled by people with the > related level of expertise/stubbornness. > > Ideally, this would somewhat reduce work for our more senior developers by > making easier tasks more visible. It would also enable new developers to > find tickets which they could make progress with while avoiding falling > into evas_map and other bug abysses. > > If this goes well, it may be worthwhile to also start tagging/creating > tickets for "todo" items using the same methods. Great idea! As I understand, "projects" in phabricator is a general mean to manage your workflow. I was checking out https://phab.enlightenment.org/project/create/ and there are actually several "types" of projects. You can see for yourself in the "Choose Icon..." button. Speaking of better workflow, I believe we can make good use of tagging to assign release goals to tasks, e.g. having "elementary-1.19" tag, and assigning tasks you intend to address for elementary v1.19. -- Danny (aka herdsman) -- Go from Idea to Many App Stores Faster with Intel(R) XDK Give your users amazing mobile app experiences with Intel(R) XDK. Use one codebase in this all-in-one HTML5 development environment. Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs. http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140 ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel